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.
Status | ||
---|---|---|
|
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:
...
If processes that have already been started in the productive environment are deleted, data inconsistencies occur. |
...
Object list
...
Status | ||
---|---|---|
|
...
Status | ||
---|---|---|
|
...
. |
Additional functions
The object distribution is designed to setup which are process objects are using which real objects already at design time. Some process objects needs additional settings based on the object list. These objects are enhancing the object list by additional columns. E.g. a object creation task does not need access to the objects of the object list but needs to know where to place the newly created objects.
Status | ||
---|---|---|
|
...
Person responsible
Process owners have special rights to make changes to running processes. Further information can be found in the user manual ofProProcess. The persons responsible for the process are determined (via existing formulas, if applicable) and saved at the start of the process.
The maintenance of the responsible persons is described in the chapter Members.
...
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 |
| User name of the initiator. Can be used e.g. for Members or Notifications. |
| 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:
|
Delta data is only available for alphabetical data. However, due to the architecture, numeric values are also offered, but may not be used. | |
| Current status at runtime |
RESPONSIBLES | Responsible Person |
| List of all process owners. Can be used, for example, for Members or Notifications. |
...