[MGNLTAGS-87] suggestion to move model logic into ftl Created: 10/Nov/21 Updated: 26/Aug/22 |
|
| Status: | Open |
| Project: | Marketing Tags Manager |
| Component/s: | None |
| Affects Version/s: | 1.4.3 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Neutral |
| Reporter: | Tomáš Gregovský | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Epic Link: | AuthorX improvements | ||||||||
| Team: | |||||||||
| Description |
|
Because marketing tags doesn't seems to be working properly for page variants (personalised pages). (At least this was our issue on corp-web with m6.2.10 - tag which has selected specific page variant where it should be rendered, then it wasn't.). So I decided to rewrite all logic from java model into ftl. Advantage: it could be easier than for clients to do more adjustments into marketing tags logic. Attached my ftl code. PS. didn't touch cookie part - not sure about how that one should works.
|