Details
-
Sub-task
-
Resolution: Fixed
-
L3 - Default
-
None
Description
AT:
- a migration is added that maps the 2.2.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.2 => 2.4:
- TargetValue Variants are the same as 2.3 from
OPT-1842attached 23_settings.json (so already handled byOPT-1842) - alwaysShowTooltips: if visualization is heat set the value to alwaysShowRelative and alwaysShowAbsolute AND set the inverted value to hideRelativeValue and hideAbsoluteValue (to be handled as case #3 in migration script)
- columnOrder.processInstanceProps: rename to columnOrder.instanceProps (handled with
OPT-1866) - There is an additional variant: (to handle make all cases of
OPT-1842safe of targetValue.values == null)targetValue: {active: false} // without the values field
2.2 config structure:
{
alwaysShowTooltips: false
targetValue: {},
columnOrder: {
variables:[],
processInstanceProps:[]
},
xml: ''
}