[
https://issues.redhat.com/browse/DROOLS-4446?page=com.atlassian.jira.plug...
]
Yeser Amer commented on DROOLS-4446:
------------------------------------
Hi [~jomarko], I just checked with master version, and the current
error is: *string* changed to *LKW* (screenshot is attached)
Considering this, I think we can close this ticket, WDYT?
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, 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)