Traversal Rules for Application Services form completion

  • Release version: Yokohama
  • Updated October 22, 2025
  • 2 minutes to read
    • Summarize
    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 for Application Services form completion

    The Traversal Rules for Application Services form is essential for editing or adding CI relationships during the tag-based discovery process. This process allows customers to manage their Configuration Items (CIs) effectively by establishing relationships between different CI classes.

    Show full answer Show less

    Key Features

    • Create a New CI Relationship: Use the 'New' option and select from available CI Relationship Types. If the desired relationship is not listed, you can create it by selecting 'New' in the CI Relationship Type Rule Definitions window.
    • Edit Existing CI Relationships: Select a preconfigured relationship, preview it, and make necessary modifications to the Parent Type, Relationship Type, or Child Type.
    • Reverse Traversal: Check the 'Is reverse' box to start the traversal from the child CI instead of the parent, allowing for more flexible discovery processes.
    • Active Status: Mark a rule as active to include it in tag-based discovery, or clear it to exclude it. A maximum of five active rules can participate in this process.
    • Order of Execution: Assign an order number to ensure that the system executes traversal rules in the correct sequence, particularly when dependencies exist.

    Key Outcomes

    By effectively using the Traversal Rules for Application Services form, customers can:

    • Establish and manage CI relationships to enhance overall visibility and governance of IT assets.
    • Streamline the discovery process by ensuring that the correct relationships are recognized and utilized.
    • Prevent conflicts and errors during CI discovery by carefully managing and ordering traversal rules.

    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.

    Field Description
    Rule Definition
    To create a new CI relationship:
    1. Select New.
    2. Select the Lookup using list icon and to view the available CI Relationship Type Rule Definitions.

      Continue as follows, depending on your situation:

      • If you see a CI relationship that you want to use:
        1. Select that relationship.
        2. Select Submit. The new CI relationship is added to the CI Relationship Type Rule Definitions [cmdb_rel_type_rule_definitions_list] table.
      • If you don’t see the desired CI relationship:
        1. Select New in the CI Relationship Type Rule Definitions window.
        2. Select the CI Class from the Parent Type list.
        3. Begin entering the relationship in the Relationship Type field and select the appropriate relationship type from the list.
        4. Select the CI Class from the Child Type list.
        5. Select Submit.
        6. Select Submit on the Traversal Rules for Application Services - New Record form. The new CI relationship is added to the CI Relationship Type Rule Definitions [cmdb_rel_type_rule_definitions_list] table.
    To edit a preconfigured CI relationship:
    1. Select the preconfigured CI relationship in the Parent Type column.
    2. Select the Preview this record icon , then select Open Record.
    3. Modify the Parent Type, Relationship Type, or Child Type as needed.
    4. Select Update.
    For example, to discover Linux servers hosting storage devices, select the following values:
    • Parent Type: Linux Server [cmdb_ci_linux_server]
    • Relationship Type: Contains::Contained by
    • Child Type: Storage Device [cmdb_ci_storage_device]
    Is reverse Select this check box to traverse a CI relationship starting from the child CI instead of the parent CI.

    Using the previous example, select this check box to begin with the storage devices and find the Linux servers that host these specific storage devices.
    Used By Select only Service by Tags.
    Note:
    Don’t select Service Recomputation. This selection helps prevent editing any existing traversal rules or adding new ones and produces an error message.
    Active Select this check box to use this traversal rule in the tag-based discovery.

    Alternatively, clear this check box to exclude this traversal rule from the tag-based discovery.

    Note:
    By default, you can have only five traversal rules participating in tag-based discovery. To change the maximum number of traversal rules, edit the value for the svc_by_tags.max.traversal.rules.active property in the System Property [sys_properties] table.
    Order Enter a number for the order. The system uses traversal rules for discovery in sequence from low order to high.
    Note:
    When configuring traversal rules with dependencies, verify that prerequisite rules are executed before dependent ones by assigning them a lower-order number.