Source: ACTICO ( Daniel Thanner)
Some built-in functions has optional parameters. Chapter 10.3.4 describes "Whenever a parameter is outside its domain, the result of the built-in is null."
Should the following call to a built-in function result to null?
The optional parameter "flags" of the built-in function replace() is null. Parameter domain is string as stated in table 60 on page 133. Null is not in the domain of type string.
This topic was already discussed in the DMN TCK. We think that the behavior should be the same as the function is called without the optional parameter:
Clarification in the specification is appreciated.
May be we can change the sentence in chapter 10.3.4 on page 130 to: "Whenever a parameter is outside its domain, the result of the built-in is null. If null is passed as value to an optional parameter, the built-in behaves like no value is passed."
Reported: DMN 1.1 — Tue, 10 Oct 2017 14:32 GMT
Disposition: Deferred — DMN 1.3
RTF 1.3 is ending
Thank you for reporting the issue; it is likely valid but unfortunately the DMN 1.3 revision task force ran out of time before a member was able to resolve it. The issue will be deferred to the next revision task force.
Updated: Mon, 30 Mar 2020 19:50 GMT