The Camunda BPM Connector is currently being developed. The information on this page is subject to change.
Interface to Camunda BPM
Information mapping from Camunda BPM to TASKANA
| Information | Source | Target | Comment |
|---|---|---|---|
| Domain | Extension property 'domain' from BPMN model. | Task.domain | |
| Classification | Extension property 'classification-key' from human task in the BPMN model. | Task.classification_key | In TASKANA, each task is associated with a classification. This concept does not exist in Camunda BPM. Therefore the additional required information is stored at the human task in the BPMN model. This way, each human task in the process can have its own classification. |
| Taskname | Task.name | Task.name | |
| Description | Task.description | Task.description | |
| Assignee | Task.assignee | Task.owner | |
| Due | Task.due | Task.due | |
| Priority | Task.priority | - | Priority will be initialized from the configuration of the associated classifications. |
| Task.creator | (Technical) user of the adapter | ||
| Workbasket | Extension property 'workbasket-key' from human task in the BPMN model. | Task.workbasket_key | |
| Custom attributes | List of relevant process variables (see comment) | Task.custom_attributes | Extension property 'taskana-attributes' from BPMN model contains a comma-seperated list of process variable names, which should be copied to TASKANA. These variables will be stored in the generic JSON structure 'custom_attributes'. |