Details
-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
Description
Cases:
- a single scope execution in an activity; set a local variable on that execution; fire a non-interrupting event (e.g. boundary or event subprocess); there are now to concurrent execution, however the local variable remains in the scope execution
- set a local variable on a concurrent, non-scope execution; compact the tree (i.e. the second-last concurrent execution ends); expand the tree (e.g. non-interrupting boundary event or event subprocess); the variable is now in the scope execution while it should be in the concurrent execution replacing the scope execution
Solution outline:
- make use of the IS_CONCURRENT_LOCAL_ flag in the variable instance table when expanding the tree
mgm-controller-panel
This is the controller panel for Smart Panels app
Attachments
Issue Links
- is depended on by
-
CAM-5602 Concurrent execution variables can get lost during migration
- Closed
- is related to
-
CAM-3832 Variables from inputMapping are created with reference to wrong scope
- Closed
-
CAM-2946 I can provide a scope reference when setting a variable
- Open
-
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
-
CAM-5154 Local execution variables are still present after joining parallel gateway
- Closed
-
CAM-3942 Refactor activity instance id assignment for leaf scope activities
- Closed
- links to