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

Start Before MI Activity with Non MI-Body ancestor creates empty MI-Body

    XMLWordPrintable

    Details

    • Type: Bug Report
    • Status: Closed
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: 7.3.0-alpha4
    • Fix Version/s: 7.3.0
    • Component/s: engine
    • Labels:
      None

      Description

      Reproduce:

      • Have a process instance with a multi-instance activity, but no running activity instances of the MI activity
      • Use Cockpit to start before the activity (not the MI body)
      • Apply modification
      • applies only to multi-instance tasks that are not a scope (i.e. not mi subprocesses)

      Expected:

      • new MI body is started (because none exist to hold the new MI activity)
      • new MI activity is started in the newly created MI body

      Observed:

      • new MI body is started
      • no new MI activity is started (or is not visible), however, MI body variable numberOfInstances is 1

      Reason:

      • modification sets the activity instance id of the mi body scope execution to null; this leads to a wrong activity instance tree

      Workaround:

      • start the activity again in a separate modification and select the previously created MI body as ancestor
      • now the numberOfInstances is 2 (even if there is only one instance), so you might have to set it back to one manually

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              matthijs.burke Matthijs Burke
              Reporter:
              sebastian.stamm Sebastian Stamm
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: