-
Key: DMN12-176
-
Status: closed
-
Source: Red Hat ( Edson Tirelli)
-
Summary:
In DMN, null seems to be used mostly to indicate absence of a value or the presence of an error.
When using the Decision Table hit policies C and C#, failure to match rules in the decision table does not mean either. In such cases, the most appropriate and expected result should be:
- for hit policy C: an empty list
- for hit policy C#: the value 0
-
Reported: DMN 1.1 — Tue, 18 Jul 2017 19:01 GMT
-
Disposition: Resolved — DMN 1.2
-
Disposition Summary:
hit policies C and C# do not return null when there are no matches
See attached Word file
-
Updated: Wed, 3 Oct 2018 14:17 GMT
-
Attachments:
- Collect hit policies default values (Issue 176) - OMG Proposal (version 2).docx 16 kB (application/vnd.openxmlformats-officedocument.wordprocessingml.document)
DMN12 — Decision Table hit policies C and C# should not return null when there are no matches
- Key: DMN12-176
- OMG Task Force: Decision Modeling and Notation 1.2 RTF