N:M relations

An N:M relation links objects many-to-many, in both directions, and can carry fields of its own: Application runs on Server, with a deployment date; Person works on Project, with a role. When to prefer it over a reference field is explained in Ways to connect objects.

You work with relations in two stages: first define a relation type — the schema — under Framework → Relations, then link individual objects with it from the object view.

Define a relation type

Open Framework → Relations and click Add.

../_images/nm_relations_relations_overview.png

The list of relation types.

The form has two steps, Basic information and Content.

Basic information

Field

Meaning

Relation Name

Required, unique. Letters, numbers and hyphens only, for example Server-Connection.

Label (parent side)

Required. How the relation reads from the parent, for example Contains or hosts.

Icon and Color (parent side)

How the relation is shown on the parent object.

Allowed Types (parent side)

Required. The types whose objects can be the parent.

Label (child side)

Required. How the relation reads from the child, for example Part Of or runs on.

Icon and Color (child side)

How the relation is shown on the child object.

Allowed Types (child side)

Required. The types whose objects can be the child.

Description

Optional. What the relation is for.

A type may be allowed on both sides at once — for example Server as parent and child of a replicates to relation.

../_images/nm_relations_create_basic_info.png

Basic information of a relation type.

Content

Optional. Build sections and fields that every link of this type carries — status, purpose, notes, dates. The builder is the same as for types (3.3), with plain Section as the only structure control and the Basic Controls; section templates and special controls are not available here.

../_images/nm_relations_create_content.png

Fields of a relation type.

Save the relation type. Edit and delete it from the Actions column of the list.