Diagrams can be set to have "diagram rules" to replicate behavior of old diagrammers

Diagram Rules	Rule Name	Description
No Rules, Generic Rules, Process Dynamics Rules, Hierarchy Rules	No overlaps	Shapes must not overlap other shapes. An overlap is where one “shape” crosses another on the diagram canvas. It does not include situations where one shape is completely contained within another.
No Rules, Generic Rules, Process Dynamics Rules	All objects are connected	All objects must EITHER have lines which connect to them OR lines which connect from them. Exceptions: Free Text objects, Diagram Title, and Version Details.
No Rules, Generic Rules	Uni-directional connectors only	Connectors must not have the category: Logical Bidirectional, or Physical Bidirectional. Note: This rule does not interrogate line endings, so the line can have two arrowheads (giving the impression of being bidirectional) without raising an error.
No Rules, Generic Rules, Hierarchy Rules	Only objects that appear in the palette are allowed on the diagram	This diagram may only contain objects that are available in the New Objects palette for this diagram.
No Rules, Generic Rules	Processes must be associated with all overlapped process rows	Processes must be associated with all of the Organizations / Locations that they overlap. If a Process overlaps a Location or an Organization, but is not associated with it the Process will be error highlighted
Process Dynamics Rules	Iteration Groups contain at least one Process	Each Iteration Group on the diagram must contain at least one Process object. Contain = The entire of the contained shape must be inside the containing shape's borders.
Process Dynamics Rules	Iteration Groups can only contain processes	The only Object Type allowed inside an iteration Group is a Process. Any other object (for example, an Event, or a Process Break) will cause an error when this rule is run.
Process Dynamics Rules	Objects within an Iteration Group cannot connect to objects outside of it	If an object is inside an Iteration Group it can only connect to other objects inside of that Iteration Group.
Process Dynamics Rules	Iteration Groups have only one start Process	All Iteration Groups on the diagram must contain exactly one Process that has no connectors connecting to it.
Process Dynamics Rules	Iteration Groups have at least one end Process	At least one Process within the Iteration Group must have no output connectors.
Process Dynamics Rules	Optional connectors must have conditions	If any connector on the diagram has the category "Optional", the property “Name” must have a value.
Process Dynamics Rules	There is at least one mandatory Result	This diagram must contain one or more Result objects whose input connector has the category "Mandatory”.
Process Dynamics Rules	There is at least one start Event	This diagram must contain one or more events with no input connectors (the event cannot be connected from another object).
Process Dynamics Rules	This diagram should not contain Process Breaks	Process Break objects are not allowed on this diagram.
Process Dynamics Rules	Processes must be associated with at least one Organization or Location object	All processes appearing on this diagram must be associated with one or more Organizations, or locations.
Process Dynamics Rules	Processes must be associated with only 1 Organization or Location	All processes appearing on this diagram must be associated with one Organization object, or one Location object. They cannot be associated with more than one of these, or with a mix of Organizations and Locations.
Process Dynamics Rules	Processes must lie within parent process row	Any Process on the diagram that is associated with an Organization or a Location object, must be contained within that Organization or Location object on the diagram. i.e. All Process - Organization and Process - Location associations must be shown on the diagram as swimlanes.
Process Dynamics Rules	Processes must be associated with all overlapped process rows	An association must exist between a Process and the Location or Organization it is contained within on the diagram.
Process Dynamics Rules	Process rows must be of the same type	This diagram can only contain either Organizations, or Locations as swimlanes. It cannot contain both.
Hierarchy Rules	Hierarchy Recursion	If there are two copies of a single object on a diagram, they cannot be connected via hierarchy links. This is true for both direct connections (where object B is connected to object B), and indirect connections (where object B is connected to object C which is connected to object D which - in turn - is connected to object B).
Hierarchy Rules	Only one repeated object with children	If there are two copies of a single object on a diagram, only one occurrence of that object is allowed to have child objects. For example, Here object B appears twice on the one diagram, and one of these instances has a child, this is allowed: Here object B appears twice on the one diagram, and both of these instances has a child, this is not allowed:
Hierarchy Rules	Only one object at root	Only one object on this diagram can have no input links.
Entity Rules	Only sub-types can overlap their own super-types	An entity should not overlap other entities, unless it is the sub-type of another object. Then it must be contained within its own super-type.
Entity Rules	Allow only orthogonal relationships	Relationships must be represented by straight vertical or horizontal lines.
Entity Rules	Entities must have attributes	All Entities on the diagram must either: be associated with one or more attributes, or be associated with a super-type Entity which has one or more attributes.
Entity Rules	Entities must have visible relationships	All entities on the diagram must have Relationships with other entities on the diagram. The relationships must all be drawn on the diagram as a line connected the two objects.
Entity Rules	Entities must have exactly one Primary Key	All entities on the diagram must be associated with exactly one key, which has the category Primary.
Entity Rules	Keys must have members	Every key that is associated with an Entity on this diagram must have Key Members. Note that Key Members are Attributes or Associations that are associated with the keys.
Entity Rules	Apply rule for: Relationships as key members	If an entity has a Relationship as its key member, any relationship connecting to it at the other end must be “Mandatory” and “1”. For example, the following diagram shows an entity model where there is a relationship between a Customer and an Order. The entity representing the Order has a key. For the “Apply Rule for: Relationships as key members” rule to be validated the relationship must have the following properties at the customer end: “Mandatory” and “1” Resulting in the meaning: “An order must be made by exactly one customer”
Entity Rules	Disallow sub-types and super-types	This diagram must not contain any entities that have a sub-type or super-type relationship with any other entities.
Entity Rules	Disallow many to many relationships	This diagram must not contain any relationships defined as being "many to many".
Entity Rules	If entity is sub-type of another, it must be displayed inside its parent	An entity should not overlap other entities, unless it is the sub-type of another object. Then it must be contained within its own super-type.

No Rules

If your diagram is based on No Rules, your diagramming behavior will not be restricted in any way (for example, you will be able to connect any object to any other).

Generic Rules

An association is automatically created between any Process object and the Location or Organization it is contained within on the diagram. This function treats the Location or Organization object as a swimlane.

Dynamics Rules

Dynamics diagrams can be simulated. When a diagram with Dynamics Rules is open in Corporate Modeler, the Simulator button is enabled on the toolbar.

A connector cannot be used to connect a Result object to any other object on the diagram (the result is the end of the process and - therefore - the Process can't progress any further).

A connector cannot be used to connect any object to an Event object, except if the source object is a Process Break. Note that an Event is needed after a Process Break so that the process can start again.

Events can only be connected to Processes, Connector Set objects and Iteration Groups via a connector.

Process Breaks can only be connected to Events and Connector Sets via a connector.

Issues cannot be connected to any other objects.

Processes can only be connected to: Processes, Results, Process Breaks, Connector Sets or Iteration groups via a connector.

Organization objects cannot be connected to any other objects via a connector.

Location objects cannot be connected to any other objects via a connector.

Free Text objects cannot be connected to any other objects.

Hierarchy Rules

When a new diagram with hierarchy rules is created from an explosion, the exploded object is displayed on the new diagram.

Diagrams can be set to have "diagram rules" to replicate behavior of old diagrammers

The purpose of the single diagrammer is to enable users to create the kinds of diagrams they want, and not be tied to the old modeler rules. But if you want to draw a diagram which is exactly equivalent to a diagram drawn in the Entity Modeler, you can do so by creating a new diagram that uses Entity rules.

What are diagramming rules?

There is a concept in Corporate Modeler of "Diagramming Rules". These rules can be applied to diagrams and / or templates to prevent users from drawing diagrams which are illogical, or which do not conform to a notation "set".

When you set a diagram's rules you are deciding the following things about that diagram:

Notes

How To...

Create a New Diagram that uses Diagram Rules

Create a diagram with No Rules, and nothing in the palette

If you define your diagram as having No Rules or base it on a template which has No Rules, your diagram will have no preset palette or appearance settings on initial creation, and will not restrict the user's diagramming in any way.

Note: This functionality may be useful if you are responsible for creating templates.