Options

History for DMN Decisions

After a decision definition has been evaluated either from a BPMN process, CMMN
case or through the Decision Service, the inputs and outputs are saved in the
History of the platform. The history entity is of type
HistoricDecisionInstance and has the event type evaluate.

History Level

History level FULL is required. Otherwise, no history
for decisions is created.

Query for evaluated Decisions

The History Service can be used to query for HistoricDecisionInstances. For
example, use the following query to get all history entries for a decision
definition with key checkOrder ordered by the time when the decision was
evaluated.

Note that the inputs and outputs of a decision are not included in the query
result by default. Call the methods includeInputs() and includeOutputs() on
the query to retrieve the inputs and outputs from the result.

In case the decision was evaluated from a process, information of the process
definition, the process instance and the activity is set in the
HistoricDecisionInstance. The same applies for decisions evaluated from
a case, where the history instance will reference the corresponding case
instances.

Additionally, if the decision is a decision table with hit policy collect and
an aggregator function, then the result of the aggregation can be retrieved by
the getCollectResultValue() method.

Note that the value may be the result of a type transformation in case the
input specifies a type.

Historic Decision Output Instance

The HistoricDecisionOutputInstance
represents one output entry of an
evaluated decision. If the decision is implemented as decision table, the
HistoricDecisionInstance contains one HistoricDecisionOutputInstance
for each output clause and matched rule.