Boundary Intermediate Events

Spec Page	Spec Rule Text	RuleId
250	The None Intermediate Event is only valid in normal flow, i.e., it MAY NOT be used on the boundary of an Activity	BPMNG046
252	The Link Intermediate Events are only valid in normal flow, i.e. they MAY NOT be used on the boundary of an Activity.	BPMNG047
254	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.	BPMNG048
254	This type of Intermediate Event is used within a Transaction Sub-Process. This type of Event [Cancel] MUST be attached to the boundary of a [Transaction] Sub-Process.	BPMNG034
254	Note that an 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.	BPMNG049
257	One or more Intermediate Events MAY be attached directly to the boundary of an Activity.
257	To be attached to the boundary of an Activity, an Intermediate Event MUST be one of the following Triggers (EventDefinition): Message, Timer, Error, Escalation, Cancel, Compensation, Conditional, Signal, Multiple, and Parallel Multiple.	BPMNG046 BPMNG047
257	An Intermediate Event with a Cancel Trigger MAY be attached to a Sub-Process boundary only if the Transaction attribute of the Sub-Process is set to true.	BPMNG034
258	If the Intermediate Event is attached to the boundary of an Activity:
258	The Intermediate Event MUST NOT be a target for Sequence Flow; it cannot have an incoming Flow.	BPMNG050
258	The Intermediate Event MUST be a source for Sequence Flow.	BPMNG051
258	Multiple Sequence Flow MAY originate from an Intermediate Event. For each Sequence Flow that has the Intermediate Event as a source, a new parallel path SHALL be generated.
258	An exception to this: an Intermediate Event with a Compensation Trigger MUST NOT have an outgoing Sequence Flow (it MAY have an outgoing Association).	BPMNG052
271	The catch None Intermediate Event MUST only be used in Normal Flow and, thus, MAY NOT be attached to the boundary of an Activity.	BPMNG046
From Table 11.7 (340)	Types of Event: Message: Attached to Activity boundary Usage In choreography? Yes. Only for Choreography Tasks.	BPMNG078
From Table 11.7 (340)	Types of Event: Timer: Attached to Activity boundary Usage In choreography? Yes
From Table 11.7 (340)	For relative timers: They [the participants] all have to be involved in the Choreography Activity that immediately precedes the Activity with the attached timer.	BPMNG092
From Table 11.7 (340)	For absolute timers (full time/date): All Participants would know the time. They all have to be involved in the Choreography Activity that immediately precedes the Activity with the attached timer.	BPMNG092

Spec Page

Spec Rule Text

RuleId

250

The None Intermediate Event is only valid in normal flow, i.e., it MAY NOT be used on the boundary of an Activity

BPMNG046

252

The Link Intermediate Events are only valid in normal flow, i.e. they MAY NOT be used on the boundary of an Activity.

BPMNG047

254

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.

BPMNG048

254

This type of Intermediate Event is used within a Transaction Sub-Process. This type of Event [Cancel] MUST be attached to the boundary of a [Transaction] Sub-Process.

BPMNG034

254

Note that an 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.

BPMNG049

257

One or more Intermediate Events MAY be attached directly to the boundary of an Activity.

257

To be attached to the boundary of an Activity, an Intermediate Event MUST be one of the following Triggers (EventDefinition): Message, Timer, Error, Escalation, Cancel, Compensation, Conditional, Signal, Multiple, and Parallel Multiple.

BPMNG046

BPMNG047

257

An Intermediate Event with a Cancel Trigger MAY be attached to a Sub-Process boundary only if the Transaction attribute of the Sub-Process is set to true.

BPMNG034

258

If the Intermediate Event is attached to the boundary of an Activity:

258

The Intermediate Event MUST NOT be a target for Sequence Flow; it cannot have an incoming Flow.

BPMNG050

258

The Intermediate Event MUST be a source for Sequence Flow.

BPMNG051

258

Multiple Sequence Flow MAY originate from an Intermediate Event. For each Sequence Flow that has the Intermediate Event as a source, a new parallel path SHALL be generated.

258

An exception to this: an Intermediate Event with a Compensation Trigger MUST NOT have an outgoing Sequence Flow (it MAY have an outgoing Association).

BPMNG052

271

The catch None Intermediate Event MUST only be used in Normal Flow and, thus, MAY NOT be attached to the boundary of an Activity.

BPMNG046

From Table 11.7

(340)

Types of Event: Message: Attached to Activity boundary Usage In choreography? Yes. Only for Choreography Tasks.

BPMNG078

From Table 11.7

(340)

Types of Event: Timer: Attached to Activity boundary Usage In choreography? Yes

From Table 11.7

(340)

For relative timers: They [the participants] all have to be involved in the Choreography Activity that immediately precedes the Activity with the attached timer.

BPMNG092

From Table 11.7

(340)

For absolute timers (full time/date): All Participants would know the time. They all have to be involved in the Choreography Activity that immediately precedes the Activity with the attached timer.

BPMNG092