[RECOMMEND-5] Scoring trait fields don't work on 6.2.x Created: 02/Jul/20  Updated: 24/Feb/21  Resolved: 24/Feb/21

Status: Closed
Project: Content Recommender
Component/s: None
Affects Version/s: 1.0.9
Fix Version/s: 2.0

Type: Bug Priority: Critical
Reporter: Edwin Guilbert Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia 6.2.1


Attachments: PNG File Screenshot 2020-07-02 at 16.31.29.png     PNG File Screenshot 2020-07-02 at 16.33.49.png    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

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  



 Comments   
Comment by Edwin Guilbert [ 02/Jul/20 ]

Updating the ruleField and valueField to 6.2 UI framework would require to migrate the current content app of score models to 6.2 framework.

Generated at Mon Feb 12 00:23:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.