Event Sub-Processes
An event sub-process executes an internal sub-process when an event is triggered. You can use event sub-processes within business processes and pageflows.
See also Event Handlers.
Note the following when using event sub-processes:
- A process can contain zero or more event sub-processes of any supported type or configuration.
- Each event sub-process must start with a single start event.
- There is no in-process communication between event sub-processes (sequence flow, signals, etc).
Business processes support interrupting/non-interrupting event sub-processes.
Note: Pageflows support non-interrupting event sub-processes. They do not support interrupting event sub-processes.
This is defined on the start event of the event sub-process by checking
Interrupt Process Flow or
Continue Process Flow. This affects the process as follows:
Interrupt Process Flow:
- The main process flow is suspended until completion of the event sub-process.
- This does not affect the processing and completion of individual activities that are already in progress related to the process instance. However, those activities' outgoing flow is not processed until the event sub-process completes.
- This does not affect the processing of other event handler flows, event sub-processes and ad-hoc activities.
- This does not affect the processing of activities in active reusable sub-processes.
- Incoming events, submits, sub-process completions and so on in the main process are preserved but ignored until the event sub-process has completed.
Copyright © 2021. Cloud Software Group, Inc. All Rights Reserved.