Details
-
Story
-
Resolution: Done
-
High
-
None
-
None
-
Sprint 6
-
13
Description
New approach:
Relation will be deprecated and replaced by RelationList. It means that we will have to also update RelationList: a new input expectation.
Type | Description | Example |
---|---|---|
int / string | Number of content items allowed | 2 |
Scenarios
Design:
Please refer to the new guidelines:
- attached screenshots
Validations
The UI should validate the following scenario
- Required field
The validations will be as it is on v1 when the field loses focus.
Error | Message |
---|---|
Required field | %field_name% field is required |
Non-translatable field.
The field is disabled when this field is not translatable.
Warning message | Translation for %field_name% is disabled |
Attachments
Issue Links
- relates to
-
EZP-28409 As an Editor I want ezobjectrelationlist fieldtype to have configurable selection limit
- Closed
-
EZP-28426 As an UDW module integrator I would like to get content type info along with the content
- Closed
-
EZP-28438 As an UDW integrator I would like to get information about an amount of selected items in UDW
- Closed
- testing discovered
-
EZP-28497 RelationList field type issues
- Closed
- links to
1.
|
Implement the fieldtype UI | Closed | Unassigned | |
2.
|
Implement backend logic for handling RelationList field type | Closed | Unassigned |