Versions Compared

Old Version 2

changes.mady.by.user Owen Ong

Saved on

compared with

New Version Current

changes.mady.by.user Jack

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

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 new process instances created under the existing process version and replace them with a new process instance from where its activity stop with the same record idprocess activity last stopped (by matching the record ID). So, the process instance id 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.