Common patterns
Several outcomes
Give a decision more than two answers, and end each outcome in its own named end event.
A decision can have as many answers as you need: one -> line for each. When the outcomes don't meet again, end each path in its own end event, named as the state the process ends in.
process Job application
lanes Recruiter | Hiring manager
lane Recruiter
start:message Application received
user Screen application
lane Hiring manager
xor Candidate fit?
strong -> Invite to interview
maybe -> Put on hold
no (default) -> Send rejection
user Invite to interview
end Interview booked
lane Recruiter
user Put on hold
end Candidate on hold
send Send rejection
end Candidate rejectedWhat to notice
- Each answer is a short label on its flow: strong, maybe, no.
- Separate end events, Interview booked, Candidate on hold and Candidate rejected, show every outcome at a glance.
- One flow is the
(default), so a case that fits no other answer still has a path.
When several paths can be taken at once, not just one, use an inclusive gateway. See Take one or more paths.