-
Story
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
-
Yes
-
Empty show more show less
-
Features 8
-
5
User story:
As a Business Analyst / Developer, I want to specify a limited set of options for the value of the property and the UI will enforce that the user can only supply one of those options.
Acceptance criteria:
- Developer can supply a set of options values
- Developer can supply a set of option labels.
- Developer can still specify the type as Integer, String or any other "raw type".
- UI will show a select box control by default.
- Developer can specify to use an alternative control (such as "radio button" group) by overriding the "class" or "fieldType" property in the app descriptor.
- Criteria
Model suggestion:
model: - name: 'firstName' - name: 'category' type: String options: - value: bullet label: Bullet - value: ordered label: Ordered - value: inline label: Inline
Note: "label" is optional.
- is causing
-
MGNLUI-5260 multi-reference properties are broken - storing paths instead of UUID
- Closed
- is depended upon by
-
MGNLCT-118 DOC: Describe Select Box - contenttype field with limited options
- Closed
- relates to
-
CFGUI-99 Defining a YAML list directly through a custom property creates null nodes
- Open
-
MGNLCT-132 Type is ignored in Select box and values fallback to String
- Accepted
-
MGNLCT-127 DOC: It is possible to define a list of options for a contentType property, which then results in a select box in the editing dialog
- Closed
- supersedes
-
MGNLCT-64 Contenttype field with limited options - Select Box
- Closed
- mentioned in
-
Page Loading...