Start activities in closest common ancestor activity instance when moving tokens in process instance view

XMLWordPrintable

    • Type: Feature Request
    • Resolution: Fixed
    • Priority: L3 - Default
    • 7.13.0, 7.13.0-alpha1
    • Affects Version/s: None
    • Component/s: cockpit
    • None

      Context

      • On the process instance page
      • In the process instance modification view
      • When I move tokens on the diagram, so that it creates modification instructions

      Current behavior:

      • For every token,
        • a cancel instruction is generated by activity instance id
        • a start before instruction is generated

      Improved behavior:

      • For every token,
        • a cancel instruction is generated by activity instance id
        • a start before instruction is generated with the closest commen ancestor of the starting activity with the cancelling activity instance

      Example:

      • Consider the attached BPMN model
      • Assume activity Inner is active with the following activity instances:
        ProcInst : 1
          Outer SubProcess: 2
            Inner SubProcess: 3
              Inner: 4
        

      If I move the token from Inner to Outer, then the following instructions should be generated:

      1. Start before Inner with ancestor Outer SubProcess: 2
      2. Cancel Inner: 4

      Outer SubProcess: 2 is the activity instance that is the closes ancestor of Inner: 4 and that runs the closest ancestor activity of Outer.

      If we move multiple tokens, this logic should be applied to each one individually.

        This is the controller panel for Smart Panels app

          1. model.png
            28 kB
            Thorben Lindhauer
          2. bildsche.gif
            79 kB
            Karl-Josef Hilger
          3. subproc_example.bpmn
            6 kB
            Martin Stamm

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

                Created:
                Updated:
                Resolved: