Versions Compared

Key

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

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
titleUnbekannter 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:

...

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

...

Object list

...

Status
titleUnbekannter Anhang

...

Status
titleUnbekannter Anhang

...

Image RemovedIn the best case, it is no longer necessary to manually adjust the distribution at runtime. However, manual processing can be very useful, especially when activities are multiplied and work packages are distributed to several locations. For this reason, when defining the distribution, special care must be taken to ensure that the object list is deactivated wherever it is not needed

.

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
titleUnbekannter Anhang

...

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

  • 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.

...