-
Type: User story
-
Status: Resolved
-
Priority: Critical
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 3.30.0
-
Component/s: Studio Designer
-
Epic Link:
-
Tags:
-
Sprint:NOS 11.1.30 - 2020-03 2, NOS 11.1.31 - 2020-04 1
-
Story Points:5
As a Studio app builder, in a doctype / wf task layout I can choose a widget to drop instead of a mode for a property
AC
- Widget names are shown instead of view / edit
- Widgets are ordered alphabetically
- Widget use the following mapping:
- When I drag and drop a complex property, I have to choose for each sub-property which widget to use
- When I drag and drop a schema, I have to choose for each property which widget to use
- Analytics event is sent when I d&d a widget
- Category: Described according to
NXS-5742 - Event: Widget drag and drop
- Label: [Widget name]
- Value: 0 for something dropped from visual mode, 1 for code mode
(goal: usage stats and understand work flow)
- Category: Described according to
- Event is sent when a schema is d&d from the document tree
- Category: according to
NXS-5742 - Event: Schema drag and drop
- Label: Schema drag and drop (kept generic - no project specific info)
- Value: 0 for something dropped from visual mode, 1 for code mode
- Category: according to
- Event is sent when a schema is generated after user confirms mode for the properties
- Category: according to
NXS-5742 - Event: Schema generation
- Label: Schema generation - [number of properties in the schema]
- Value: 0 for something dropped from visual mode, 1 for code mode
- Category: according to
- is duplicated by
-
NXS-5776 Widget drag and drop in doc / wf layouts
- Resolved
-
NXS-5790 Default widget mapping
- Resolved
-
NXS-5791 Registry for widget mapping
- Resolved
- is related to
-
NXP-28827 Fix upload of multiple files with nuxeo-dropzone on 10.10
- Resolved
-
NXS-5866 Allow multiple templates using nuxeo-data-table for the same field type
- Resolved
-
NXS-5790 Default widget mapping
- Resolved
-
NXS-5791 Registry for widget mapping
- Resolved