In Business Process Model and Notation (BPMN), the Sub-Process is a powerful element that allows you to encapsulate a set of activities into a single, reusable task. While a standard Sub-Process acts as a single step in a workflow, it becomes significantly more powerful when equipped with specific markers. These markers define advanced behaviors, such as repeating a sequence, executing tasks in parallel, or handling compensation.

This tutorial focuses on the Loop Marker, one of the five distinct markers defined by the BPMN specification. We will explore its function, how to implement it, and why it is critical for creating robust, real-world process models.

Understanding the Loop Marker

The Loop Marker is represented by a curved arrow icon located at the bottom of the Sub-Process rectangle. When applied, this marker fundamentally changes the execution behavior of the contained elements.

By default, a Sub-Process is executed exactly once: the flow enters the subprocess, executes the internal activities, and then exits. However, when you attach a Loop Marker to a Sub-Process, you are instructing the engine that this entire block of logic must repeat itself.

Key characteristics of the Loop Marker include:

• Sequential Repetition: The internal activities of the Sub-Process are executed in a continuous cycle.
• Termination Condition: The loop continues until a specific condition is met. This is usually defined by an exit condition on the outgoing sequence flow.
• Visual Clarity: It keeps the main process diagram clean by hiding the complexity of the iteration logic within the sub-process.

How to Apply a Loop Marker in Visual Paradigm

Using Visual Paradigm, a leading BPMN tool, applying a loop marker is straightforward and visual. Follow these steps to model a process that requires repetition:

1. Create the Sub-Process: Drag a Sub-Process element from the palette onto your canvas. Double-click it to open the internal editor and add your specific activities.
2. Open the Properties: Right-click on the Sub-Process border and select Properties from the context menu.
3. Select the Marker Type: Navigate to the Marker tab within the properties dialog.
4. Choose Loop: Select the Loop option from the list of available markers (Loop, Multi-Instance, Compensation, Ad-Hoc, Compensation and Ad-Hoc).
5. Configure Conditions: To prevent an infinite loop, you must define an exit condition on the sequence flow leaving the Sub-Process. For example, a condition like count < 10 ensures the loop stops after 10 iterations.

Implementation Example: Validating User Input

Consider a scenario where a system requires a user to enter data that must meet a specific format. If the data is invalid, the user must be prompted again. You can model this “retry” logic using a Sub-Process with a Loop Marker.

Inside the Sub-Process, you might have a task called Validate Data. The flow would look like this:

Sub-Process: [Loop Marker]
  |
  |---> Task: Validate Data
  |
  +---> (Internal Logic)
        |
        +---> Decision: Is Valid?
              |-- Yes --> Exit Sub-Process
              |-- No  --> (Flow back to Validate Data)

In this architecture, the Loop Marker ensures that the Validate Data task is executed repeatedly until the “Is Valid?” decision returns true.

Loop vs. Standard Sequence Flows

It is a common misconception that one should simply draw a sequence flow back to the start of a process to create a loop. While this is technically possible with standard tasks, using a Loop Marker on a Sub-Process offers several architectural advantages:

• Encapsulation: The internal logic of the loop is hidden, keeping the parent process diagram readable.
• Standardization: It adheres strictly to the BPMN 2.0 specification for sub-process behaviors, ensuring better compatibility with execution engines.
• Debugging: Many BPMN engines can easily pause or step through a looped Sub-Process, making it easier to debug iteration logic compared to complex, nested sequence flows.

Conclusion

The Loop Marker is an essential tool for any BPMN modeler looking to represent iterative logic cleanly and effectively. By encapsulating repetitive tasks within a Looped Sub-Process, you can create models that are not only visually appealing but also logically sound and easy to execute. When using Visual Paradigm, ensure you always pair the Loop Marker with a clear exit condition to guarantee your process terminates correctly.