Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-1766 Migrate report configuration structure
  3. OPT-1842

Migrate report configuration from 2.3.0 to 2.4.0 structure

    XMLWordPrintable

Details

    Description

      AT:

      • a migration is added that maps the 2.3.0 report configuration structure to the explicitly modeled 2.4 structure
      • 2.4.0 configuration property defaults are kept if there was no existing configuration
      • compatible fields are taken over 1:1 if present in existing configuration
        • showInstanceCount, pointMarkers, precision, hideAbsoluteValue, hideRelativeValue, xLabel, yLabel, xml, columnOrder
      • incompatible fields are mapped as described below

      Mapping 2.3 => 2.4:
      SingleProcessReport:

      • color:
        • convert single array element into string (#1)
      • hideRelativeValue
        • if visualization is heatmap, store inverted value as alwaysShowRelative (#2.1)
      • hideAbsoluteValue
        • if visualization is heatmap, store inverted value as alwaysShowAbsolute (#2.1)
      • targetValue.values
        • if visualization is heat and view is flow node duration: (#2.1.1)
          • store targetValue.values as heatmapTargetValue.values
          • use targetValue.active as heatmapTargetValue.active
        • if report visualization is line or bar and view property is frequency: (#2.2.1)
          • store target as value and isBelow in countChart
        • if report visualization is line or bar and view property is duration: (#2.2.2 )
          • store target as value, dateFormat as unit and isBelow as durationChart
        • if report is Count PI frequency grouped by none: (#2.3)
          • store baseline and target in countProgress
        • if report is PI Duration grouped by none: (#2.4)
          • store baseline and target in durationProgress

      CombinedReport:

      • color:
        • if it's a combined report, rename property to reportColors => won't do as we will refactor color location again with OPT-1862
      • targetValue.values
        • if report visualization is line or bar or number and view property is frequency:* (#1.1)
          • store target as value and isBelow in countChart
        • if report visualization is line or bar or number and view property is duration:* (#1.2)
          • store target as value, dateFormat as unit and isBelow as durationChart

      check the view property of the first report in the combined set

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          1. data.zip
            608 kB
          2. 23_settings.json
            0.8 kB

          Issue Links

            Activity

              People

                Unassigned Unassigned
                sebastian.bathke Sebastian Bathke
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce