Details
-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
Description
Steps to reproduce:
1) deploy a process foo with a multi instance call activity
2) deploy another process bar that contains a user task (bar is called by foo)
3) start a process instance of foo
4) perform the following modification:
runtimeService.createModification("bar") .startAfterActivity("userTask") .cancelAllForActivity("userTask") .processInstanceIds(...) .execute();
Observed Behavior:
The calling process instance of foo is still active.
Expected Behavior:
The calling process instance of foo is cancelled.
Hints:
- see failing test cases [1] and [2]
[1]: https://github.com/camunda/camunda-bpm-platform/blob/6056ad9aa8047e1477e20cbcec75a1b497eaceb4/engine/src/test/java/org/camunda/bpm/engine/test/api/runtime/ProcessInstanceModificationSubProcessTest.java#L499-L543
[2]: https://github.com/camunda/camunda-bpm-platform/blob/6056ad9aa8047e1477e20cbcec75a1b497eaceb4/engine/src/test/java/org/camunda/bpm/engine/test/api/runtime/ProcessInstanceModificationSubProcessTest.java#L545-L594
mgm-controller-panel
This is the controller panel for Smart Panels app
Attachments
Issue Links
- is related to
-
CAM-8949 Cancelling a called process instance leaves concurrent execution in calling instance
-
- Closed
-