Updating In-Flight SharePoint 2013 Workflows (Visual Studio) RRS feed

  • Question

  • Is there any guidance on the best strategy for upgrading in-flight SharePoint 2013 Workflows?  I am currently developing a SharePoint 2013 Workflow using Visual Studio 2012.  The workflow has 6 phases and may take up to a month to complete.  I need a plan for when I will inevitably need to make a change to the workflow.

    I am concerned that simply deploying a new version of a WSP with new XAML might cause a breaking change to in-flight workflows.  This was a major problem in 2007/2010, and in the past I have created a new version of the workflow when deploying a change.  SharePoint 2013 designer workflows automatically create a new version when published, but unfortunately with Visual Studio workflows this is not the case.  Updating the WSP and reactivating the feature will force new workflow code to run, but I think this could cause issues when the workflow state data is de-serialized.

    Wednesday, October 29, 2014 11:15 PM