Steps to reproduce:
- start a process instance of the as screenshot attached process, the execution tree looks as follows:
PI ^ | +------------------- e1[activityId: A] | +------------------- e2[activityId: B] | +------------------- e3[activityId: C]
- set a local execution variable on user task B: runtimeService.setVariableLocal(B, "foo", "bar");
- complete user task A: taskService.complete(A);
- complete user task B: taskService.complete(B);
- the joining parallel gateway is executed
- the resulting execution tree looks as follows:
PI ^ | +------------------- e2[activityId: D] | +------------------- e3[activityId: C]
Problem:
The variable foo is still set as local variable of the execution e2.
Expected behavior:
- the local variable foo is deleted after joining parallel gateway.
Hint:
The joining parallel gateway is left by the execution e2.
See failing test case: https://github.com/camunda/camunda-bpm-platform/commit/5a069dc35ea533c1d04de1d04ec5ddb45f8f3c83
This is the controller panel for Smart Panels app
- is related to
-
CAM-3941 Variable to execution assignment is not correct after repeated tree compaction/expansion
- Closed
-
CAM-5128 Copy Local Variables in Parallel Gateway to Parent Execution
- Closed
-
CAM-5152 Local variable instances are duplicated in the history when execution tree compaction happens
- Closed