[JBoss JIRA] (DROOLS-5147) [DMN Designer] DMN Decision Table - Input/Output clauses enhancements (UX)
by Guilherme Gomes (Jira)
[ https://issues.redhat.com/browse/DROOLS-5147?page=com.atlassian.jira.plug... ]
Guilherme Gomes commented on DROOLS-5147:
-----------------------------------------
Hi [~uxdlc], I'd like to leave a proposal here:
!prototype.png|width=600!
I'm not sure if it makes sense, but I think it's a possible direction we could evolve :)
> [DMN Designer] DMN Decision Table - Input/Output clauses enhancements (UX)
> --------------------------------------------------------------------------
>
> Key: DROOLS-5147
> URL: https://issues.redhat.com/browse/DROOLS-5147
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: drools-tools
> Attachments: prototype.png
>
>
> Currently, the DMN Decision Tables input/output clauses work fine, but they have the following unpractical scenarios:
> - When users have a structure input node "associated" with an input clause (input column), they frequently need to go back to the data types page and remember the name of some field.
> - When users select a structure data type as the type of an output clause, they need to create sub-columns for each field manually.
> The goal for this JIRA is to get input from UX to enhance interactions with input and output clauses.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-5147) [DMN Designer] DMN Decision Table - Input/Output clauses enhancements (UX)
by Guilherme Gomes (Jira)
[ https://issues.redhat.com/browse/DROOLS-5147?page=com.atlassian.jira.plug... ]
Guilherme Gomes updated DROOLS-5147:
------------------------------------
Attachment: prototype.png
> [DMN Designer] DMN Decision Table - Input/Output clauses enhancements (UX)
> --------------------------------------------------------------------------
>
> Key: DROOLS-5147
> URL: https://issues.redhat.com/browse/DROOLS-5147
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: drools-tools
> Attachments: prototype.png
>
>
> Currently, the DMN Decision Tables input/output clauses work fine, but they have the following unpractical scenarios:
> - When users have a structure input node "associated" with an input clause (input column), they frequently need to go back to the data types page and remember the name of some field.
> - When users select a structure data type as the type of an output clause, they need to create sub-columns for each field manually.
> The goal for this JIRA is to get input from UX to enhance interactions with input and output clauses.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-5147) [DMN Designer] DMN Decision Table - Input/Output clauses enhancements (UX)
by Guilherme Gomes (Jira)
Guilherme Gomes created DROOLS-5147:
---------------------------------------
Summary: [DMN Designer] DMN Decision Table - Input/Output clauses enhancements (UX)
Key: DROOLS-5147
URL: https://issues.redhat.com/browse/DROOLS-5147
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Reporter: Guilherme Gomes
Assignee: Elizabeth Clayton
Currently, the DMN Decision Tables input/output clauses work fine, but they have the following unpractical scenarios:
- When users have a structure input node "associated" with an input clause (input column), they frequently need to go back to the data types page and remember the name of some field.
- When users select a structure data type as the type of an output clause, they need to create sub-columns for each field manually.
The goal for this JIRA is to get input from UX to enhance interactions with input and output clauses.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13221) Remove package-schema cruft from wildfly-feature-pack-build.xml files
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-13221:
---------------------------------------
Summary: Remove package-schema cruft from wildfly-feature-pack-build.xml files
Key: WFLY-13221
URL: https://issues.redhat.com/browse/WFLY-13221
Project: WildFly
Issue Type: Task
Components: Build System
Reporter: Brian Stansberry
Assignee: Yeray Borges Santana
The various wildfly-feature-pack-build.xml files include 'package-schemas' elements. AIUI the children of those elements only need to refer to maven groupId for which that specific feature pack provides artifacts with schemas. It does not need to include schemas from other f-ps that the f-p depends on; the WF galleon plugin itself combines those.
So the task is
1) to clean out cruft, i.e. elements that are related to artifacts from other feature packs. Helps clarify the expected use of these files.
2) Perhaps in the verifier tests for servlet-dist, ee-dist, dist add verification of the presence of 1 schema from each relevant maven groupId. Guard against schemas suddenly not getting picked up.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months