I have a Reusable Workflow that is associated to a List. I would like to tweak this workflow and continue using it. Solutions that require a one-time migration (e.g. using a different type of work flow) are acceptable IF they provide this functionality in the future.
If I edit the Reusable Workflow and Publish it, the changes are not propagated to the associated list. If this "just worked," that would be the ideal solution. [A] Is there any way for Publish to propagate Reusable Workflow changes to an associated list?
There are various articles listing these solutions, but they are all for SP2010:
- Wait for all workflow items to end. Delete existing workflow. Re-associate workflow.
- Terminate all workflow items. Delete existing workflow. Re-associate workflow.
- Version workflows (wf_v1, wf_v2) and continue adding a new workflow for every change.
- Update/replace workflow file directly using PowerShell.
None of these 4 solutions seem feasible except #3. Manually versioning the workflow is possible, but it means losing the workflow history & tasks for each item. This also lends itself to the Approval Status being spread across 3-4 different columns. [B] Is there a way to preserve Tasks, History, and Status Column when versioning a workflow?