Skip to content

BPMN Validation

Overview

With BPMN Validation, process models are automatically checked for errors and potential issues. Validation runs continuously during editing and displays results directly in the toolbar.

In Brief

During process modeling, rules are automatically checked – e.g., whether start and end events are present or whether all elements have a business label. Issues are displayed as a badge in the toolbar and can be located directly in the diagram with a click.

Why This Is Helpful

Errors are detected during modeling, not just at deployment. This saves time and prevents faulty process executions.

Benefits

  • ⚡ Real-time Feedback: Validation occurs automatically with every change to the diagram.
  • 🎯 Direct Navigation: Clicking on an issue selects and centers the affected element in the diagram.
  • 🌍 Multilingual: Error messages are displayed in German and English, depending on language settings.
  • 🔧 Extensible: In addition to standard BPMN rules, Pantarey-specific rules are checked.
Validation badge in toolbar
Warnings and errors are displayed in the toolbar

Using Validation

Display Results

  1. The Process Designer is opened.
  2. The warning symbol (validation) is displayed in the toolbar.

  3. The badge number shows the number of issues found:

    • Green: No issues found.
    • Orange: Only warnings present.
    • Red: At least one error present.

  4. The symbol is clicked to open the issue list.

Dropdown with validation results
The dropdown shows all found issues with element ID and description.

Find Element in Diagram

  1. The issue list is opened (click on the warning symbol).
  2. An entry is clicked.

  3. The affected element in the diagram is:

    • Selected (outlined in blue).
    • Centered (view automatically scrolls to the element).

Note

Validation is automatically executed with every change to the diagram. Manual triggering is not required.

Validation Rules

Errors

Errors are critical issues that should be resolved before deployment.

Rule Description
Start event required Every process must have at least one start event.
End event required Every process must have at least one end event.
Single event definition An event may only have one definition (e.g., timer or message, not both).

Warnings

Warnings indicate potential issues that should be reviewed.

Rule Description
Unconnected elements An element has no incoming or outgoing connections.
Gateway join/fork A gateway should not merge and branch simultaneously.
Implicit split An element has multiple outgoing flows – a gateway should be used.
Implicit end An element (except end event) has no outgoing flow.
Implicit start An element (except start event) has no incoming flow.
Overlapping elements Two or more elements overlap in the diagram.
Business label required Activities, events, and gateways require a valid business label.

Best Practices

Process Design

  • Business labels are assigned to all elements – they appear in logs and the process overview.
  • Start and end events are not forgotten.
  • Gateways are used for branching, not implicit splits.

Using Validation

  • The issue list is regularly checked, especially before deployment.
  • Errors (red) are always resolved.
  • Warnings (orange) are reviewed – not every warning needs to be resolved.

Clarity

  • Overlapping elements are avoided – they make readability difficult.
  • Unconnected elements are removed or properly connected.

Troubleshooting

Validation Shows No Results

Cause: The diagram has not been loaded or modified yet.

Solution:

  1. A small change is made to the diagram (e.g., move an element).
  2. Validation is automatically triggered.

Element Not Found on Click

Cause: The element no longer exists in the diagram.

Solution:

  1. The element may have been deleted.
  2. A change to the diagram triggers a new validation.
  3. The issue list updates automatically.

Error Messages Displayed in Wrong Language

Cause: The language is determined during validation.

Solution:

  1. The desired language is selected in settings.
  2. A change to the diagram triggers a new validation.
  3. New messages are displayed in the current language.

FAQ – Frequently Asked Questions about BPMN Validation

Is validation executed automatically?
Yes. Validation is automatically executed with every change to the diagram (with a short delay for performance).

Do I need to fix all warnings?
No. Warnings are hints about potential issues. Some are intentional depending on process design (e.g., implicit end for certain patterns).

Can I disable rules?
Currently, rules cannot be individually disabled. The rules are configured to be useful for most processes.

Does validation block deployment?
No. Validation is an advisory system. Even with errors, a process can be deployed – however, fixing errors beforehand is recommended.

Are custom fields validated?
Yes. The business label is a Pantarey-specific field and is checked for presence.

How often is validation executed?
Validation is executed with every change.