Update Existing Running Process Instances to the Newer Process Flow After Process Changes

There are 2 situations, as described below:

  1. Updating a process in the same app version: all existing running processes in the same app version will automatically be updated to the new process flow in the background.
  2. Branch an app to a new version and update from it: all existing running processes will continue to run as 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 version, one by one, if you wish to do that. We do have plans to integrate this function into the web console soon.)

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 by your uncommitted/incomplete development work.

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 stopped (by matching the record ID). So, the process instance 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.

  • No labels