Autopilot transforms a business process defined within a BPMN file into an Automation Anywhere process outline. BPMN files with complex processes might include structures that are unsupported or only minimally supported, and are subject to certain limitations.

To ensure a successful transformation with Autopilot, the process defined within the BPMN file will need to adhere to the following guidelines and limitations.

  • To ensure you are starting with a valid BPMN file and structure, use a BPMN 2.0-compliant editor such as https://bpmn.io to verify the BPMN file loads without any consistency errors.
  • Since multiple processes are not supported within a BPMN file, ensure your BPMN file contains only a single process before uploading.
  • Ensure your BPMN file does not contain embedded processes or swim lanes, as they are not supported.
  • The automation outline created will only have the information from the prose within the BPMN to work with. Add text annotations to all tasks to elaborate on the automation actions to be performed within the task.
  • Your BPMN file must have fully connected flows, as orphaned flows are not supported during conversion. Separate any non-connected flows into individual BPMN files.
  • The BPMN file must include exactly one start node and at least one end node.
  • Each branch path originating from a gateway must contain at least one task element before converging with another path or reaching an end node. Empty sequence flows (direct gateway-to-gateway connections) are not supported.
  • BPMN transformation does not support Process Engine 2.0 split and merge patterns. Branching logic will be represented as nested if/then blocks to reflect different BPMN branch structures within the transformed process. This may require implementing specific task or activity logic to properly define branching conditions within the BPMN diagram.
  • Only exclusive (XOR) gateways are supported. All branching logic will be converted into nested if/then conditional blocks.
  • Parallel (AND) gateways have minimal support, as they require concurrent execution paths.
Refer to the following image for an example BPMN file.
bpmn file example