Configuration Item Types

Configuration Item Types

Configuration Item Types (CI Types) categorizes Cis with similar properties. Any organization-specific entity can be considered as a CI Type, such as Business Services, Workstations, Servers, Documents, or the People working for your organization.
Info
Every CI must belong to a CI type. 
All CI types should fall into the base CI type CMDB. A separate hierarchy for CI types is not allowed.
Role Required: SDAdmin and SDCMDBAdmin

CI Types List View 

Go to Setup > Customization > CMDB > CI Types.
The list view is in the form of a tree structure that displays the hierarchy of all available CI types and their descriptions.The CI types are arranged in the parent-child structure.
Click Expand/Collapse Tree on the toolbar to toggle the list view between fully expanded and fully collapsed views. Click   and to view and hide the children CI types, respectively.

Create CI Types 

You can define new CI types to match your business needs. Click New CI Type on the list view.

The New CI Type form contains the following tabs:
  1. Details
  2. Fields
  3. Relationships
  4. Sync Rules
Info
You will be able to configure the CI type fields and relationships only if you complete the basic details. 
The CI type name is unique across the CMDB. 
The parent CI type can be any one of the existing CI types only. All the CI types fall under the base CMDB CI type. 
You can add a maximum of 5 levels to the CI type hierarchy. 
You can only add 200 CI types.

Details

Fill out the details as explained below:
Fields
Explanation
CI Type Name*
Provide a name for the CI type.
Parent CI Type*
Select a parent type from the available list.
API Name*
Will be populated automatically based on the CI type name. You can still modify it.
Enter the value in snake case consisting only of lowercase characters separated by an underscore. The API name will be prefixed by 'ci_' automatically.
Description
Describe the CI type.
Icon
Add an icon, if required.
* mandatory fields
Click Save. You will be redirected to the Fields tab.

Fields

  1. The Fields tab allows you to customize the layout of the CI Type form. It contains two sections: Canvas and Fields List.
  2. The CI Type and Parent CI Type details are displayed at the top of the section.
 
Info
There is a limitation to the total number of allowed fields in CMDB and this number keeps reducing as you drag fields inside the canvas while creating different CI types. 
The CIs inherit their fields from parent and super-parent CI types.
 
Canvas
The canvas is where you build a template. It contains two sections:

Parent Fields
  1. Click to expand and view the section. Fields in this section are displayed based on the Parent CI Type.
  2. You cannot add, edit, or delete parent fields/sections.
Child Fields
  1. Add fields and sections from the Fields List to the canvas using a simple drag-and-drop method.
  2. By default, the Child Fields section is named the same as the CI type name. You can rename them by clicking on the section header and typing in the relevant section name.
  3. To add existing fields, drag them from the right pane to the canvas.
  4. To add new fields, drag a field type to the canvas and add the required details. Know more.
  5. Additional fields can be edited or deleted from the canvas. Hover over an additional field and click to edit and to remove the field.
  6. To add new sections, drag the New Section element from the right pane into the canvas and group the fields within the section. Hover over a section and click to set the section properties.
  7. Rearrange the fields and sections by using a simple drag-and-drop method.
  8. Hover over a field and use or on either sides of a field to resize the field length.

Fields List

The field list on the right pane contains two tabs:
  1. Available Fields - Contains additional fields configured in the application that are not used in the canvas. Drag any field from this list to the canvas.
  2. New Fields - Contains various field types that you can use to create additional fields for the CI type. To create a new field, drag a field type to the canvas and add the required details.
    1. Based on the selected field type, the field properties vary. Refer to this admin page to know how to configure different field types.
    2. You can also add sections to the template from the right pane. Use the New Section element to add sections to the canvas and group the fields within the section.
 
After configuring the fields, click Save.  

Relationships

Admin can define certain relationships between CI types, called the Suggested relationships. Admins decide the relationship type, the destination CI type, and the cardinality, based on the organization's requirements or policies. Child CI types inherit the relationships from parent and super parent CI types.
Info
To create relationship types, go to Setup > Customization > CMDB > Relationship Types. Learn more. 
Adhere to the following rules while adding suggested relationships:
Rule
Example
Relationships are not possible between parent and child CI types.
Consider the parent CI type 'Computer' and its child CI type 'Server'. While adding the relationship for 'Computer', the 'Server' option will be disabled under the Related CI Type picklist.
Sibling to sibling relationship is possible.
Assume, 'Workstation' and 'Server' are children of 'Computer'. You can create a relationship between 'Workstation' and 'Server'.
Self-relationships are possible but;
     - they cannot be duplicated.
     - they are not inherited by the children CI types.
'Computer Backed up by Computer'.
Say, 'Computer' is the parent CI type and 'Server' is its child CI type. You cannot view this relationship under Parent Relationships of 'Server'.
You cannot create more than one relationship between two CI Types using the same relationship type. This means only one combination of a Source CI Type, a Relationship Type, and a Related CI Type is possible.
Consider the relationship 'Web Server Connected to IBM Workstation'.
If you try to add the same relationship again, you will not see the option 'IBM Workstation' under the Related CI Type picklist.
Conflicting suggested relationships are not allowed.
Consider the suggested relationship 'User controls computer'. You cannot create 'Computer controls user' as another suggested relationship.
Suggested relationships cannot be edited but can be deleted.
If you delete a suggested relationship, the CI relationship created using this relationship will not be deleted, rather it will be treated as a custom relationship.
 
To add relationships,
  1. Click Add Relationship.
  2. Fill out the fields as required:
Field Name
Description
Source CI Type
This field will already be set to the current CI type and cannot be edited.
Relationship type*
The type of relationship shared between the Source and Related CI types. This can be either direct or inverse.
Related CI type*
Choose a CI type from the hierarchy of all available CI types.
Cardinality
Cardinality is the property of a relationship between one CI type and another. The relationship can be one of the following:
  1. One-To-One
  2. One-To-Many
  3. Many-To-One
  4. Many-To-Many
If you do not choose a cardinality, the default value is taken as many to many.
* mandatory fields
Click Save.
To delete a relationship, hover over it and click .

Info
The suggested relationships of the parent and super parent CI types, if any, are inherited by the children CI types and are displayed under Parent Relationships at the top of the relationships list view. Click to expand the view. You cannot edit or delete the parent relationships. 
No direct relationships are possible for the base CI type CMDB. 

 

Sync Rules

Sync rules define the data to be synced from assets, users, or software installations to CMDB.
  1. Click New Rule to add a sync rule. Learn More.
  2. Select a sync rule name to expand and preview the details.
  3. Click to edit, delete, or run through a sync rule.
  4. Use the toggle under Status column to enable or disable a sync rule.
  5. Use the Actions button on the toolbar to enable, disable, or delete sync rules in bulk.

Edit CI Types   

From the CI types list view, click the CI type or > Edit beside the CI type to modify its details.
 
Info
You can modify all basic details, except Parent CI Type and API Name. 
You can edit the fields, but not the relationships. 
You cannot edit the base CI type CMDB. 

Delete CI Types   

From the CI types list view, click   > Delete beside the CI type.
Info
You cannot delete the base CI type CMDB. 
Deleting a CI type will permanently delete its CIs, child CI Types, their CIs, its suggested relationships, relationships of all its CIs, and all the user-defined fields associated with it. 

    • Related Articles

    • Configure Leave Types

      Leave types is the type of leave taken by the technician, such as sick leave, casual leave, and so on. This is essential while marking leave for the technicians in Scheduler. To configure leave types, Go to Setup > Instance Configurations > Leave ...

    • Contract Types

      Categorize contracts into various types, such as lease, maintenance, support, warranty, and the like. Besides the default contract types, you can configure new ones. Role Required: SDAdmin Create Contract Types Go to Setup > Customization > Contract ...

    • Project Types

      Project types classify projects based on the goals they are trying to meet and are common for all customers. Role Required: SDAdmin Create Project Type Go to Setup > Customization > Project Management > Project Type. Click New Project Type. Enter a ...

    • Relationship types

      Relationship types define the nature of relationship between CIs or CI types. It shows how the CIs are interconnected and interdependent with other CIs. Each relationship type is direct when viewed from one side and inverse from the other side. Role ...

    • Software License Types

      Customize license types specific to software based on workstations and users. Role Required: AssetConfig A few of the default license types are as follows Client access license (CAL) Client access license maintains a relationship between server ...