[JBoss JIRA] (DROOLS-5236) Decision table validation produces runtime exception in Business Central
by Matteo Mortari (Jira)
[ https://issues.redhat.com/browse/DROOLS-5236?page=com.atlassian.jira.plug... ]
Matteo Mortari reassigned DROOLS-5236:
--------------------------------------
Assignee: Matteo Mortari (was: Mario Fusco)
> 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)
6 years
[JBoss JIRA] (DROOLS-2222) Stunner: Ensure "copy/paste" (nodes) supports DMN's deep definition
by Valentino Pellegrino (Jira)
[ https://issues.redhat.com/browse/DROOLS-2222?page=com.atlassian.jira.plug... ]
Valentino Pellegrino commented on DROOLS-2222:
----------------------------------------------
Hi [~roger600],
I followed the approach of implementing a specific cloning mechanism for DMN, that is very similar to the one you are describing.
I opened the Pull Request https://github.com/kiegroup/kie-wb-common/pull/3266, where I tried to explain the strategy in both the description and the Java DOC.
Thanks for your valuable feedback!
> Stunner: Ensure "copy/paste" (nodes) supports DMN's deep definition
> -------------------------------------------------------------------
>
> Key: DROOLS-2222
> URL: https://issues.redhat.com/browse/DROOLS-2222
> Project: Drools
> Issue Type: Sub-task
> Components: DMN Editor, Stunner
> Reporter: Michael Anstis
> Assignee: Tiago Dolphine
> Priority: Major
>
> As discussed on DROOLS-2214 Stunner needs to support (or provide extension points) for DMN's "copy/paste" of a {{Node}} to also deep-clone the definition. Please either (a) use this JIRA to record any changes needed in Stunner, (b) provide an explanation of how DMN can override the copy/paste to deep-clone definitions. Thanks.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5253) [DMN Designer] Copied node should be distinguished from original one
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5253?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5253:
--------------------------------
Summary: [DMN Designer] Copied node should be distinguished from original one (was: [DMN Designer] Copied node should be distinguished form original one)
> [DMN Designer] Copied node should be distinguished from original one
> --------------------------------------------------------------------
>
> Key: DROOLS-5253
> URL: https://issues.redhat.com/browse/DROOLS-5253
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.37.0.Final
> Reporter: Jozef Marko
> Assignee: Valentino Pellegrino
> Priority: Minor
> Labels: drools-tools
>
> If user copy a DMN diagram node, the copy has exactly name name as the original node. It causes validation issues as the node names have to be unique. We should add some suffix to the copied node, probably numbers (-1, -2, -3 ...).
> It will not break rule about node unique names and will help to distinguish original node from the copied one.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5253) [DMN Designer] Copied node should be distinguished form original one
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5253?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5253:
--------------------------------
Description:
If user copy a DMN diagram node, the copy has exactly name name as the original node. It causes validation issues as the node names have to be unique. We should add some suffix to the copied node, probably numbers (-1, -2, -3 ...).
It will not break rule about node unique names and will help to distinguish original node from the copied one.
was:
This issue is related to two features of DMN editor.
- Copy and paste diagram node
- Nodes of imported model
If user imported another DMN model into his DMN model, he can use imported nodes in his diagram. They can be easily distinguished by prefix of the imported model. The issue is if we copy and paste such imported node. Created copy shouldn't have the prefix of the original node.
> [DMN Designer] Copied node should be distinguished form original one
> --------------------------------------------------------------------
>
> Key: DROOLS-5253
> URL: https://issues.redhat.com/browse/DROOLS-5253
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.37.0.Final
> Reporter: Jozef Marko
> Assignee: Valentino Pellegrino
> Priority: Minor
> Labels: drools-tools
>
> If user copy a DMN diagram node, the copy has exactly name name as the original node. It causes validation issues as the node names have to be unique. We should add some suffix to the copied node, probably numbers (-1, -2, -3 ...).
> It will not break rule about node unique names and will help to distinguish original node from the copied one.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5253) [DMN Designer] Copied node should be distinguished form original one
by Jozef Marko (Jira)
Jozef Marko created DROOLS-5253:
-----------------------------------
Summary: [DMN Designer] Copied node should be distinguished form original one
Key: DROOLS-5253
URL: https://issues.redhat.com/browse/DROOLS-5253
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.37.0.Final
Reporter: Jozef Marko
Assignee: Valentino Pellegrino
This issue is related to two features of DMN editor.
- Copy and paste diagram node
- Nodes of imported model
If user imported another DMN model into his DMN model, he can use imported nodes in his diagram. They can be easily distinguished by prefix of the imported model. The issue is if we copy and paste such imported node. Created copy shouldn't have the prefix of the original node.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years