none
Workflow Manager 1.0-SharePoint 2013

    Question

  • Hi

       I need to know,

               1. Under What scenarios Workflow Manager 1.0 is used?

               2. What are the Pros & Cons in Workflow Manager 1.0

               3. How it will be used in SharePoint Server 2013?

               4. Can custom code to be implemented using Workflow Manager 1.0?

               5. Using this, will it be possible to bind the entire  workflow to a single list or entire workflow to be bind to multiple lists?

               6. What are the limitations using Workflow Manager 1.0 with SharePoint 2013?

    Regards

    Siva

         

      


    • Edited by Siva_SREC Friday, August 02, 2013 10:57 AM
    Friday, August 02, 2013 10:48 AM

Answers

    1. Workflow Manager is required if you want to do 2013 workflows in SharePoint 2013.  2010 style workflows are still supported but offer no new functionality.
    2. The major advantage is that workflow manager can be implemented on separate server(s) so it is much more scale-able than legacy 2010 workflows.  This means it doesn't run under  the OWS timer service which makes it scale-able but also limits some of the actions that it can do.  (For example it can't change item level permissions)
    3. It is the primary workflow engine for SharePoint 2013 moving forward.
    4. One of the advantages that Workflow Manager has over traditional 2010 workflows is that it can call XML web services or 2010 workflows.  You can't do custom code directly in Workflow Manager, but can call a custom XML web service or 2010 workflow with custom code in it.
    5. Not sure I understand this question.  Are you asking whether reusable workflows are supported?  Or are you referring to the inherent list item focus for workflows?  Workflow manager is still focused on a particular item.  To process a whole list would be a site workflow.  
    6. As mentioned, because it runs out of process there are some actions that are not included in 2013 workflows that were in 2010 workflows.  But there are also new actions that weren't in 2010 workflows.  Its a trade-off.

    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.

    Friday, August 02, 2013 11:49 AM
  • There's nothing special about it in 2013.  You create one using SPD the same way you do in 2010.  A site workflow is just a workflow that runs in the context of a site rather than the context of a document or list item.  Since it runs on a particular site it has access to all the lists and libraries in a site and to all the items in those lists or libraries.

    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.

    Friday, August 02, 2013 3:03 PM

All replies

    1. Workflow Manager is required if you want to do 2013 workflows in SharePoint 2013.  2010 style workflows are still supported but offer no new functionality.
    2. The major advantage is that workflow manager can be implemented on separate server(s) so it is much more scale-able than legacy 2010 workflows.  This means it doesn't run under  the OWS timer service which makes it scale-able but also limits some of the actions that it can do.  (For example it can't change item level permissions)
    3. It is the primary workflow engine for SharePoint 2013 moving forward.
    4. One of the advantages that Workflow Manager has over traditional 2010 workflows is that it can call XML web services or 2010 workflows.  You can't do custom code directly in Workflow Manager, but can call a custom XML web service or 2010 workflow with custom code in it.
    5. Not sure I understand this question.  Are you asking whether reusable workflows are supported?  Or are you referring to the inherent list item focus for workflows?  Workflow manager is still focused on a particular item.  To process a whole list would be a site workflow.  
    6. As mentioned, because it runs out of process there are some actions that are not included in 2013 workflows that were in 2010 workflows.  But there are also new actions that weren't in 2010 workflows.  Its a trade-off.

    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.

    Friday, August 02, 2013 11:49 AM
  • Hi Paul

      Thanks  for the reply.

       It would be helpful, if you give the detailed explanation of site workflow in workflow manager with SharePoint server 2013.

    Regards,

    Siva

    Friday, August 02, 2013 12:49 PM
  • There's nothing special about it in 2013.  You create one using SPD the same way you do in 2010.  A site workflow is just a workflow that runs in the context of a site rather than the context of a document or list item.  Since it runs on a particular site it has access to all the lists and libraries in a site and to all the items in those lists or libraries.

    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.

    Friday, August 02, 2013 3:03 PM
  • Can u give the detailed list of pros and cons for Workflow manager 1.0 ?

    Regards,

    Siva

    Tuesday, August 13, 2013 9:16 AM
  • There is no specific list of pros and cons available.  Basically it comes down to the following points.

    1. SharePoint 2010 workflows are only available for legacy support and should be considered deprecated.  Workflow Manager 1.0 is the direction moving forward and may be the only supported workflow system in future versions.
    2. Workflow manager runs workflow "Out of Band" where 2010 workflows are run "In Process" under the OWS timer service.  That makes 2010 workflows compete for resources with regular SharePoint processes so they are less scaleable and reliable in a Farm where servers don't have abundant resources.  Workflow manager servers can be added as needed to increase capacity.
    3. Workflow manager workflows are completely declarative.  This removes the ability to do custom server side code which is one of the most frequent sources of instability and upgrade issues.  But that also makes 2013 workflows less easy to extend.  You can extend them using REST calls or custom XML web services.
    4. Because 2013 workflows run "out of band" there are some things that 2010 workflows can do that 2013 workflows cannot.  For example 2013 workflows can't change item level permissions.  But 2013 workflows can do things that 2010 workflows can't like make REST calls.

    That's the basic list.


    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.

    Tuesday, August 13, 2013 12:27 PM
  •  Thanks Paul for this information.It is very helpful for me.

    Also I Installed and Configured Workflow Manager 1.0 in my machine where SharePoint Server 2013 is installed i.e everything in a single box. I created a workflow via SharePoint Designer 2013(using Visual Designer).It gets created and publised to SharePoint Site. But When i tried to see the workflow status (in my case i have associated with document library item creation) the workflow triggered and not ended with success state instead it throws the below error

    RequestorId: c5168ff4-a66a-1748-e5c4-f281f3972425. Details: System.ApplicationException: HTTP 401 {"error_description":"Invalid JWT token. Could not resolve issuer token."} {"x-ms-diagnostics":["3000006;reason=\"Token contains invalid signature.\";category=\"invalid_client\""],"SPRequestGuid":["c5168ff4-a66a-1748-e5c4-f281f3972425"],"request-id":["c5168ff4-a66a-1748-e5c4-f281f3972425"],

    Can you guide me to resolve this issue?

    ______________________________________________

    Siva

    Wednesday, August 14, 2013 12:59 PM
  • I have the same problem. I installed with the instructions here at

    http://technet.microsoft.com/en-us/library/jj193514.aspx

    ANY IDEAS?


    Kathryn Birstein, Senior SharePoint Architect

    Sunday, August 25, 2013 10:49 PM
  • What account are you logged in with when you run the workflow?  any chance its the system account for the Farm?  I've seen this error when trying to invoke workflows using the system account.

    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.

    Monday, August 26, 2013 12:04 PM
  • I am NOT running the workflow with the Farm Administrator account, but with a user account which is site collection admin on the site collection where the workflow resides. I know that bug. And I have tested setting up the Workflow Manager with both the Farm Administrator account and a normal service account with the same issue.

    Kathryn Birstein, Senior SharePoint Architect

    Monday, August 26, 2013 1:30 PM
  • I'm thinking this is a bug introduced by June CU maybe because I installed Workflow Manager in EXACTLY the same way I'm doing it on two other farms and had no problem.

    Kathryn Birstein, Senior SharePoint Architect

    Monday, August 26, 2013 1:35 PM
  • WEIRDLY, when went back into the farm this morning, after getting the JWT error all day yesterday, the workflows suddenly started working. Which leads me to believe some process overnight on that farm kicked off that fixed it. I did have the Profile Sync running so maybe running a sync AFTER installing the Workflow, even though it has synced before, is the fix. Very strange stuff. Trying on another similar farm that I had the same error on and will report back results.

    Kathryn Birstein, Senior SharePoint Architect

    Monday, August 26, 2013 3:58 PM
  • There is a timer job that runs daily which updates the trusted certs, I'm willing to bet when this ran it corrected your issue.

    Refresh Trusted Security Token Services Metadata feed


    MCITP-EA | "Never test how deep the water is with both feet"


    Tuesday, July 29, 2014 2:40 PM
  • Yes, you do need to run a User Profile Sync after the workflow Manager is registered with  the farm.  Otherwise it doesn't tend to pickup the user context of the initiator properly.

    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.

    Wednesday, July 30, 2014 11:30 AM