I believe when you said this was possible in SharePoint 2010, you were referring to this link:
I have got this working with SharePoint 2013 too. Here is the sample project:
I have tested this in Office365 too and it works.
There is one caveat ...
Finally, I was able to address this requirement as follows:
Create a Custom Activity which takes a SharePoint group as an input parameter and outputs a set of email addresses of people added directly in the group. At the core of the activity I used following method which gives me list of email addresses for people belonging to the group
strOutput = ...
We've found it's much easier to just add a webconfig.something.xml file to the Config folder. So for your one entry you can create an xml file with these contents:
<?xml version="1.0" encoding="utf-8" ?>
I've implemented this method in the past, so I just share my code with you:
private void AddAuthorizedType(SPWebApplication webApplication, string assembly, string namespace_)
var modification = new SPWebConfigModification();
modification.Path = "configuration/System.Workflow....
I haven't tried this method, but I think it should work. If you use the Lists web service to query for the particular item, you should be able to retrieve the workflow status column and see it's value. It should give you In Progress/Complete. In your code, you'd just need to check that status and wait/recheck in a few seconds or redirect to your page based ...
Our issue was the missing feature.xml for the PowerView feature: 14\Template\Features\PowerView\feature.xml on our WFE.
Rather than using Fiddler which didn't seem to help, we discovered the error in our ULS logs (see below).
Working on this missing feature, we then activated the feature on the Root Site collection, but this didn't solve the problem. I ...
The most common issues are:
Make sure the authorizedType entry is in your web.config (for testing you can manually add it or add it using code)
If this is a new iteration of an existing DLL, you may have to clear your cache on the machine where you are using SharePoint designer.
Make sure your .actions file is correct.
You might also want to check out ...
Ours didn't send an email to a SharePoint Group until we:
Set the "Who can view the membership of the group?" to Everyone
Give Read permissions to the group for the site
We then tested with a very simple workflow with SPD and it worked. We got some hints from here.
If your email is still not sending after that, then you may need to see:
Verify it's a ...
This may just be a work around, and not a real solution, but if you set those old workflows to fire when an item is changed, you can add a new column ('Fire Workflow' with a yes or no drop down) and then go into the datasheet view and set them all to Yes.
That should force designer to see that every entry changed. Once the workflows have completed, you can ...
You don't have the copy item in the 2013 workflow engine, indeed. This doesn't mean you can't do it in SharePoint 2013 - you just need to choose the 2010 platform, you have a dropdown when you create the workflow and the default is 2013 but you can change it.
2013 lost some actions as it's a platform that sits outside of SharePoint (WAW - Windows Azure ...
This is a bug in workflow runtime System.Workflow.Runtime.dll.
And after I installed Sharepoint 2010 Service Pack 2 the issue has been solved.
To download SP2 , you should check
Install Sharepoint Server 2010 Service Pack 2
Install Sharepoint Foundation 2010 Service Pack 2
Note :: it's heavily recommended to apply it first on your dev server.
based on what your saying sounds like the workflow time job is not kicking in the time that your waiting for hence why it would run when you restart the computer because the workflow timer service and the w3wp service have been refreshed and kicked in to action.
You can test it by doing:
net stop "Windows SharePoint Services Timer"
net start "...
The problem here was actually a custom branding solution. I was helped by Microsoft Support on this issue, and we discovered that the branding solution had been applied twice. Once as a Farm-level solution and once as a Site Collection-level solution. There must have been something wrong with the Farm solution because when we removed that one the problems ...
If you want to use Workflow Foundation 4.5 (that is used in SharePoint 2013 and SharePoint Online) you can use different approach to create custom action (but, it will work only in Sharepoint 2013, in Sharepoint Online you can use only declarative activities)
The second way, you can deploy your action in SharePoint 2013 and use 3.5 Workflows Foundation for ...
I've found an answer here - https://social.msdn.microsoft.com/Forums/vstudio/en-US/a3acdbb0-079a-4c14-97f8-72d0af64eff8/updating-sp2013-workflow-custom-activities?forum=sharepointdevelopment
So, the instruction how to update an existing workflow if it’s necessary to make changes to the workflow, but all running workflows must keep going:
The Association form is used when a user attaches (aka enables, associates) your workflow with a list/doc lib. This is the form that appears right after he choses the WF definition/name/task list/etc. when he clicks OK, if you have an Association form on your workflow, it will be displayed. Information from the first default page will be passed to the ...
You can use Multiple line of text with selected Append Changes to Existing Text. Every time you set this column it will show information about the change (modified by, modified date and value itself). Unfortunately this can be done only in a list and not in document library.
To save you from searching around, I'll elaborate on how to do logging effectively. I use this method, found under Action->Core Actions->Log to History List in Workflow Designer.
I put these logs after every branch and step, and from there I write all the relevant fields to the log using the lookups. Then you just navigate to the workflow history at
Unfortunatley you cannot debug SharePoint Designer created workflows easily (unless you actually debug the SharePoint codebase).
I suggest you add some logging features to the Workflow, examine the ULS logs, check that your workflow history is cleaned up properly etc.
(If you updated your post with the Visio diagram of your Workflow it could possibly help ...
To link back to your item, you can do something like
"<a href=\"" + li.Web.Url + "/" + li.ParentList.Forms[PAGETYPE.PAGE_DISPLAYFORM].Url +
"?ID=" + li.ID.ToString() + "\">Link to Page</a>"
Where li is the SPListItem.
You would need to look at VS Studio workflows as your option here. You are correct that the OOTB workflows are limited and won't fit your requirements. You could look at SharePoint Designer to offer a lot more actions etc. The problem here is that you won't get the State Machine workflow you are looking for. If you ha the budget the Nintex workflow product ...
I have two recommendations:
Professional Workflow in SharePoint 2010: Real World Business Workflow Solutions (Wrox Programmer to Programmer)
SharePoint 2010 Workflows in Action
You would be correct, support is blowing smoke at you. This isn't the first time I have heard people complain that Sandbox solutions that run on-premise get this exception when running on Office 365.
I have deployed and run Sandboxed workflow actions on Office 365, and they have run just fine, however that may simply be that the servers my account run on ...
I've encountered the same issue and I had the SP1 for SharePoint Designer2010 already installed.
SP D2010 Version : 14.0.6123.5001 (32-bit) with SP1
The issue :
I am using SP2010 with infopath 2010. i've designed a custom approval which contains one approval process. this workflow prompts users to fill in reviewer, CC and comments on the workflow ...
You can publish the form to a SharePoint forms library. People create a new item in the library with that form and save the item in the library. For the approval side of things, create a custom workflow in SharePoint Designer or use the out of the box three state workflow that comes with SharePoint.
Assuming you have InfoPath set up to be integrated in SharePoint (configure from Central Admin, SharePoint 2010 Enterprise is required), you can create your list first, with say a column for approval status, and then click the button on the ribbon called "Customize Form" that has an InfoPath icon. This will allow you to edit your form which submits directly ...
You can create a workflow by browser ( ex. I.e ) or by SP Designer, to send the entry , to manager by email ...
Then manager will find the url of the form and open it from email. And change the status field...
You should keep a field as status and keep the default value as submitted.
So any time a form is filled up, it's status will be submitted ...