End Event

An end event denotes the point at which a process’s path will come to an end. End events can only result in a “throw” of a result.[1] Symbol 1]     Silver, B. (2009). BPMN Method and Style: A levels-based methodology for BPM process modeling and improvement using BPMN 2.0. In CodyCassidy Press US.

Start Event (Message)

A message is received from a participant, which initiates the process. The actual recipient of the message can be identified by connecting the event to a participant via a message flow within the process’s definitional collaboration.1] [1]     Silver, B. (2009). BPMN Method and Style: A levels-based methodology for BPM process modeling and improvement using BPMN […]

Intermediate Event (Message/Catching)

A message intermediate event can be used to both send and receive messages. When used to “catch” the message, the event marker must be left empty. If the process was waiting for a message, this causes it to continue, or it changes the flow for exception handling. Symbol [1]     Silver, B. (2009). BPMN Method and […]

Intermediate Event (Message/Throwing)

A message intermediate event can be used to both send and receive messages. The event marker must be filled when used to “throw” the message (see the upper figure on the right). If the process was waiting for a message, this causes it to continue, or it changes the flow for exception handling.[1] Symbol 1]     […]

End Event (Message)

At the end of the process, this type of end indicates that a message is sent to a participant.[1] Symbol N Method and Style: A levels-based methodology for BPM process modeling and improvement using BPMN 2.0. In CodyCassidy Press US.

Intermediate Event (Link/Catching)

Paired link events can also be used as “off-page connectors” in order to print a process across multiple pages. Within the process level, they can also be used as generic “go to” objects. There can only be one target link event at any given time. The event marker will be empty when used to “catch” […]

Intermediate Event (Link/Throwing) Gateway

A gateway is a device that controls the divergence and convergence of sequence flows in a process or choreography. As a result, it will determine path branching, forking, merging, and joining. The type of behaviour control will be indicated by internal markers.[1] Method and Style: A levels-based methodology for BPM process modeling and improvement using […]

Gateway (Exclusive)

[XOR] When splitting, directs the sequence flow to one of the outgoing branches. When merging, it waits for one incoming branch to finish before starting the outgoing flow.[1] Symbol    Silver, B. (2009). BPMN Method and Style: A levels-based methodology for BPM process modeling and improvement using BPMN 2.0. In CodyCassidy Press US.

Gateway (Parallel)

[And] When used to split the sequence flow, all outgoing branches are activated at the same time. When parallel branches are merged, it waits for all incoming branches to complete before initiating the outgoing flow.[1] Symbol      Silver, B. (2009). BPMN Method and Style: A levels-based methodology for BPM process modeling and improvement using BPMN […]

Gateway (Inclusive)

[Or] When a branch splits, one or more branches are activated. Before merging, all active incoming branches must be completed.[1] Symbol 1]     Silver, B. (2009). BPMN Method and Style: A levels-based methodology for BPM process modeling and improvement using BPMN 2.0. In CodyCassidy Press US.