[MGNLPN-716] Supporting a way to define Trait values coming from JCR Created: 16/Jun/23  Updated: 13/Sep/23

Status: Open
Project: Magnolia Personalization
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Medium
Reporter: Tobias Kerschbaum Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
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)
Date of First Response:
Epic Link: AuthorX Support
Team: AuthorX

 Description   

Context / Use Cases

The following requirement arose during the integration of BSI as a CDP solution: we need help solving with Magnolia standard functionality.

The starting point was that we would like the list of selectable segments (just a list of Strings) for the BSI cross-selling recommendation from the category app. Although this worked technically, it brought a decisive disadvantage. The NameAndValueVoter class uses the UUID of the category for comparison. This would mean we would have to set a Magnolia UUID in the cookie from BSI, which is not optimal for security reasons.

A possible solution would be to create a possibility in the trait data source configuration to configure an id property used for comparison in the voter.



 Comments   
Comment by Tobias Kerschbaum [ 28/Jul/23 ]

Hey viet.nguyen,
yes, I think this describes the same thing. I was not aware of this ticket. 

Generated at Mon Feb 12 06:40:22 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.