Key takeaway: When selecting BPMN tools, the first step is to decide whether you want to document a process, model it according to the standard or actually run it. Excel is primarily used for data collection, draw.io and Visio for visual documentation, and Camunda for BPMN-based modeling and process execution. As a business workflow platform, xFLOWer may belong on your shortlist when the goal is to manage tasks, responsibilities, deadlines and related case data. Standard BPMN import capabilities and support for individual elements must be verified separately.
The question “Which is best?” is therefore misleading on its own. An approval process mapped out collaboratively in a workshop and an auditable case management process integrated with multiple systems have different requirements. In this installment of the BPMN 2.0 in Practice series, we examine which tools suit which types of work, and where implementation beyond diagramming begins.
Practical focus: This series is not a complete BPMN 2.0 reference manual—the official notation set is far broader, and here we focus on the most essential elements and practical workflows used in everyday operations.
1. Three categories: drawing, modeling and execution
A drawing tool helps visualize the process. It lets us place boxes, arrows, participants and notes on a diagram. The diagram can be understandable even if the application does not validate BPMN rules. This may be suitable for discussions, but it does not in itself confirm that the model is correct.
A BPMN modeler works with the concepts defined by the standard: events, activities, gateways and connections. Some tools also support modeling through validation checks. An important distinction is that displaying standard notation does not necessarily mean the tool provides standard BPMN 2.0 XML export that another system can process.
An execution platform manages specific process instances: it assigns tasks, waits for data, calls services or responds to timer events. However, a workflow platform may also use its own configuration model. BPMN compatibility should therefore be established through documentation and testing, rather than the symbols displayed on screen.
2. BPMN tools comparison table
The table below shows typical use cases. Exact capabilities may also depend on the product version, edition, deployment and associated components.
| Tool | Primary role | BPMN and validation | Process execution | When is it appropriate? |
|---|---|---|---|---|
| Excel | Data collection, process inventory | Can illustrate processes using shapes; not a BPMN modeler | Not a BPMN execution engine on its own | For collecting steps, responsible parties and exceptions |
| Visio | Visual documentation | BPMN templates and validation in the relevant editions | Not a BPMN execution engine on its own | For detailed business process diagrams |
| draw.io | Fast, collaborative diagramming | BPMN shapes; notation must be reviewed for correctness | Not a process execution platform | For workshops and explanatory diagrams |
| Camunda | BPMN modeling and execution | BPMN 2.0 models; supported elements determine what can be executed | Yes, with the runtime environment | For process orchestration across systems |
| xFLOWer | Running business workflows | BPMN import and element mapping must be clarified separately | Yes, as a workflow platform; this is not the same as executing any arbitrary BPMN file | For assessing the digitalization of task-driven case handling and approvals |
An important distinction: draw.io's native XML file is not the same as the BPMN 2.0 XML format. Similarly, a BPMN diagram created in Visio cannot automatically be considered a process definition that can be loaded into another engine. Portability should be tested with an actual sample file.
3. Seven numbered criteria for choosing a tool
- What will the tangible outcome be? If the expected output is a training diagram, do not start with the capabilities of the execution engine. If task assignment and deadline management are required, however, comparing drawing features alone is not enough.
- Who will create and maintain it? Business analysts, process owners and developers may need different working interfaces. Have them try making the same change, such as adding a new approval branch.
- How important is standards-based transfer? Check BPMN 2.0 XML import and export, as well as custom extensions. Successfully loading a file does not prove that all execution settings have been transferred.
- What errors does the tool detect? Checking notation rules, executability and business logic are separate matters. The application may not flag missing delegation arrangements or an incorrectly chosen value threshold.
- What integrations are needed? Take stock of business systems, document repositories, authentication solutions and notification channels. Clarify not only whether an integration exists, but also how errors are handled and who is responsible for operating it.
- How can changes be tracked? Documentation may require version control, while execution may also require traceability of process instances and changes. Ask what happens to cases already in progress when a new version is introduced.
- What is the total investment required? Beyond licensing, consider modeling, configuration, integration, testing, training and support. A low initial cost does not necessarily mean simpler long-term operation.
4. Practical test: approving a purchase request
Consider a simple case: an employee submits a purchase request, a manager makes a decision, and financial approval is also required above a specified value threshold. If rejected, the request is closed; if information is missing, it is returned to the requester. The rules must be clarified before creating the diagram.
Prepare in Excel, align using a diagram
Excel is useful for collecting the steps, responsible parties, input data and possible outcomes. draw.io or Visio can then help build a shared understanding. Lanes can represent roles within the organization, activities represent the work, and gateways represent branching points.
Approval and rejection following the manager's decision typically form an exclusive branch. If two checks must run independently of each other, a parallel branch may be needed. If the next step is determined by whichever happens first—a response or a deadline expiring—an event-based approach can be considered.
Testing the same process in operation
For a model intended for execution, you must also specify who receives the task, what data they can see and how the decision is recorded. In Camunda, execution settings and application integrations are attached to the model. When evaluating xFLOWer, ask for a demonstration of the same business scenario, including the specific configuration.
Do not test only the happy path. Also test requests for missing information, rejection, an absent approver and a failed system integration. These scenarios reveal whether the tool is suitable for day-to-day operations.
5. How does a diagram become an executable process?
Implementation work bridges the gap between a model and a working solution. BPMN can describe the control logic, but a complete business application also requires a data model, a user interface, permissions and integrations. A standards-compliant diagram is therefore not a finished application.
- Define the behavior precisely: every decision should have a clear condition, and every waiting state should have a defined way to proceed.
- Assign the data and roles: which fields are mandatory, who can make changes, and who can make decisions?
- Implement the integrations: system calls, document management, notifications and error alerts.
- Test, then operate: check exception handling, logging, permissions and change procedures.
When choosing xFLOWer, it is important to clarify how the agreed process can be mapped to the platform’s functionality. Implementing a process based on BPMN and directly executing a BPMN file are two distinct capabilities. It is worth specifying this as a separate requirement in the request for quotation.
6. Related Practical BPMN 2.0 Topics
Beyond tool selection, modeling expertise is also essential. Further articles in this series address the following topics:
- BPMN 2.0 elements explained with examples: the role of events, activities, gateways and lanes in a process.
- Exclusive, parallel and event-based gateways: when to use each? Distinguishing between decisions, concurrent work and waiting for events.
- The 10 most common BPMN modeling mistakes: ambiguous branches, incorrect connections and missing exception handling.
- BPMN vs. flowcharts vs. UML activity diagrams: choosing a notation based on the audience and the task.
- How does a BPMN diagram become an executable process? The additional technical and organizational details required for execution.
Summary: not every process needs an execution engine, but a polished diagram is no substitute for running a process. Let your objectives, standards-based portability and a trial with a real process guide your choice of BPMN tools.
Would you like to see the difference in your own process? Consult xFLOWer’s experts and bring a specific approval or case management example. This will help clarify the requirements for implementation, integration and operation.
This article is part of our complete guide: BPMN 2.0 in Practice: A Complete Guide from Modeling to a Working Process
xFLOWer.ai
Design the process behind this article – for free!
AI reads the processes hidden in this article; open any of them in xFLOWer.ai with one click.
