--- sourceDocument: Yokohama IT Operations Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Traversal Rules # Traversal rules in Service Mapping {#ariaid-title1} * Release version: Yokohama * * Updated November 4, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Traversal rules in Service Mapping Traversal rules in Service Mapping enable the identification and mapping of relationships between configuration items (CIs) to create detailed and accurate application service maps. These rules connect related CIs through specific relationships in the Configuration Management Database (CMDB), enhancing service map completeness by including related CIs even when they are not directly tagged. Show full answer Show less ## Key Features * **Parent Type:** Defines the starting CI class for mapping related child CIs. * **Relationship:** Specifies the association between Parent and Child CIs, including traversal direction based on the **Is Reverse** flag. * **Child Type:** Identifies the related CI class mapped from the Parent CI. * **Priority Level:** Determines the order in which traversal rules are applied, with lower numbers having higher precedence to ensure accurate mapping. * **Is Reverse:** Controls traversal direction; when enabled, traversal begins from the Child CI instead of the Parent CI. ## Configuring Traversal Rules Service Mapping provides predefined traversal rules that serve as a foundation for tag-based discovery and service mapping. Customers can customize these rules to align with their organization's unique environment and needs. Service Mapping administrators (with the **servicemappingadmin** role) manage traversal rules in the **Traversal Rules for Application Services \[svctraversalrules\]** table. Proper ordering and priority configuration are critical because tag-based discovery depends on these rules to identify which CIs to map. By default, up to five traversal rules can participate in tag-based discovery; this limit can be increased by adjusting the **sysproperty svctraversal.rules.active** system property. ## Benefits for ServiceNow Customers * Enables precise and comprehensive service maps by ensuring related CIs are included beyond direct tagging. * Improves service visualization and understanding of application dependencies through relationship-based mapping. * Allows customization and scalability of traversal rules to fit complex organizational CMDB structures. * Supports efficient management and prioritization of traversal rules to optimize service mapping accuracy and performance. Traversal rules identify and map relationships between configuration items to create comprehensive application service maps. They connect relevant configuration items based on predefined relationships, promoting accurate service mapping and visualization. Traversal rules facilitate comprehensive service mapping by identifying related configuration items (CIs) through specific relationships that exist in the Configuration Management Database (CMDB). These rules support the mapping of related CIs even when they aren't directly tagged, providing a more accurate service map. ## Components of traversal rules {#traversal-rules-service-mapping__components-of-traversal-rules} When configuring traversal rules, it's essential to add them in the correct order, as tag-based discovery uses these rules to identify CIs that can be mapped. The Service Mapping administrator (service_mapping_admin) manages traversal rules in the Traversal Rules for Application Services \[svc_traversal_rules\] table. When configuring these rules, the following key components are considered: * Parent Type: The CI class that serves as the starting point for mapping related configuration items that belong to the Child class as specified by the traversal rule. * Relationship: The specific association or link between the Parent CI and Child CI that determines how they're related in the service mapping context. The direction of the traversal depends on the Is Reverse setting. * Child Type: The CI class that contains the related configuration items being mapped from the Parent CI class as specified by the traversal rule. * Priority Level: The level that specifies the order in which traversal rules are applied, with lower numbers taking precedence over higher numbers. * Is Reverse: A flag that determines the direction of traversal for the relationship between Parent CI and Child CI. When selected, the mapping process starts from the Child CI instead of the Parent CI. Note: To promote accurate mapping, configure traversal rules with the correct priority levels, as tag-based discovery relies on these rules to identify mappable CIs. {#traversal-rules-service-mapping__ul_yrb_2n2_fhc} ## Configuring traversal rules {#traversal-rules-service-mapping__configuring-traversal-rules} Service Mapping includes predefined traversal rules, simplifying the initial configuration. These rules provide a starting point for your tag-based service mapping setup. For details on the specific predefined rules, see [Predefined traversal rules for application services](https://servicenow-prod.fluidtopics.net/CYy_aVwDvC7Slg4Fo1Maiw "Service Mapping uses traversal rules to bring in related configuration items and expand the application service map. Several predefined rules are provided by default to help find and correctly map these relationships."). In addition to these predefined traversal rules, you can configure custom traversal rules to meet your organization's specific needs. For detailed instructions on how to configure traversal rules, including information on the required fields and settings, see [Traversal Rules for Application Services form completion](https://servicenow-prod.fluidtopics.net/e6xIhRqkraMlp_mvL5u1vg "To edit an existing CI relationship or add a new CI relationship during the tag-based discovery process, complete the Traversal Rules for Application Services form."). By default, you can only have five traversal rules participate in tag-based discovery. However, you can adjust this limit by configuring the sys_property svc_traversal.rules.active system property to enable more active traversal rules.