Activities Conversations
Events
Gateways
Conversation Diagram
None: Untyped events,
indicate start point, state
changes or final states.
Message: Receiving and
sending messages.
Timer: Cyclic timer events,
points in time, time spans or
timeouts.
Error: Catching or throwing
named errors.
Cancel: Reacting to cancelled
transactions or triggering
cancellation.
Compensation: Handling or
triggering compensation.
Conditional: Reacting to
changed business conditions
or integrating business rules.
Signal: Signalling across different
processes. A signal thrown
can be caught multiple times.
Multiple: Catching one out of
a set of events. Throwing all
events defined
Link: Off-page connectors.
Two corresponding link events
equal a sequence flow.
Terminate: Triggering the
immediate termination of a
process.
Escalation: Escalating to
an higher level of
responsibility.
Parallel Multiple: Catching
all out of a set of parallel
events.
Start EndIntermediate
Catching
Throwing
EventSub-Process
Interrupting
Standard
EventSub-Process
Non-Interrupting
Boundary
Interrupting
BoundaryNon-
Interrupting
Sequence Flow
defines the execution
order of activities.
Conditional Flow
has a condition
assigned that defines
whether or not the
flow is used.
Default Flow
is the default branch
to be chosen if all
other conditions
evaluate to false.
Task
A Task is a unit of work, the job to be
performed. When marked with a symbol
it indicates a Sub-Process, an activity that can
be refined.
Transaction
A Transaction is a set of activities that logically
belong together; it might follow a specified
transaction protocol.
Event
Sub-Process
An Event Sub-Process is placed into a Process or
Sub-Process. It is activated when its start event
gets triggered and can interrupt the higher level
process context or run in parallel (noninterrupting)
depending on the start event.
Call Activity
A Call Activity is a wrapper for a globally defined
Task or Process reused in the current Process. A
call to a Process is marked with a symbol.
Task Types
Types specify the nature of
the action to be performed:
Send Task
Receive Task
User Task
Manual Task
Business Rule Task
Service Task
Script Task
Markers indicate execution
behavior of activities:
Activity Markers
Sub-Process Marker
Loop Marker
Parallel MI Marker
Sequential MI Marker
~ Ad Hoc Marker
Compensation Marker
A Conversation defines a set of
logically related message exchanges.
When marked with a symbol it
indicates a Sub-Conversation, a
compound conversation element.
A Conversation Link connects
Conversations and Participants.
Inclusive Gateway
When splitting, one or more
branches are activated. All
active incoming branches must
complete before merging.
Complex Gateway
Complex merging and
branching behavior that is not
captured by other gateways.
Exclusive Event-based Gateway
(instantiate)
Each occurrence of a subsequent
event starts a new process
instance.
Parallel Event-based Gateway
(instantiate)
The occurrence of all subsequent
events starts a new process
instance.
Multi Instance Pool
(Black Box)
Conversation
Sub-Conversation
Pool
(Black Box)
Participant B
The order of message
exchanges can be
specified by combining
message flow and
sequence flow.
PoolPool
Pools (Participants) and Lanes
represent responsibilities for
activities in a process. A pool
or a lane can be an
organization, a role, or a
system. Lanes subdivide pools
or other lanes hierarchically.
Lane
Task
Lane
Task
Pool
Message Flow symbolizes
information flow across
organizational boundaries.
Message flow can be attached
to pools, activities, or
message events. The Message
Flow can be decorated with
an envelope depicting the
content of the message.
Data
Out-
put
Data Store
A Data Object represents information flowing
through the process, such as business
documents, e-mails, or letters.
A Data Store is a place where the process can
read or write data, e.g., a database or a filing
cabinet. It persists beyond the lifetime of the
process instance.
A Data Input is an external input for the
entire process.A kind of input parameter.
A Collection Data Object represents a
collection of information, e.g., a list of order
items.
Collaboration Diagram
Pool(WhiteBox)
LaneLane
Choreographies
Choreography Diagram
A Choreography Task
represents an Interaction
(Message Exchange)
between two Participants.
Choreography
Task
Participant A
Participant B
A Sub-Choreography contains
a refined choreography with
several Interactions.
Multiple
Participants Marker
Swimlanes
BPMN 2.0 - Business Process Model and Notation
Collection
Ad-hoc Subprocess
Task
Task
~
Message
Start Event
Message Flow
Data Object
Collapsed
Subprocess
Event-based
Gateway
Escalation
End Event
Timer
Intermediate
Event
Receive Task
Attached
Intermediate
Timer Event
Link
Intermediate
Event
Manual Task
End
Event
Data
Store
Link
Intermediate
Event
Parallel
Multiple
Intermediate
Event
Text Annotation
Group
Multi Instance
Task (Parallel)
Message
End Event
Send Task
Parallel
Gateway
Exclusive
Gateway
Attached
Intermediate
Error Event
Signal
End
Event
Call Activity
Subprocess
Event Subprocess
Conditional
Start Event
Error End
Event
Start
Event
End
Event
Looped
Subprocess
condition
http://bpmb.de/poster
Participant A
Participant C
Participant B
Choreography
Task
Participant A
Participant B
Choreography
Task
Participant A
Participant C
Initiating
Message
(decorator)
Response
Message
(decorator)
Choreography
Task
Participant B
Participant A
When splitting, it routes the sequence flow to exactly
one of the outgoing branches. When merging, it awaits
one incoming branch to complete before triggering the
outgoing flow.
Exclusive Gateway
Is always followed by catching events or receive tasks.
Sequence flow is routed to the subsequent event/task
which happens first.
Event-based Gateway
When used to split the sequence flow, all outgoing
branches are activated simultaneously. When merging
parallel branches it waits for all incoming branches to
complete before triggering the outgoing flow.
Parallel Gateway
A Call Conversation is a wrapper for a
globally defined Conversation or SubConversation.
A call to a Sub-conversation
is marked with a symbol.
Sub-Choreography
Participant A
Participant C
Participant B
Call
Choreography
Participant A
Participant B
A Call Choreography is a
wrapper for a globally
defined Choreography Task
or Sub-Choreography. A call
to a Sub-Choreography is
marked with a symbol.
Input
A Data Output is data result of the entire
process. A kind of output parameter.
A Data Association is used to associate data
elements to Activities, Processes and Global
Tasks.
denotes a set of
Participants of the
same kind.
Message
a decorator depicting
the content of the
message. It can only
be attached to
Choreography Tasks.
Pool
(Black
Box)
Pool (Black Box)
Pool
(Black Box)
© 2011
Standard