Loading...

XML

Word

Printable

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

is depended on by

CAM-5602 Concurrent execution variables can get lost during migration

is related to

CAM-3832 Variables from inputMapping are created with reference to wrong scope

CAM-2946 I can provide a scope reference when setting a variable

CAM-5128 Copy Local Variables in Parallel Gateway to Parent Execution

CAM-5152 Local variable instances are duplicated in the history when execution tree compaction happens

CAM-5154 Local execution variables are still present after joining parallel gateway

CAM-3942 Refactor activity instance id assignment for leaf scope activities

links to

https://github.com/camunda/camunda-bpm-platform/issues/2143

(2 is related to, 1 links to)