...
The activation of a new version of process A and B does indeed lead to new processes being started with version 002. However, processes already running in version 001 of process A always start process B in version 002 from this point on.
| Info |
|---|
This means that used processes must always remain compatible with already activated uses. Special attention is paid to the object list that is transported between processes. If this list is restructured from the perspective of an overall process, this may lead to inconsistencies in processes that are already running. If entire processes are to be completely restructured, it is recommended to define completely new processes instead of new process versions. |
Activation
To ensure that the dependencies described above are adhered to, an automatic activation logic takes place. All processes involved are determined and the target versions are determined. It is ensured that no inconsistencies arise, e.g. by forcing a versioning of process A for the above mentioned case. New versions can be created directly and automatically during activation. Therefore, it is not necessary to manually version all involved processes before activation.
However, if versions have already been created, the user can decide which version should be used. If one assumes the above example, but the user would also have prepared a new version of process A, then this version would be recognized during activation and automatically suggested for activation. In the dialog, however, a new version can still be forced explicitly.
...