[jboss-jira] [JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.

[Edson Tirelli (JIRA)]

    [ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611709#comment-13611709 ] 

Edson Tirelli commented on DROOLS-2787:
---------------------------------------

[~uxdlc] in line with what [~manstis] said, I am attaching an idea. This is *not* a mockup, just trying to convey the idea.

There are three basic scenarios:

* either the user selects a simple type (like number, text, etc), in which case he only selects the "type" of the field, no name.
* or the user selects a name and an existing type, like he can create type "tAge" that is an alias for type "Number", or "tEmployee" that is an alias for type "tPerson".
* or the user creates a structured type with fields, in which case he has to select a name and create all the fields, like "tPerson", of type "Structure" with fields "age" (number) and "address" (text).

These 3 scenarios have to be clear and supported, and that is the idea I tried to express with the attached PDF.


> "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, add_basic.png, treegrid.png
>
>
> *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. 



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)