Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-3941

Variable to execution assignment is not correct after repeated tree compaction/expansion

    XMLWordPrintable

    Details

    • Type: Bug Report
    • Status: Closed
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.5.0, 7.5.0-alpha3
    • Component/s: engine
    • Labels:
      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

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              meyer Daniel Meyer
              Reporter:
              thorben.lindhauer Thorben Lindhauer
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: