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

Parallel Multiple

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

Catch

 

within normal flow, the Event can only “catch” the trigger. When attached

 

 

 

 

 

 

to the boundary of an Activity, the Event can only “catch” the trigger.

 

 

 

 

 

 

 

 

 

 

 

 

Unlike the normal Multiple Intermediate Event, all of the assigned

 

 

 

 

 

 

 

 

 

 

 

 

triggers are REQUIRED for the Event to be triggered.

 

 

 

 

 

 

The Event marker will be an unfilled plus sign (see the figure on the right).

 

 

 

 

 

 

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

 

 

 

 

 

 

Parallel Multiple Intermediate Events. If the Intermediate Event has

 

 

 

 

 

 

more than one associated EventDefinition and the

 

 

 

 

 

 

parallelMultiple attribute of the Intermediate Event is true, then the

 

 

 

 

 

 

Event will be displayed with the Parallel Multiple Event marker.

 

 

 

 

 

Intermediate Events Attached to an Activity Boundary

Table 10.90 describes the Intermediate Events that can be attached to the boundary of an Activity.

Table 10.90 – Intermediate Event Types Attached to an Activity Boundary

Trigger

Description

Marker

Message

A Message arrives from a participant and triggers the Event. If a

Interrupting

 

Message Event is attached to the boundary of an Activity, it will change

 

 

the normal flow into an exception flow upon being triggered.

 

 

For a Message Event that interrupts the Activity to which it is attached,

 

 

the boundary of the Event is solid (see upper figure on the right). Note

 

 

that if using this notation, the attribute cancelActivity of the Activity

Non-

 

to which the Event is attached is implicitly set to true.

Interrupting

 

For a Message Event that does not interrupt the Activity to which it is

 

 

attached, the boundary of the Event is dashed (see lower figure on the

 

 

right). Note that if using this notation, the attribute cancelActivity of

 

 

the Activity to which the Event is attached is implicitly set to false.

 

 

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.

 

Timer

A specific time-date or a specific cycle (e.g., every Monday at 9am) can

Interrupting

 

be set that will trigger the Event. If a Timer Event is attached to the

 

 

boundary of an Activity, it will change the normal flow into an exception

 

 

flow upon being triggered.

 

 

For a Timer Event that interrupts the Activity to which it is attached, the

 

 

boundary of the Event is solid (see upper figure on the right). Note that if

Non-

 

using this notation, the attribute cancelActivity of the Activity to

Interrupting

 

which the Event is attached is implicitly set to true.

 

 

For a Timer Event that does not interrupt the Activity to which it is

 

 

attached, the boundary of the Event is dashed (see lower figure on the

 

 

right). Note that if using this notation, the attribute cancelActivity of

 

 

the Activity to which the Event is attached is implicitly set to false.

 

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

253

Table 10.90 – Intermediate Event Types Attached to an Activity Boundary

Escalation

This type of Event is used for handling a named Escalation. If attached

Interrupting

 

to the boundary of an Activity, the Intermediate Event catches an

 

 

Escalation. In contrast to an Error, an Escalation by default is

 

 

assumed to not abort the Activity to which the boundary Event is

 

 

attached. However, a modeler can decide to override this setting by using

Non-

 

the notation described in the following:

 

Interrupting

 

For an Escalation Event that interrupts the Activity to which it is

 

 

 

attached, the boundary of the Event is solid (see upper figure on the

 

 

right). Note that if using this notation, the attribute cancelActivity of

 

 

the Activity to which the Event is attached is implicitly set to true.

 

 

For an Escalation Event that does not interrupt the Activity to

 

 

which it is attached, the boundary of the Event is dashed (see lower

 

 

figure on the right). Note that if using this notation, the attribute

 

 

cancelActivity of the Activity to which the Event is attached is

 

 

implicitly set to false.

 

 

 

 

Error

A catch Intermediate Error Event can only be attached to the boundary

Interrupting

 

of an Activity, i.e., it MAY NOT be used in normal flow. If used in this

 

 

context, it reacts to (catches) a named Error, or to any Error if a name

 

 

is not specified.

 

 

Note that an Error Event always interrupts the Activity to which it is

 

 

attached, i.e., there is not a non-interrupting version of this Event. The

 

 

boundary of the Event thus always solid (see figure on the right).

 

 

 

 

Cancel

This type of Intermediate Event is used within a Transaction Sub-

Interrupting

 

Process. This type of Event MUST be attached to the boundary of a Sub-

 

 

Process. It SHALL be triggered if a Cancel End Event is reached within

 

 

the Transaction Sub-Process. It also SHALL be triggered if a

 

 

TransactionProtocol “Cancel” Message has been received while the

 

 

transaction is being performed.

 

 

Note that a Cancel Event always interrupts the Activity to which it is

 

 

attached, i.e., there is not a non-interrupting version of this Event. The

 

 

boundary of the Event thus always solid (see figure on the right).

 

 

 

 

Compensation

When attached to the boundary of an Activity, this Event is used to

 

 

"catch" the Compensation Event, thus the Event marker MUST be

 

 

unfilled (see figure on the right). The Event will be triggered by a thrown

 

 

compensation targeting that Activity. When the Event is triggered, the

 

 

Compensation Activity that is associated to the Event will be performed

 

 

(see page 301).

 

 

Note that the interrupting a non-interrupting aspect of other Events does

 

 

not apply in the case of a Compensation Event. Compensations can

 

 

only be triggered after completion of the Activity to which they are

 

 

attached. Thus they cannot interrupt the Activity. The boundary of the

 

 

Event is always solid.

 

 

 

 

254

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

Table 10.90 – Intermediate Event Types Attached to an Activity Boundary

Conditional

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

Interrupting

 

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

 

 

 

 

 

 

be found page 82. If a Conditional Event is attached to the boundary of

 

 

 

 

 

 

 

 

 

 

 

 

an Activity, it will change the normal flow into an exception flow upon

 

 

 

 

 

 

 

 

 

 

 

 

being triggered.

Non-

 

For a Conditional Event that interrupts the Activity to which it is

 

attached, the boundary of the Event is solid (see upper figure on the

Interrupting

 

right). Note that if using this notation, the attribute cancelActivity of

 

 

 

 

 

 

the Activity to which the Event is attached is implicitly set to true.

 

 

 

 

 

 

For a Conditional Event that does not interrupt the Activity to which it is

 

 

 

 

 

 

 

 

 

 

 

 

attached, the boundary of the Event is dashed (see lower figure on the

 

 

 

 

 

 

right). Note that if using this notation, the attribute cancelActivity of

 

 

 

 

 

 

the Activity to which the Event is attached is implicitly set to false.

 

 

 

 

 

Signal

The Signal Event can receive a Signal when attached to the boundary

Interrupting

 

of an Activity. In this context, it will change the normal flow into an excep-

 

 

 

 

 

 

tion flow upon being triggered. 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

Non-

 

Activity) as well as having a larger scope than Error Events. When used

 

Interrupting

 

to “catch” the Signal, the Event marker will be unfilled. The attributes of

 

 

 

 

 

 

a Signal can be found on page 272.

For a Signal Event that interrupts the Activity to which it is attached, the boundary of the Event is solid (see upper figure on the right). Note that if using this notation, the attribute cancelActivity of the Activity to which the Event is attached is implicitly set to true.

For a Signal Event that does not interrupt the Activity to which it is attached, the boundary of the Event is dashed (see lower figure on the right). Note that if using this notation, the attribute cancelActivity of the Activity to which the Event is attached is implicitly set to false.

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

255

Table 10.90 – Intermediate Event Types Attached to an Activity Boundary

Multiple

A Multiple Event indicates that there are multiple triggers assigned to the

Interrupting

 

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

 

 

“catch” the trigger. In this case, only one of the assigned triggers is

 

 

REQUIRED and the Event marker will be unfilled upon being triggered,

 

 

the Event that occurred will change the normal flow into an exception

Non-

 

flow.

 

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

Interrupting

 

 

 

Multiple Intermediate Events. If the Intermediate Event has more than

 

 

one associated EventDefinition, then the Event will be displayed

 

 

with the Multiple Event marker.

 

 

For a Multiple Event that interrupts the Activity to which it is attached,

 

 

the boundary of the Event is solid (see upper figure on the right). Note

 

 

that if using this notation, the attribute cancelActivity of the Activity

 

 

to which the Event is attached is implicitly set to true.

 

 

For a Multiple Event that does not interrupt the Activity to which it is

 

 

attached, the boundary of the Event is dashed (see lower figure on the

 

 

right). Note that if using this notation, the attribute cancelActivity of

 

 

the Activity to which the Event is attached is implicitly set to false.

 

Parallel

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

Interrupting

Multiple

attached to the boundary of an Activity, the Event can only “catch” the

 

 

 

 

trigger. Unlike the normal Multiple Intermediate Event, all of the

 

 

assigned triggers are REQUIRED for the Event to be triggered. The

 

 

Event marker will be an unfilled plus sign (see the figures on the right).

 

 

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

Non-

 

Parallel Multiple Intermediate Events. If the Intermediate Event has

Interrupting

 

more than one associated EventDefinition and the

 

 

parallelMultiple attribute of the Intermediate Event is true, then the

 

 

Event will be displayed with the Parallel Multiple Event marker.

 

 

For a Parallel Multiple Event that interrupts the Activity to which it is

 

 

attached, the boundary of the Event is solid (see the upper figure to the

 

 

right). Note that if using this notation, the attribute cancelActivity of

 

 

the Activity to which the Event is attached is implicitly set to true.

 

 

For a Parallel Multiple Event that does not interrupt the Activity to which

 

 

it is attached, the boundary of the Event is dashed (see the lower figure to

 

 

the right). Note that if using this notation, the attribute cancelActivity

 

 

of the Activity to which the Event is attached is implicitly set to false.

 

Attributes for Boundary Events

For boundary Events, the following additional attributes exists:

The BoundaryEvent element inherits the attributes and model associations of CatchEvent (see Table 8.44). Table 8.46 presents the additional attributes and model associations of the Boundary Event element.

256

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