BPMN 2.0 – Business Process Model and Notation camunda.

com

Activities Events Gateways

Intermediate
A task is a unit of work (the job to be performed). Start End
Exclusive Gateway t merges the incoming sequence flows while directly
When marked with a symbol, it indicates 
 I

passing on incoming tokens. When splitting, exactly one

Event Subprocess


Event Subprocess

Task
a collapsed sub-process, an activity that can 


Non-Interrupting

Non-Interrupting
be refined. branch is activated.

Interrupting

Interrupting
y


y


Throwing
Standard

Standard
Catching

Boundar

Boundar
A transaction is a set of activities that logically Event-based Gateway Is always followed by catching events or receive tasks.
Transaction belong together; it might follow a specified The branch whose event/task is triggered first is
transaction protocol. activated.
None: Untyped events, 

An event subprocess is placed into a process or indicate start point, state

subprocess. It is activated when its start event gets
Event

triggered and can interrupt the higher level process
changes or final states.
Parallel Gateway When used to split the sequence flow, all outgoing
Subprocess
context or run in parallel (noninterrupting), branches are activated simultaneously. When merging
depending on the start event. Message: Receiving and

parallel branches, it waits for all incoming branches to
sending messages.
complete before triggering the outgoing flow.

Call
 A call activity is a wrapper for a globally defined Timer: Cyclic timer events,

Activity
task or process reused in the current process. 
 points in time, time spans or

A call to a process is marked with a symbol. timeouts. Inclu ive Gateway

When s litting, one or ore br nches re

p m a a a ctivated. All active incoming
Escalation: Escalating to a br nches ust co lete be ore erging.
a m mp f m

Activity Markers
a k Types

T s higher level of responsibility.

describe the execution specify the nature of the action Com lex Gateway

p
behavior of activities: to be performed: Conditional: Reacting to Co lex erging
mp m a nd branching behavior that is not captured by 

changed conditions. other g tew s.
a ay

S ubprocess Marker S end Task

Loop Marker R eceive Task

Link: Two corresponding link

events represent a sequence

Exclu ive s E vent-based Gateway (instantiate)

flow. Ea ch occurence of a subsequent event starts a new process instance.

P arallel MI Marker U ser Task
arallel Event-based Gateway (instantiate)

Error: Catching or throwing

S equential MI Marker Manual Task P

he occurence of all subsequent events starts a new process instance.

named errors.

Ad Hoc Marker B usiness Rule Task Cancel: Reacting to cancelled

transactions or triggering

C ompensation Marker S ervice Task cancellation.

S cript Task Compensation: Handling or

triggering compensation.

Sequence Flow Default Flow Conditional Flow Signal: Signalling across differ-


ent processes. A signal thrown

can be caught multiple times.

Terminate: Triggering the

Participants
defines the execution is the default branch has a condition immediate termination of 

order of the process to be chosen if all assigned that defines a process or sub-process.

elements. other conditions whether or not the

evaluate to false. flow is used.

ane
Task
Pools and lanes represent

L
responsibility for activities. 



Pool
A pool or a lane can be an
organization, a role, or a system.

ane
f
Task

L
Data Arti acts
Message flow

Message flow symbolizes the

A data object represents information message exchange. Message
flowing through the process, such as
A data output is a data result of the entire
x
Te t Annotation flows can be attached to pools,
business documents, emails, or letters.
process. A kind of output parameter.
Grou ings
p
sub-processes, activities and
visu ll
a y combine elements message events.

A collection data object represents a A data association is used to associate r

(di ected)

collection of information, e.g., a list of data elements with flow objects such as ss
A ociation

Pool
order items. activities, events and sub-processes. Message

Exchange/Collaboration

The collaboration of multiple

Indi idual
 v processes can be defined
A data store is a place where the process
S m ol y b s through a combination of
A data input is an external input for 
 message and sequence flows.
Pool

can read or write data, e.g. a database or 


the entire process. A kind of input
a filing cabinet. It persists beyond the
parameter.
lifetime of the process instance. links artifacts and flow objects can be used as artifacts © 2025