[jboss-jira] [JBoss JIRA] (DROOLS-5080) [DMN Designer] Automatically create InputClause supporting Decisions

[Michael Anstis (Jira)]

     [ https://issues.redhat.com/browse/DROOLS-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Anstis moved RHDM-1254 to DROOLS-5080:
----------------------------------------------

               Project: Drools  (was: Red Hat Decision Manager)
                   Key: DROOLS-5080  (was: RHDM-1254)
            Issue Type: Enhancement  (was: Bug)
              Workflow: GIT Pull Request workflow   (was: CDW with docs v1)
        Docs QE Status: NEW
           Component/s: DMN Editor
                            (was: Decision Central)
                            (was: DMN)
           Environment:     (was: RHDM 7.6.0)
    Steps to Reproduce:   (was: 1. Create a DRD
2. Create a Decision node (1)
3. Create a data input and associate to the decision node (1)
4. Create a Decision node (2)
5. Create 2 data inputs and associate to the decision node (2)
6. Associate Decision 2 to Decision 1.
7. Edit decision 1 and set Decision Table as the expression type

Expected to see 2 columns: Data Input 1 and Decision 2; with output Decision 1.
Actual: Only Data Input 1 is available.)
     Affects Version/s: 7.33.0.Final
                            (was: 7.6.0.GA)
             QE Status: NEW


> [DMN Designer] Automatically create InputClause supporting Decisions
> --------------------------------------------------------------------
>
>                 Key: DROOLS-5080
>                 URL: https://issues.redhat.com/browse/DROOLS-5080
>             Project: Drools
>          Issue Type: Enhancement
>          Components: DMN Editor
>    Affects Versions: 7.33.0.Final
>            Reporter: Michael Anstis
>            Assignee: Michael Anstis
>            Priority: Major
>              Labels: drools-tools
>         Attachments: Screenshot from 2020-02-18 19-06-44.png, Screenshot from 2020-02-18 19-07-07.png
>
>
> I am working on reproducing the use cases from the DMN Method and Style book, and while following their methodology was unable to create the same behavior documented from Trisotech tooling, the so called "Decisions first". In this methodology the practitioner starts from the DRD definition of decisions, inputs and types; and then follows to create the decision tables and calculations from top to bottom.
> While creating the decision table that requires an input and a defined output of a "supporting decision", the decision table generated when selecting the expression type of the decision comes with no reference to the required supported decision.
> More clarity in this mojo: https://mojo.redhat.com/docs/DOC-1215621#jive_content_id_DRD_Supporting_decisions
> and in the steps to reproduce.



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