Related Lists of CI components
Summarize
Summary of Related Lists of CI components
Related Lists in Configuration Item (CI) records display additional CI components contained within a CI, such as disk drives on a server or network router rules. These lists are dynamically populated by Discovery scans, showing only components identified in the most recent scan. Components not found in the latest scan are marked absent and excluded from the lists.
Show less
Key Features
- Dynamic Component Display: Related Lists show CI components discovered during the last scan, reflecting real-time asset relationships and statuses.
- Component Types: Two types appear in Related Lists:
- CIs themselves (e.g., hard disks)
- Non-CI components (e.g., serial numbers, rules)
- Filter Conditions: Components that are CIs are filtered to exclude those with status “Absent.” Non-CI components are filtered to exclude those marked absent.
- Icon Indicators: Various icons indicate active or recent incidents, problems, changes, and outages related to the CI, helping users quickly identify operational issues or ongoing work affecting the CI.
- Teams Related List: Associates user groups to Service CIs (and descendants) based on group type, enabling flexible tracking of team assignments per CI.
Practical Benefits for ServiceNow Customers
- Gain visibility into the real-time component makeup of CIs as discovered by Discovery scans, improving accuracy in asset management.
- Understand the operational status and issues affecting CI components through intuitive iconography, aiding faster incident and change management decisions.
- Track team ownership and responsibilities via the Teams related list for service-related CIs, supporting collaboration and accountability.
- Ensure CMDB data reflects only present components, reducing confusion from outdated or absent assets.
Related lists in CI records display additional components contained by that CI, such as disk drives on a server and the rules that control the behavior of a network router.
When Discovery runs, the Related List is populated with the components that Discovery finds running on the CI. The CI record might show different lists from scan to scan, depending on whether or not Discovery found the component.
By default, the Related Lists only display those components that are associated with that CI in the CMDB that has been discovered by the last scan. Components that are recorded in the CMDB but are not discovered in a scan, are deemed absent and do not appear in the list.
There are two types of components that appear in the Related List: components that are CIs themselves (such as hard disks), and components that are not (serial numbers and rules). The default filter condition in the breadcrumbs for components that are CIs is [Status] [!=] [Absent]. The filter condition for components that are not CIs is [Absent] [=] [false].
For example, a router can have several Related Lists affected by these filter conditions, including routing rules, disk drives, interfaces, and network adapters. Only those components found during the last Discovery appear in these Related Lists.
Icons in related lists
|
|
For currently active incidents against this configuration item |
|
|
For currently active problems against the configuration item |
|
|
For currently active changes against the configuration item that are not covered in the past, current, pending changes. For example, a request to update the operating system on a server that is currently in progress may display this icon. |
|
|
For changes that were recently completed against the configuration item. changes with an "Actual_end_date" in the past. |
|
|
For changes that are planned soon against the configuration item. changes with an "Actual start date" in the future. |
|
|
For currently active changes against the configuration item that have an "Actual start date" |
|
|
For outages that were recently completed against the configuration item. outages with an "end" date in the past. |
|
|
For outages that are planned soon against the configuration item. outages with a "begin" date in the future. |
|
|
For currently active outages against the configuration item that have a "begin" date in the past and no "end" date |
|
|
This will only show up in the Tree view and indicates that a configuration item that is downstream has at least one of the above issues against it. |
The system looks five calendar days into the past and seven calendar days into the future when looking at recent outages and changes.