[JBoss JIRA] (DROOLS-3685) [DMN Designer] Boxed expressions - Decision Table - Output clause - hen selecting a structured type
by Valentino Pellegrino (Jira)
[ https://issues.redhat.com/browse/DROOLS-3685?page=com.atlassian.jira.plug... ]
Valentino Pellegrino updated DROOLS-3685:
-----------------------------------------
Summary: [DMN Designer] Boxed expressions - Decision Table - Output clause - hen selecting a structured type (was: [DMN Designer] Boxed expressions - Decision Table - Output clause - Show Data Type fields automatically)
> [DMN Designer] Boxed expressions - Decision Table - Output clause - hen selecting a structured type
> ---------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3685
> URL: https://issues.redhat.com/browse/DROOLS-3685
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.18.0.Final
> Reporter: Guilherme Gomes
> Assignee: Valentino Pellegrino
> Priority: Major
> Labels: drools-tools
>
> When users select a "Structured" Data Type in a Decision Table output clause, the Data Type fields should be automatically shown as "sub-cells".
> h2. Acceptance criteria
> - Action should be undoable/redoable, especially if user had structure data type, more columns with a lot of data and mistakenly change to simple type, i.e. single column
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-3685) [DMN Designer] Boxed expressions - Decision Table - Output clause - Show Data Type fields automatically
by Valentino Pellegrino (Jira)
[ https://issues.redhat.com/browse/DROOLS-3685?page=com.atlassian.jira.plug... ]
Valentino Pellegrino updated DROOLS-3685:
-----------------------------------------
Summary: [DMN Designer] Boxed expressions - Decision Table - Output clause - Show Data Type fields automatically (was: [DMN Designer] Boxed expressions - Decision Table - Output clause - hen selecting a structured type)
> [DMN Designer] Boxed expressions - Decision Table - Output clause - Show Data Type fields automatically
> -------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3685
> URL: https://issues.redhat.com/browse/DROOLS-3685
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.18.0.Final
> Reporter: Guilherme Gomes
> Assignee: Valentino Pellegrino
> Priority: Major
> Labels: drools-tools
>
> When users select a "Structured" Data Type in a Decision Table output clause, the Data Type fields should be automatically shown as "sub-cells".
> h2. Acceptance criteria
> - Action should be undoable/redoable, especially if user had structure data type, more columns with a lot of data and mistakenly change to simple type, i.e. single column
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-4729) Change Unexpected error on Error if DMN got invalidated
by Daniele Zonca (Jira)
[ https://issues.redhat.com/browse/DROOLS-4729?page=com.atlassian.jira.plug... ]
Daniele Zonca reassigned DROOLS-4729:
-------------------------------------
Assignee: Yeser Amer (was: Daniele Zonca)
> Change Unexpected error on Error if DMN got invalidated
> --------------------------------------------------------
>
> Key: DROOLS-4729
> URL: https://issues.redhat.com/browse/DROOLS-4729
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.29.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Minor
> Labels: CustomerFocus, drools-tools
> Attachments: Traffic Violation Rules.dmn, image-2019-11-05-18-30-40-011.png, image-2019-11-05-18-31-30-232.png
>
>
> If user created DMN based scenario test and used a property from it and after some time that property disappeared - then if we reopen test scenario editor we got
> *Error as expected see*
> !image-2019-11-05-18-30-40-011.png|thumbnail!
> But if user wants to edit any of the value we got
> *Unexpected error*
> !image-2019-11-05-18-31-30-232.png|thumbnail!
> Steps to reproduce
> # Import DMN [^Traffic Violation Rules.dmn]
> # Create test scenario asset for this dmn and save
> # Go back to DMN and remove Driver Should the driver... DMN objects and save
> # Open test scenario
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-4446) Confusing scenario validation message for collection types
by Daniele Zonca (Jira)
[ https://issues.redhat.com/browse/DROOLS-4446?page=com.atlassian.jira.plug... ]
Daniele Zonca reassigned DROOLS-4446:
-------------------------------------
Assignee: Yeser Amer (was: Daniele Zonca)
> Confusing scenario validation message for collection types
> ----------------------------------------------------------
>
> Key: DROOLS-4446
> URL: https://issues.redhat.com/browse/DROOLS-4446
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.26.0.Final
> Reporter: Jozef Marko
> Assignee: Yeser Amer
> Priority: Minor
> Labels: drools-tools
> Attachments: Screenshot from 2019-08-20 10-19-46.png
>
>
> There is small enhancement needed if the user validates dmn scenario with *collection* data type, being previously simple data type.
> h2. Steps to reproduce
> - Create new DMN
> - Define there custom data type *LKW:string*
> - Set this LKW type for some *input data* node
> - Save DMN
> - Create a Scenario for this DMN
> - Go back to DMN
> - Check tickbox *Is Collection* for the *LKW* type
> - Save DMN
> - Validate Scenario, you will get message as shown in the picture. It can be confusing as it says *LKW* changed to *LKW*
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month