Create an interrupting or non-interrupting event-based embedded subprocess.
Prerequisites
A subprocess which does not have any incoming or outgoing sequence flows is inserted in the BPMN process.
Context
The respective events can only be used in event-based subprocesses as start events for the following event definitions:
- Error
- Escalation
- Compensation
An event with one of these event definitions can only be defined as a start event for event-based subprocesses.
The following event definitions cannot be used for start events in event-based subprocesses:
- Failed completion
- Terminate
The decision as to whether an event-based embedded subprocess is interrupting or non-interrupting is made for the relevant start event.
How to proceed
-
Right-click on the subprocess and select the Is Triggered by Event embedded subprocess type from the mini toolbar:
Or activate the corresponding property in the Properties window.
The subprocess is shown as an event-based subprocess.
-
Insert a start event with an appropriate event definition or convert an existing event into a start event.
The event is always initially shown as an interrupting event.
-
To flag the start event as non-interrupting, deactivate the is interrupting check box in the Properties tool window.
The event is displayed as a non-interrupting start event.
Note
An empty event (with no event definition) is always inserted in an event-based subprocess as an end event. Only when the event has been linked to a suitable event definition can it be defined as a start event.
Related Topics
