[MGNLPN-522] Cannot Create Cookie Trait Using Composite Fields on 6.x Created: 11/Feb/21  Updated: 18/Feb/21  Resolved: 18/Feb/21

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

Type: Bug Priority: Neutral
Reporter: Julian Nodarse Assignee: Unassigned
Resolution: Not an issue Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
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
Date of First Response:
Epic Link: Migrate apps to new UI framework

 Description   

I have attached a sample config for a cookie trait composed of a composite field.
All you have to do is import this into modules/personalization-traits/traits/cookies/ruleField and use one of the two paths below.

Path 1
Open Segments App
Click “Add Segment”
On the “Traits” tab, click “Add”
Select “Query Parameter” (this is the name of the attached trait)
Error “Failed to create multi field entry”

Path 2
Select a page variant
Select “Choose Audience”
Add a trait and select “Query Parameter”
Error “Failed to create multi field entry”

Expected Results
The trait can be selected and created within a segment without problems.

Actual Results
you get an error when selecting the trait

Additional Notes

  • I tried with info.magnolia.ui.form.field.transformer.multi.DelegatingMultiValueFieldTransformer and
    info.magnolia.ui.form.field.transformer.composite.DelegatingCompositeFieldTransformer just to test them out and still got same error.
  • This was tested on 6.2.6 and 5.7.7. Failed on 6.2.6. For 5.7.7, I was able to import the config, create a segment with the trait and even choose an audience without problems.


 Comments   
Comment by Thomas Duffey [ 16/Feb/21 ]

Update: This might not be a bug, or at least not the one you'd think it would be. Please see comment here: https://jira.magnolia-cms.com/browse/SUPPORT-12575?focusedCommentId=250960&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-250960

Comment by Šimon Demočko [ 18/Feb/21 ]

Customer resolved the situation on their end.

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