Details

    • Type: Sub-task
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4.0, 2.4.0-alpha2
    • Component/s: backend
    • Labels:
      None

      Description

      AT:

      • a migration is added that maps the 2.1.0 report configuration structure that might be still present in 2.3 reports 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
        • xml, columnOrder
      • incompatible fields are mapped as described below

      Mapping 2.1 => 2.4:

      1. TargetValue Variants are Variant 1, Variant 2, Variant 4 from OPT-1842 attached 23_settings.json (so already handled by OPT-1842)
      2. columnOrder.processInstanceProps: rename to columnOrder.instanceProps (handle as case #4 in migration script)
      3. There are two additional variants:
        1. no targetValue.values (covered by OPT-1843)
          targetValue: {active: false} // without the values field
          
        2. empty targetValue object (e.g. on raw data reports) => already handled by null-safe mapping, just add tests that it get's default config for this case
          targetValue: {}
          

      2.2 config structure:

      {
        targetValue: {},
        columnOrder: {
          variables:[],
          processInstanceProps:[]
        },
        xml: ''
      }
      

        Activity

        There are no comments yet on this issue.

          People

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

            Dates

            • Created:
              Updated:
              Resolved: