Beta verzia novej dokumentácie.

The global settings of the Configuration Management Database (CMDB) module are used to define the module’s basic structure, behavior, and process integration. They include the configuration of relationship types between configuration items, settings for the lifecycle of items (statuses), and their security attributes. The settings also determine the default view of the list of items (CIs) for different user types, rules for automatic record retrieval, and integration with the scheduled work module. All changes in this section require saving the settings to take effect in the system.

The Basic settings tab includes:

  • Snapshot to DMS – when enabled, an export of the current list of items (CI) with all user fields is saved to the DMS in XLS format at the beginning of each month
  • CM Autodiscovery – defines the number of days until an autodiscovery item is removed—the number of days after device detection when a device that has been moved to the deleted devices list is deleted. The default value for deletion is 180 days. This setting is only applicable in environments where Customer Monitor is used.
  • Assigning CIs to records for all companies – disabled by default; this setting defines the visibility rule for configuration items (CIs) when assigning them to records such as requests or work orders. When the setting is disabled, only items registered to the same company as the one selected in the given record can be assigned to it. When enabled, you can select from all visible items for records, regardless of the company to which these items are assigned.
  • Bulk creation of requests from the list of CI items – enables the creation of requests for CIs from the list of items via a bulk action.

Connection Types (Links)

This section is used to define relationships that can be applied between configuration items. The table defines a name for the primary direction (the relationship from item A to B) and a name for the inverse direction (the relationship from item B to A). This is a list of possible connection types (CI) with translations into supported languages. To visualize connections in the graph, you can set the line color and style in these properties. Within the connection properties, you can also set the connection direction (one-way or two-way). The options that can be selected as properties for one-way connections are:

  • Impact – for the selected connection, it determines the impact in the primary direction (A → B). Defines that the source item (A) affects the target item (B). For example: If Server (A) operates Service (B), it has an impact on it.
  • Propagation of security attributes – transfer of attributes in the inverse direction (B → A). Enables the inheritance of security attributes (e.g., criticality) from an affected item (B) to an item (A) that impacts item B. In the event of a conflict (if multiple CIs with different criticality levels are linked), the system always propagates the strictest attribute value. For example: If a server runs three different services with varying levels of criticality, the server will automatically be set to the highest criticality among all services linked to it.
  • RPO/RTO Propagation – Recovery Time Objective (RTO) and Recovery Point Objective (RPO) – transfer of attributes from service category items to items affecting the service (inverse direction).

Attribute propagation can only be enabled for one-way connections with impact in the primary direction.

You can disable predefined types by toggling the switch in the Status column, and you can expand the list with custom types by clicking the + Add icon. If a row was added by mistake, you can remove it by clicking – the link can only be removed if the settings have not yet been saved.

Figure: Connection types in CMDB settings

Item statuses

Item statuses represent the current status of an item (CI) in its lifecycle (e.g., in stock, in use, retired).

  • Check for CI links when changing status / archiving / deletingdisabled by default – when changing the status, archiving, or deleting a CI that has existing links to other items, the user is notified of these links. The notification of existing links when changing status applies only if the status is changed to an Inactive status.

The status list defines a list of all statuses from which relevant ones can be selected in the item type; new statuses are added using the “” + “Add” button. Saved statuses can only be deactivated, not deleted. Those items (CI) that had a status selected before the status was deactivated will remain in that status.

Within the status list, each status has the option to be marked as Inactive. Items set to inactive status (including archived items) will not appear in the system’s selection fields (for example, when linking a CI to a new request).

State Transition Control

To ensure the correct procedure in the item lifecycle (CI), you can define allowed transitions between states in the item type settings. This specifies which states an item can transition from and to (e.g., from the In service state, it is not possible to transition directly to the Archived state, but only to the Retired state).

Optional naming conventions

If necessary, you can choose your own terminology for

  • CMDB,
  • Item Groups,
  • Item Types,
  • Item List.
Image: Configuring custom names

Default settings for the list of items

  • List Settings for Operators and Assignees – allows you to set the default filter in the item list (CI), the list of columns, and the sorting order for assignees, operators, and administrators.
  • List Settings for Other Accounts – allows you to set the default filter in the item list (CI), column list, and sorting for other accounts for customer accounts and approvers.
  • Allow users to reorder columns – ability to reorder columns to customize data display

If you use a filter, you must first confirm the search; otherwise, the settings will not be applied. All of the settings mentioned above are applied after you save the configuration database settings by clicking the Save button.