DMN hit policy P not possible


#1

The simple Camunda DMN engine does not support hit policy P (https://docs.camunda.org/manual/7.5/reference/dmn11/decision-table/hit-policy/).

Apparently, the more advanced scala dmn engine does. (https://github.com/camunda/dmn-scala)

In dmn-js it is possible to enter P as hit policy, but I am unable to define allowed values for output entries, which would be required for P to work. Therefore I cannot use a dmn-js decision model to express a P hit policy for dmn-scala.

Is it possible to define allowed values for outputs somehow in dmn-js? Otherwise I would like to see this as a feature request.


#2

Currently allowed values are only supported for inputs with the type string. If you’d like to be able to configure allowed values feel free to open a feature request.


#3