The root object is the Process. Each process has a unique, freely selectable Process ID and a continuous version number beginning with 1, as well as a description.
Versioning makes it possible to change and extend processes at a later date without already running processes being affected. When saving, the modeling application checks whether the changes made result in a structural change to the process and automatically proposes the creation of a new process version.
The determination of whether a new version is necessary is fully automatic. The structure of the modeled process is compared with the structure of the generated workflow template. This structure differs as soon as one of the following actions is performed:
Creating new objects (without tasks)
Deleting existing objects (without tasks)
Moving existing objects incl. changing the order of activities and gates
Changing a subprocess from serial to parallel and vice versa
Changing a gateway from exclusive to parallel and vice versa
Enabling or disabling a gateway Repetition
Activating or Deactivating the Multiplication of Activities
All other changes do not lead to a structural change and therefore do not require a new version (e.g. changes to processors, persons responsible, texts, notifications etc.).
It is possible to overwrite the current version. However, if processes already exist for the current version, such changes can lead to unexpected errors with data inconsistencies. Running processes may be irreparably damaged.
Delete Processes/Versions
Processes or versions that have already been used can no longer be deleted. However, this check only takes place on the current system, where there may be no data at all. The deletion is confirmed with the following popup, where you can also choose whether the entire process or only the current version is to be deleted.
If processes that have already been started in the productive environment are deleted, data inconsistencies occur.