As a marketing manager, I create a localized campaign page variant for every major market area, then specify manually for every variant to which visitors it should only show. (MGNLPN-1)

[MGNLPN-6] Create first version of VariantManager Created: 11/Feb/14  Updated: 27/Feb/14  Resolved: 13/Feb/14

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

Type: Sub-task Priority: Neutral
Reporter: Philip Mundt Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLPN-7 Create P13nNodeWrapper Closed
dependency
is depended upon by MGNLPN-10 Create and add "CreateVariantAction" ... Closed
Template:
Sprint: 5.3 Preparation 2

 Description   

First version of the variant manager should create a full copy of the master page (parent page).

Mixin definition has to be done too:

Properties:

  • mgnl:variationOf: single-valued reference to parent (mandatory)
  • mgnl:assignedSegments: multi-valued String
    Subnode:
  • mgnl:constraintSet: sub node of constraint set

Ideally, we need to ensure that only one of mgnl:assignedSegments or mgnl:constraintSet is defined, but I don't think that one can enforce that sort of rule in a nodetype/mixin definition (TBV)


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