Uploaded image for project: 'Magnolia Personalization'
  1. Magnolia Personalization
  2. MGNLPN-716

Supporting a way to define Trait values coming from JCR

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Unresolved
    • Medium
    • None
    • None
    • None
    • None

    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.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              tobias.kerschbaum Tobias Kerschbaum
              AuthorX
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:

                Checklists

                  Task DoD