Historic instances of MI Loop counter and element variable are assigned to MI body activity instance

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Unresolved
    • Priority: L3 - Default
    • None
    • Affects Version/s: 7.4.0, 7.5.0, 7.6.0
    • Component/s: engine
    • None

      See current.png for the current situation and expected.png for the way it should be.

      The current situation is bad, because:

      • the variables do not belong to the MI body scope; they are not visible in that scope
      • it is not possible to distinguish which variable pair belongs to which MI instance based on activity instance IDs

      Also check for historic details.

      Forum post: https://forum.camunda.org/t/historyservice-reporting-issue/1567

        This is the controller panel for Smart Panels app

          1. expected.PNG
            expected.PNG
            28 kB
          2. current.PNG
            current.PNG
            28 kB

              Assignee:
              Unassigned
              Reporter:
              Thorben Lindhauer
              Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: