-
Type:
Bug Report
-
Resolution: Won't Fix
-
Priority:
L2 - Critical
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
According to the Object Management Group, the BPMN norm on chaper 10-06-02, specify:
Multiple instances typically exist for Loop or Multi-Instance Sub-Processes. Each of these has its own instance of its Compensation Event Sub-Process, which has access to the specific snapshot data that was current at the time of completion of that particular instance. Triggering compensation for the Multi-Instance Sub-Process individually triggers compensation for all instances within the current scope. If compensation is specified via a boundary compensation handler, this boundary compensation handler also is invoked once for each instance of the Multi-Instance Sub-Process in the current scope.
Current implementation of camunda lack of triggering compensation for the others instances. Only the instance throwing the error / compensation is compensate. Others completed instances remain unchange and the others one in progress are stop without compensation.
This is the controller panel for Smart Panels app
- is related to
-
CAM-8341 Clarify: Multiple compensation is not performed when cancelling a multi-instance transaction
-
- Open
-
- links to
