[MGNLPN-156] Enable setting AND/OR operand in trait aggregator Created: 10/Jun/14  Updated: 17/Jun/14  Resolved: 16/Jun/14

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

Type: New Feature Priority: Critical
Reporter: Mikaël Geljić Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: traitchooser
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Reworked Choose audience dialog.png    
Issue Links:
dependency
depends upon MGNLUI-2995 MultiField shouldn't rely on index/co... Closed
is depended upon by MGNLPN-157 Update sample segments to represent e... Closed
Template:
Acceptance criteria:
Empty
Epic Link: Personalisation

 Description   
  • + rework layout of the choose audience dialog (split audience vs. additional traits fields, add introductory labels)
  • support of the AND/OR operand in ruleSet (VoterSet) is already functional.


 Comments   
Comment by Mikaël Geljić [ 11/Jun/14 ]

https://git.magnolia-cms.com/gitweb/?p=enterprise/personalization.git;a=shortlog;h=refs/heads/MGNLPN-156-mge

Comment by Mikaël Geljić [ 11/Jun/14 ]

Ouch, hard-coding introductory Labels inside SegmentationMultiField or TraitAggregatorMultiField actually breaks the inherited logic from MultiField:
see the deleteButton click listener at MultiField#createEntryComponent().new ClickListener() {...}, it removes properties based on position in the layout!!!

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