End Event
A None End Event terminates a path of execution in the process. When all paths reach End Events, the process instance completes. It represents normal, successful process termination.
What is an End Event?
A None End Event marks the end of a sequence flow path. When a token reaches this event, that path terminates. The process instance completes when all active tokens have reached End Events.
Visual Representation
The End Event displays as a thick-bordered circle that is empty inside. The thick border distinguishes End Events from Start Events (thin border) and Intermediate Events (double border).
Key Characteristics
- Path termination: Ends one execution path; other parallel paths may continue
- No trigger: Simply terminates the reaching token
- Normal completion: Indicates successful, expected process ending
- Multiple allowed: A process can have several End Events for different outcomes
Trigger Variants
End Event can be triggered by different mechanisms. Each variant uses a specific icon marker to indicate its trigger type.
Common Use Cases
Successful Completion
Order processing ends successfully after all items are shipped and customer is notified.
Multiple Outcomes
A request process has separate End Events for "Approved" and "Rejected" paths to distinguish outcomes.
Parallel Path Completion
Each parallel branch ends at its own End Event; process completes when all branches finish.
Frequently Asked Questions
Related BPMN Elements
Try this element in Crismo
Create beautiful BPMN diagrams with our modern process modeling platform.