[I] Provide decision table analysis even with null values in input columns [incubator-kie]

["hanjoosten (via GitHub)" <gi...@apache.org>]

hanjoosten opened a new issue, #6957:
URL: https://github.com/apache/incubator-kie/issues/6957

   Sometimes it is convenient to have optional input values in a decision table. The semantics is clear: Either there is a value, which has to be of the specified domain, or there is no value, which is denoted by `null`. Unfortunately there is no way in DMN to distinguish between these to (eg `Number` or `Optional<Number>`)
   Even if `null` values are provided, the decision table works as one would expect. However, the decision table analysis currently cannot cope with null values in the input. The user now has two options:
   
   1. "Externalize" the null checks in a sub decision, something that happens "before" the DT, so to check the "special handling" of null values, in order to have the DT only deal with the proper domain. This goes arguable at the expense of conciseness and readability of the decision. 
   2. Keep the null values in the decision table, and live without the decision table analysis. It goes without saying that this is undesirable. 
   
   This is a plea to enhance the decision table analysis to cope with Optional values.
   
   Note: See also [this discussion at Zulip](https://kie.zulipchat.com/#narrow/stream/232676-kogito/topic/.E2.9C.94.20How.20to.20force.20decision.20table.20analysis.3F)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org