We have a requirement to split a multi-instance subprocess(parallel) into 2 different multi instances(both parallel), and the tasks will also be split across both these multi-instances. I am facing challenges while defining mapping during migrating process-instances from older version to newer version, as multi-instance from source version can only be mapped to either one of the 2 split multi-instances in new version - this is stopping defining mapping across all the tasks that are now spread between 2 multi instances. Is there a solution to this?
Hello my friend!
Welcome to the Community!
This is a scenario that I haven’t had the need to do so far, so maybe it’s not the most correct way… but…
What if you try to start one of the multi-instances from migration, and right after migrating the instance, you use process instance modification, to “clone” the instance also to the other necessary multi-instance?
Wouldn’t this solve your problem?
It is worth remembering again that I have never experienced this scenario, so it will be necessary to carry out tests before running this in production.
William Robert Alves