[jboss-jira] [JBoss JIRA] (DROOLS-2728) UX for custom data-types modal

[Guilherme Carreiro (JIRA)]

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

Guilherme Carreiro edited comment on DROOLS-2728 at 7/12/18 9:14 AM:
---------------------------------------------------------------------

[~uxdlc], thank you for the prototypes :-)

I think that the Custom data-type popup handles with three kinds of scenarios. Let's check them:

1) Simple (basic) data type
Here the user inserts the name of the field and its type, for example, "Age" (the name of the data type) and "Number" (the type of the data type). So, the popup would be something like this:
 !Screen Shot 2018-07-12 at 9.41.34 AM.png|thumbnail! 

Am I missing something?

2) Structured data type
Here the user can create a complex type with fields, something like this:

* Person
  * name (String)
  * age (Number)
  * email (String)
}}

I think that this prototype refers to this scenario:
 !Screen Shot 2018-07-12 at 9.41.40 AM.png|thumbnail! 

However, I think that we need a field specifying the name of the data-type (in our example, the name is "Person"). And, the list of fields does not need 3 columns ("Name", "Field Name" and "Field Type"), we need just two columns "Field Name" and "Field Type".

WDYT?


3) Deep structured data type
Sometimes a data type can have nested structures, something like this:
{{- Person
    - name (String)
    - age (Number)
    - email (String)
    - address
        - street (String)
        - house_number (Number)
        - city_name (String)}}

How could the "address" _nested_ structure (with its own fields) be inserted in the "Person" data type?

Thanks again, Liz.


was (Author: karreiro):
[~uxdlc], thank you for the prototypes :-)

I think that the Custom data-type popup handles with three kinds of scenarios. Let's check them:

1) Simple (basic) data type
Here the user inserts the name of the field and its type, for example, "Age" (the name of the data type) and "Number" (the type of the data type). So, the popup would be something like this:
 !Screen Shot 2018-07-12 at 9.41.34 AM.png|thumbnail! 

Am I missing something?

2) Structured data type
Here the user can create a complex type with fields, something like this:
{{
- Person
    - name (String)
    - age (Number)
    - email (String)
}}

I think that this prototype refers to this scenario:
 !Screen Shot 2018-07-12 at 9.41.40 AM.png|thumbnail! 

However, I think that we need a field specifying the name of the data-type (in our example, the name is "Person"). And, the list of fields does not need 3 columns ("Name", "Field Name" and "Field Type"), we need just two columns "Field Name" and "Field Type".

WDYT?


3) Deep structured data type
Sometimes a data type can have nested structures, something like this:
{{- Person
    - name (String)
    - age (Number)
    - email (String)
    - address
        - street (String)
        - house_number (Number)
        - city_name (String)}}

How could the "address" _nested_ structure (with its own fields) be inserted in the "Person" data type?

Thanks again, Liz.

> UX for custom data-types modal 
> -------------------------------
>
>                 Key: DROOLS-2728
>                 URL: https://issues.jboss.org/browse/DROOLS-2728
>             Project: Drools
>          Issue Type: Task
>          Components: DMN Editor
>            Reporter: Liz Clayton
>            Assignee: Liz Clayton
>              Labels: UX, UXTeam, drools-tools
>         Attachments: DROOLS-2700.png, First-draft.png, Screen Shot 2018-07-11 at 7.37.12 PM.png, Screen Shot 2018-07-12 at 9.41.34 AM.png, Screen Shot 2018-07-12 at 9.41.40 AM.png, edit.png, grid-alt.png, triggerDataType.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by: 
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.



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