SharePoint 2013 workflows requires site level contribute access or higher

I have a SP 2013 workflow on a list that resides on the root of the site collection. All users have
contribute rights to this list, to the
Workflow Tasks list, and to the Tasks list. But all general users have only READ level access to the site.
If users go to the list, click on any item and either try to initiate a workflow or check status of a workflow (by clicking "..." and choose workflows or check item checkbox and choose workflows from ribbon), they get an error of "This site
has not been shared with you" as it tried to bring the user to http://<root site collection>/_layouts/15/workflow.aspx
I have tried this with a custom workflow, an out of the box workflow and the result is the same every time. However by granting any user CONTRIBUTE level access to the site resolves the issue immediately. I have also gone back and tried this
on a SP 2010 VM and this was not an issue then. You could do the same thing in 2010 with only read level access to the site.
So is this a limitation now with 2013 or a bug??? Surely, the system can't expect that a user needs contribute level access to the entire site just to initiate a workflow of one list.
Please advise.
*This READ level access is very important because the root site is extremely publishing heavy and needs to be controlled and maintained by only a select group of users - not everyone that needs access to the workflow.

I went into the masterpage gallery library and added the users to the read permission level. They are still having the same issue.
Thanks,
Jesse
Jesse A. Brandenburg

Similar Messages

Sharepoint 2013 Workflow not available on Site created from Sharepoint 2013 Foundation Solution Template

If I create a template on SharePoint 2013 Foundation, then create a site on SharePoint Enterprise (or Office/365) fully configured to support SharePoint 2013 workflows. When I access the site through SharePoint Designer 2013, and attempt to create a workflow
SharePoint 2013 Workflows are not available -- you get message that SharePoint 2013 Workflow platform is not available because it is not configured on the server. This appears to be a bug in SharePoint Designer as the 2013 Workflows are available on the team
site on the same site collection. There is no reason that a site created from a SharePoint 2013 foundation template should have this restriction.   To make matters worse if you then save that site as a template on the SharePoint 2013 Enterprise (or
Office/365) system and create a new site from the that template you get the same issue.
Anyone know a workaround/fix to this issue.   Have imported the template into Visual Studio but I can not find any way in Visual Studio to enable SharePoint 2013 workflows.   A solution that involves Visual Studio import would work fine
for me.
Earllibby

Apparently you did not read my question very carefully.   The workflow manager is configured properly on this server and for the basic Team site in this site collection the full SharePoint 2013 workflows are available in SharePoint Designer 2013.
BUT they are not available on another site in the SAME SITE COLLECTION that was created from a solution template that was created on a SharePoint Foundation server.
Earllibby

Custom SharePoint 2013 workflow activities in site template throw error on site creation

Hi all,
I have created a number of custom activities for SharePoint 2013 Workflows and I am using them on an Office 365 environment. The custom activities are packaged as a sandbox solution and deployed on my Office 365 site. Everything works as expected.
I have now created a site with all the functionality I need, including some Site and List workflows - all of them containing my custom activities. I saved the site as a template - including content - and the process was completed successfully.
My problem is that when I try to create a site based on that template, I get the following error:
Microsoft.Workflow.Client.ActivityNotFoundException: The activity named 'WorkflowXaml_66b9230b_823e_4783_82b8_daf481237847' from scope '/spo/d42a4487-9465-4347-9f2c-a2718e92fc02/74d0f9e7-fb35-493d-86fb-ab7aa27da7e0/c2e1bf45-cf67-4e13-9755-421cf92395f8'
was not found. HTTP headers received from the server - ActivityId: 0997496a-5a15-4b83-82eb-727881eefa67. NodeId: . Scope: . Client ActivityId : c82f6e9c-9f8f-808b-7679-f2c0f92a339d. ---> System.Net.WebException: The remote server returned an error
After a number of trials and errors, I am certain that this relates to my custom activities. i have already tested all of the following scenarios:
Delete the workflow with the custom actions: Site is created successfully.
Create a new workflow with no custom actions and save the site as a template:
Site is created successfully.
Save the site template including a workflow with my custom activities, but not including content:
Site is created successfully, but my workflow is not there.
Create a new custom workflow activities sandbox with one custom activity that just writes something to the history list - just to make sure that this is not related to any specific solution. Save the site as a template:
Site creation throws the same error.
Packaged my workflow (with my custom activities) as a wsp from SharePoint Designer and deployed it as a custom solution. Activated the feature in the target site. The workflow gets created and executing finally. Saved the site as template: Site
creation throws the same error.
Same as above, but without activating the feature in the target site: Site created successfully, workflow works fine after I activate the feature in the new site.
My custom activities feature is always enabled in the site I save as template - in all of the above scenarios.
I have tested all of the above scenarios both on SharePoint 2013 on-premise and Office 365. There is
a forum post regarding some inconsistencies in the wsp file, but unfortunately this is not my case. Am I doing something wrong? Are custom 2013 workflow activities not supported in site templates - which would not actually make any sense, as it would "break"
the fundamental concept of re-usability.
Any ideas/feedback/guidance?
Thanx in advance

Hi,
I am facing the same issue. Kindly help me out if any of them have solved similar issue.
Your help would be appreciated.
manikantan

SharePoint 2013 Workflow (SPD 2013) fails for Active Directory Group members

Hi
I have a SharePoint 2013 site called "Team Meetings". There are a number of lists and an InfoPath form library.
The site's SharePoint Group "Team Meeting Members" has two Active Directory groups (All Club Managers and All Club Police) as members. Those two AD groups contain all the people that I want to have access to the library and list, except for
a few additional folk who I have made individual members.
My PROBLEM:
I have created a SharePoint 2013 Workflow using SPD 2013 associated with the Form Library. Workflow is set to start on new or modified item. The first action is to write to history list, then determine the status (Submitted or Pending) of
the form and go to different Stages depending on that status.
The workflow works perfectly for any user who has been added directly to the SharePoint group (Team Meetings Members) BUT FAILS at the very first action for anyone who is a member of one of the AD groups. I know the Workflow is fine because I've tested it
with numerous people who are direct members of the SharePoint Group, but whenever a person who is a member of the AD group tries it the Workflow just fails.
Here's a print of the info from the Workflow Status page (I don't have access to server logs):
RequestorId: 4494760f-92ff-2e8c-90d2-cc7df0e6baa4. Details: System.ApplicationException: HTTP 401 {"Transfer-Encoding":["chunked"],"X-SharePointHealthScore":["0"],"SPRequestGuid":["4494760f-92ff-2e8c-90d2-cc7df0e6baa4"],"request-id":["4494760f-92ff-2e8c-90d2-cc7df0e6baa4"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"MicrosoftSharePointTeamServices":["15.0.0.4420"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1;
RequireReadOnly"],"Cache-Control":["max-age=0, private"],"Date":["Mon, 10 Mar 2014 01:31:42 GMT"],"Server":["Microsoft-IIS\/8.0"],"WWW-Authenticate":["NTLM"],"X-AspNet-Version":["4.0.30319"],"X-Powered-By":["ASP.NET"]}
The HTTP response content could not be read. 'Error while copying content to a stream.'. at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance
instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor
Members of the SharePoint Group "Team Meetings Members" have Contribute Access to both the form library and another list that the workflow writes to as well as the Workflow History list (which in SP 2013 uses the credentials of the
user who started the workflow, unlike 2010 which used System Account).
All members of the Team Meetings Members group, whether they are individual members or part of one of the AD groups, have no problems opening and saving forms etc. It's just the Workflow that doesn't like them...
I am stumped. I've spent many hours searching for a reason for this. There are about 200 people in the two AD groups so I really don't want to have to add them all individually - especially when these groups are managed in AD for a whole bunch of other reasons
and using the AD groups means I'll basically never have to worry about modifying the SharePoint access permissions.
Does anyone have any ideas why this is happening and what I can try to fix it?
Mark

Hi Lars,
I'm afraid not so far but we are trying a few things today so I will post back with results.
First thing we are doing is making the AD Group universal because one of our (external provider) gurus remembers seeing something about that. He also sent me a link to a post where they were talking about earlier
versions but having similar issues and their solution was to make sure the app pool account has sufficient permissions in AD::
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/27a547da-5cc0-49d7-8056-6eb40b4c3242/failed-to-start-workflow-access-is-denied-exception-from-hresult-0x80070005-eaccessdenied
This part of that thread looks interesting but we haven't checked it yet as were trying the universal setting first:
"If the users participating in the workflows have been added to the SharePoint site via Active Directory groups, SharePoint has to update the user’s security token periodically by connecting to
the domain controller. By default, the token times out every 24 hours. But if the application pool account did not have the right permissions on the domain controller to update the user’s token, user will keep getting the access denied error. The error was
intermittent because when the user browsed to any page other than the workflow form, the token was getting updated successfully.
You can try to fix it through granting the application pool account the appropriate permission by adding the account to the group “Windows Authorization Access Group” in Active Directory."
I'll update when we try these ideas. If you have any luck please do the same.
Mark
(sorry about formatting - using my phone....)
Mark

SharePoint 2013 Workflow Permission

We are running into a problem with SharePoint 2013 and workflows.
We have the following site collection setup:
Site Collection
    Subsite A
    Subsite B
The following are the permissions:
[Site Collection] Owners
[Site Collection] Members
[Site Collection] Vistors
The members of these SharePoint groups are Active Directory security groups. If we put these AD groups into the SharePoint group we get the following error when trying to run a workflow:
RequestorId:
171a693d-7b50-a70a-0000-000000000000. Details: RequestorId: 171a693d-7b50-a70a-0000-000000000000.
Details: An unhandled exception occurred during the execution of the workflow
instance. Exception details: System.ApplicationException: HTTP 401
{"error":{"code":"-2147024891, System.UnauthorizedAccessException","message":{"lang":"en-US","value":"Access
denied. You do not have permission to perform this action or access this
resource."}}}
{"Transfer-Encoding":["chunked"],"X-SharePointHealthScore":["0"],"SPRequestGuid":["171a693d-7b50-a70a-ba75-67ea8bc83fb4"],"request-id":["171a693d-7b50-a70a-ba75-67ea8bc83fb4"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"MicrosoftSharePointTeamServices":["15.0.0.4481"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1;
RequireReadOnly"],"Cache-Control":["max-age=0,
private"],"Date":["Tue, 16 Jul 2013 15:28:13
GMT"],"Server":["Microsoft-IIS\/8.0"],"WWW-Authenticate":["NTLM"],"X-AspNet-Version":["4.0.30319"],"X-Powered-By":["ASP.NET"]}
at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext
context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance
instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at
System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor
executor, BookmarkManager bookmarkManager, Location resultLocation
Obviously, this is a permissions issue. I am able to resolve the issue by adding individuals to the SharePoint group 1 by 1, however, I don't want to do this. Can anyone explain why this is acting the way it is?

Hi,
I am also running into this issue and am stuck in solving it.
I have a list workflow that runs on item change event, checks if a certain value is true and then should create a new list item in a list on a different site.
Site structure is the same as Hhancocks:
Site Collection
   Subsite A => workflow
   Subsite B => list where new item should be created
With the same HTTP REST call I can create a new item on any list of Subsite A, but as soon as I try to create the item on a list in Subsite B, I get the response Code "Unautherized" and the response:
{"error":{"code":"-2147024891, System.UnauthorizedAccessException","message":{"lang":"en-US","value":"Access denied. You do not have permission to perform this action or access this
resource."}}}
I found the following blogs on the internet, none of which solved my issue:
http://www.sharepointviking.com/system-unauthorizedaccessexception-when-running-sharepoint-2013-workflows/
http://www.sharepointmaestra.com/Blog/Post/1/Workflow-2013-Not-Starting-on-Incoming-Email
According to this thread:
http://community.office365.com/en-us/forums/148/p/178921/527970.aspx the REST calls don't work in SharePoint online which would explain the behaviour in one of our environments, but the error also occurs for our on prem environment. The user triggering
the workflow has full control on both subsites.
Any hints would be really appreciated.

SharePoint 2013 workflow for page publishing

Hi Folks,
I need to implement a page publishing workflow.I am going in brief to explain scenario.
When a page is getting created by a user from a specific group it needed to be approved by four different group of people in a sequential approach.
After getting approval from all group only last user group member should be authorized to publish the page.
There could be a scenario where once page is created it will require to be directly published without any approval
Kindly suggest me which approach i should follow ?
Either of SharePoint designer workflow or Visual Studio Workflow ?
Appreciate if can provide some tutorial kind link or suggestion.
Keshav Roy

There's not really too many examples out there to share for SharePoint 2013 workflows. Personally I believe SharePoint Designer workflow is an quick and easy of developing workflows but it has limitations - like it's tightly integrated with the SharePoint
site/list. However if you have an existing Visual Studio project then I don't see any reason to use SharePoint Designer (SPD) workflow. Visual Studio workflow is more like developer tools and you can do more with VS than SPD. So if you have developer
skills (or someone in your team), have already a VS project and need more customisation (as per your requirements, you have complex one), I would prefer to go for Visual Studio workflow.
Thanks,
Sohel Rana
http://ranaictiu-technicalblog.blogspot.com

SharePoint 2013 Workflow Lookup Column Error

When I try to use the value from a lookup column (e.g. display the selected value in the body of a email) in a SharePoint 2013 workflow I receive the following error. It works fine if I use the SharePoint 2010 workflow platform, but I always receive a error
with 2013.
First Error:
Retrying last request. Next attempt scheduled in less than one minute. Details of last request: HTTP NotFound to http://portal.test.com/sites/Test/_vti_bin/client.svc/web/lists/getbyid(guid'00000000-0000-0000-0000-000000000000')/Items(10)?%24select=ID%2CLookupId%2CLookup%2FTitle&%24expand=Lookup
Correlation Id: 3fb1bac9-f4b6-bbf1-a664-b3748668ea3c Instance Id: e7b4064d-029d-4a8b-9a75-7939f10e8817
<script type="text/javascript">// <![CDATA[ var errorMessage = "Something went wrong. To try again, reload the page and then resume
the workflow."; var dlg = null; function RetryWorkflow4(instanceName) { showDialog(); var ctx = SP.ClientContext.get_current(); var wfManager = SP.WorkflowServices.WorkflowServicesManager.newObject(ctx, ctx.get_web()); var instanceService = wfManager.getWorkflowInstanceService();
var instance = instanceService.getInstance(instanceName); instanceService.resumeWorkflow(instance); ctx.executeQueryAsync( function(sender, args) { closeDialog(); theForm.submit(); }, function (sender, args) { closeDialog(); alert(errorMessage); } ); } //
]]> </script>
Error from SharePoint Logs:
Microsoft.SharePoint.SPException: List does not exist. The page you selected contains a list that does not exist.
It may have been deleted by another user. ---> System.Runtime.InteropServices.COMException: List does not exist.
The page you selected contains a list that does not exist.
It may have been deleted by another user.     at Microsoft.SharePoint.Library.SPRequestInternalClass.GetListsWithCallback(String bstrUrl, Guid foreignWebId, String bstrListInternalName, Int32 dwBaseType, Int32 dwBaseTypeAlt,
Int32 dwServerTemplate, UInt32 dwGetListFlags, UInt32 dwListFilterFlags, Boolean bPrefetchMetaData, Boolean bSecurityTrimmed, Boolean bGetSecurityData, Boolean bPrefetchRelatedFields, ISP2DSafeArrayWriter p2DWriter, Int32& plRecycleBinCount)
    at Microsoft.SharePoint.Library.SPRequest.GetListsWithCallback(String bstrUrl, Guid foreignWebId, String bstrListInternalName, Int32 dwBaseType, Int32 dwBaseTypeAlt, Int32 dwServerTemplate, UInt32 dwGetListFlags, UInt32
dwListFilterFlags, Boolean bPrefetchMetaData, Boolean bSecurityTrimmed, Boolean bGetSecurityData, Boolean bPrefetchRelatedFields, ISP2DSafeArrayWriter p2DWriter, Int32& plRecycleBinCount)
--- End of inner exception stack trace ---
at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
at Microsoft.SharePoint.Library.SPRequest.GetListsWithCallback(String bstrUrl, Guid foreignWebId, String bstrListInternalName, Int32 dwBaseType, Int32 dwBaseTypeAlt, Int32 dwServerTemplate, UInt32 dwGetListFlags, UInt32 dwListFilterFlags, Boolean bPrefetchMetaData,
Boolean bSecurityTrimmed, Boolean bGetSecurityData, Boolean bPrefetchRelatedFields, ISP2DSafeArrayWriter p2DWriter, Int32& plRecycleBinCount)
at Microsoft.SharePoint.SPListCollection.EnsureListsData(Guid webId, String strListName)
at Microsoft.SharePoint.SPListCollection.ItemByInternalName(String strInternalName, Boolean bThrowException)
at Microsoft.SharePoint.SPListCollection.GetListById(Guid uniqueID, Boolean bThrowException)
at Microsoft.SharePoint.SPListCollection.get_Item(Guid uniqueID)
at Microsoft.SharePoint.SPListCollection.GetList(Guid uniqueId, Boolean fetchMetadata)
at Microsoft.SharePoint.SPListCollection.GetById(Guid uniqueId)
at Microsoft.SharePoint.ServerStub.SPListCollectionServerStub.InvokeMethod(Object target, String methodName, ClientValueCollection xmlargs, ProxyContext proxyContext, Boolean& isVoid)
at Microsoft.SharePoint.Client.ServerStub.InvokeMethodWithMonitoredScope(Object target, String methodName, ClientValueCollection args, ProxyContext proxyContext, Boolean& isVoid)
at Microsoft.SharePoint.Client.Rest.RestRequestProcessor.InvokeMethod(Boolean mainRequestPath, Object value, ServerStub serverProxy, EdmParserNode node, Boolean resourceEndpoint, MethodInformation methodInfo, Boolean isExtensionMethod, Boolean isIndexerMethod)
at Microsoft.SharePoint.Client.Rest.RestRequestProcessor.GetObjectFromPathMember(Boolean mainRequestPath, String path, Object value, EdmParserNode node, Boolean resourceEndpoint, MethodInformation& methodInfo)
at Microsoft.SharePoint.Client.Rest.RestRequestProcessor.GetObjectFromPath(Boolean mainRequestPath, String path, String pathForErrorMessage)
at Microsoft.SharePoint.Client.Rest.RestRequestProcessor.Process()
at Microsoft.SharePoint.Client.Rest.RestRequestProcessor.ProcessRequest()

Hi
XantosX5 ,
Thank you for your posting!
According to your description, I try to reproduce your scenario in my SharePoint Server 2013 environment.
I create a lookup column in a list and create a workflow 2013 for the list. In the workflow, I add Send an email action. Then I display the lookup column in the body of the email as the below figure:
When I start the workflow, it works fine.
Have you installed
the workflow manager 1.0 cumulative update 1 ? It can be the point. If not, please install it.
Thank you for your understanding and support.
Best Regards,
Eric
Eric Tao
TechNet Community Support

Sharepoint 2010 Workflow successful: Sharepoint 2013 Workflow UNsuccessful:

Observation 1
1. I created 2 workflows that write "completed" to the workflow history
a. 1 workflow uses sp2010 workflow manager
b. 1 workflow uses sp2013 workflow manager
2. sp2010 workflow works fine; it will start either manually or automatically (when a new item is created ) without issue; "completed' is written to the log as expected. Good.
3. sp2013 does not start automatically (when a new item is created ); when trying to start manually I get error message "Something went wrong. To try again, reload the page and then start the workflow." Which I do, but still fails.
Bad.
4.On Workflows.aspx I can see the links to start the 2 workflows manually.
a. When I hover over the sp2010 workflow link I can see something that look like this:
http://playground/sites/falcontt/_layouts/15/IniWrkflIP.aspx?List={ae95de8e-508b-4aa6-b4b6-490288e35e9f}&ID=53&ItemGuid={697E4218-D889-4FB8-A27B-D188F5D93250}&TemplateID={199c3d86-89a8-4286-b285-37e2d2067b52}&Source=http%3A%2F%2Fplayground%2Fsites%2Ffalcontt%2FLists%2FTrouble%2520Tickets%2Fall%2520requests%2Easpx
b. But when I hover over the sp2013 workflow link I can see something that look like this:
javascript:StartWorkflow4('949cb889-9b46-4959-9673-842e60cc5a42', '53', '{697E4218-D889-4FB8-A27B-D188F5D93250}')
Should this link also look similar to the sp2010 workflow link? If so, do you have any idea why it is different?
Observation 2
In Sharepoint Designer 2013, when I goto Navigation -> Workflows and click on the 2010 workflow, I see a file listed under "Forms" that looks like this "sp2010 test workflow.xsn". By the way the name of the workflow happens
to be "sp2010 test workflow".
But when I goto Navigation -> Workflows and click on the 2013 workflow, I see a NO file listed under "Forms". Should I see "sp2013 test workflow.xsn" listed there? If yes, can you think of why it is not listed there?
I saved the workflow debug logs from Event Viewer but won't share that info here unless necessary, to avoid making things look more complicated than they have to be.
Thanks for any comments suggestions, tips, questions, anything, etc.
Thanks and have a great weekend.
George

Hi George,
First of all, I'd like to clarify that workflow manager is dedicated for SharePoint 2013 workflow platform. SharePoint 2010 workflow is integrated in SharePoint server, while 2013 workflow is based on a new platform named workflow manager server.
In SharePoint 2013 designer, 2010 workflow has forms while 2013 workflow doesn't have forms.
For this issue, I suspect there is something incorrect with workflow manager. From the error message "Something went wrong. To try again, reload the page and then start the workflow", please flush the DNS cache via executing
IPCONFIG /FLUSHDNS, and restart workflow manager related services such as below, then recreate 2013 workflow to test the issue:
Service Bus Gateway
Service Bus Message Broker
http://blog.houratious.com/2014/05/sharepoint-2013-workflow-something-went.html
Regards,
Rebecca Tu
TechNet Community Support

Sharepoint 2013 workflows and Due date

hi, i'm a sharepoint designer 2010 user, and i recently migrate to sharepoint 2013 (and use sharepoint designer 2013).
I understood it was impossible to migrate sharepoint 2010 workflow to sharepoint 2013 workflows ! But it was possible to call 2010 workflow from 2013 worikflow.
However, i thought i could reproduce workflow under SPD 2013. I recently discover that was not as possible as it seems
for example, it was possible to escalate a task after due date, under SP2010 workflow. I try to reproduce it under sharepoint 20103 workflow, but it seems not to be possible any more (i read this article >>
link <<!
Does any sharepoint's expert can confirm it to me !?
Mon blog : http://spinfopath2010.blogspot.fr/ Sharepoint online 2010 Sharepoint Designer 2010 - InfoPath 2010 - newbie level !

Also please note that you can combine both workflow engines together! It means you can create 2013 workflow using the new model and if you face any action which is no longer available (and you cannot find any other way, e.g. impersonation step) -
you are able to just easily invoke 2010 workflow with its set of actions.
To do so, please read following article, which also describes why some features are no longer available and how to implement these deprecated activities in 2013 environment:
http://msdn.microsoft.com/en-us/library/jj728659.aspx
Hi martin,
Yes, i know i can call a 2010 worklfow from a 2013 one, but it seems to me "tricky", and not a very good practice. Because, these workflows can be either deprecated or abandonned.
I prefered to use a "full" 20130 workflow instead of mixing it with an older version
Anyway, if there is no other way, i'll do it
Mon blog : http://spinfopath2010.blogspot.fr/ Sharepoint online 2010 Sharepoint Designer 2010 - InfoPath 2010 - newbie level !

Any way i can create and manage SharePoint 2013 workflows in browser.

Guys,
is there any way i can created and manager sharepoint 2013 workflows in browser like Nintex lets you do. This will eliminate the need for sharepoint designer.
thanks
MM

No. SharePoint's work flows are created from SharePoint Designer or Visual Studio. Third party solutions like Nintex have other approaches.
Mike Smith TechTrainingNotes.blogspot.com
Books:
SharePoint 2007 2010 Customization for the Site Owner,
SharePoint 2010 Security for the Site Owner

SharePoint 2013 workflow deployment doens't update workflow definition

In Visual Studio 2013, we can develop SharePoint 2013 workflow and deploy directly in SharePoint. However, once a workflow is deployed and later modified and redeployed, the modified workflow definition doesn't take effects. Even if you retract the solution
and redeploy, the associated workflow with the sharepoint solution doesn't get updated in the SharePoint. Retracting the SharePoint solution then restarting the development server and finally redeploying will reset the workflow definition.

try this link:
https://connect.microsoft.com/VisualStudio/feedback/details/779905/sharepoint-2013-workflow-deployment-doenst-update-workflow-definition
http://www.sharepointeurope.com/blog/2011/8/30/5-easy-ways-to-turn-sharepoint-workflow-solution-into-a-failure-by-pawe%C5%82-wr%C3%B3bel-datapolis
http://ranaictiu-technicalblog.blogspot.in/2013/02/sharepoint-2013-workflow-manager.html
according to links workflow is cached in site so delete it from designer also.

SharePoint 2013 Workflows

Hi there
I seem to be having trouble running any workflows using the 2013 engine in SharePoint Designer. The 2010 workflows work fine, however I cannot seem to get the 2013 ones to even start. Looking at the list/library settings, I can see the workflow has been
added but for whatever reason it doesn't seem to start.
I cannot even go back into a list item to view the workflow either...
Where to I even begin to try to unravel this mystery? HELP!! :-)
Many thanks in advance.

SharePoint 2013 Workflow engine has undergone a drastic change. Before you begin developing workflows in SharePoint 2013 you must ensure you
have taken care of the pre-requisites.
Ensure you have gone through each points in this article in configuring your Workflow Manager 2013:
https://technet.microsoft.com/en-us/library/jj658588.aspx
Before you start installing/developing SharePoint Workflows in 2013 you should to know few important points:
Never use ‘System Account’ to develop/run workflow, the workflow will fail to run.
You should not use ‘System Account’ to test the workflow.
You need to make sure User Profile Service (UPS) is running and the user who is running workflow has a profile created in UPS. Workflow Manager use UPS under
the hood.
Make sure App Management Service is created and running. You don’t need to configure SharePoint 2013 App settings in the server, just creating App Management
service (with proxy) will do.
Make sure the hidden feature WorkflowServiceStore is enabled.
Enable-SPFeature -Identity WorkflowServiceStore –Url $yourUrl
Note: To register Workflow Server with SharePoint, a SharePoint site collection URL is provided. Apparently it seems, each and every site collection need to be registered
with workflow server. But it’s not, registering a single SharePoint site collection, will enable workflow manager for all SharePoint web applications/site collections.
Now you can check from above listed points, which points resolves your issue.
More detailed troubleshooting steps on SP workflows 2013:
http://blogs.msdn.com/b/vincent_runge/archive/2014/01/07/troubleshooting-actions-for-sharepoint-2013-workflows.aspx
Please remember to click 'Mark as Answer'
if the reply answers your query or 'Upvote' if it helps you.

SharePoint 2013 Workflow for MDS 2012 - Sample Code

Hi All, I want to integrate MDS 2012 with SharePoint 2013 workflow. I have read the whitepaper on this integration but I am looking for code samples on SharePoint 2013 workflow which can be used for this as I am not much into SharePoint development. If
not the source code, any good blog links to achieve this integration?
Thanks, Ashish Singh

If you want to avoid the SharePoint development, then use a custom IWorkflowTypeExtender and interact with SharePoint using the Lists OData service. That way your code runs on the MDS server, and you don't have to deploy custom code to SharePoint.
You would simply add an item to an existing or purpose-built SharePoint list, and that could kick off a standard list workflow (which can be built without custom code).
Otherwise you need to create a custom SharePoint Site Workflow in Visual Studio, and deploy it to SharePoint (yuck). Per:
http://msdn.microsoft.com/en-us/library/ee231573.aspx
David
David http://blogs.msdn.com/b/dbrowne/

Sharepoint 2013 Workflow InitForm.aspx Visual Studio 2013

Hi,
I have a small problem. In my initform.aspx for my SP 2013 workflow I have a people editor element so that users can select multiple users (reviewers). I successfully used jquery to get the login-names. I want to use these names for a composite task in my
workflow, and the task want a collection<string> in the AssignedTo-box. How do i store these logins in a collection<string> object? What datatype do I use for my workflow argument to store these logins from the javascript(wfParams) in my InitForm.aspx?
//Regards Kjell

Hi,
To develop SharePoint 2013 workflows using Visual Studio 2012, it requires to set up a workflow development environment first.
It is recommended to look through the two documentations from MSDN about
Prepare to set up and configure a SharePoint workflow development environment
before starting the workflow development:
http://msdn.microsoft.com/en-us/library/office/dn413607.aspx
http://msdn.microsoft.com/en-us/library/office/jj163917.aspx
Best regards
Patrick Liang
TechNet Community Support

Can SharePoint Apps and SharePoint 2013 workflow run on the same servers?

As the SharePoint 2013 workflow manager can run on non-sharePoint servers. Can I also use those server to host SharePoint apps in the Provider host model?
Or should I keep them separate?
This is a medium size deployment, 2 WFEs, 2 Apps, 1 Clustered DB. I would be adding 2 additional servers for hosting workflow manager, and SharePoint apps.
One other option I can think of would be to host the Workflow manager on the SharePoint Apps servers. And then host the SharePoint Apps on the 2 separate servers.
Any guidance or gatchas would be great the hear about.
Thanks!
Joshua Fuente

Yes, you should be able to run SharePoint Provider hosted apps using the Workflow Server as the provider. There is nothing in workflow manager that prevents running web sites on the same server.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

SharePoint 2013 workflows requires site level contribute access or higher

Similar Messages

Maybe you are looking for