-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
When there is a variable on a concurrent execution and we compact the execution tree, then the variable is moved to the scope execution.
However, the implementation works in a way that recreates the variable instance on the scope execution and removes it on the concurrent execution. This has the problem that the corresponding variable instance is recreated and receives a new ID. Existing history entries for that variable can no longer be safely related to that variable instance.
This is the controller panel for Smart Panels app
[CAM-5653] Variable identity is not stable during tree expansion/compaction
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Rank | New: Ranked higher |
Assignee | Original: Thorben Lindhauer [ thorben.lindhauer ] | New: Daniel Meyer [ meyer ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Remaining Estimate | New: 0 minutes [ 0 ] | |
Original Estimate | New: 0 minutes [ 0 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Fix Version/s | New: 7.5.0-alpha3 [ 14591 ] |
Workflow | Original: camunda BPM [ 38052 ] | New: Backup_camunda BPM [ 61311 ] |