The BPMN correctness (active) validation rules defined in Cameo Business Modeler for BPMN2 projects are described in the table.
| Validation rule | Severity |
|---|---|
A Sequence Flow cannot connect the elements inside a SubProcess to the elements outside the SubProcess. | Error |
| A Message Flow must connect two separate Pools or elements in separate pools. | Error |
A Conversation Link can be from a Participant to a Communication, a SubConversation, or to a CallConversation. It can also be from a Communication, a SubConversation, or a CallConversation to a Participant. | Error |
| An Ad Hoc SubProcess may not have a Start Event. An Ad Hoc SubProcess may not have an End Event. | Warning |
| A Message Start Event cannot be used in a Choreography diagram. | Warning |
| An Error Start Event cannot be used in a Choreography diagram. | Error |
| An Error Boundary Event cannot be used in a Choreography diagram. | Error |
| A Message End Event cannot be used in a Choreography diagram. | Error |
| An Error End Event cannot be used in a Choreography diagram. | Error |
| An Escalation End Event cannot be used in a Choreography diagram. | Error |
| A Cancel End Event cannot be used in a Choreography diagram. | Error |
| A Signal End Event cannot be used in a Choreography diagram. | Error |
| A Multiple End Event cannot be used in a Choreography diagram. | Error |
| A Compensation End Event cannot be used in a Choreography diagram. | Error |
| A Sequence Flow cannot cross the Pool Boundary. | Error |
| A BPMN Process Diagram should be owned by BPMN Process or SubProcess. | Error |
| A BPMN Process diagram should be owned by a BPMN Process or SubProcess. | Error |