Decision Task

A decision task can be used to invoke a DMN 1.3 decision from a case.

A decision task is a regular task that requires a decisionRef attribute that references a decision definition by its key. Such a decision task can be defined as follows:

<decisionTask id="checkCreditDecision"
              name="Check credit"
              decisionRef="checkCreditDecision" />

Instead of the decisionRef attribute it is also possible to use an expression which must evaluate to a key of a decision definition at runtime.

<decisionTask id="checkCreditDecision" name="Check credit">

One of the attributes decisionRef or decisionRefExpression must be present.

The referenced decision definition is resolved at runtime. This means that the referenced decision can be deployed independently from the calling case, if needed.

A decision task in state ENABLED can be started manually using the CaseService as follows:


When the decision task instance becomes ACTIVE, the referenced decision is evaluated synchronously. As a consequence, the decision task is always executed as blocking, because the engine does not distinguish between a blocking and a non-blocking decision task.

Transactional Behavior

The activation of the decision task as well as the evaluation of the decision are performed in the same transaction.

Decision Binding

By default, the decision task always evaluates the latest decision definition with the specified key. To specify a different version of a decision, it is possible to define a binding with the Camunda custom attribute decisionBinding. The following values are allowed for the attribute decisionBinding:

  • latest: use the latest decision definition version (which is also the default behavior if the attribute is not defined)
  • deployment: use the decision definition version that is part of the calling case definition’s deployment (note: this requires that a decision with the specified key is deployed along with the calling case definition)
  • version: use a fixed version of the decision definition, in this case the attribute decisionVersion is required

The following is an example of a decision task that calls the checkCreditDecision decision with version 3.

<decisionTask id="checkCreditDecision" decisionRef="checkCreditDecision"

Note: It is also possible to use an expression for the attribute decisionVersion that must resolve to an integer at runtime.

Decision Tenant Id

When the decision task resolves the decision definition to be evaluated it must take into account multi tenancy.

Default Tenant Resolution

By default, the tenant id of the calling case definition is used to evaluate the decision definition. That is, if the calling case definition has no tenant id, then the decision task evaluate a decision definition using the provided key, binding and without a tenant id (tenant id = null). If the calling case definition has a tenant id, a decision definition with the provided key and the same tenant id is evaluated.

Note that the tenant id of the calling case instance is not taken into account in the default behavior.

Explicit Tenant Resolution

In some situations it may be useful to override this default behavior and specify the tenant id explicitly.

The camunda:decisionTenantId attribute allows to explicitly specify a tenant id:

<decisionTask id="checkCreditDecision" decisionRef="checkCreditDecision"

If the tenant id is not known at design time, an expression can be used as well:

<decisionTask id="checkCreditDecision" decisionRef="checkCreditDecision"
  camunda:decisionTenantId="${ myBean.calculateTenantId(variable) }">

An expression also allows using the tenant id of the calling case instance instead of the calling case definition:

<decisionTask id="checkCreditDecision" decisionRef="checkCreditDecision"
  camunda:decisionTenantId="${ caseExecution.tenantId }">

Decision Result

The output of the decision, also called decision result, is not saved as case variable automatically. It has to pass into a case variable by using a predefined or a custom mapping of the decision result.

In case of a predefined mapping, the camunda:mapDecisionResult attribute references the mapper to use. The result of the mapping is saved in the variable which is specified by the camunda:resultVariable attribute. If no predefined mapper is set then the resultList mapper is used by default.

The following example calls the latest version of the checkCreditDecision and maps the singleEntry of the decision result into the case variable result. The mapper singleEntry assumes that the decision result only contains one entry or none at all.

<decisionTask id="checkCreditDecision" decisionRef="checkCreditDecision"
    camunda:resultVariable="result" />

See the User Guide for details about the mapping.

Name of the Result Variable

The result variable should not have the name decisionResult since the decision result itself is saved in a variable with this name. Otherwise an exception is thrown while saving the result variable.

Limitations of the Decision Task

To evaluate a referenced decision, the integration of the Camunda DMN engine is used. As a result, only DMN 1.3 decisions can be evaluated with a decision task. There is no option to integrate with other rule engines.

Camunda Extensions

Attributes camunda:decisionBinding, camunda:decisionTenantId, camunda:decisionVersion, camunda:mapDecisionResult, camunda:resultVariable
Extension Elements camunda:caseExecutionListener, camunda:variableListener
Constraints The attribute camunda:decisionVersion should only be set if the attribute camunda:decisionBinding equals version

On this Page: