[jboss-jira] [JBoss JIRA] (DROOLS-3185) [DMN Designer] Change Literal Expression to Decision Table

[Jozef Marko (Jira)]

    [ https://issues.jboss.org/browse/DROOLS-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13654044#comment-13654044 ] 

Jozef Marko commented on DROOLS-3185:
-------------------------------------

[~tari_manga] Ok and what about *a1*, should we somehow differentiate (I mean visually in DMN Designer) *collection* and *non-collection* input columns of decision tables?

> [DMN Designer] Change Literal Expression to Decision Table
> ----------------------------------------------------------
>
>                 Key: DROOLS-3185
>                 URL: https://issues.jboss.org/browse/DROOLS-3185
>             Project: Drools
>          Issue Type: Bug
>          Components: DMN Editor
>    Affects Versions: 7.14.0.Final
>            Reporter: Jozef Marko
>            Assignee: Michael Anstis
>            Priority: Major
>              Labels: drools-tools
>         Attachments: Screenshot from 2018-10-25 14-40-06.png, Screenshot from 2018-10-29 12-25-14.png, Screenshot from 2018-10-29 12-25-31.png, a1.dmn, a2.dmn, screenshot-1.png
>
>
> When user changes Decision node top level expression from literal expression to decision table, that decision table misses InputClause columns.
> h2. 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



--
This message was sent by Atlassian Jira
(v7.12.1#712002)