[Red Hat JIRA] (DROOLS-5945) Type coercion does not work for bound variables in executable model.
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5945?page=com.atlassian.jira.plug... ]
Mario Fusco moved RHDM-1569 to DROOLS-5945:
-------------------------------------------
Component/s: executable model
(was: BRE)
Docs QE Status: NEW
Key: DROOLS-5945 (was: RHDM-1569)
QE Status: NEW
Affects Version/s: (was: 7.5.0.GA)
(was: 7.4.1.GA)
(was: 7.6.0.GA)
(was: 7.5.1.GA)
(was: 7.7.0.GA)
(was: 7.8.0.GA)
(was: 7.7.1.GA)
(was: 7.9.0.GA)
(was: 7.8.1.GA)
Workflow: GIT Pull Request workflow (was: CDW with docs v1)
Environment: (was: This issue occurs on releases from RHDM 7.4.1 to 7.9.0.)
Project: Drools (was: Red Hat Decision Manager)
> Type coercion does not work for bound variables in executable model.
> --------------------------------------------------------------------
>
> Key: DROOLS-5945
> URL: https://issues.redhat.com/browse/DROOLS-5945
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Priority: Major
> Labels: support
> Attachments: reproducer_model_compiler_15a.zip
>
>
> When executing a rule like (\*1) that uses comparison between different-type bound variables (for example, an Integer variable and a String variable consisting of digit characters like (\*1-1)), the action part of the rule is unexpectedly fired in executable model though the result of the comparison is expected to be {{false}}.
> (\*1)
> {noformat}
> package com.example.reproducer
> import static com.example.reproducer.CommonUtils.getListSize
> dialect "java"
> rule "rule15a1"
> when
> Order( $target : "3",
> $items : getListSize(items),
> $items != $target ) // ..... (*1-1)
> then
> System.out.println("***** Action of rule15a1 -- $items = " + $items);
> end
> {noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 8 months
[Red Hat JIRA] (DROOLS-5512) Unsaved changes dialog for a Test Scenario executed right after creation
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-5512?page=com.atlassian.jira.plug... ]
Yeser Amer updated DROOLS-5512:
-------------------------------
Sprint: 2020 Week 52-03 (from Dec 21)
> Unsaved changes dialog for a Test Scenario executed right after creation
> ------------------------------------------------------------------------
>
> Key: DROOLS-5512
> URL: https://issues.redhat.com/browse/DROOLS-5512
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.41.0.Final
> Reporter: Jan Stastny
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
>
> There is once again an Unsaved Changes dialog presented to user even though no changes has been made.
> This time it is when user creates Test Scenario, fills in facts and values, saves and executes the test scenario right away. When clicking save and trying to close again it does not appear again. There us not commit in niogit connected with the second save.
> When user closes and reopens editor between save and run, all works fine.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 8 months
[Red Hat JIRA] (DROOLS-5689) Test Scenario DMN included models decision support
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-5689?page=com.atlassian.jira.plug... ]
Yeser Amer updated DROOLS-5689:
-------------------------------
Sprint: 2021 Week 04-06 (from Jan 25)
> Test Scenario DMN included models decision support
> --------------------------------------------------
>
> Key: DROOLS-5689
> URL: https://issues.redhat.com/browse/DROOLS-5689
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Affects Versions: 7.44.0.Final
> Reporter: Jan Stastny
> Assignee: Yeser Amer
> Priority: Major
> Attachments: reproducer.zip
>
>
> Test scenario does not currently fully support DMN models with included DMN model.
> Currently just Data types are correctly included, but issue is with Decisions. When running a test scenario where such imported decision is referenced in the decision being tested it results in SKIPPED evaluation of the decision and similar log entry:
> {code:java}
> 12:27:45,784 ERROR [org.kie.dmn.core.impl.DMNRuntimeImpl] (default task-20) Required dependency 'input-a' not found on node 'LessThanZero'
> 12:27:45,784 ERROR [org.kie.dmn.core.impl.DMNRuntimeImpl] (default task-20) Unable to evaluate decision 'NotLessThanZero' as it depends on decision 'a.LessThanZero'
> {code}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 8 months