Details
-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
Description
Steps to reproduce:
- start a process instance of the as screenshot attached process
- set a local execution variable on user task B: runtimeService.setVariableLocal(B, "foo", "bar");
- complete user task A: taskService.complete(A);
- the engine performs internally an execution tree compaction
Problem:
In the history there are two historic variable instances of variable foo.
Expected behavior:
- the local variables are still present
- the corresponding historic variable instance is updated and there does not exist a second historic variable instance for the variable foo
Hint:
The local variables are copied from the child execution to the parent execution.
See failing test cases: https://github.com/camunda/camunda-bpm-platform/commit/9c85f156c058dcc4ab42f79c6dca546700178a26
mgm-controller-panel
This is the controller panel for Smart Panels app
Attachments
Issue Links
- 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-5154 Local execution variables are still present after joining parallel gateway
- Closed
-
CAM-5653 Variable identity is not stable during tree expansion/compaction
- Closed