[MGNLPN-283] Create a component variant as a copy of the parent component Created: 31/May/16 Updated: 13/Jun/16 Resolved: 13/Jun/16 |
|
| Status: | Closed |
| Project: | Magnolia Personalization |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Date of First Response: | |
| Epic Link: | Component P13N |
| Story Points: | 0 |
| Description |
|
In phase 1 of component personalization we create component variants by copying the parent component (original), just like we do with page variants. In a subsequent release we create page and component variants by referencing the parent item (referential variant management). When referential variant management is available, support both copied and referenced variants so that users don't have to migrate their old (copied) variants. |
| Comments |
| Comment by Jan Haderka [ 13/Jun/16 ] |
|
Functionality is already present since P13N 1.0 and was verified to be working correctly when enabled on components. |