Loading...

XML

Word

Printable

Epic Link:
[DMN Designer] Runtime issues [7.2.x]
Sprint:
2018 Week 42-44
Story Points:
3
Steps to Reproduce:
Hide

Create new DMN diagram

Add two nodes: Decision, InputData

Connect them: InputData -> Decision

Set Decision ndoe top level expression as Literal Expression

Save and reopen the diagram

Change the Decision top level expression to Decision table

You will be in situation like shown in attachment, the input clause will miss
Show
Create new DMN diagram Add two nodes: Decision, InputData Connect them: InputData -> Decision Set Decision ndoe top level expression as Literal Expression Save and reopen the diagram Change the Decision top level expression to Decision table You will be in situation like shown in attachment, the input clause will miss
Git Pull Request:
https://github.com/kiegroup/kie-wb-common/pull/2204
Docs QE Status:
NEW
QE Status:
NEW

When user changes Decision node top level expression from literal expression to decision table, that decision table misses InputClause columns.

Manual Acceptance Test

Check steps to reproduce, while InputData node has data type

Built in type
Custom type that has constraint
Custom type that is collection
Custom type that is recursive
Multiple InputData nodes
~~Multiple input nodes, mixed InputData and Decision~~ doesn't work, not supported

incorporates

DROOLS-3111 [DMN Designer] Decision table generation fails if custom input data connected

relates to

DROOLS-3143 [DMN Designer] DMN unmarshal from 1.1, 1.2; marshal as 1.2