Modelling processes with the BPMN designer

Why Is a BPMN Designer Essential for Your Team?

When it comes to documenting and improving organizational processes, the first challenge teams face is the lack of a common language. Everyone describes the process differently—one uses colorful arrows in PowerPoint, another uses text descriptions in Word, and another uses tables in Excel. The result? Confusion, different interpretations, and execution errors.

This is where the BPMN designer comes in. BPMN (short for Business Process Model and Notation) is an international standard for drawing business process diagrams. By using a good BPMN designer, you not only create a beautiful picture of the process, but you also produce a living, executable document that all team members—from business analysts to developers—understand in the same way.

In this article, instead of theoretical explanations, we will follow a practical path: from understanding the main components of a BPMN diagram, to building a real process, and finally producing a standard output for delivery to the technical or management team. If you are looking for a tool to move your processes out of a scattered state, this guide is for you.

Getting to Know the Main Components in a BPMN Designer

Before you start drawing shapes, you need to become familiar with the four main categories of elements in BPMN 2.0. This categorization helps you understand exactly what each element means and when you should use it.

1. Flow Objects

These are the heart of any BPMN diagram and come in three types:

• Event: Something that happens during the process. It is displayed as a circle. The Start Event is shown as a hollow circle, the End Event as a hollow circle with a thick border, and Intermediate Events as a double-lined circle.
• Activity: Work that needs to be done. It is displayed as a rounded rectangle. If the activity is simple, it is called a Task, and if it is a combination of several sub-processes, it is a Sub-Process, which is marked with a + sign at the bottom of the rectangle.
• Gateway: A decision point or branch in the process. It is displayed as a diamond. The most common type is the Exclusive Gateway, where only one path is selected from among several.

2. Connecting Objects

These elements show how flow objects are related to each other:

• Sequence Flow: A solid arrow that shows the order of activity execution.
• Message Flow: A dashed arrow that shows communication between two different participants (Pools).
• Association: A dotted line that links data or documents to activities.

3. Swimlanes

To show responsibilities, Pool and Lane are used. A Pool represents an independent participant (e.g., an organization or department), and a Lane specifies the subdivisions within the Pool (e.g., sales unit, support unit).

4. Artifacts

These are supplementary pieces of information: Data Object (a rectangle with a folded corner) to show input/output data, Text Annotation for additional explanations, and Group for visually categorizing elements.

Building a Real Process with a BPMN Designer

Now let's model a real example together: the order registration process in an online store. This example is simple but complete and covers all the key elements.

Step 1: Define the Scope and Participants

First, determine where the process starts and where it ends. In our example:

• Start: The customer registers their order.
• End: The order is delivered and final payment is made.
• Participants: Customer (external Pool), Store (main Pool with Lanes: order acceptance, warehouse, finance).

Step 2: Draw the Main Flow

In your BPMN designer, create a Pool for the store and build three Lanes inside it. Then add the following elements in order:

1. Start Event: "Receive customer order"
2. Task (in the acceptance Lane): "Check product availability"
3. Exclusive Gateway: "Is the product available?"
4. If yes: Task (in the warehouse Lane): "Pack and ship"
5. If no: Task (in the acceptance Lane): "Notify the customer and suggest an alternative product"
6. In both paths, reach the Task (in the finance Lane): "Issue invoice and receive payment"
7. End Event: "Order completed"

Step 3: Add Details and Data

Now add the details:

• Attach a Data Object named "Order Form" to the inventory check Task.
• Add a Text Annotation to the gateway: "Inventory check is performed automatically from the warehouse system."
• For the "product not available" path, add a Timer Intermediate Event: "Wait 24 hours for customer response".

Step 4: Validate the Model

Before exporting, ask yourself these questions:

• Does every path reach from Start to End? (Are there any dead-end paths?)
• Do all gateways have at least two outgoing paths?
• Do activity names start with a verb and are they clear? (e.g., "Check inventory" instead of "Inventory")
• Is the responsibility for each activity correctly placed in the relevant Lane?

Standard Output for Delivery to the Team

One of the most important advantages of using a BPMN designer is the ability to produce standard outputs usable by different teams. Here, we examine three common types of output.

1. Image Output (PNG/SVG)

This is the simplest type of output and is suitable for management documentation or presentations. Important note: before exporting, make sure the diagram is understandable at a glance. If your diagram has more than 15 main elements, you probably need to break it down into several sub-processes.

2. XML Output (BPMN 2.0)

This output is critical for the technical team. The standard BPMN 2.0 XML file can be loaded into process execution engines (such as Camunda or Activiti) to run the process automatically. Here is a simple example of the structure of this file:

<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL"
             xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI"
             targetNamespace="http://servernet.ir/process">
  <process id="orderProcess" name="Order Fulfillment" isExecutable="true">
    <startEvent id="start" name="Order Received"/>
    <task id="checkInventory" name="Check Inventory"/>
    <exclusiveGateway id="inventoryGateway" name="Inventory Available?"/>
    <sequenceFlow id="flow1" sourceRef="start" targetRef="checkInventory"/>
    <sequenceFlow id="flow2" sourceRef="checkInventory" targetRef="inventoryGateway"/>
  </process>
</definitions>

Note that in the XML output, each element must have a unique id, and all connections must be correctly referenced with sourceRef and targetRef. If you are using a good BPMN designer, this file is generated automatically, but knowing its structure helps you detect potential errors.

3. Analytical Documentation

Many BPMN designers offer analytical report output that includes the following:

• Number of activities, gateways, and events
• Detection of critical paths
• Identification of activities without an owner (those not placed in any Lane)
• Warnings about infinite loops

Choosing the Right BPMN Designer

There are many tools for BPMN modeling, from free browser extensions to enterprise platforms. When choosing, consider these criteria:

• Full BPMN 2.0 support: Not just basic elements, but also Boundary Events and complex gateways.
• Simulation capability: The ability to run the process with test data to find bottlenecks.
• Standard output: Ensure that the generated XML file is compatible with well-known execution engines.
• Team collaboration: The ability to comment and edit simultaneously for team members.

If you are looking for a hosted solution for your team, some cloud service providers like ServerNet enable the deployment of process modeling tools on cloud infrastructure so your team can focus on modeling without worrying about infrastructure.

Common Mistakes in BPMN Modeling

Finally, let's review a few frequent mistakes that even experienced modelers sometimes make:

1. Using a Gateway Instead of a Condition on a Sequence Flow

Sometimes you have only one outgoing path from an activity, but you need to apply a condition to it (e.g., "if the amount exceeds 1 million Toman"). In this case, there is no need for a gateway; just write the condition on the arrow itself. A gateway is only needed when you have at least two outgoing paths.

2. Forgetting Intermediate Events

Intermediate events (such as time delays, receiving messages, or errors) are an important part of real processes. If your process includes "waiting for manager approval," be sure to use an Intermediate Timer Event, not an empty Task.

3. Mismatch Between Element Names and XML Content

If you change the name of an activity after creating connections, make sure the XML output is updated. Some tools do this automatically, but if you are manually editing the XML file, be careful that the name and id of each element are consistent.

4. Ignoring the Level of Detail

A BPMN diagram should not show everything. If your process has more than 30 elements, break it down into several sub-processes. Each sub-process can have its own separate diagram that opens when you click on the + sign.

Conclusion

A BPMN designer is not just a drawing tool; it is a common language for communication between business and technical units. By following the principles we reviewed in this article—understanding elements, building the process step by step, producing standard output, and avoiding common mistakes—you can model organizational processes in a clear, measurable, and executable way.

Start with a small, real process. Share it with your team and get feedback. Soon you will see how a good BPMN diagram turns unproductive meetings into focused discussions and quick decisions.