A Signal Boundary Event is attached to an activity or sub-process and waits for a named signal while the attached element is executing.
Use a Signal Boundary Event when a running activity must react to a signal that can be broadcast from another process, workflow, or event source. When the expected signal is received, the Signal Boundary Event triggers an alternate process path.
Signal Boundary Events are always catching events, meaning they wait for a signal to be received rather than sending one.
Depending on the configuration, a Signal Boundary Event can be either interrupting or non-interrupting.
Signal boundary events are displayed as:
| Message Boundary Event Icon | Description |
|---|---|
|
|
Two thin concentric circles with a triangle inside attached to the main activity for an interrupting event. |
|
|
Two thin dashed concentric circles with a triangle inside attached to the main activity for non-interrupting event. |
Use a Signal Boundary Event when:
- A running activity must respond to a broadcast signal.
- Multiple processes or activities may need to react to the same event.
- An external event should affect process execution.
- Alternative processing should begin when a signal is received.