Migration expanded sub process

[nicetokillye]

Hi there,
I have a process which contains expanded sub process.
I am trying to migrate process instance to newer version. However, sub process stays the same version after migration, when main process is migrated successfully.

For example: I have this running process. [test:1:id]

After migration it becomes [test:2:id]. However sub process stays at [test:1:id] version

I migrate processes like this:

And Migration plan is:

definition keys here are definition ids, im just wrong with naming;
They are like test:1:id and test:2:id

I was trying to set id of sub process using .mapActivities(“sub_process”,“sub_process”)
But got exception:
There are multiple mappings for source activity id

So the question is: How to migrate process and sub process to new version?

[Ingo_Richtsmeier]

Hi @nicetokillye,

your diagram includes technically two different process models (without distinguishing them).

When you start a process instance with runtimeService.startProcessInstanceByKey(), Task 1 will be activated.

When you correlate a message to the message start event, only the subprocess will be instantiated and is now waiting in the second (intermediate) message event.

Both are independent process instances and have to migrated one after the other.

But I think that you modeled the with another intention.

Hope this helps, Ingo