Loading...

XML

Word

Printable

AT:

implemented according to BPMN spec
interrupting and non-interrupting
the boundary should be attached to a subprocess or a call activity
only one escalation boundary event on a scope that can catch the escalation event

is depended on by

CAM-4403 Escalation Boundary Event not cancel activity by default

CAM-4426 I can use multiple escalation boundary events with different escalationCode

CAM-4427 I can use multiple non-interrupting Escalation Event Subprocesses with the same EscalationCode

CAM-4428 Map output variables to super execution when throw an escalation event from a call activity

is related to

CAM-394 I can use a throwing escalation intermediate event

CAM-4392 I can read docs about escalation

(1 is related to)