-
Key: DMN12-175
-
Status: closed
-
Source: ACTICO ( Daniel Thanner)
-
Summary:
On page 83 for DMN: "the result of the decision table is the sum of all the distinct outputs"
On page 137 for FEEL built-in function: "return the sum of the outputs"Same applies to count aggregation.
Why does a DMN decision table only aggregates distinct values, but a FEEL built-in function does not?
Is this difference between the DMN Decision Table in chapter 8 and the FEEL built-in function in chapter 10 the intended meaning?
-
Reported: DMN 1.1 — Fri, 26 May 2017 09:28 GMT
-
Disposition: Resolved — DMN 1.2
-
Disposition Summary:
remove 'distinct' from hit policy aggregation definitions
see attached Word document
-
Updated: Wed, 3 Oct 2018 14:17 GMT
-
Attachments:
- Hit policies collect aggregations (Issue 175) - OMG Proposal (version 1).docx 14 kB (application/vnd.openxmlformats-officedocument.wordprocessingml.document)
DMN12 — Different definition of hit policy collect aggregations in FEEL and DMN
- Key: DMN12-175
- OMG Task Force: Decision Modeling and Notation 1.2 RTF