Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-1425 I can analyze the duration between two flow nodes in a diagram (process instance parts)
  3. OPT-1456

Highlighting part between flow nodes works with Boundary Events

XMLWordPrintable

    • Icon: Feature Part Feature Part
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 2.2.0
    • None
    • frontend
    • None

      AT:

      • When the process contains boundary events, and the user selects nodes, the highlighting considers boundary events as potential ways through the process

        This is the controller panel for Smart Panels app

            [OPT-1456] Highlighting part between flow nodes works with Boundary Events

            Omran Abazeed added a comment - - edited

            Works great, few comments:

            • if start node is: the start of a subprocess that has subprocess inside or the subprocess itself
              and the end node is a boundary event in the inner subprocess
              then
              the outer subprocess gets highlighted.
            • maybe move graph construction out of the getNodesBetween into another function.

            also, one thing that is not related to this ticket:

            • if a subprocess gets selected as a start node, the activities inside do not get highlighted.

            Omran Abazeed added a comment - - edited Works great, few comments: if start node is: the start of a subprocess that has subprocess inside or the subprocess itself and the end node is a boundary event in the inner subprocess then the outer subprocess gets highlighted. maybe move graph construction out of the getNodesBetween into another function. also, one thing that is not related to this ticket: if a subprocess gets selected as a start node, the activities inside do not get highlighted.

              Unassigned Unassigned
              sebastian.stamm Sebastian Stamm
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: