Hi everyone,
I’m currently working with ARIS Flows and have run into a challenge regarding versioning and instance management.
As we frequently update our workflow definitions and deploy new versions, we are left with "in-flight" (running) instances tied to the older versions. In many other BPMS platforms, there is usually a mechanism to migrate these active instances to the new definition (via automatic mapping or transition rules).
However, I cannot find documentation on how ARIS handles this specific scenario.
My specific questions are:
- Is there a native function to migrate running instances to a new workflow version, or are they permanently pinned to the version they started on?
- If migration is not supported, what is the recommended strategy? (e.g., "draining" old instances, version-parallelism, or specific API workarounds).
Any documentation links or experiences you could share would be incredibly helpful.
Thanks!
Florian Gerdes on
Hello Tim.
I am not aware of any solution to migrate a running instance to a new version. We are having the same issue, when small adaptions are required in dialogues or mails.
If the instance really needs to be transferred to a new version of the workflow, we are stopping the old instance and starting a new instance.
If the old instance has already completed a few manual tasks and you don't want to repeat those, you can skip these. At least thats, how we did it in the APG. Not sure, if the procedure is also working for flows.
Here the system asks for a XML statement. Either you edit this manually or you copy the exact XML of the previous completed task.
This feels a little weird, but was working for us. I would recommend to test this a couple of times, if this is also working for your workflow and those continue like intended.
Kind regards,
Florian