CMDB structure¶

The CMDB structure defines types, field groups, fields, statuses, and relationship types.

Overview¶

This page explains how to use CMDB structure and describes its main effects. Test changes in a test environment first whenever they may affect existing tickets, permissions, notifications, or automations.

Typical workflow¶

Create, edit, and activate a CI type. Open the relevant administration or action form, enter the required values, and save only after checking assignments and required fields.
Manage field groups. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.
Define fields and field types. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.
Set required, search, uniqueness, and customer-visibility options. Open the existing record, change only the required fields, and check dependent assignments before saving.
Manage statuses and assign them to types. Open the existing record, change only the required fields, and check dependent assignments before saving.
Manage relationship types. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.

Notes¶

Visible menu items and actions depend on the signed-in agent’s group and program permissions.
Deactivated entries are often retained for existing tickets and reports, but are no longer available for new assignments.
After making changes, test at least one realistic use case with a user in the affected role.