Loading...

XML

Word

Printable

Type: Feature Request
Resolution: Fixed
Priority: L3 - Default
Fix Version/s: 7.4.0, 7.4.0-alpha2
Affects Version/s: None
Component/s: engine
Labels:
None

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

This is the controller panel for Smart Panels app

is depended on by

CAM-4403 Escalation Boundary Event not cancel activity by default

Closed

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

Closed

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

Closed

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

Closed

is related to

CAM-394 I can use a throwing escalation intermediate event

Closed

CAM-4392 I can read docs about escalation

Closed

(1 is related to)

Assignee:: Roman Smirnov
Reporter:: Robert Gimbel
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: 11/Mar/13 1:51 PM
Updated:: 18/May/16 11:26 AM
Resolved:: 13/Aug/15 10:06 AM