Choosing the resource binding type
Camunda 8 offers version binding for linked processes, decisions, or forms. This allows you to deploy new versions without disrupting live processes, and prevents production outages.
You can choose the binding type for the linked target resource for the following BPMN process elements:
- Call activities
- Business rule tasks (if the DMN decision implementation is used)
- User tasks (if a Camunda Form is linked)
The binding type determines the version of the target resource used at runtime.
For example, for a call activity this would be the version of the called process to be instantiated.
Supported binding types
Camunda 8 supports the following binding types:
Type | Description |
---|---|
latest | Resolves to the latest deployed version of the target resource at the moment the process element is activated.
|
deployment | Resolves to the specific version of the target resource that was deployed together with the currently running version of the process in the same deployment.
|
versionTag | Resolves to the specific version of the target resource that is annotated with the given version tag.
Caution:
|
If the binding type is not explicitly specified in your BPMN diagram, latest
is used as the default.