-
Key: DMN17-9
-
Status: open
-
Source: ACTICO ( Daniel Thanner)
-
Summary:
The expected output of the built-in function string() should be defined for each type. Otherwise it is unclear what the result for a value, for example of type time, is. Is it the string literal or the full expression with built-in function time()?
// which FEEL expression is valid? string(time("11:00:00")) = "11:00:00" string(time("11:00:00")) = "time("11:00:00")"
Recommendation: Introduce a new table that lists example outputs for all types:
- null -> null
- boolean -> "true" or "false"
- string -> "This is a string"
- number -> "-1.234"
- date -> "2017-10-11"
- time -> "11:00:00.123" or "11:00:00.123+02:00" or "11:00:00.123@Europe/Paris"
- date and time -> "2017-10-11T11:00:00.123" or "2017-10-11T11:00:00.123+02:00" or "2017-10-11T11:00:00.123@Europe/Paris"
- days and time duration -> "P2DT3H4M5.123S"
- years and months duration -> "P2Y3M"
- list -> "[1,2,3]"
- context -> "{a: true, b: false}"
- range -> "[1..100]"
- unary test -> "> 10"
- function -> null
-
Reported: DMN 1.1 — Wed, 11 Oct 2017 09:02 GMT
-
Updated: Fri, 21 Jun 2024 17:56 GMT
DMN17 — Improve description of built-in function string()
- Key: DMN17-9
- OMG Task Force: Decision Model and Notation 1.7 RTF