Sub processes can be used to model the start of further processes within a process. Thus, processes can be divided into smaller reusable sub-processes and processed both serially and in parallel. In addition, it is possible to specify at the process start whether the process to be started should be synchronized, i.e. waited for the process end, or whether the process to be started should run completely independently.
The prerequisite for starting a process by another process is on the one hand the activation of the Start by process start option on the process to be started (see also Process Chaining ). At the same time, a process can only be started if either no main object has been defined or if it can be provided correctly by the triggering process and no status conflicts occur. Furthermore, the process to be started can also be configured so that several processes are started in parallel at runtime depending on the object list.
...
The complete functionality and distribution of the objects is described in chapter Object List of the Process.
Container
The functionality of containers is described in the chapter Containers and Items. In the following the most important containers and items are described:
Container/Item | Description |
|---|---|
HEADER | Header data |
ASYNCHRONOUS | Process was started asynchronously |
ITERATION | Number of Iterations |
RUNTIME_STATUS | Current status at runtime |