[MGNLUI-5340] Implement special multi-value field bound to an array/list Created: 23/Aug/19  Updated: 25/Aug/20  Resolved: 24/Aug/20

Status: Closed
Project: Magnolia UI
Component/s: framework
Affects Version/s: 6.1
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Federico Grilli Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
documentation
to be documented by MGNLUI-5333 DOC: Valid Transformer implementation... Closed
duplicate
duplicates MGNLUI-6151 Multi field not saving the data as in M5 Closed
is duplicated by MGNLUI-5639 Multifield for JCR multivalue property Closed
relation
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: UI framework: forms, dialogs, content editing

 Description   

Assume a customer wants to migrate their M5 app to M6 and its new uI framework.

They used a multifield with a transformer storing data as a multivalue property https://documentation.magnolia-cms.com/display/DOCS61/Transforming+field+values#Transformingfieldvalues-MultiValueTransformer.

M6 currently offers a Multifield (a complex field holding a form potentially holding more complex fields) which ends up saved as a structure like that of https://documentation.magnolia-cms.com/display/DOCS61/Transforming+field+values#Transformingfieldvalues-DelegatingMultiValueTransformer

We should not force a data migration to the expected data structure of the new multifield, rather implement a special multi-value field, that would be bound to an array/list on the presentation side. It would look like a bunch of components of same type, and would write the data to the multivalue property.



 Comments   
Comment by Leah Staniorski [ 10/Feb/20 ]

2 (improvement) + 5 (two support tickets one SLA 3 one SLA0 partner) + 3 (could benefit others) + 3 (average) + 5 (latest version) + 0 (no threat) + 0 (no blocker) = 18

Comment by Roman Kovařík [ 19/Aug/20 ]

Anything still missing in jcrMultiValueField?

Comment by Federico Grilli [ 20/Aug/20 ]

Apparently jcrMultiValueField covers this case - I tested it with personalization on 6.2.2 https://git.magnolia-cms.com/projects/ENTERPRISE/repos/personalization/browse/magnolia-personalization-pages/src/main/resources/personalization-pages/dialogs/chooseAudience.yaml

Comment by Roman Kovařík [ 25/Aug/20 ]

https://documentation.magnolia-cms.com/display/DOCS62/Multi+field#Multifield-JCRmulti-valuefield

Generated at Mon Feb 12 09:25:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.