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

For details about the history mechanism as such, refer to the History and AuditEvent Log.

History Level

History level FULL is required. Otherwise, no historyfor decisions is created.

Query for evaluated Decisions

The History Service can be used to query for HistoricDecisionInstances. Forexample, use the following query to get all history entries for a decisiondefinition with key checkOrder ordered by the time when the decision wasevaluated.

List<HistoricDecisionInstance> historicDecisions = processEngine
  .getHistoryService()
  .createHistoricDecisionInstanceQuery()
  .decisionDefinitionKey("checkOrder")
  .orderByEvaluationTime()
  .asc()
  .list();

Decisions which were evaluated from a BPMN business rule task can befiltered by the process definition id or key and process instance id.

HistoryService historyService = processEngine.getHistoryService();
List<HistoricDecisionInstance> historicDecisionInstances = historyService
  .createHistoricDecisionInstanceQuery()
  .processDefinitionId("processDefinitionId")
  .list();
historicDecisionInstances = historyService
  .createHistoricDecisionInstanceQuery()
  .processDefinitionKey("processDefinitionKey")
  .list();
historicDecisionInstances = historyService
  .createHistoricDecisionInstanceQuery()
  .processInstanceId("processInstanceId")
  .list();

Decisions which were evaluated from a CMMN decision task can be filteredby the case definition id or key and case instance id.

HistoryService historyService = processEngine.getHistoryService();
List<HistoricDecisionInstance> historicDecisionInstances = historyService
  .createHistoricDecisionInstanceQuery()
  .caseDefinitionId("caseDefinitionId")
  .list();
historicDecisionInstances = historyService
  .createHistoricDecisionInstanceQuery()
  .caseDefinitionKey("caseDefinitionKey")
  .list();
historicDecisionInstances = historyService
  .createHistoricDecisionInstanceQuery()
  .caseInstanceId("caseInstanceId")
  .list();

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

List<HistoricDecisionInstance> historicDecisions = processEngine
  .getHistoryService()
  .createHistoricDecisionInstanceQuery()
  .decisionDefinitionKey("checkOrder")
  .includeInputs()
  .includeOutputs()
  .list();

The Historic Decision Instance

The HistoricDecisionInstance contains information about a singleevaluation of a decision.

HistoricDecisionInstance historicDecision = ...;
// id of the decision definition
String decisionDefinitionId = historicDecision.getDecisionDefinitionId();
// key of the decision definition
String decisionDefinitionKey = historicDecision.getDecisionDefinitionKey();
// name of the decision
String decisionDefinitionName = historicDecision.getDecisionDefinitionName();
// time when the decision was evaluated
Date evaluationTime = historicDecision.getEvaluationTime();
// inputs of the decision (if includeInputs was specified in the query)
List<HistoricDecisionInputInstance> inputs = historicDecision.getInputs();
// outputs of the decision (if includeOutputs was specified in the query)
List<HistoricDecisionOutputInstance> outputs = historicDecision.getOutputs();

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

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

For more information on supported hit policies please see the DMN 1.1reference.

Historic Decision Input Instance

The HistoricDecisionInputInstance represents one input of anevaluated decision (e.g., an input clause of a decision table).

HistoricDecisionInputInstance input = ...;
// id of the input clause
String clauseId = input.getClauseId();
// label of the input clause
String clauseName = input.getClauseName();
// evaluated value of the input expression
Object value = input.getValue();
// evaluated value of the input expression as typed value
// which contains type information
TypedValue typedValue = input.getTypedValue();

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

Historic Decision Output Instance

The HistoricDecisionOutputInstance represents one output entry of anevaluated decision. If the decision is implemented as decision table, theHistoricDecisionInstance contains one HistoricDecisionOutputInstancefor each output clause and matched rule.

HistoricDecisionOutputInstance output = ...;
// id of the output clause
String clauseId = output.getClauseId();
// label of the output clause
String clauseName = output.getClauseName();
// evaluated value of the output entry
Object value = output.getValue();
// evaluated value of the output entry as typed value
// which contains type information
TypedValue typedValue = output.getTypedValue();
// id of matched rule the output belongs to
String ruleId = output.getRuleId();
// the position of the rule in the list of matched rules
Integer ruleOrder = output.getRuleOrder();
// name of the output clause used as output variable identifier
String variableName = output.getVariableName();

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

Cockpit

You can audit the evaluated decision definitions in the Cockpit webapp.

原文: https://docs.camunda.org/manual/7.9/user-guide/process-engine/decisions/history/