-
Sub-task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
None
AT
In DMN Wrapper, evaluation listeners can be registered
Reasoning
- The evaluation listener is present in the legacy DMN Engine and provides more context about the evaluation beyond the end-result (e.g., intermediate results, results of all rules and not only the ones chosen by the hit policy, etc.)
- It fits perfectly into the extensibility story of Camunda BPM to provide more evaluation context via a plugin point
- It makes migrating from the legacy DMN Engine to the Scala DMN Engine more smooth
Solution ideas
- Notify listener via Scala DMN Engine Audit log listener
- Reuse legacy DMN Engine interface DmnDecisionEvaluationListener
- Deprecate DmnDecisionTableEvaluationListener
- Reuse legacy DMN Engine interface DmnDecisionEvaluationListener
- Design a Java-friendly wrapper which allows using all capabilities the Scala DMN Audit Log provides
- Deprecate DmnDecisionTableEvaluationListener and DmnDecisionEvaluationListener
See
- https://docs.google.com/document/d/1fvp2qf75W7VBSFjfHVz3iRN4Ynq349R6qtq3eP62opw/edit#bookmark=id.2bma215zkkc2
- https://docs.google.com/document/d/1fvp2qf75W7VBSFjfHVz3iRN4Ynq349R6qtq3eP62opw/edit#bookmark=id.hbmt06revau0
- https://docs.google.com/document/d/1fvp2qf75W7VBSFjfHVz3iRN4Ynq349R6qtq3eP62opw/edit#bookmark=id.93ve3abueb7c