Скачиваний:
20
Добавлен:
28.01.2021
Размер:
7.15 Mб
Скачать

Table 10.88 – End Event Types

Multiple

This means that there are multiple consequences of ending the Process.

 

 

All of them will occur (e.g., there might be multiple Messages sent).

 

 

There is no specific EventDefinition subclass (see page 259) for

 

 

Multiple End Events. If the End Event has more than one associated

 

 

EventDefinition, then the Event will be displayed with the Multiple

 

 

Event marker (a pentagon—see the figure on the right).

 

Sequence Flow Connections

See “Sequence Flow Connections Rules” on page 40 for the entire set of objects and how they MAY be a source or target of a Sequence Flow.

An End Event MUST be a target for a Sequence Flow.

An End Event MAY have multiple incoming Sequence Flows.

The Flow MAY come from either alternative or parallel paths. For modeling convenience, each path MAY connect to a separate End Event object. The End Event is used as a Sink for all tokens that arrive at the Event. All tokens that are generated at the Start Event for that Process MUST eventually arrive at an End Event. The Process will be in a running state until all tokens are consumed.

An End Event MUST NOT be a source for Sequence Flows; that is, there MUST NOT be outgoing

Sequence Flows.

An exception to this is when an End Event is used in an Expanded Sub-Process and is attached to the boundary of that Sub-Process. In this case, a Sequence Flow from the higher-level Process MAY connect from that End Event in lieu of connecting from the actual boundary of the Sub-Process.

Message Flow Connections

See “Message Flow Connection Rules” on page 41 for the entire set of objects and how they MAY be a source or target of a Message Flow.

NOTE: All Message Flows MUST connect two separate Pools. They MAY connect to the Pool boundary or to Flow Objects within the Pool boundary. They MUST NOT connect two objects within the same Pool.

An End Event MUST NOT be the target of a Message Flow; it can have no incoming Message Flows.

An End Event MAY be the source of a Message Flow; it can have zero (0) or more outgoing Message Flows. Each Message Flow leaving the End Event will have a Message sent when the Event is triggered.

The Result attribute of the End Event MUST be set to Message or Multiple if there are any outgoing

Message Flows.

The Result attribute of the End Event MUST be set to Multiple if there is more than one outgoing

Message Flows.

10.5.4 Intermediate Event

As the name implies, the Intermediate Event indicates where something happens (an Event) somewhere between the start and end of a Process. It will affect the flow of the Process, but will not start or (directly) terminate the Process.

Intermediate Events can be used to:

248

Business Process Model and Notation (BPMN), v2.0.2

Show where Messages are expected or sent within the Process,

Show delays are expected within the Process,

Disrupt the normal flow through exception handling, or

Show the extra work needed for compensation.

The Intermediate Event shares the same basic shape of the Start Event and End Event, a circle with an open center so that markers can be placed within the circle to indicate variations of the Event.

An Intermediate Event is a circle that MUST be drawn with a double thin line (see Figure 10.72).

The use of text, color, size, and lines for an Intermediate Event MUST follow the rules defined in

“Use of Text, Color, Size, and Lines in a Diagram” on page 39 with the exception that the thickness of the line MUST remain double so that the Intermediate Event can be distinguished from the Start and End Events.

Figure 10.72 – Intermediate Event

One use of Intermediate Events is to represent exception or compensation handling. This will be shown by placing the Intermediate Event on the boundary of a Task or Sub-Process (either collapsed or expanded). The Intermediate Event can be attached to any location of the Activity boundary and the outgoing Sequence Flows can flow in any direction. However, in the interest of clarity of the Diagram, we RECOMMEND that the modeler choose a consistent location on the boundary. For example, if the Diagram orientation is horizontal, then the Intermediate Events can be attached to the bottom of the Activity and the Sequence Flows directed down, then to the right. If the Diagram orientation is vertical, then the Intermediate Events can be attached to the left or right side of the Activity and the Sequence Flows directed to the left or right, then down.

Intermediate Event Triggers

There are twelve types of Intermediate Events in BPMN: None, Message, Timer, Escalation, Error, Cancel, Compensation, Conditional, Link, Signal, Multiple, and Parallel Multiple. Each type of Intermediate Event will have a different icon placed in the center of the Intermediate Event shape to distinguish one from another.

There are two ways that Intermediate Events are used in BPMN:

1.An Intermediate Event that is placed within the normal flow of a Process can be used for one of two purposes. The Event can respond to (“catch”) the Event trigger or the Event can be used to set off (“throw”) the Event trigger.

2.An Intermediate Event that is attached to the boundary of an Activity can only be used to “catch” the Event trigger.

Intermediate Events in Normal Flow

When a token arrives at an Intermediate Event that is placed within the normal flow of a Process, one of two things will happen.

Business Process Model and Notation (BPMN), v2.0.2

249

If the Event is used to “throw” the Event trigger, then trigger of the Event will immediately occur (e.g., the Message will be sent) and the token will move down the outgoing Sequence Flow.

If the Event is used to “catch” the Event trigger, then the token will remain at the Event until the trigger occurs (e.g., the Message is received). Then the token will move down the outgoing Sequence Flow.

Ten of the twelve Intermediate Events can be used in normal flow as shown in Table 10.89.

Table 10.89 – Intermediate Event Types in Normal Flow

Trigger

Description

Marker

 

 

 

 

 

None

The None Intermediate Event is only valid in normal flow, i.e., it MAY

Throw

 

NOT be used on the boundary of an Activity. Although there is no specific

 

 

 

 

trigger for this Event, it is defined as throw Event. It is used for modeling

 

 

 

 

methodologies that use Events to indicate some change of state in the

 

 

 

 

Process.

 

 

 

 

There is no specific EventDefinition subclass (see page 259) for

 

 

 

 

None Intermediate Events. If the (throw) Intermediate Event has no

 

 

 

 

associated EventDefinition, then the Event MUST be displayed

 

 

 

 

without a marker (see the figure on the right).

 

 

 

 

 

 

 

 

Message

A Message Intermediate Event can be used to either send a Message

Throw

 

or receive a Message.

 

 

 

 

When used to “throw” the Message, the Event marker MUST be filled

 

 

 

 

 

 

 

 

(see the upper figure on the right). When used to “catch” the Message,

 

 

 

 

 

 

 

 

then the Event marker MUST be unfilled (see the lower figure on the

 

 

 

 

right). This causes the Process to continue if it was waiting for the

Catch

 

Message, or changes the flow for exception handling.

 

 

 

 

The actual Participant from which the Message is received can be

 

 

 

 

identified by connecting the Event to a Participant using a Message Flow

 

 

 

 

within the definitional Collaboration of the Process – see Table 10.1.

 

 

 

 

 

 

 

 

See page 91 for more details on Messages.

 

 

 

 

 

 

 

 

Timer

In normal flow the Timer Intermediate Event acts as a delay mechanism

Catch

 

based on a specific time-date or a specific cycle (e.g., every Monday at

 

 

 

 

9am) can be set that will trigger the Event. This Event MUST be dis-

 

 

 

 

played with a clock marker (see the figure on the right).

 

 

 

 

 

 

 

 

250

Business Process Model and Notation (BPMN), v2.0.2

Trigger

Description

Marker

 

 

 

 

 

 

 

Escalation

In normal flow, the Escalation Intermediate Event raises an Escalation.

Throw

 

Since this is a Throw Event, the arrowhead marker will be filled (see the

 

 

 

 

 

 

figure to the right).

 

 

 

 

 

 

 

 

 

 

 

 

Compensation

In normal flow, this Intermediate Event indicates that compensation is

Throw

 

necessary. Thus, it is used to "throw" the Compensation Event, and the

 

 

 

 

 

 

Event marker MUST be filled (see figure on the right). If an Activity is

 

 

 

 

 

 

identified, and it was successfully completed, then that Activity will be

 

 

 

 

 

 

compensated. The Activity MUST be visible from the Compensation

 

 

 

 

 

 

Intermediate Event, i.e., one of the following MUST be true:

 

 

 

 

 

 

• The Compensation Intermediate Event is contained in normal

 

 

 

 

 

 

flow at the same level of Sub-Process.

 

 

 

 

 

 

• The Compensation Intermediate Event is contained in a

 

 

 

 

 

 

Compensation Event Sub-Process which is contained in the Sub-

 

 

 

 

 

 

Process containing the Activity.

 

 

 

 

 

 

If no Activity is identified, all successfully completed Activities visible

 

 

 

 

 

 

from the Compensation Intermediate Event are compensated, in

 

 

 

 

 

 

reverse order of their Sequence Flows. Visible means one of the

 

 

 

 

 

 

following:

 

 

 

 

 

 

• The Compensation Intermediate Event is contained in normal

 

 

 

 

 

 

flow and at the same level of Sub-Process as the Activities.

 

 

 

 

 

 

• The Compensation Intermediate Event is contained in a

 

 

 

 

 

 

Compensation Event Sub-Process which is contained in the Sub-

 

 

 

 

 

 

Process containing the Activities.

 

 

 

 

 

 

To be compensated, an Activity MUST have a boundary Compensation

 

 

 

 

 

 

Event, or contain a Compensation Event Sub-Process.

 

 

 

 

 

 

 

 

 

 

 

 

Conditional

This type of Event is triggered when a condition becomes true. A

Catch

 

condition is a type of Expression. The attributes of an Expression can

 

 

 

 

 

 

be found on page 82.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Business Process Model and Notation (BPMN), v2.0.2

251

Link

The Link Intermediate Events are only valid in normal flow, i.e., they

Throw

 

MAY NOT be used on the boundary of an Activity. A Link is a

 

 

mechanism for connecting two sections of a Process. Link Events can

 

 

be used to create looping situations or to avoid long Sequence Flow

 

 

lines. Link Event uses are limited to a single Process level (i.e., they

Catch

 

cannot link a parent Process with a Sub-Process). Paired Intermediate

 

Events can also be used as “Off-Page Connectors” for printing a Process

 

 

across multiple pages. They can also be used as generic “Go To” objects

 

 

within the Process level. There can be multiple source Link Events, but

 

 

there can only be one target Link Event.

 

 

When used to “throw” to the target Link, the Event marker will be filled

 

 

(see the top figure on the right). When used to “catch” from the source

 

 

Link, the Event marker will be unfilled (see the bottom figure on the right).

 

 

 

 

Signal

This type of Event is used for sending or receiving Signals. A Signal is

Throw

 

for general communication within and across Process levels, across

 

 

Pools, and between Business Process Diagrams. A BPMN Signal is

 

 

similar to a signal flare that shot into the sky for anyone who might be

 

 

interested to notice and then react. Thus, there is a source of the Signal,

Catch

 

but no specific intended target. This type of Intermediate Event can send

 

 

 

or receive a Signal if the Event is part of a normal flow. The Event can

 

 

only receive a Signal when attached to the boundary of an Activity. The

 

 

Signal Event differs from an Error Event in that the Signal defines a

 

 

more general, non-error condition for interrupting Activities (such as the

 

 

successful completion of another Activity) as well as having a larger

 

 

scope than Error Events. When used to “catch” the Signal, the Event

 

 

marker will be unfilled (see the middle figure on the right). When used to

 

 

“throw” the Signal, the Event marker will be filled (see the top figure on

 

 

the right). The attributes of a Signal can be found on page 272.

 

Multiple

This means that there are multiple triggers assigned to the Event. If used

Throw

 

within normal flow, the Event can “catch” the trigger or “throw” the trig-

 

 

gers. When attached to the boundary of an Activity, the Event can only

 

 

“catch” the trigger. When used to “catch” the trigger, only one of the

 

 

assigned triggers is REQUIRED and the Event marker will be unfilled

Catch

 

(see the middle figure on the right). When used to “throw” the trigger (the

 

same as a Multiple End Event), all the assigned triggers will be thrown

 

 

and the Event marker will be filled (see the top figure on the right).

 

 

There is no specific EventDefinition subclass (see page 259) for

 

 

Multiple Intermediate Events. If the Intermediate Event has more than

 

 

one associated EventDefinition, then the Event will be displayed with

 

 

the Multiple Event marker.

 

252

Business Process Model and Notation (BPMN), v2.0.2