[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=13604510#comment-13604510 ] 

Guilherme Carreiro edited comment on DROOLS-2728 at 7/12/18 10:57 AM:
----------------------------------------------------------------------

Hi [~uxdlc],

---

1) Simple (basic) data type

> wrt 1) one thing that's missing is if you look at the Process Modeler widget I believe it's not just a list of the added items, but also allows one to edit existing ones. Wdyt?

I just tried the Process Modeller widget:
 !2018-07-12 11.41.43 AM.gif|thumbnail! 
..but I'm not seeing how it solves in the problem of the _simple_ data type definition.

I think that the dialog handles only one data type, right?
The user would be creating one data type, or updating the selected one.

Am I missing something?

---

2) Structured data type

> 2) Ok, so both 2 and 3 are structured (or hierarchical?), it wasn't clear from you initial mockups - thanks for clarifying.

No problem :)

---

3) Deep structured data type

> 3) Michael Anstis, Guilherme Carreiro as I mentioned in my comments, I only starting working on this last night so didn't have time to work on this variant. But if you're good with this forms based approach I'll work on that next.

I'm good with the forms based approach :) One thing that I think we should try to avoid is having a "popup hell", due to this hierarchical scenario that we handling.

---

Thank you Liz :)


was (Author: karreiro):
Hi [~uxdlc],

---

1) Simple (basic) data type

> wrt 1) one thing that's missing is if you look at the Process Modeler widget I believe it's not just a list of the added items, but also allows one to edit existing ones. Wdyt?

I just tried the Process Modeller widget:
 !2018-07-12 11.41.43 AM.gif! 
..but I'm not seeing how it solves in the problem of the _simple_ data type definition.

I think that the dialog handles only one data type, right?
The user would be creating one data type, or updating the selected one.

Am I missing something?

---

2) Structured data type

> 2) Ok, so both 2 and 3 are structured (or hierarchical?), it wasn't clear from you initial mockups - thanks for clarifying.

No problem :)

---

3) Deep structured data type

> 3) Michael Anstis, Guilherme Carreiro as I mentioned in my comments, I only starting working on this last night so didn't have time to work on this variant. But if you're good with this forms based approach I'll work on that next.

I'm good with the forms based approach :) One thing that I think we should try to avoid is having a "popup hell", due to this hierarchical scenario that we handling.

---

Thank you 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: 2018-07-12 11.41.43 AM.gif, 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)