Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-3939

Improve handling of running instances in endDate reports

    XMLWordPrintable

Details

    • Task
    • Status: Done
    • L3 - Default
    • Resolution: Done
    • None
    • 3.1.0
    • backend
    • None
    • Not defined

    Description

      Context:

      While working on OPT-3787, I noticed that the baseQuery for endDateReports does not exclude instances that do not have an endDate. Since the baseQuery is used to evaluate the combined instanceCount, this can lead to confusion as running instances are technically evaluated (hence count towards the combined instanceCount), but don't show up in the result of endDate reports.
      In variable reports for example, we have a "missing" value bucket to account for those instances.
      We should implement a solution to avoid any confusion here - either add some sort of "missing/still running" bucket to endDate reports or add a filter to the baseQuery of those reports to exclude these instances from being evaluated in the first place.

       

      AT:

      • a solution is implemented that ensures that the instance count of endDate reports is coherent with the result of the baseQuery of endDate reports, ensuring combined instance counts don't create unnecessary confusion

       

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                helene.waechtler Helene Waechtler
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce