...
- 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.
| Panel |
|---|
We are advice our user would like to advice you to branch the app to a new version whenever they you 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 yetchanges to your app that is already rolled out to production. This would ensure that existing process instances will continue to run without being affected the uncommitted/incomplete development work of yours. Another thing that you need to keep in mind is that when we say updating update the existing running process to a newer process flow, it is the system will actually abort the currect one and start the instances created under the existing process version and replace with a new process instance from where its process activity last stop with at (By matching the same record id). So, the process instance id will be different from the original one. This will cause the SLA data become not accuratemay be an issue with the SLA as new instances are created causing a reset with the calculation data. This is the reason why we are do not encourage a running process instance in production mode to update to a newer process flowyou to update your process design when running in production. |