Guide / Every rule
Extension of another engine
The check engine/foreign-extension, in the group Flowable and Activiti.
Why it matters
Flowable and Activiti ignore the attributes and elements of the Camunda, Zeebe, Operaton and each other's namespaces, so what they set is silently lost at run time.
How to fix it
Replace it with the extension of the engine the diagram is written for, or remove it.
Where you see it
The Problems tab lists it under Engine, the editor marks the element on the canvas, and penstock check reports it as engine/foreign-extension. It runs on diagrams of the Flowable and Activiti profiles, and checks what those engines ignore or cannot run. This check is free.
To turn it off, set engine/foreign-extension to off in your .bpmnlintrc. See Validation.
Rule details
| Id | engine/foreign-extension |
| Group | Flowable and Activiti |
| Level | Error: the diagram or the process is wrong |
Name in penstock check | engine/foreign-extension |
Read more: Validation. All rules: Every rule.