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.
UNBEKANNTER ANHANG
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.

Prozesse/Versionen löschen
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.
UNBEKANNTER ANHANG

If processes that have already been started in the productive environment are deleted, data inconsistencies occur.

Container

The functionality of containers is described in the chapter Sub Objects, section Container
The most important containers and items are described below:

Container/Item	Description
HEADER	Kopfdaten
INITIATOR	User name of the initiator. Can be used e.g. for Members or Notifications.
OBJECT	Object reference to the main object. All properties (technical: attributes and methods) are provided within the object. Some data is available in all objects, but each object can provide additional data: IS_NEW tells you whether the object is (still) new. GET_DESCRIPTION returns the name GET_EXTERNAL_KEY returns the object key in external, readable format. GET_OBJECT_TYPE_DESCRIPTION returns the name of the object type (for example, material). GET_CHAR_VALUE returns the value of a characteristic. GET_EXTERNAL_STATUS returns the status in external format (if status supported). GET_INTERNAL_STATUS returns the status in internal format (if status supported). GET_STATUS_DESCRIPTION returns the status description (if status supported). The following data is usually available for accessing the main data of the object: GET_MAIN_DATA returns the current main data and also takes into account data changes that are not yet saved. GET_MAIN_DATA_OLD returns the old main data from the database. GET_MAIN_DATA_DELTA returns the delta between the current and old data. The new value is delivered if there is a deviation. If the values are identical, the placeholder "^" is returned.
	Delta data is only available for alphabetical data. However, due to the architecture, numeric values are also offered, but may not be used.
RUNTIME_STATUS	Current status at runtime
RESPONSIBLES	Responsible Person
All	List of all process owners. Can be used, for example, for Members or Notifications.

If customer specific container extensions are set up, then the relevant container items can be choosen.
UNBEKANNTER ANHANG