3. Introduction
It would be more accurate to say
that a BPMN event describes
how the process
responds to a signal that something
happened, or – in the case of a
throwing event – how the process
generates a signal that something
happened.
4. ● Event-triggered behavior refers to
process actions initiated
immediately upon occurrence of a
specific trigger signal.
Event-Triggered Behavior
5. ● Intermediate events, the ones
with the double ring. As the name
suggests, intermediate events
occur after the start of a process
level and before the end.
Event-Triggered Behavior
6. ● A throwing intermediate event, with the black icon
inside, means the process generates
the trigger signal.
● Throwing the signal occurs immediately and
automatically as soon as the incoming sequence flow
arrives, and the process continues immediately
afterward on the sequence flow out of the throwing
event.
Event-Triggered Behavior
7. ● A catching intermediate event, with the white icon
inside, drawn with sequence flow
in and sequence flow out, means the process waits for
the trigger signal. When the
trigger signal arrives, the process resumes on the
sequence flow out of the event.
Event-Triggered Behavior
8. Drawn on the boundary of an activity, called
a boundary event, does not signify waiting. It
means while the activity is running, the
process listens for that signal. If it occurs
before the activity completes, the sequence
flow out of the event, called the exception
flow, is triggered.
A catching
intermediate
event
9. Timer Event
Catching Timer Event :
Drawn with sequence flow in and out, a
catching Timer intermediate event
represents a delay.
It means either wait for [specified duration]
or wait until [specified date/time].
10. Timer Event
Timer Boundary Event :
A Timer boundary event acts like a
combination stopwatch and alarm clock.
By convention,
the stopwatch starts when the activity
the event is attached to starts.
11. Timer Event
Timed Interval :
A Timer boundary event measures the time
from start to completion of a single activity,.
13. Message Event
Message and Message Flow :
The terms send and receive should be
considered “keywords” in BPMN, reserved
specifically
for sending and receiving a message,
represented in the diagram by a message
flow.
Send Task and Throwing Message Event:
15. Message Event
Receive Task and Catching Message Event :
Receiving is closely related to sending. Again, the term technically applies
only to messages,communications from external participants.
16. Message Event
Message Boundary Event:
A message you are waiting for usually implies a response to a prior
request. But BPMN provides a way to respond to unsolicited messages
as well. In that case, the process is not paused waiting for the message,
but listening for it while running. A Message boundary event attached to
an activity initiates the response to the message if it arrives while the
activity is running.
17.
18. Error Event
Representing an exception end state of a process activity. Error
events only come in two flavors:
• An interrupting Error boundary event
• Error end event.
You cannot throw or wait for an Error signal in an intermediate
event, and there is no Error start event.
19. Error Event
Represents the exception end state exit from the task. The normal
flow, the sequence flow out of the task, represents the exit when the
task completes successfully, and the exception flow, the sequence
flow out of the Error event, is the exit when it does not. Its meaning is
exactly the same as an XOR gateway following the task with a
success gate and an exception gate.
20. Escalation Event
In BPMN,Escalation is the non-interrupting counterpart of Error, with
similar throw-catch behavior. An Escalation boundary event simply
signifies a non-interrupting exception inside an activity.
that activity could be either a task or subprocess. A valuable use case
for an Escalation boundary event on a User task is ad-hoc user action.
21. Signal Event
Error and Escalation can only throw to the boundary of the parent
subprocess; Message can only throw to another pool.
22. Signal Event
It is incorrect to attach a message flow to a Signal event.
The link between the Signal thrower and catcher is
suggested only by matching labels.
23. Conditional Event
The Conditional event signifies a continuously monitored
data condition. When the condition, defined by a data
expression, becomes true, the event is triggered.
24. Link Event
The Link event is more of a drawing aid than a true event.
It does not really throw or catch a
trigger signal. Link only supports throwing and catching
intermediate events.
25. Event Subprocess
An event subprocess is defined within a particular process
level, either the top-level process or a regular subprocess.
It works similar to a boundary event.
27. CREDITS: This presentation template was created by Slidesgo,
including icons by Flaticon, infographics & images by Freepik
Thanks
Do you have any question?
