[MGNLPN-117] Develop trait for gender if a visitor stored in user profile Created: 15/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: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Description |
|
This mockup describes a UI for a trait to select visitors by their gender. It allows to distinguish between male and female visitors, as well as those where the gender is not set or unknown. The field offers to either search for a value and then suggests matches. Or it works as a combobox offering to pick a single value out of a small set of defined values. In case the trait field is used in a rule builder (e.g. in a segment definition), its order within the rule may be changed using the arrow keys shown when the field has the focus. The UI described by the mockups attached to this issue also acts as an example for a trait offering a small set of values. The trait value is either not set or set to one of the defined values. |
| Comments |
| Comment by Andreas Weder [ 15/May/14 ] |
|
Added clickable PDF prototype. |