--- sourceDocument: Xanadu ServiceNow AI Platform Capabilities sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/servicenow-platform Release : - xanadu ft:locale : - en-US ft:publication_title : - Xanadu ServiceNow AI Platform Capabilities ft:clusterId : - platcap bundleId : - platcap workflow : - Platform --- # Related Lists of CI components # Related Lists of CI components {#ariaid-title1} * Release version: Xanadu * * Updated August 1, 2024 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read 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 {#r_RelatedListsOfCIComponents__section_uf2_pjp_pgb} Any of the following icons may appear in lists of CI related items. |-|-| | ![Currently active incidents.]() | For currently active incidents against this configuration item | | ![Currently active problems.]() | For currently active problems against the configuration item | | ![Currently active changes.]() | 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. | | ![Recently completed changes.]() | For changes that were recently completed against the configuration item. changes with an "Actual_end_date" in the past. | | ![Planned changes.]() | For changes that are planned soon against the configuration item. changes with an "Actual start date" in the future. | | ![Currently active changes.]() | For currently active changes against the configuration item that have an "Actual start date" | | ![Recently completed outages.]() | For outages that were recently completed against the configuration item. outages with an "end" date in the past. | | ![Planned outages.]() | For outages that are planned soon against the configuration item. outages with a "begin" date in the future. | | ![Currently active outages.]() | For currently active outages against the configuration item that have a "begin" date in the past and no "end" date | | ![Issues with downstream CI.]() | 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. | [ ] {#r_RelatedListsOfCIComponents__simpletable_wf2_pjp_pgb} The system looks five calendar days into the past and seven calendar days into the future when looking at recent outages and changes. * **[Teams related list](https://www.servicenow.com/docs/BkhU4lFCTgcFqjHPDCox~g#teams-related-list)** The Teams related list associates a user group to a CI based on group type, providing flexibility in tracking the different types of groups assigned to a CI. The Teams related list appears on CI forms for CIs of the Service \[cmdb_ci_service\] class and its descendent classes such as the Application Service \[cmdb_ci_service_auto\] class. **Related concepts** * [Dependent CIs management](https://www.servicenow.com/docs/OIm~Oreug3X9v2OPRN7Cmw "A life cycle update for a CI affects its dependent CIs. For example, when the CI that a dependent CI depends on is deleted, the dependent CI becomes orphan with no further use. To maintain the integrity and health of the CMDB, the system applies cascade-cleanup processes to dependent CIs that are affected by a life cycle update.") **Related tasks** * [Create a CI class](https://www.servicenow.com/docs/312mILvM_60~fmGC6kig1w "Create a CI class (table) that is an extension of an existing CI class. Then create identification and reconciliation rules for the new class.") * [Reclassify a CI](https://www.servicenow.com/docs/CJyQhWWWYFzIObIakULOEw "You can upgrade, downgrade, or switch the class of a CI by modifying its Class attribute.") * [Delete CIs](https://www.servicenow.com/docs/~2TSPcYXdqZUZxn1BEce0g "You can use the CI Class Manager to delete CIs that are no longer needed.") * [View and edit class definitions and metadata](https://www.servicenow.com/docs/8dwScazclfWWAbJfF3xziQ "Use the CI Class Manager as a central location to explore the CMDB class hierarchy, CI table definitions, and class CIs. View the details of each table such as its label and fields, relationships, and all related metadata definitions.") * [Update the list of classes in the Principal Class filter](https://www.servicenow.com/docs/3ssmYlSviAzINKXgsnLbYw "Manage the list of classes that are included in the Principal Class filter to restrict the CIs that appear in CIs list views to only specific classes that you need. You can add or remove CMDB classes from the Principal Class filter.") **Related reference** * [CMDB record types](https://www.servicenow.com/docs/B_DrHguvuFFGW1E~pH3dzA "The CMDB contains the following major record types.")