Update
...
Existing Running Process Instances to the Newer Process Flow After Process Changes
There are 2 situations, as described below:
- Updating a process in same App Version, all the the same app version: all existing running process processes in the same App app version will automatically update be updated to the new process flow in the background.
- Branch an App app to a new version and update from it, : all the existing running process processes will continue to run as it is and no automatically update will run. But we provided a JSON API that allow you they are and will not be updated. (Note: You may also make use of Joget's JSON API to manually update your running process to the new process flow version, 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.have plans to integrate this function into the web console soon.)
| Panel |
|---|
We would like to advice you to branch the app to a new version whenever you would like to make changes 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 by your uncommitted/incomplete development work of yours. Another thing that you need to keep in mind is that, when we update the existing running process to a newer process flow, the system will actually abort instances created under the existing process version and replace them with a new process instance from where its process activity last stop at stopped (By by matching the record idID). So, the process instance id ID will be different from the original one. This may be an issue with the SLA as new instances are created causing a reset with the calculation data. This is the reason why we do not encourage you to update your process design when running in production. |