End Event

Introduction

A BPMN 2.0 End Event represents the conclusion or termination of a business process. It signifies the point at which the process completes, and no further actions occur after the end event. In BPMN diagrams, the End Event is visualized as a bolded circle and can be used to signal different types of process endings, such as normal completion or an error condition.

Key Points about End Events:

• Visual Representation: A bold circle.
• Types of End Events:
  • Message End Event: Sends a message when the process finishes.
  • Signal End Event: Broadcasts a signal to other processes or systems when the process ends.
  • Error End Event: Indicates that the process has ended due to an error.
  • Terminate End Event: Immediately stops all activities in the process, terminating the entire process instance.
  • Escalation End Event: Indicates an escalation has occurred, which requires handling at a higher level.

End Events have no outgoing sequence flows, as they represent the final point of the process. They play a critical role in signaling the result of the process and ensuring that the flow is properly completed.

An end event signifies the conclusion of a process. The process concludes once all the steps outlined in the diagram are executed, culminating at the end event. Given that a process may yield various results, such as success or failure, it is possible to use multiple end events to indicate different outcomes. For example, if an order is successfully processed, the process ends with a successful completion. Conversely, if the card details are incorrect, leading to a transaction failure, no receipt is generated, and the order is considered unsuccessful.

In this example, the final outcomes vary significantly even though both are categorized as end events. It is important to note that when a process includes multiple end events, each end event must be distinctly named to avoid confusion.

All events with their corresponding symbols