Trait storage differs between Magnolia 5.7 and Magnolia 6.2
(MGNLPN-663)
|
|
| Status: | Closed |
| Project: | Magnolia Personalization |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Documentation Task | Priority: | Neutral |
| Reporter: | Adrian Brooks | Assignee: | Adrian Brooks |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Sprint: | AuthX 15, AuthX 16 |
| Team: |
| Description |
|
Problem: The explanations here about transformer classes don't mention that for personalisation the ruleField is different - it is wrapped implicitly inside MultiField, thus its definition should start with a compositeField as described here. Fix: Add a note in the Personalization transformers section of the transformer classes page with a link to the "Creating custom traits with complex fields" page. |