Result

Intro

A result is the consequence of reaching an End Event in a process. BPMN recognizes different end results such as message, error, compensation, signal, link, and multiple.

Key points:

• Makes end states explicit for clarity and handling.
• Supports exception and compensation logic.
• Common use cases across EA/BPM/Data/App/Tech include notifications, rollbacks, error reporting, and event signaling.
• Pitfall: modeling one generic end without differentiating outcomes.

Examples:

• Message end sends confirmation to a customer.
• Error end triggers failure handling and alerts.
• Compensation end reverses prior steps after cancellation.

In practice:

Choose specific end event types to reflect business outcomes and downstream handling.

Related terms: Event; Exception Flow; BPMN

FAQs:

Q: Can a process have multiple end results?
A: Yes; model distinct end events for different outcomes.

Q: Do end results carry data?
A: Some do, like message and signal ends.

‍