BPMN21 — “cancelActivity” is not an attribute of Activity

i) Chapter/Section 10.4. Page 241. Figure 10.69.
Class BoundaryEvent has attribute cancelActivity
(See Table 10.91, p. 266)

ii) Chapter/Section 10.4.4. Page 262. Table 10.90. Rows “Message”, “Timer”, “Escalation”, “Conditional”, “Signal”, “Multiple” and “Parallel Multiple”
It says:
“Note that if using this notation, the attribute cancelActivity of the Activity to which the Event is attached is implicitly set to true.”

or

“Note that if using this notation, the attribute cancelActivity of the Activity to which the Event is attached is implicitly set to false.”

iii) Chapter/Section 10.4.4. Page 266. Table 10.92.
This Table doesn’t contain o row for Parallel Multiple Event.

iv) Chapter/Section 13.4.3. Page 455. It says:
“For boundary Events, handling first consists of consuming the Event occurrence. If the cancelActivity attribute is
set, the Activity the Event is attached to is then cancelled (in case of a multi-instance, all its instances are cancelled); if
the attribute is not set, the Activity continues execution (only possible for Message, Signal, Timer, and Conditional
Events, not for Error Events). Execution then follows the Sequence Flow connected to the boundary Event.”

COMMENTS:

According to the meta-model cancelActivity is an attribute of BoundaryEvent, but in (ii) it is said that it is an attribute of Activity.

In (iii) a row is needed for Parallel Multiple.

In (iv) it is suggested that cancelActivity is optional. This is not the case, cancelActivity is mandatory: it is always set (to true or to false).

SUGGESTIONS:

In (ii)
“the attribute cancelActivity of the Activity” should be replaced by “the attribute cancelActivity of the BoundaryEvent” (14 times)

In (iii) add an additional row for Parallel Multiple.

In (iv)
“If the cancelActivity attribute is set,” should be replaced by “If the cancelActivity attribute is set to true,”

“if the attribute is not set” should be replaced by “if the attribute is set to false”