Administration Guide

Object Relationship Map

On this page

A relationship links two records and has a type. A relationship type is a pair of names, one read from each side of the relationship, plus a list of the object classes allowed on each side. Which classes may take part in a type is configuration data: adding a class to a relationship type is an administrative change you make on the Object Relationship Map. For relationships between configuration items, see CI Relationships.

In the Admin Center

Before you begin

You need the permission that opens the Object Relationship Map page. For permissions in general, see Permissions Reference.

The relationship type list

The page is titled General > Object Relationship Map. Its list shows every relationship type with the columns Parent name, Child name, and System (a check mark for a system type). The list is ordered by rank, then by name. You cannot sort it by a column, and the page has no context menu. The list does not show whether a type is in use.

A single click selects a row. You can select several rows.

Create a relationship type

  1. Click New. The New Relationship pane opens.
  2. Under Relationship Type, choose Parent-Child (the default) or Sibling.
    • For Parent-Child, enter a Parent name and a Child name. Both are required, and they must differ, ignoring case.
    • For Sibling, enter one Name. It is required.
    • A line under the names shows how the relationship reads, with the names you entered filled in. For Parent-Child it reads: Displays as "<parent name>" from parent objects and "<child name>" from child objects. For Sibling it reads: Displays as "<name>" from both sibling objects.
  3. Select the classes allowed on each side, in Parent Object Classes and Child Object Classes. For a Sibling type there is one Object Classes list, used for both sides.
    • Classes are grouped by category, and each category has its own check box.
    • Type in Filter items to find classes by name. A category stays visible while it still has a matching class.
    • Select All selects every class in the list. Once every class is selected, the button reads Clear all.
  4. Click OK. The pane checks its fields when you click OK.

If a side has no class selected, OK shows this question before saving: "You should select at least one object for each side of the relationship, otherwise this relationship type will be unusable. Are you sure you want to save this?"

If the two names of a Parent-Child type are the same, the pane shows "The 'Parent name' and 'Child name' fields must be different".

A new type is not a system type, and whether a type is a system type cannot be changed. A new type gets a rank one above the highest, so it appears last in the list.

In the class lists, the category groups Service Desk, Service Management, Project Management, Asset Management, Purchasing, Configuration Management, Software Asset Management, and Organization Management come first, in this order. Any other category follows. A class that has no category is not listed, and neither are activity classes.

Edit a relationship type

To open a type, double-click its row, click the link in its Parent name cell, or select exactly one row and click Edit. The pane title shows both names separated by a slash for a Parent-Child type, and the one name for a Sibling type.

Some types have parts of the pane locked, and a locked control appears disabled:

  • On a field-linked type, only the names can be changed. Relationship Type and both class lists are locked.
  • Two other types are also partly locked. On one of them, only the names can be changed. On the other, Relationship Type and the parent class list are locked, and the names and the child class list can be changed. In a new 2026.1 database created with the Default Workflow (see Default Workflow Configuration), these are Collaborating / Collaborators, on which only the names can be changed, and Following / Followed by, on which the names and the child class list can be changed. An upgraded database need not have these types, and an administrator may have renamed them.
  • Every other type can be edited in full.

Click OK to save. The pane checks the names and the class lists as it does for a new type: the two names of a Parent-Child type must differ, and a side with no class selected brings up the same question before saving.

When you save, the names are always saved, and a locked class list is not changed. Saving new class lists does not remove relationships that are already stored, even if a record's class is no longer in the list.

Reorder relationship types

  • Select one row and click Move Up or Move Down. Each swaps the row with its neighbor. Move Up is unavailable for the first row and Move Down for the last.
  • Or drag rows into a new order.

The new order is saved at once; there is no separate save step. A system type can be moved like any other.

Delete a relationship type

  1. Select one or more rows. Delete is unavailable while the selection includes a row marked System.
  2. Click Delete.
  3. Answer Yes to "Are you sure you want to delete the selected item?" or, for several rows, to "Are you sure you want to delete <number> selected items?" with the number filled in.

If any selected type is used by a stored relationship, nothing is deleted. An error dialog headed "Relationship type in use" reads "Unable to delete item because it is referenced by other database object(s). To delete the item, you need to remove these dependencies first."

In the Settings App

Before you begin

The Object Relationship Map node is in the General group. It requires the Object Relationship Map permission; see Permissions Reference. The Admin Center checks a different permission for its page.

The relationship type list

The node opens one list, Relationship Types, with the columns Parent-Child Name, Child-Parent Name, and System (a check box). The list is ordered by rank, then by name. It does not show whether a type is field-linked.

Every command that changes the list writes the change to the database when the command completes. There is no separate save step, and Apply stays unavailable on this page.

To copy a type's ID, select one row and choose Copy Item ID (GUID) to Clipboard, or press Ctrl+Alt+C.

Create a relationship type

  1. Click New, or press Ins. The New Relationship Type window opens.
  2. Choose the kind: Parent-Child (the default) or Sibling.

    NOTE: Switching from Sibling back to Parent-Child does not restore the reverse name. Enter it again.

  3. Enter the names:

    • For Parent-Child, enter Parent-Child Name: and Child-Parent Name:.
    • For Sibling, enter Name:. The same text is used for both directions.
  4. Under "Select the object classes that can be connected by this relationship type:", select the classes allowed on each side, in Parent Object Classes and Child Object Classes. For a Sibling type there is one Object classes list, used for both sides.
  5. Click OK. OK is available once both names hold text.

In the class lists:

  • Selecting a group selects all of its classes. A group whose classes are partly selected shows an indeterminate check box.
  • Select All and Deselect All select or clear every class in every list.
  • Space selects or clears the focused row, and Left and Right collapse and expand a group.

When you click OK:

  • If the two names of a Parent-Child type are the same, letter case included, the window shows "The field values in the 'Parent-Child Name' and 'Child-Parent Name' fields should be different for a relationship of the Parent-Child kind. Please change the relationship kind or enter a different value in the 'Parent-Child Name' or 'Child-Parent Name' field." and stays open.
  • If a side has no class selected, you are asked "You should select at least one object for each side of the relationship, otherwise this relationship type will be unusable. Are you sure you want to save this?" A Sibling type with no class selected brings up the same question, worded for its one list. Click Yes to save, or Cancel to return to the window.

A new type is not a system type and not field-linked. It gets a rank one above the last type's, so it appears last in the list.

Classes offered in the Settings App

The Settings App offers a fixed list of 34 classes in eight groups. The Admin Center builds its class lists from the classes in the database instead, so the two applications need not offer the same classes.

Group Classes Shown when
Service Desk Incident, Service Request, Problem, Change Request, Work Order, Approval Stage, Knowledge Base Article, Announcement The license includes the ITSM module.
Service Management Service Catalog Item, Service, SLA The license includes the ITSM module.
Project Management Project, Project Task The license includes the ITSM module.
Asset Management Asset, Contract, Library Item, Equipment Reservation, Stock Rule, Consumable The license includes the ITAM module.
Purchasing Purchase Order, Invoice, Vendor, Product The license includes the ITAM module.
Configuration Management Computer, Hardware, Network, Document, Configuration Always.
Software Asset Management Software License, Tracked Software The license includes the ITAM module.
Organization Management Organization, Location, Person, Group Always.

IMPORTANT: Saving a type in the Settings App replaces both of its class lists with the classes selected in the window. A class that the window does not show, because the license hides its group or because it is not in the list above, is removed from the type when you save it here. This holds for every type, the partly locked ones included. A Sibling type's one list shows the type's parent classes, and saving writes that list to both sides.

Saving does not change relationships that are already stored.

Edit a relationship type

  1. Select one row, and click Edit, press Enter, or double-click the row. The Relationship Type window opens.
  2. Change the names or the class lists as for a new type.
  3. Click OK. The same checks apply as for a new type.

A type opens as Sibling when its two names are exactly the same, letter case included. The Admin Center ignores letter case here, so a type whose names differ only in case opens as Sibling in the Admin Center and as Parent-Child in the Settings App.

Field-linked types and the two other partly locked types described for the Admin Center are partly locked here too. On each of them the kind cannot be changed, Select All and Deselect All are unavailable, and the names stay editable:

  • On a field-linked type, and on the type that is Collaborating / Collaborators in the Default Workflow, no class list can be changed.
  • On the type that is Following / Followed by in the Default Workflow, a click changes every class list except Parent Object Classes, and Space changes nothing.

Reorder relationship types

  • Select one row and click Move Up or Move Down. Each swaps the row with its neighbor.
  • Or click Sort by Name and confirm "Are you sure you want to sort the Relationship Types items by name? This will reset the existing order." The list is then ordered by Parent-Child Name.

Move Up, Move Down, and Sort by Name are unavailable while the list is filtered. Once a filter has hidden rows, Sort by Name stays unavailable until you open the page again. Rows cannot be dragged into a new order. The new order is saved at once.

Delete a relationship type

  1. Select one or more rows.
  2. Click Delete, or press Del.
  3. Answer Yes to "Are you sure you want to delete the selected Relationship Types?" or, for several rows, to "Are you sure you want to delete n selected items?".

A system type cannot be deleted. When the only selected row is a system type, the Settings App shows "This is a system record and it cannot be deleted." and asks nothing; in a selection of several rows, system types are skipped.

The Settings App does not check beforehand whether a type is in use. A type that a stored relationship still uses is refused by the database, and the Settings App shows "Unable to delete item because it is referenced by other database object(s). To delete the item, you need to remove these dependencies first." with the server's reply. While other selected rows remain, it asks "Would you like to continue removing the remaining records?" with Yes, Yes to All, and No.

How relationships are stored

  • Alloy Navigator does not store a second relationship with the same two records, in the same direction, and of the same type. It also does not store a relationship that links a record to itself.
  • The duplicate check applies to each insertion as a whole: when one insertion carries several relationships and one of them repeats a stored relationship, none of them is stored, and no history entry is written.
  • The database does not check a relationship against the class lists of its type.
  • Adding or removing a relationship writes an entry into the history of both records. Each entry names the other record; for an added relationship, it gives that record's class, ID, and name. Changing a stored relationship's type also writes an entry to both records, with the old and the new type name.

Field-linked relationship types

A field-linked relationship type is not stored as separate relationship records. Its relationships come from a reference field on the record itself. Because no relationship record is added or removed, a field-linked relationship writes no such history entries. Types you create on the Object Relationship Map are never field-linked.