CMDB List View

 

The CMDB list view displays all existing Configuration Items (CIs) categorized under different CI types.

SDCMDBAdmin, SDCMDBManager, and technicians with access to the CMDB module can access the list view under CMDB in the application header.

 If no CIs are displayed in the list view, you may have not populated any CIs into the CMDB. Follow these steps to populate the CIs in CMDB. 

Contents:

 

View CIs under a CI type

The CMDB list view has two sections:

 

Add CIs under a CI type

You cannot add CIs under the CI type CMDB


Sample screenshot of a CI added under Tomcat Server, which is a child CI type of Application Servers (parent) and CMDB (super-parent).

 

Search CIs 

You can search for CIs three ways:

 

Filter CIs 

Filter Active/Inactive CIs: Use the filter drop-down on the CI list view to filter active and inactive CIs.

By default, CMDB lists all active CIs. 

Filter CIs by Site: Use the site drop-down on the CI list view to filter CIs by site.

Advanced Filter: Click to filter CIs based on criteria.

 

View Relationship Map   

A relationship map gives a consolidated view of the relationships between different CIs. The relationship map represents the relationships between only the CIs and not the CI types.

To view the relationship map of a CI from the CMDB list view, click > Relationship Map against a CI.

Learn more about relationship maps.

 

 
Populate CIs

You can populate entities such as assets, technician groups, departments, users, etc that are critical to your organization as CIs from the list view. This helps you differentiate the critical items from others.

You can populate CIs in two ways from the list view:

 

Mark as CI 

The items selected will be added as CIs under the destination CI type. You can view the marked CIs from the relevant CI list view.

Also, you can view the item you have marked as CI under Link this CI section of the relevant CI details page.

You can import the items from a particular module/category, but not the details.  

 

Import CIs

If existing CIs are imported again under a different CI Type, then the CIs are grouped under the new CI Type. 
Recommendation: If there are any failed records during import, do not re-import the same CSV file. Instead, download the import results, correct the errors, and then import the corrected file to avoid creating duplicate CIs.

 

Import CI Relationships 

You can import CIs from XLS, XLSX, and CSV files.

 

Export CIs 

You can export CIs in HTML, XLS, XLSX, PDF, and CSV files from the Ci list view by clicking > Export CIs.

 

Modify CI Type 

Modify the CI type of a CI to populate it under the appropriate CI type. For example, servers categorized under the Server CI Type and be reclassified into Windows Servers and Linux Servers.

Limitations to modifying CI types:

Moving to a Child CI Type (Server - Windows Server):
No data loss occurs as all parent fields and relationships are preserved, but child-specific attributes may be changed. 
Moving to a Parent CI Type (Windows Server - Server):
Child-specific data may be lost; however, custom relationships are retained, and invalid suggested relationships become custom. For CMDB Lookup fields, values are removed from the lookup field if the CI was previously referred to in a child CI type lookup field. 
Moving to a Different Hierarchy (Server - Workstation):
This operation is not recommended. For CMDB Lookup field, values are cleared in the lookup field when the CI is moved to an entirely different hierarchy. 

 

Edit or Delete CIs   

CIs linked to a request, problem, change, or release can't be deleted. They will be marked inactive and moved to the Inactive CIs filter.