-
Key: DMN17-24
-
Status: open
-
Source: Decision Management Solutions ( James Taylor [X] (Inactive))
-
Summary:
I remember discussions about allowing "-" in conclusions to mark an unspecified conclusion in a decision table. This would allow some of the conclusions in a multiple output decision table to be marked as "unspecified" where there was no output relevant for that conclusion for a specific rule and to allow rules in multi-hit tables to show that a particular combination of conditions had been considered but did not result in anything being added to the result set.
However the standard as written says that an output entry must adhere to the literal expression grammar, and '-' is not allowed. You have to return some FEEL value, e.g. 0, false, "N/A", null, etc. -
Reported: DMN 1.1 — Mon, 13 Jun 2016 21:41 GMT
-
Updated: Fri, 21 Jun 2024 17:56 GMT
DMN17 — Unspecified conclusion is not supported
- Key: DMN17-24
- OMG Task Force: Decision Model and Notation 1.7 RTF