-
Bug Report
-
Resolution: Won't Fix
-
L3 - Default
-
None
-
7.4.0
-
None
AT:
- attach multiple escalation boundary events to an activity / subprocess
- the boundary events should have a diffent escalation event definition / escalationCode
- an escalation boundary event without escalationCode (or empty escalationCode, or no ecalationRef) catch all escalation events
- an escalation boundary event with escalationCode have precedence over an escalation boundary event without escalationCode
- similar behavior to error propagation
- use the same behavior for escalation event subprocess