[JBoss JIRA] (DROOLS-2655) [DMN Designer]: Decision Table: Automatically create input columns for each InputData element
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2655?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2655:
----------------------------------------
The changes for this JIRA depend on DROOLS-2653 being first merged as they both affect the same area of the codebase.
> [DMN Designer]: Decision Table: Automatically create input columns for each InputData element
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-2655
> URL: https://issues.jboss.org/browse/DROOLS-2655
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> [~tari_manga] suggested it advantageous to create input columns for each {{InputData}} element linked to the {{Decision}}/{{BusinessKnowledgeModel}} containing the {{DecisionTable}} expression. For example, if a BKM has 2 {{InputData}} nodes of simple data-types then two columns should be created. If a BKM has 1 {{InputData}} node of complex data-type that consists of 3 elements then 3 columns should be created.
> - For simple data types the input column names should correspond exactly to InputData elements.
> - For complex data types, we should use dot notation, e.g. Person.name, Person.salary ...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2696) Dialog to name test and define bindings (UX)
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2696?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2696:
-------------------------------------
To address the feedback that the "rule binding" terminology might be too techie for a business user, I have revised the dialog a bit:
* Whilethe current "session" is still the default, and the terminology is more or less the same - the change I made was to describe this is an "advanced" setting, and require that the user take an explicit action to change it (check the checkbox to rename the session." I went with this approach because I'm not sure there is a point to getting around the fact that this is a setting that primarily a more technical user would be doing - so why mince words? It will just be less direct for that persona. And rather it might help the novice user to understand that this is (for now) an advanced option.
[~danielezonca] Could you offer me a sentence or two that describes the rule binding and sessions concepts? I think will also demonstrate that this is a more technical user action, and we can use the text for the info tip. Let me know, thanks.
> Dialog to name test and define bindings (UX)
> --------------------------------------------
>
> Key: DROOLS-2696
> URL: https://issues.jboss.org/browse/DROOLS-2696
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Attachments: Screen Shot 2018-07-02 at 3.08.48 PM.png, Screen Shot 2018-07-02 at 3.09.02 PM.png
>
>
> As a business user I want the ability to name a scenario test and define the rule bindings so that I can create a test asset.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months