Related Records and Form Tabs
On this page
A record's form in the Web App can include tabs and grids for related objects, service and SLA receivers and service levels, history, invoice items, work orders, tickets, and configuration items. A person's form also includes e-mail addresses and logins. The tabs and grids available depend on the record's class.
For opening a record and working with its fields, see Open and Edit a Record.
Related records and form tabs in the Web App
The Relationships tab
The Relationships tab lists the objects related to the open record as a tree. The first level has one group row per relation type, captioned with the type and the number of objects, and the related objects of that type sit under it.
- The Filter menu narrows the first level, and the map, to All, CIs, Tickets, or Impact Analysis. It starts at All each time you open the tab.
- Show only active limits the list to active objects. View as map shows the relationships as a map, which runs left to right, and Vertical turns the map to run top to bottom. These three choices are saved to your settings.
- A row's link, a double-click, or Open goes to the related object's page. When your setting to open records in a new tab is on, the page opens in a new tab.
- A plain click on a row only focuses it and clears the selection. Select rows with their check boxes, or with a Ctrl-click or Shift-click. Group rows and rows below the first level cannot be selected with a check box, and selecting all passes the rows below the first level by, but a Ctrl-click or Shift-click still selects a row below the first level.
Some relations are held by a field of the record rather than stored on their own, for example a ticket's related configuration item. The check box of such a row is disabled and selecting all passes it by, though a Ctrl-click or Shift-click still selects it, and the relation leaves the tab when the field that holds it is emptied or pointed elsewhere, by you or by a workflow that updates the field.
In a new 2026.1 database created with the Default Workflow (see Default Workflow Configuration), the relationship types held by a field include Associated CI / Associated Configuration, Related CI / Related Ticket, Related Change Request / Related Problem, Related Change Request / Related Incident, Related Problem (Root Problem) / Related Incident, and Associated Asset / Associated Library Item. An upgraded database need not have these types, and an administrator may have changed them.
Add, change, or remove a relation
Add Relation, Modify Relation, and Unrelate are disabled while the form is read-only. On the view page of a Knowledge Base article, the Relationships tab works without clicking Edit when you may edit Knowledge Base articles; without that right, the three buttons are disabled.
Add a relation
To relate objects to the open record:
- On the Relationships tab, click Add Relation. The Select object from list dialog opens on All Tickets, or, when you may not view tickets, on the first class of its class drop-down. It lists results at once, unless your setting not to prepopulate select dialogs is on.
- To relate an object of another class, choose the class in the drop-down beside the search box, and then click Search. The drop-down lists the classes that can be related, keeping only those whose forms you may view and that are licensed, among them All Tickets and All CIs. Changing the class resets the field filters but does not search by itself: the list keeps the previous class's results until you click Search. The dialog also has saved criteria and an options panel with Activities, Closed, and History switches, a time period, and field filters.
- Pick one or more rows and click Select or press Enter, or double-click a row.
- In the dialog that opens, choose the relationship type. The dialog offers only the types that apply to the classes involved, and when you relate several objects at once, only the types that apply to all of them.
You cannot relate a record to itself. When the objects you pick include the open record, an alert appears and the relationship-type dialog does not open. The relationship-type dialog itself also refuses such a relation, with the message You cannot relate an object to itself.
Change a relation's type
- Select exactly one relation and click Modify Relation.
- Choose the type in the Relation dialog and confirm the dialog.
The tab refreshes after you confirm.
Remove relations
- Select one or more relations and click Unrelate.
- Confirm Remove selected relationships?
When the removal succeeds, the selection is cleared and the tab refreshes.
The relationship map
With View as map selected, the open record is the root of the map, with one group node per relation type under it and the related objects under each group.
- The root shows the record's ID, name, status, and class icon. A group node shows the relation type and, while you point to it or it has focus, the number of its objects. An object node shows its class icon, ID, name, and status.
- Group nodes start collapsed; expand one to see its objects. An object with relations of its own expands to show them, grouped by type again. An object you may not view cannot be expanded, and neither can any object from the second level down under Impact Analysis.
- Point to an object node to show its menu button. The menu has Open, Open in new tab, and Details, followed by the object's workflow actions under Actions, where a named group of actions shows as a submenu. An action that is not available is shown disabled, and when the server returns a message instead of actions, that message is the only entry under Actions. Open always replaces the page, whatever your new-tab setting. Details opens the object's preview.
- A Ctrl-click on an object node opens it in a new tab, unless that node already has focus.
- A click on an object node at the first level selects its relation, except a relation held by a field of the record. A click on a group node or a deeper node selects nothing.
- Hold Ctrl and turn the mouse wheel, or pinch on a touch screen, to zoom between half and seven times the size. Drag the background to move the map. There are no zoom or fit buttons.
- With the keyboard, Tab moves to a node and clicks it, as a click with the mouse would, and Space shows or hides a focused node's children.
- A record with no relations shows No data to display.
While the map is shown, the tab keeps the Filter menu, Add Relation, Modify Relation, Unrelate, Show only active, View as map, Vertical, and Refresh, and hides the right-hand side of the grid toolbar.
Services and SLAs
For what services and SLAs are, see Services and SLAs.
- An SLA's Receivers tab adds a receiver from a menu with an organization, a group, and a person item. Each opens a picker for that class, and the record you pick is added. The tab also has a Delete button.
- The service levels of a Service are a grid on the Service form's General tab. Opening a level, by a click, a double-click, or Open, shows it in a panel instead of a details page; a middle-click on its link opens it in a new tab. The grid has no menu item that opens a level in a new tab and no details item. The grid's new button creates a level in the same panel, and the grid also has a Delete button.
- An Organization's SLA grid adds an existing SLA that you pick.
- A Service Catalog Item's Categories tab adds one category at a time, picked from a category tree, and its rows cannot be opened. See Service Catalog.
The History tab
The History tab lists the record's recorded changes. It has no actions button.
In a new 2026.1 database created with the Default Workflow (see Default Workflow Configuration), the tab offers six views: List, by Change Date, by Changed by, by WF Item #, Executed Actions, and Object Changes. Each shows the change date, who made the change, the action, the attribute, the old and new values, and the WF item number. When no current view has been saved, the tab opens on List.
Opening a row, by a click, a double-click, or Open, shows the change in a panel titled History instead of leaving the form. The panel shows Change Date, Changed by, Action, Attribute, WF Item #, and WF Action #, then the Old Value and New Value. Beside Changed by, a button opens a preview of the person who made the change; it is not shown when that person is one of the system's special persons. For a change to a rich-text field, each value has a maximize icon that shows the full text in its own dialog. The row menu keeps its item that opens the change in a new tab, and a middle-click on a row's link also opens it in a new tab.
The circulation history of a Library Item cannot be opened row by row; its links show as plain text. The rows of a Knowledge Base article's category grid, which adds one category at a time picked from a category tree, and of a person's device list cannot be opened either.
Invoice items and work orders
- An Invoice's invoice-items grid shows its new-item button only while the invoice can be edited. The grid has no details item.
- The Work Orders tab of the Incident, Service Request, Problem, Change Request, and Work Order forms lists the work orders as a tree. Its new button is shown only while the form can be edited. A work order created there gets the open record as its parent, or the open record's own parent when it has one. The tab's actions menu keeps its delete item, which is disabled without the permission to delete. Opening a row goes to the work order's page, or to a new tab when your setting to open records in a new tab is on.
Ticket and configuration item lists
These tabs list records that point at the open record. Opening a row goes to the record's page, or to a new tab when your setting to open records in a new tab is on.
| Tab | Form | Lists |
|---|---|---|
| Ticket History | Contract, Computer, Hardware, Network, Document, Configuration, Software License, Tracked Software | Tickets whose related configuration item is the record |
| Tickets | Person | Tickets whose requester is the person |
| Tickets | Organization | Tickets of the organization |
| Tickets | Group | Tickets assigned to the group |
| Tickets | Project | Tickets of the project |
| Request History | Service Catalog Item | Service requests for the item |
| Related Incidents | Problem | Incidents whose related problem is the problem |
| Configuration Items | Location, Organization, Person | Configuration items whose location, organization, or owner is the record |
The Ticket History tab is not the History tab of the record.
All of these tabs have the grid's actions button. The Person's Tickets tab and the Related Incidents tab keep the grid's row delete; the other tabs in the table hide it.
When the system setting to show tickets with subprojects is on, a Project's Tickets tab adds a with subprojects check box. While it is selected, the tab also lists the tickets of the project's subprojects. Your choice is saved to your settings.
The Configuration Items tabs and the Organization's Tickets tab have no add or remove control beyond the grid's actions button.
People and accounts
A Person's e-mail addresses and logins are rows that you add and edit in small dialogs, not fields of the form. Each dialog has a button that creates the new row or saves the existing one, hidden when the dialog is read-only, and a Cancel button that discards your entries and closes the dialog.
- The e-mail dialog has a type and a required e-mail address. An address that is not a valid format is refused with Invalid E-mail address. The fields are checked when you first click the create or save button and then as you change them; the button stays disabled while a field is in error and while the row is being saved. On saving, the server refuses an empty address with Email is required. and an address already in use.
- The login dialog requires a domain and a login, with no format check. On saving, the server refuses them with Domain is required., Login is required., or Login is not unique.
To make an e-mail address or a login the primary one, select exactly one row and click the grid's set-primary button. When the form has unsaved changes, you choose between saving the form first, so the change runs once the save succeeds, and running the change at once without saving. When the form has no unsaved changes, the change runs without a prompt. When the change succeeds, the grid and the form's data are reloaded.
On a Group form, the membership tab adds persons that you pick, several at a time, and its order dialog changes the order of the members. When the new order is saved, the form's data is reloaded.
Related topics
- Open and Edit a Record - the rest of a record's form.
- Stock and Consumables - the tabs of a Stock Room.