Configurable rules in the delivery state

You can find and create configurable rules at SystemAdministration in the Default BPMN diagram profile under Rules. In the delivery state, you will also find the following preconfigured rules there, which you can customize:

Rule	What is validated?	Suggested correction
Start / end event must be formulated as an occurred state	For event names, Aeneis checks whether the initial name has been changed.	Change the description and formulate it as a completed action or a state that has occurred. Example: Change End event name to Invoice posted.
At least one output has no successor	For Outputs, Aeneis checks whether the attribute Is input for is empty.	Reference a corresponding object in the Is input for property of the output.
No responsible assigned	For the shapes, Aeneis checks whether the Responsible attribute is empty.	Reference a corresponding object in the Responsible property.
No consulted assigned	For the shapes, Aeneis checks whether the Consulted attribute is empty.	Reference a corresponding object in the Consulted property.
No applicable document available	In the case of activities, Aeneis checks whether the Applicable documents attribute is empty.	Reference a corresponding object in the Applicable documents property.
No triggered process referenced	For start and intermediate events, Aeneis checks whether the Trigger attribute is empty.	Reference a corresponding object in the Trigger property.
No triggered process referenced (end event)	For intermediate and final events, the system checks whether the Triggered processes attribute is empty.	Reference a corresponding object in the Triggered processes property.
No description available	For shapes, Aeneis checks whether the Description attribute is empty.	Enter a description in the Description property.