[MGNLPRIV-47] Cookie field inside a multivalue field has save issues Created: 30/Jan/19  Updated: 06/Feb/19  Resolved: 06/Feb/19

Status: Closed
Project: Privacy
Component/s: None
Affects Version/s: 1.1
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File cookies.png    
Issue Links:
duplicate
duplicates MGNLPRIV-52 Select field inside of multivalue doe... Closed
relation
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

It the marketing tags app we have a cookie field wrapped in a multivalue field. When you try and add one value to the list the save does not work. If you try and add more than one value the save works.

In the end there is a corner case of adding one value. It seems to only be when using the cookie field inside.

The configuration is here: /modules/marketing-tags/apps/marketing-tags/subApps/detail/editor/form/tabs/tag-cookies/fields/cookies/field@class



 Comments   
Comment by Richard Gange [ 30/Jan/19 ]

Update: Another weird scenario. If I open a tag that does not already have a cookie attached and I add 2 cookies only one is saved.

Comment by Florian Reiser [ 30/Jan/19 ]

The field saves the cookies value (not its name or id). This is a major problem with regards to marketing tags because the tag is not handled correctly. (Renders always)

Comment by Richard Gange [ 30/Jan/19 ]

For some reason I still don't see that behavior. If I go to Eloqua and add 2 cookies I get this:

Which are the IDs of those cookies.

Generated at Mon Feb 12 10:31:08 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.