Long running process and process upgrade

[vanden]

Hi,

I've seen similar topics but none answered my question.
My question is : Is there a way to upgrade a process and make currently running instances benefit from it?

A short example to illustrate:
Let's say that my process was deployed several months ago. Many instances are currently running.
I now want to change the process and add a mandatory step for each one, including already started processes as the rule changed and every user has to conform, even if he started his process before the change.
I do not want to ask all users to start a new process.

I saw the following in another post:

With long running processes deploying a new process definition will not change anything.
The long running process will just keep running in the old process definition.

But is this a default behaviour that can be changed by setting any attribute?

[trademak]

Hi,

Migrating running process instances to a new process definition is not supported.
So you would need to write your own migration logic for this.

Best regards,

[tomdc]

Hi,

I think it is not possible to do this automatically.
Lets assume you have a simple workflow:
Start–>Task1–>Task2–>end
and you would change this to
Start–>Task1–>Tast3–>Tast2–>end.

How should the system know how to migrate? Should they all go back to the first, second or third? What if data was already commited via a webservice? The migration will always be a brain breaker.

However, it would be nice if we could say: move all processes being at a specific step to a new version of the process at a new specified step. (I suppose this is not possible).


Just an idea…