Merge

Intro

A Merge is a point where two or more alternative process paths combine into one. In BPMN, it clarifies decision outcomes without synchronizing parallel work.

Key points:

• Simplifies converging decision branches.
• Reduces modeling ambiguity around path selection.
• Common use cases across EA/BPM/Data/App/Tech include exclusive decisions, alternative approvals, and conditional routing.
• Pitfall: confusing a merge with a join that requires synchronization.

Examples:

• Approved or Rejected paths merge before closing a case.
• Alternative validation routes merge into a single fulfillment step.
• Different escalation outcomes merge to a common resolution activity.

In practice:

Use an Exclusive Gateway or multiple incoming flows to an activity when only one path is active at a time.

Related terms: Gateway; Exclusive Gateway; Join

FAQs:

Q: Does a merge wait for multiple inputs?
A: No; only one incoming path is active at a merge.

Q: Is “OR-Join” the same as a merge?
A: Yes; it’s another name for this construct.

‍