A collection process collects several chain strings to form one string in the process chain maintenance.
Process chain management handles collection processes in a particular way. The system makes the variant names consistent and guarantees that all processes of the same name that have been scheduled more than once, trigger the same event. This enables the several chain strings to be collected to form one and also makes multiple-scheduling of the actual application processes unnecessary.
The following collection processes are available in the process chain maintenance:
This process does not start before all events of the predecessor processes, that is including the last event, that it has waited for, have been successfully triggered.
Use this collection process when you want to combine processes and when further processing is dependent on all these predecessors.
The application process starts every time a predecessor process event has been successfully triggered.
Use this collection process when you want to avoid multi-scheduling the actual application process.
The application process starts when the first event in one of the predecessor processes has been successfully triggered .
Use this collection process when you want to process processes in parallel and schedule further independent processes after these ones.
Owing to the time components, the collection processes do not display logical gates in the normal sense, because the system cannot distinguish between whether a 0 entry (no event received), means that the event was never received or whether it has not been received yet. The reason for this is that the checks do not run continuously but only take place when the event is received.