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

Local execution variables are still present after joining parallel gateway

XMLWordPrintable

      Steps to reproduce:

      1. start a process instance of the as screenshot attached process, the execution tree looks as follows:
         PI
         ^
         |
         +------------------- e1[activityId: A]
         |
         +------------------- e2[activityId: B]
         |
         +------------------- e3[activityId: C]
        
      2. set a local execution variable on user task B: runtimeService.setVariableLocal(B, "foo", "bar");
      3. complete user task A: taskService.complete(A);
      4. complete user task B: taskService.complete(B);
      5. the joining parallel gateway is executed
      6. the resulting execution tree looks as follows:
         PI
         ^
         |
         +------------------- e2[activityId: D]
         |
         +------------------- e3[activityId: C]
        

      Problem:
      The variable foo is still set as local variable of the execution e2.

      Expected behavior:

      • the local variable foo is deleted after joining parallel gateway.

      Hint:
      The joining parallel gateway is left by the execution e2.
      See failing test case: https://github.com/camunda/camunda-bpm-platform/commit/5a069dc35ea533c1d04de1d04ec5ddb45f8f3c83

        This is the controller panel for Smart Panels app

              roman.smirnov Roman Smirnov
              roman.smirnov Roman Smirnov
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: