[MGNLPN-572] Self-service request traits Created: 26/Aug/21 Updated: 26/Aug/22 |
|
| Status: | Open |
| Project: | Magnolia Personalization |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| 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: | AuthorX improvements | ||||||||
| Team: | |||||||||
| Description |
|
As a (non-developer) marketer I can create custom request-based traits "ad-hoc" so that I can perform personalization without needing a developer. Context: We have recently added the capability for developers to easily create request traits for specific hard-coded "names"in a header, cookie or requestParameter. https://jira.magnolia-cms.com/browse/MGNLPN-557 But a marketer cannot do this as gthey typically do not work with definitions.
|
| Comments |
| Comment by Christopher Zimmermann [ 26/Aug/21 ] |
|
Idea how the definition could work A new trait... CustomRequestTrait or AdhocRequestTrait. It would be preinstalled OOTB by the p13n module. When marketer adds the trait, they get 3 fields:
The trait matches when the request has a property of "Name" which is the value of "Value".
Alternatively - we could introduce 3 new traits - AdhocCookie, AdhocHeader, AdhocRequestParameter |
| Comment by Chris Jennings [ 26/Aug/21 ] |
|
This will require work on the Preview App as it currently does not support composite fields and entering 3 fields or selecting "adHocHeader" and entering 2 fields will not work. I know this from this RECOMMEND-7 but have not seen a ticket requesting UI support for composite fields in the app. |