Versions Compared

Old Version 1

changes.mady.by.user Hugo

Saved on

compared with

New Version Current

changes.mady.by.user Zhang Allen

Saved on

Key

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

将流程更改后，将现有的运行流程实例更新为较新的流程流程

有两种情况，如下所述：

  1. 在同一应用程序版本中更新进程：同一应用程序版本中的所有现有正在运行的进程将自动更新到后台的新进程流。
  2. 将应用程序分支到新版本并从中更新：所有现有的正在运行的流程实例将继续运行，因此不会更新。
    （注意：如果你愿意的话，你也可以使用Joget的JSON API逐个手动更新正在运行的进程到新的进程版本，我们计划很快将这个功能集成到Web控制台中。
Panel

我们想建议您将应用程序分支到新版本，只要您想对已经推出到生产环境的应用程序进行更改。这将确保现有的流程实例将继续运行，而不会受到未提交/不完整的开发工作的影响。

另一件需要牢记的事情是，当我们将现有的运行流程更新为新的流程流程时，系统实际上将中止在现有流程版本下创建的实例，并将其替换为流程活动所在的新流程实例上次停止（通过匹配记录ID）。所以，流程实例ID将与原来的ID不同。这可能是SLA的一个问题，因为创建新的实例会导致重置计算数据。这就是为什么我们不鼓励您在生产环境中更新流程设计的原因。

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 process instances 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.)
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 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.