You are viewing limited content. For full access, please sign in.

Question

Question

update all running jobs after workflow change

asked on June 20, 2014

is there a way to update all jobs in the workflow to the latest version once a change to the workflow has been published.   It seems that it will only make the update after the job moves in the workflow.  Can i force the change so that all jobs are showing the current workflow ?

 

0 0

Replies

replied on June 20, 2014

When you publish a workflow with running instances it gives you an option to update all running instances. This should do what you are asking for.

0 0
replied on June 22, 2014

Please be careful when using the Update Workflows option.

I have had a case where thousands of earlier version workflows lost their tokens.  This resulted in missing information, images moving to root folders because their metadata was missing and breaks in security.

 

Please refer to:

https://answers.laserfiche.com/questions/54354/Broken-Workflow-Missing-Tokens

0 0
replied on June 23, 2014

I agree with Peter about being careful.

 

Can anyone help me understand how a running workflow state can be reassigned to a newer version whose logic can potentially be totally different ?

0 0
replied on June 26, 2014

I agree, I can't see how an earlier workflow that contains certain metadata could possibly work in a new version if it is vastly different. e.g. new tokens that did not exist in the previous workflow could break logical decisions.

 

However, when my workflows broke all I had done was to add a month to the period of a Token Calculator.  No new tokens; just a new value. The rest of the workflow was not touched. I thought I was pretty safe!

But, workflows broke even if they had already passed this point in the workflow.  It was not just the Token Calculator token that was lost. All tokens were lost.

 

0 0
replied on June 23, 2014

There have been some bugs with updating running instances in the past (it is a very complicated process to do), but it is the best we can do to cover this usecase.

 

As to what it does: Say you have your workflow stopped at a wait condition, and you update the workflow by adding an activity after that wait, or changing the properties of an activity after that wait, it will then use that new definition to set the course of the workflow instead of the one originally published.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.