]
Liz Clayton commented on DROOLS-2787:
-------------------------------------
[~tirelli] [~manstis] [~karreiro] I'm documenting the info gleaned from the call
today:
1. Modal dialog options need to cover the following cases:
Select only a "default" type (no need to name the data type because it's a
default type.)
# The requires only a selection mechanism for selecting a "default" type.
2. Create a custom type - provide a "custom" name and select either a default
type or a pre-existing custom type.
3. This requires an input field for providing a custom name and a means to select from
one of two types: existing custom or default.
* Create a structured type - type with children types, the whole works plus nested.
In addition to the use cases above, preference/requirement for the design offering the
following:
* All types available through modal dialog (including simple default type.)
* Tree or tree/table to represent nested hierarchy within Structured type.
* Inline editing where possible.
If I didn't capture this correctly please let me know, thanks. I plan to do A/B
click-thru - one example using the tree-table, one without basically.
"Data Type" tree-grid table interactions.
-----------------------------------------
Key: DROOLS-2787
URL:
https://issues.jboss.org/browse/DROOLS-2787
Project: Drools
Issue Type: Story
Components: DMN Editor
Reporter: Liz Clayton
Assignee: Liz Clayton
Labels: UX, UXTeam, drools-tools
Attachments: DROOLS-2738.bmpr, Screen Shot 2018-07-24 at 3.51.03 PM.png, Screen
Shot 2018-07-27 at 11.48.34 AM.png, Screen Shot 2018-07-27 at 12.24.49 PM.png, Screen Shot
2018-07-27 at 12.27.13 PM.png, add_basic.png, treegrid.png, type_definitions.pdf
*Background*
Persona: Business analyst or Rules practitioner
Use Cases:
As a user I want to:
* *Edit* the list of Data Types, using the appropriate type considering the DMN model
(eg: in the age line, we need to select "Numeric" in the combobox.)
* *Add* a new data type, which might be a nested or otherwise complex object as defined
by the (ItemDefinition.)
* *Remove* Data Types from the list of available selections.
* be prevented from making selections that are not valid or would cause an error.
* know that when I edit a data type the changes will be updated in the DMN model.
Functional considerations/ pre conditions:
* Outside of simple view/select, Data Types list (and options) will be presented as a
tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same.
* Design needs to be consistent with Stunner and PF components, such as:
https://www.patternfly.org/pattern-library/widgets/#treegrid-table
Verification conditions:
* Scrum team and PO review.