Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-1862 Change configuration structure of combined report
  3. OPT-1921

Store report color of combined reports in report array instead of configuration

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Fixed
    • L3 - Default
    • 2.4.0-alpha2, 2.4.0
    • None
    • frontend
    • None

    Description

      Context:
      The structure of the data field of the combined report looks currently like the following:

      "data" : {
          "configuration": {}, // all possible configurations 
          "visualization": "bar",
          "reportIds": [
            "ReportA", "ReportB", ... // a list of report ids
          ]
        }
      

      This has two problems:

      • In the configuration we have a "reportColor": [] field that contains the color for each report that belongs the combined report. If one report is deleted, we need to make sure that this is also automatically done for the color to keep the configuration consistent.
      • The combined report configuration contains a lot of configuration properties that it just doesn't need.

      Hence, we should rather have a structure like this following:

      "data" : {
          "configuration": {}, // only configurations that belong to the combined setup e.g. the target value for combined reports
          "visualization": "bar",
          "reports": [
            {
               "id": "ReportA", 
                "color": "blue", 
             },
             {
               "id": "ReportB", 
                "color": "red", 
             },...]
        }
      

      AT:

      • the combined report data restructure has been changed, such that the report color is not stored in the configuration field any longer
      • the rest API documentation has been adjusted accordingly

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                johannes.heinemann Johannes
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce