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

Adjust columns configuration for raw data report

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Fixed
    • L3 - Default
    • 3.11.0-alpha4
    • None
    • None

    Description

      User Problem:

      Context:

      • The raw data report allows the configuration of columns included in the report.
      • For the Machine Learning User Case, we added additional columns (e.g. Count)

      Problem:

      • The UX to disable NOT needed fields, e.g. if you are NOT doing Machine Learning, is time-consuming.

      User Story:

      • As a user of Optimize, I would like to have an improved way to exclude a certain columns from the raw data report. This allows me to build a report more quickly.

      Solution Ideas

      • Group all "count columns" in a group called "Counts" similar to the grouping of variables
      • Set the default status for all columns included in collapsed groups to "disabled" (this is not done, see the comment below). This results in the default report only containing the main process columns that are not grouped by "Counts" / "Variables" / "Flow Node Duration"

      Testing Notes:

      the columns Incidents CountOpen Incidents Count and Executed User Tasks Count are now grouped together into counts group and column names are now called: Count: incidentsCount: openIncidents and Count: userTasks.

      In the report configuration popover (when you click on the cog button in top right) there is new collapsible section called Counts which groups the incidentsopenIncidents and userTasks together

      All the functionalities like column rearrangement and disabling columns should work as before

       

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                tobias.conz Tobias Conz
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce