[
https://issues.redhat.com/browse/DROOLS-5080?page=com.atlassian.jira.plug...
]
Michael Anstis updated DROOLS-5080:
-----------------------------------
Description:
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_d...
and in the steps to reproduce.
*_Acceptance criteria_*
- Create a new DMN model
- Add an {{InputData}}
- Add a {{Decision}}, called {{A}}
- Add another {{Decision}}, called {{B}}
- Link the {{InputData}} to {{A}}
- Link the {{B}} to {{A}}
- Edit {{A}} and set its expression to {{DecisionTable}}
- It should have input columns for the {{InputData}} and {{B}}.
- You should be able to use _built in types_ and custom types (including structures).
was:
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_d...
and in the steps to reproduce.
[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_d...
and in the steps to reproduce.
*_Acceptance criteria_*
- Create a new DMN model
- Add an {{InputData}}
- Add a {{Decision}}, called {{A}}
- Add another {{Decision}}, called {{B}}
- Link the {{InputData}} to {{A}}
- Link the {{B}} to {{A}}
- Edit {{A}} and set its expression to {{DecisionTable}}
- It should have input columns for the {{InputData}} and {{B}}.
- You should be able to use _built in types_ and custom types (including structures).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)