[MGNLUI-6607] MultiFields can't be set as required Created: 10/Mar/21  Updated: 09/Jul/21  Resolved: 20/May/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.6
Fix Version/s: 6.2.9

Type: Bug Priority: Neutral
Reporter: Janine Kleeßen Assignee: Sang Ngo Huu
Resolution: Fixed Votes: 1
Labels: VN-Analysis, VN-Implementation
Remaining Estimate: Not Specified
Time Spent: 7d 5.45h
Original Estimate: Not Specified

Issue Links:
Problem/Incident
dependency
is depended upon by MGNLUI-3527 Item count validation for multi field Closed
documentation
to be documented by MGNLUI-6709 DOC: New properties for multi fields Closed
duplicate
is duplicated by MGNLUI-3527 Item count validation for multi field Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: formLevelValidation
Sprint: UI FW 27, UI FW 28
Story Points: 5

 Description   

Steps to reproduce

In Magnolia 6.2.6 is it not possible to set multifields as required.

Expected results

See required-symbol on multiField-label.

Can't save component without adding a multi field and get errormessage.

Actual results

Error Message on Definitionsapp: Property [required] not found in class [info.magnolia.ui.field.JcrMultiFieldDefinition], property is not assigned

 



 Comments   
Comment by Roman Kovařík [ 10/Mar/21 ]

Hi Janine Kleeßen,

 

would MGNLUI-3527 work for you?

 

Regards

Roman

Comment by Janine Kleeßen [ 10/Mar/21 ]

Hi Roman,

at the moment this doesn´t work for fields with new ui6 from $type: jcrMultiField

But this would be also nice if max/min is implemented.

 

Regards

Janine

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