[JBoss JIRA] (DROOLS-3475) [DMN Designer] Ensure integrity of DecisionService node
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-3475?page=com.atlassian.jira.plug... ]
Michael Anstis reassigned DROOLS-3475:
--------------------------------------
Assignee: Guilherme Gomes (was: Michael Anstis)
> [DMN Designer] Ensure integrity of DecisionService node
> -------------------------------------------------------
>
> Key: DROOLS-3475
> URL: https://issues.redhat.com/browse/DROOLS-3475
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Michael Anstis
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> The {{DecisionService}} node contains lists of {{DMNElementReference}} for "Output Decisions", "Encapsulated Decisions", "Input Decision" and "Input Data". These are currently only populated when unmarshalling a DMN XML file to Stunner model. Their members are not maintained as and when Users add, delete etc nodes that could affect them. They are used as reference when marshalling back from Stunner to DML XML to maintain the positional information \[*\] of such references.
> The {{DecisionService}} node reference lists should be updated as and when the User interacts with the diagram (e.g. add/remove "Output Decision" to/from the "Decision Service", add/remove "Encapsulated Decision" to/from the "Decision Service", add/remove an "Input Data" or "Input Decision" reference to/from the "Decision Service" or move the "splitter" in such a way that could affect the "Output/Encapsulated" Decisions. This will require (at least) custom commands for add/remove child, add connection and update property (splitter location).
> \[*\] See [here|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-...] that uses the order of the references set-up during marshalling from XML to Stunner to ensure identical references maintain the same index in the list marshalled from Stunner to XML. This is a DMN Specification requirement that "positional information" is preserved (without using this transient mechanism it would otherwise be impossible to preserve the index order as XML->Stunner looses the lists and Stunner->XML walks the graph to add element references to the Decision Service. The original ordering is lost by the conversion from {{List}} to _Graph_ to {{List}}.
> This "workaround" to preserve ordering should NOT be required when the integrity of {{DecisionService}} Node's element references is maintained by custom commands.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-3390) Investigate hover state presentation for tables (DMN, scenario, DT)
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-3390?page=com.atlassian.jira.plug... ]
Michael Anstis reassigned DROOLS-3390:
--------------------------------------
Assignee: Guilherme Gomes (was: Michael Anstis)
> Investigate hover state presentation for tables (DMN, scenario, DT)
> --------------------------------------------------------------------
>
> Key: DROOLS-3390
> URL: https://issues.redhat.com/browse/DROOLS-3390
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor, Scenario Simulation and Testing, Test Scenarios Editor
> Reporter: Elizabeth Clayton
> Assignee: Guilherme Gomes
> Priority: Minor
> Labels: ScenarioSimulation, UX, UXTeam, VisualDesign, drools-tools
>
> As a practitioner I need a clear and consistent presentation of table styles, so that I can learn the visual cues once for all tables in the application suite.
> When possible, iteratively update visual styles for tables using the following proposed options: https://redhat.invisionapp.com/share/RXLG7XB2TCW
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-3288) [DMN Designer] The Input Node type should be synchronised with the column type in the Decision Table
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-3288?page=com.atlassian.jira.plug... ]
Michael Anstis reassigned DROOLS-3288:
--------------------------------------
Assignee: Guilherme Gomes (was: Michael Anstis)
> [DMN Designer] The Input Node type should be synchronised with the column type in the Decision Table
> ----------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3288
> URL: https://issues.redhat.com/browse/DROOLS-3288
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Guilherme Gomes
> Priority: Minor
> Labels: drools-tools
> Attachments: diagram.png, dtable.png, steps.gif
>
>
> When the user persists the following diagram:
> !diagram.png|thumbnail!
> ..with the following Decision Table:
> !dtable.png|thumbnail!
> ..and change the Input Node type, the type in the Decision Table does not change.
> *Steps to reproduce*
> !steps.gif|thumbnail!
> *Expected behaviour*
> Ideally, those types should be synchronised. However, since the type in the DT column is persisted as {{dmn:inputExpression}} and the type in the Input Node is persisted as a {{dmn:variable}}, the user should be able to re-define the types, keeping them unsynchronised.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-3200) [DMN Designer] Properties Panel Hints
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-3200?page=com.atlassian.jira.plug... ]
Michael Anstis reassigned DROOLS-3200:
--------------------------------------
Assignee: Guilherme Gomes (was: Michael Anstis)
> [DMN Designer] Properties Panel Hints
> -------------------------------------
>
> Key: DROOLS-3200
> URL: https://issues.redhat.com/browse/DROOLS-3200
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> Following DROOLS-3145 we need to identify most important fields set via properties panel and provide hints directly in the properties panel to support self-documentary product effort.
> The hints should shortly explain the fields and provide sample valid values if applicable.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-3657) [DMN Designer] Highlight invalid DRGElements
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-3657?page=com.atlassian.jira.plug... ]
Michael Anstis reassigned DROOLS-3657:
--------------------------------------
Assignee: Guilherme Gomes (was: Michael Anstis)
> [DMN Designer] Highlight invalid DRGElements
> --------------------------------------------
>
> Key: DROOLS-3657
> URL: https://issues.redhat.com/browse/DROOLS-3657
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> Whenever a DMN file is validated (be it when the Project is compiled or via the Validate button on the toolbar) the DMN editor should highlight issues reported by the validation. This should include DRG nodes (on the graph view) or DRGElements (in the Boxed Expression, aka grid, view). The nature of the highlighting is to be defined; but probably consists of an orange background for warnings and red background for errors; possibly both with a warning triangle positioned somewhere. UX will need engaging for design proposals.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month