nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

how to deal with old process instance when the process updated

mm524262909

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 ?

Find more posts tagged with

Comments

martin_grofcik

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

mm524262909

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 ?

mm524262909

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 ?

martin_grofcik

Hi,

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

Regards
Martin

mm524262909

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 ?

ollib

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.

mm524262909

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 ?

trademak

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

Best regards,

mm524262909

viggo_navarsete

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

martin_grofcik

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