Update existing running process to the newer process flow after process changes
There are 2 situations as below:
- Updating process in same App Version, all the existing running process in the same App version will automatically update to the new process flow in background.
- Branch an App to a new version and update from it, all the existing running process will continue as it is and no automatically update will run. But we provided a JSON API that allow you to manually update your running process to the new process flow one by one manually if you wish to do that. We do plan for build an UI for it and it is in low priority in our roadmap.
We are advice our user to branch the app to a new version whenever they would like to make some change on an app which is in production already. So that, all the running will continue running without affected by the work that not production ready yet.
Another thing need to keep in mind is when we say updating the existing running process to a newer process flow, it is actually abort the currect one and start the new process from where its activity stop with the same record id. So, the process instance id will be different from the original one. This will cause the SLA data become not accurate. This is the reason why we are not encourage a running process instance in production mode to update to a newer process flow.