Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-2097 Flow Node Execution Status selection (running, completed, all)
  3. OPT-2222

Allow usertask/flownode control with execution state

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 2.5.0-alpha2, 2.5.0
    • None
    • backend
    • None

      AT:

      • report configuration has a new property flowNodeExecutionState that changes the evaluation result of reports grouped by flownode/usertasks to include running/completed/all usertasks/flownodes. Flownode frequency count is also affected by this change, i.e. selecting running only displays the count of running flownodes, etc.
      • default value of flowNodeExecutionState is set to all
      • running user tasks only influence the metrics if it makes sense (i.e. if the idleDurationTime is set)
      • the result returns a single value per flownode/usertask
      • the upgrade script includes the new configuration field and its initialization to the default value
      • the rest api documentation is updated

      OPT-2260 is the follow up ticket handling the scripted fields to calculate idleTime/workTime for usertasks, as well as duration for flownodes.

        This is the controller panel for Smart Panels app

              Unassigned Unassigned
              michael.wagner Michael
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: