Key takeaway: an executable BPMN process is more than an uploaded diagram. The model requires unambiguous execution rules, data, assigned responsibilities and, where necessary, system connections and error handling. The first step in implementing it in xFLOWer is therefore to clarify what the selected environment supports directly and what needs to be mapped through configuration or integration.
In this part of the “BPMN 2.0 in Practice” article series, we follow a purchase request approval process from diagram to live operation. The aim is not to make the diagram look better, but to create a solution that handles everyday exceptions and has clear accountability for its operation.
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. Check whether the model and the environment are compatible
BPMN 2.0 provides a common notation, but it does not guarantee automatic interoperability between all modeling and execution systems. A valid BPMN file may contain an element, extension or expression that the target environment does not support. Being able to read the file and being able to execute the process are two separate requirements.
A traditional flowchart primarily illustrates a process, an UML activity diagram can also be used to model systems and behavior, while BPMN provides detailed semantics for describing business processes. However, using the right notation does not in itself provide an execution specification. Statements that require human interpretation must also be converted into unambiguous rules for the process engine.
| Requirement | What needs to be clarified? | Acceptable outcome |
|---|---|---|
| Model compatibility | Are import and all elements used supported? | A verified list of supported features or a mapping plan. |
| Data model | Which fields and documents are required? | Data types, mandatory fields and validation rules documented. |
| Task assignment | Who works on each step? | Roles, delegation arrangements and permissions defined. |
| Decision logic | What determines the next branch? | Unambiguous, testable conditions. |
| Integration | How is data exchanged? | A documented connection and error-handling rule. |
| Operations | Who detects and resolves stalled processes? | Defined procedures for logging, monitoring and intervention. |
When implementing xFLOWer, these points must be verified against the documentation for the specific version and setup, and with the implementation team. If direct BPMN import has not been confirmed, we use the diagram as an implementation specification and map its logic through configuration. This can still produce an automated process, but it does not automatically qualify as native BPMN execution.
2. Define the data and roles
In our example, an employee submits a purchase request, a manager makes a decision, finance reviews it if necessary, and the approved request is then entered into an enterprise resource planning system. The diagram may show this in five boxes, but making it work requires more information.
The data model should be more precise than the form outline
Record the request ID, requester, amount, currency, cost center, justification and attachments. Each field should have a data type, a mandatory or optional status, and a validation rule. Also determine where each piece of data comes from: the requester, a master data source or a calculation.
If the threshold is defined in forints, currency conversion rules must also be specified for foreign-currency requests. “High-value purchase” is not an executable condition; a comparison based on a specified currency and an exact amount threshold can be. Do not leave the handling of missing data to unpredictable system behavior either.
A lane is not a permission
A BPMN lane helps illustrate responsibilities; it does not automatically create a user group or an access rule. You must separately define who can view, modify and approve the request. The “manager” role also needs a rule for identifying the relevant person: for example, the current manager of the requester’s organizational unit.
- What happens during leave or when a position is vacant?
- Can someone approve their own request?
- Is a new approval required if the amount changes later?
- Who can access confidential attachments?
3. Clarify control flow and integrations
Check the execution semantics of BPMN elements separately. The start event specifies what initiates the case; an activity represents work to be done; a gateway controls the paths; and a lane organizes responsibilities. In the procurement example, submitting a form can start the process, while managerial approval can be a human task.
Use an exclusive gateway when only one path can continue, such as approval or rejection. Conditions must not overlap, and handling must be defined for cases where none of them are met. A parallel gateway is appropriate when both legal and financial reviews are required and can be performed independently.
An event-based gateway is appropriate when the outcome depends on which event occurs first: for example, the supplier's response arrives or the waiting period expires. This does not involve evaluating data conditions. Before implementation, support for this element in the target system must also be verified.
For integrations, a label saying “send to ERP” is not enough. The call method, field mapping, authentication, response processing, and timeout handling must all be specified. Do not store secrets in the diagram text.
Document when a failed operation can be retried and how to prevent duplicate orders. If the external system has already created the item but the response was lost, blindly resending the request may produce an incorrect result. A unique business identifier and a reconciliation procedure can help ensure safe recovery.
4. Map the model to the xFLOWer environment
Start configuration based on the approved specification in a separate test environment. The sequence below is an implementation plan, not a description of menu options in a specific xFLOWer version: available features and connectivity options must be checked in advance.
The procurement process can also be built directly in xFLOWer. In xFLOWer.ai, business users can create an executable workflow from a text description, complete with related forms and business rules, and then test it using specific requests.
- Record the model version. Make it clear which approved diagram the team is working from.
- Set up data management. Create the fields, forms, document links, and validation checks.
- Configure task assignment. Assign steps to roles and manage substitution arrangements.
- Implement the control flow. Map branches, waits, deadlines, and returns for revision.
- Connect external systems. Start with test connections and controlled data.
- Make operations traceable. Define the required statuses, log entries, and notifications.
- Verify alignment with requirements. Ensure every business rule has a corresponding configuration solution and test case.
Keep the mapping traceable: it must be clear which configured step implements the diagram's “managerial approval” task. This avoids having to reconstruct the relationships when making changes later. If you deviate from the original model, update the documentation as well.
5. Test exceptions, not just the happy path
Successfully clicking through the process is necessary, but not sufficient. Alongside technical testing, acceptance testing with business users is also required. For each case, record the input, expected result, and verifiable evidence.
- Boundary values: what happens exactly at the approval amount threshold?
- Return for revision: can the request be corrected, and is its history preserved?
- Parallel branches: does the process correctly wait for the required reviews?
- Access permissions: can unauthorized viewing and decision-making be prevented?
- Integration error: can timeouts, retries and invalid responses be handled?
- Deadline: does the right person receive the notification or escalation?
Among common modeling errors, contradictory conditions, incorrectly connected parallel branches and return loops that cannot be closed are particularly dangerous. These should be identified during the model review. Testing can only be completed once the process owner has also approved the intended behavior, not merely when technical errors have been eliminated.
6. Roll out in a controlled manner and measure performance
For go-live, designate a responsible owner, a launch date and time, support procedures and a rollback plan. Cases already in progress require a separate decision: will they be completed on the previous version, or undergo a controlled transition? Automatic migration must not be assumed.
Start with a clearly defined user group and monitor turnaround times, stalled tasks, returns and integration errors. Define the start and end points for metrics in advance. Initial experience can also inform refinements to rules, forms and notifications.
Summary: an executable BPMN process depends on alignment between an accurate model and a verified execution environment. Data handling, task assignment, decision logic, system integrations where needed, and error handling together make the diagram operational. When implementing it in xFLOWer, every important business rule should have a verifiable counterpart.
Ready for the next step? Choose a well-defined process and arrange a technical consultation with the xFLOWer team. Bring your BPMN diagram, data fields, roles and list of connected systems: these provide a solid basis for clarifying implementation requirements.
This article is part of our complete guide: BPMN 2.0 in Practice: A Complete Guide from Modeling to an Operational 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.
