[MGNLPN-102] Develop trait to select locations 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 S03 - Restrict by location 1.png     PNG File S03 - Restrict by location 2 - search 1.png     PNG File S03 - Restrict by location 2 - search 2.png     PNG File S03 - Restrict by location 3 - one loc.png     PNG File S03 - Restrict by location 4 - add 1.png     PNG File S03 - Restrict by location 5 - pick 1.png     PNG File S03 - Restrict by location 6 - two locs.png     File Trait for selecting locations V3.pdf    
Issue Links:
relation
is related to MGNLPN-103 Develop trait to select segments 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 a location from a pre-defined, hierarchically organized list of locations. It allows to either search for a location and then suggest matches, or to directly pick a location from the set of defined locations managed by a content app.

The mockup assumes that the most basic location is a "country", which are grouped into "regions". Both "countries" and "regions" are possible selections, and they can be mixed and matched in a single location definition. Additional hierarchy levels (e.g. "continents", "cities" or "marketing areas") could exist in addition and would be selectable as well.

This mockup does NOT use our basic rule builder: it assumes that its values are always "OR" connected (hence the use of the term "any" in the introduction text of the field). When a rule builder would be used, a combobox would allow to require "any" (OR) or "all" (AND) locations to be matching.

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 - other traits with the same requirement should be modeled after it.



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

Attached clickable PDF prototype for playing with the control.

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