[MGNLPN-103] Develop trait to select segments Created: 09/May/14  Updated: 11/Mar/21  Resolved: 11/Mar/21

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

Type: Task Priority: Critical
Reporter: Andreas Weder Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File S01 - Choose audience 1.png     PNG File S02 - Restrict by segment 1 - pick 1.png     PNG File S02 - Restrict by segment 1 - pick 2.png     PNG File S02 - Restrict by segment 2 - two segs.png     PNG File S02 - Restrict by segment 3 - one seg.png     PNG File S02 - Restrict by segment 4 - pick 1.png     PNG File S02 - Restrict by segment 4 - pick 2.png     File Trait for selecting segments.pdf     PNG File Visual design of segment def.png    
Issue Links:
relation
is related to MGNLPN-102 Develop trait to select locations Closed
is related to MGNLPN-110 Develop trait to specify visit date Closed
is related to MGNLPN-114 Develop trait to target a specific ty... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

This mockup describes a UI for a trait to select one or more segments from the set of defined segments in the Segments app. It only allows to pick segments, not to search for them, but this is not mandatory, actually: if the control is easily capable of auto-suggesting matches for segment names typed into one of its input fields, feel free to offer this. You should then model the search part after the trait UI for selecting locations.

This mockup does NOT use our basic rule builder: it assumes that its values are always "OR" connected (hence the term "any of" next to the field's label). When a rule builder is available used, just replace that label with a combobox offering "any" (OR) or "all" (AND) to concatenate terms (see visual design example attach here as well).

The UI of a trait is largely depending on the trait itself, but it also has some aspects it shares with other traits. The UI described here acts as a good example of a trait supporting multiple values, but only offers to pick, not search for them - other traits with the same requirement should be modeled after it.



 Comments   
Comment by Andreas Weder [ 09/May/14 ]

Attached clickable PDF prototype for experiencing the field.

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