Disallow dummy conditions on outgoing sequence flows from OR/XOR gateways

[till-stadtler]

The rule should detect the following modeling patterns

Conditions on outgoing sequence flows should always contain at least one process variable. If these conditions do not contain any process variable (dummy condition), they always evaluate to the same value.

If this value is false, the outgoing sequence flow will never be taken. This should be highlighted.

If this value is true:

• in XOR gateways: this sequence flow will always be taken, and an incident might be thrown if another outgoing sequence flow evaluates to true as well
• in OR gateways: in this case, the OR gateway should be replaced with the combination of a parallel gateway and another XOR/OR gateway to improve readability

How does the rule improve the BPMN diagram?

If the dummy condition evaluates to false, this rule highlights that a certain path can never be taken. If the dummy condition evaluates to true, this rule helps to avoid an incident arising or suggests a helpful refactoring.

Rule Details

• Name: no-dummy-conditions / static-expression
• Default notification level: warn

What alternatives did you consider?

Without the rule, BPMN models will continue to include dummy conditions on sequence flows behind OR/XOR gateways.

[nikku]

Name could be static-expression, too.

[nikku]

Further investigating this it may not be solved on the level of bpmnlint. We don't have full context here regarding the used expression language, and hence cannot derive any insights.

We can (and should) check this when validating for implementation. I hence move this to the Camunda compat rules.

[nikku]

Superceeded by https://github.com/camunda/bpmnlint-plugin-camunda-compat/issues/152.