topic Re: how to deal with old process instance when the process updated in Alfresco Archive

how to deal with old process instance when the process updated

mm524262909 — Mon, 08 Dec 2014 15:41:17 GMT

the process defination will change and when changed, how to deal with the old process instance this is to say , how the old process instance will carry on next ?

Re: how to deal with old process instance when the process updated

martin_grofcik — Tue, 09 Dec 2014 07:23:02 GMT

Hi,

"old" - already running process instances behaves according to exact process definition version. This process definition (exact version) did not change. (does not matter that there is new process definition version). "Old" process instances works according to "old" process definition.

Regards
Martin

Re: how to deal with old process instance when the process updated

mm524262909 — Tue, 09 Dec 2014 13:58:58 GMT

but i want the "Old" process instances works according to "new" process definition. what can i do ? can you help me or give me some advice ?

Re: how to deal with old process instance when the process updated

mm524262909 — Tue, 09 Dec 2014 14:00:50 GMT

but i want the "Old" process instances works according to "new" process definition.
what can i do ? can you help me or give me some advice ?

Re: how to deal with old process instance when the process updated

martin_grofcik — Wed, 10 Dec 2014 07:28:55 GMT

Hi,

There are several posts on the forum which deals with this topic. Use org.activiti.engine.impl.cmd.SetProcessDefinitionVersionCmd.

Regards
Martin

Re: how to deal with old process instance when the process updated

mm524262909 — Wed, 10 Dec 2014 12:06:26 GMT

but when the new process and the old one has conflict , what will the engine do ?
for example, in the old , there is three parallel tasks and one of them is completed, but now we changed the process defination and merge this three tasks and Use org.activiti.engine.impl.cmd.SetProcessDefinitionVersionCmd. now in the new process , the process instance is in the places of the merged task ? and what about some even worse conflict ?
can you give me some links about the problem i mentioned here ?

Re: how to deal with old process instance when the process updated

ollib — Wed, 10 Dec 2014 19:01:15 GMT

in general, this rule applies (i guess this is true for most workflow engines like activiti, jbpm …):

when you start a process instance based upon a given process definition, it is bound the this process definition forever. you can not work on an old process instance with a newer process definition. old process instances will continue to execute on the old process definition, new process instances will execute on the new process definition.

Re: how to deal with old process instance when the process updated

mm524262909 — Thu, 11 Dec 2014 08:34:08 GMT

but if i want , is there a solution ?
or can i do something to transform the old to the new ?
and someone up said org.activiti.engine.impl.cmd.SetProcessDefinitionVersionCmd
i think activiti should have supply something ?

Re: how to deal with old process instance when the process updated

trademak — Thu, 11 Dec 2014 08:37:15 GMT

You can use the SetProcessDefinitionVersionCmd yes. This will move a process instance to a different process definition.

Best regards,

Re: how to deal with old process instance when the process updated

mm524262909 — Thu, 11 Dec 2014 08:40:38 GMT

Re: how to deal with old process instance when the process updated

viggo_navarsete — Thu, 11 Dec 2014 11:30:41 GMT

Do you have a real world scenario to use as an example mm524262909?

Re: how to deal with old process instance when the process updated

martin_grofcik — Fri, 12 Dec 2014 09:18:28 GMT

Hi mm524262909

but when the new process and the old one has conflict , what will the engine do ?

Your example and use case is valid - I faced this problem many times. (the simplest one is - small bug in process definition (100 process instances are running according to this process definition… you have fix already but you do not have possibility to change it - this is solved by SetProcessDefinitionVersionCmd).
SetProcessDefinitionVersionCmd sets only process definition version of the running process instance. It does not cope with process instance state transition to the new process definition. Process instance state transition can not be done automatically in general, but you can use activiti commands/DB to transform process instance to the new state.

Links

Search the forum - I like this topic very much because it is crucial for workflow platform administration.

Regards
Martin