[MGNLPN-267] Disable component-level personalization if a page already has page variants Created: 27/May/16  Updated: 11/Oct/16  Resolved: 23/Jun/16

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

Type: Story Priority: Neutral
Reporter: Antti Hietala Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLPN-272 Disable page-level personalization if... Closed
relation
is related to MGNLPN-317 It is possible to add component varia... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: Component P13N
Sprint: Kromeriz 49
Story Points: 2

 Description   

Page and component personalization are mutually exclusive. You can either personalize a page or its components but not both.

This restriction helps avoid situations where:

  • Component variants are never resolved because they reside under a page variant that was not resolved.
  • The user creates complicated and confusing page+components personalization setups.

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