-
Key: DMNFTF-35
-
Status: closed
-
Source: International Business Machines ( Mr. Christian De Sainte Marie)
-
Summary:
Whereas the items from InputData can be defined by associating an ItemDefinition to the InputData element, the only way to define the outcome of a decision is by associating a decisionLogic to the Decision, and an ItemDefinition to the decisionLogic.
Proposal: Add an outcomeDefinition association that is an ItemDefinition to Decision, and make the itemDefinition of a decisionLogic a derived attribute (or otherwise constrain the itemDefinition of the decisionLogic to be the same as the outcomeDefinition of the owning Decision).
-
Reported: DMN 1.0b1 — Tue, 21 Jan 2014 16:02 GMT
-
Disposition: Resolved — DMN 1.0
-
Disposition Summary:
Proposed resolution to add an optional outputDefinition attribute to the Decision element, and to require that the output definition of a decision be the same as the item definition of its decision logic, if they are all specified.
-
Updated: Tue, 21 Apr 2015 01:19 GMT
-
Attachments:
- DMN beta 3 corrected for issue 35.doc 4.48 MB (application/msword)
DMNFTF — No way to associate to a Decision the ItemDefinition of its outcome without defining decisionLogic
- Key: DMNFTF-35
- OMG Task Force: Decision Model And Notation 1.0 FTF