The Camunda import takes a Camunda file (.bpmn) and converts it to the BPM definition.

The bpm steps and properties are read from the model in a fairly intuitive way: each entity is a bpm step, each link is a flow attached to the source. Global process name and properties are read from the model

Ensure that the model meets the following requirements:

  • Give the overall model a meaningful id.
  • Set the processName property of the overall model to something meaningful.
  • Add more process-level attributes as overall properties.
  • Give each process (swimlane) a meaningful id that reflects the role and a name. Role-level properties are added to the global properties, by adding a role. prefix. This can be useful for adding the standard connection path property, @{data:init.connectionPaths.supplier}, to each role.
  • Ensure one of the processes has an id of "owner", and that the one and only start event is in that process. Give the start event an id of "start".
  • Give each step a meaningful id and name.
  • Use the properties of each step to set stepType and to add any further step attributes.
  • Use flow properties to indicate flow logic: state for process execution, status for business process status rules (user menus). Add properties to the flows.

You can use exclusive gateways as switches. The links from them aremerged into steps that link to the gateway,.

If you want to reference a process definition, status rules, form or file in the process, use the syntax ${action:ref}. Available actions are processDefinition, statusRules, form and fileInfo.

The Camunda Importer type can be used to import a Camunda model. It derives the appropriate process definition and status rules. The BPM process definition, step types and properties can use placeholders such as ${action:ref}. These will be resolved against the properties node. Available actions are processDefinition, statusRules, form and fileInfo. For example, if you want to reference a form in process definition, use the syntax ${form:formRef}, and then bind formRef to your form node in the properties node.