Open Edition

 View Only

 Query regarding Process Instance Migration (PIM) with Nested Subprocess in BAMOE 9.4.x

Mangesh Panchal's profile image
Mangesh Panchal posted 08/11/26 07:18 AM

In the older 8.0.x version, process instance migration was straightforward - we could easily migrate all active process instances from a source KJAR container to a target KJAR container using container IDs. However, in the latest version, migration operates at Process ID level, and I have a question regarding nested subprocesses.

Use Case:
I have a parent process with multiple nested subprocesses:

CaseApprovalProcess -> StartApprovalProcess -> ProductApprovalProcess -> ApprovalProcess

The ApprovalProcess contains user tasks.

Suppose my changes are strictly inside ApprovalProcess:

1. As per the new version's migration design, I create ApprovalProcessV2.

2. To Update the call elements up the hierarchy, do I also need to create new versions for the parent processes (ProductApprovalProcessV1, StartApprovalProcessV1, etc)?

3. Does the migration plan need to include all parent processes whose call elements were updated, or do we only include ApprovalProcess in the migration plan?

Could someone please clarify how process instance migration handles nested call elements in new version?

Thanks!

soniya abraham's profile image
soniya abraham posted 08/14/26 07:18 AM


Hi Mangesh,

If only ApprovalProcess changes, you create ApprovalProcessV2 and migrate all active ApprovalProcess instances to the new version. Parent processes do not require new versions unless their Call Activity references are updated.

When a fresh CaseApprovalProcess (or any parent) starts, it will still call the original ApprovalProcess unless the parent’s Call Activity is updated. To make new instances use ApprovalProcessV2, you must redeploy the parent processes with updated references — for example, creating ProductApprovalProcessV1, StartApprovalProcessV1, etc., pointing to the new subprocess ID.

For existing parent process instances, if you want them to call ApprovalProcessV2 instead of the old version, those parent instances also need to be migrated.

Thanks,
Soniya

 

Related Content