-
Bug
-
Resolution: Fixed
-
Critical
-
1.0.9
-
Magnolia 6.2.1
Due to lack of compatibility of personalization traits in 6.2.1 (latest version at the moment) the ruleFIeld stores the id of the scoreModel instead of its name (See ). The ruleField is a compositeFIeld containing 2 internal fields, only the scoreModel linkField is broken, the scoreThreshold textField works just fine.
A workaround is needed for using scoring models with personalization which is one of the main selling points of the module.
Note: The value field is broken for the same root cause (lack of compatibility of personalization traits on 6.2). See
Acceptance criteria