Currently we are using a third party workflow engine which is proprietary. We are replacing the third party engine with Camunda. However, we are facing difficulty as we need to migrate long-running process instances on the third party engine to Camunda during production release.
We’ve considering a few options, one option is to run both engines in parallel and let third party engine continues to handle the in-flight instances while Camunda starts to handle the new ones; another option is to take data migration approach
For the data migration, at high level, it seems we ought to use API to start a new process in Camunda and move the process instance to corresponding state. but specifically, what is considered to be the best practices in terms of migration?
By the way, we are using version 7.12, and Spring Boot.
Thank you so much @Niall for your insight and quick response.
It’s good to know that we can start process in any activity in the workflow. I think it would be a cleaner solution than using createProcessInstanceModification(). My next question is how start process can help to handle the a symbol in a sub process? A concrete example would be very helpful.
Let’s say I have a main process, via call activity, the mail process connects to a sub process. And the sub process has a task called ‘subprocessTask’. I’d like to start process and land directly on ‘subprocessTask’ inside a supprocess.
