BPMN Error Event
The BPMN Error Event article provides a detailed explanation of the error event BPMN element, including the definition, notation, rules, guidelines and examples.
The BPMN Error Event article delves deep into the intricacies and applications of the error event element as outlined in the BPMN 2.0 specification. The definition, notation, and rules sections offer a concise summary of the BPMN 2.0 Specification pertaining to the error event element. Meanwhile, the guidelines section presents a curated collection of best practices specific to the error event, showcasing its proper and effective utilisation in process modelling.
BPMN Definition
An Error represents the content of an Error Event or the Fault of a failed Operation. ~ BPMN Specification
BPMN Notation
The BPMN specification defines the different types of Error Event elements using the following description and notation:
Element | Description | Notation |
---|---|---|
Error Event Sub-Process Event (Interrupting) | Whenever the Event occurs, the associated process is terminated. A downstream token is then generated, which activates the next element of the event-sub-process connected to the Event. | |
Error Boundary Event (Interrupting) | Whenever the Event occurs, the associated Activity is terminated. A downstream token is then generated, which activates the next element of the process connected to the Event. | |
Error End Event | Whenever this event is reached, the event will raise an error and the process will end. |
BPMN Event Types
BPMN events represent various types of occurrences that affect the flow of a process, and they can be categorized based on their position and behavior in the process.
- Start Event: The Start Event indicates where a particular Process will start.
- Intermediate Event: The Intermediate Event indicates where something happens (an Event) somewhere between the start and end of a Process.
- End Event: The End Event indicates where a Process will end.
- Catching Events: Events that catch a trigger. All Start Events and some Intermediate Events are catching Events.
- Throwing Events: Events that throw a Result. All End Events and some Intermediate Events are throwing Events that MAY eventually be caught by another Event.
- Boundary Event: An Intermediate Event that is attached to the boundary of an Activity.
The following table illustrates how the different types of Error Events are grouped as per the BPMN Event types:
Catching Events | Throwing Events | |||||||
Start Event | Intermediate Event | End Event | ||||||
Standard | Event Sub-Process Interrupting | Event Sub-Process Non-Interrupting | Catching | Boundary Interrupting | Boundary Non- Interrupting | Throwing | Standard | |
Error Event |
BPMN Diagram
The following is an example of a BPMN Error Event within a diagram:
BPMN Standards & Guidelines
The difference between standard and guideline is that a standard is a level of quality or attainment while a guideline is a non-specific rule or principle that provides direction to action or behaviour. A standard are high in authority and needs to be adhered to versus a guideline is low in authority and guide one in setting standards or determining a course of action.
BPMN Standards
The BPMN Standards section contains a list of rules that are applicable to the BPMN Error Event as per the official rules of the BPMN Specification.
- A catch Intermediate Error Event can only be attached to the boundary of an Activity and MAY NOT be used in normal flow.
BPMN Guidelines
The BPMN guidelines section contains a list of optional rules that can be used as a guide.
- An Error Catch Events should have a Text Annotation with the
Error Code: {Error Code}
associated with it. - An Error Throw Event should have a Text Annotation with the
Error Code: {Error Code}
associated with it.
Finally
This article provided a detailed explanation of the BPMN Error Event element. Follow me on any of the different social media platforms, and feel free to leave comments.
Reference
- Business Process Model and Notation Specification Version 2.0.2. (2014, January). https://www.omg.org/spec/BPMN/2.0.2/