In Studio using 10.x
- Create a schema that has a complex property (e.g. address)
- Create subfields for the complex property (e.g. number / street / etc)
- Add the required constraint on the complex field
=> means users needs to enter at least one address, and we don't care if values are empty
- Studio Designer will scaffold the subfields individually (number, street etc)
- Web UI has no way to tell a user that if user doesn't fill something in at least one of the fields of the address it will cause an error
Currently best solution we have is to make every field of the complex shown as required, but it doesn't really make sense: means that all values need to be set when it's not the case.
=> We need a UX pattern that can make it clear to the user that at least one of the fields is required
=> How should we do that?
- is required by
-
NXS-4540 Handle required constraint in Designer for nuxeo-data-table element
- Open