[jboss-jira] [JBoss JIRA] (DROOLS-4446) Confusing scenario validation message for collection types
Jozef Marko (Jira)
issues at jboss.org
Thu Jun 11 01:39:59 EDT 2020
[ https://issues.redhat.com/browse/DROOLS-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jozef Marko closed DROOLS-4446.
-------------------------------
Fix Version/s: 7.39.0.Final
Resolution: Out of Date
Thank you [~yamer]. I can confirm this is not reproducible anymore. Closing.
> 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
> Fix For: 7.39.0.Final
>
> Attachments: Screenshot from 2019-08-20 10-19-46.png, Screenshot from 2020-06-10 16-24-49.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)
More information about the jboss-jira
mailing list