[jboss-jira] [JBoss JIRA] (DROOLS-5236) Decision table validation produces runtime exception in Business Central

[Matteo Mortari (Jira)]

    [ https://issues.redhat.com/browse/DROOLS-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045862#comment-14045862 ] 

Matteo Mortari commented on DROOLS-5236:
----------------------------------------

[~tracyhires] this problem was already solved by [RHDM-1281] so bumping Drools version to 7.35.0.Final or higher should do it.

My suggestion is to always try against the latest version, as there are chances the problem was already fixes ;)

That said, thank you for sharing the model, as I believe one of the overlap messages, can be improved; I will work on it on a separa jira.

To conclude, as this was solved by [RHDM-1281] going to mark it as Resolved, update Drools version. If there are still problems, don't hesitate to reopen this jira or file a new one.

> Decision table validation produces runtime exception in Business Central
> ------------------------------------------------------------------------
>
>                 Key: DROOLS-5236
>                 URL: https://issues.redhat.com/browse/DROOLS-5236
>             Project: Drools
>          Issue Type: Bug
>          Components: decision tables, DMN Editor
>    Affects Versions: 7.34.0.Final
>            Reporter: Tracy Hires
>            Assignee: Matteo Mortari
>            Priority: Minor
>         Attachments: Benefits Calculator.dmn
>
>
> In Business Central's DMN Modeler, a decision table with "Unique" Hit policy and overlapping rules, when placed into a context, produces a Runtime Exception on validate. Error Message is: "[uuid] DMN: Validation of the DMN Model cannot be performed because of some runtime exception 'org.kie.dmn.model.v1_2.TContextEntry cannot be cast to org.kie.dmn.model.api.NamedElement'. (DMN Validation stopped on failed validation for some DMN Model)"
> We expected to see 'DMN: Overlap detected: Overlap values: [...] for rules: [...]. UNIQUE hit policy decision tables can only have one matching rule' among the validation errors, and in fact this error is displayed when the decision table is not nested within a context.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)