Validation while modeling
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
|Since 3.14.0-ENTERPRISE.|
Automated diagram validation helps you to keep process models consistent and at a uniform quality level even with a large number of different authors. If diagram validation is activated, the process diagram is continuously checked for certain quality criteria during editing. Opportunities for improvement are then displayed directly on the respective process element. The easy to understand messages enable even inexperienced modelers to design easily understandable and valid process diagrams. However, the implementation of the improvement suggestions is never obligatory. Thus, diagrams can be saved at any time, even in spite of quality issues.
Diagram validation continuously checks the process model for the following rules:
Elements always require a label | |
---|---|
Error | Solution |
A (sub-)process requires at least one start and one end event | |
---|---|
Error | Solution |
A (sub-)process might only have one unspecified start event | |
---|---|
Error | Solution |
In an event-based sub-process, the start event must be specified | |
---|---|
Error | Solution |
All elements must be connected | |
---|---|
Error | Solution |
Multiple incoming sequence flows to an activity must be merged in a gateway before | |
---|---|
Error | Solution |
Sequence flows might not be split implicitly in an activity, but rather be split by a gateway afterwards | |
---|---|
Error | Solution |
There cannot exist duplicate sequence flows (equal start and end) | |
---|---|
Error | Solution |
No redundant gateways (only one source and one target) | |
---|---|
Error | Solution |
Gateways may not simultaneously merge and split sequence flows | |
---|---|
Error | Solution |
Rule Configuration per Space
Status | ||||
---|---|---|---|---|
|
|Since 3.23.0-ENTERPRISE.|