Tag Categorization in Tag Governance

  • Release version: Yokohama
  • Updated June 23, 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 Tag Categorization in Tag Governance

    Tag Categorization in Tag Governance automates the grouping of similar tag keys into predefined categories to streamline the management of configuration items (CIs) and cloud resources. This promotes clear, consistent tagging practices and improves tag management accuracy. A daily scheduled job categorizes new tags and maps unrecognized tag keys to appropriate categories, enabling ongoing organization and compliance.

    Show full answer Show less

    Key Features

    • Predefined and Customizable Categories: Provides preconfigured tag categories which can be modified or expanded by adding custom categories and tag keys.
    • Automated Categorization and Recategorization: Uses a daily scheduled job to categorize newly added tags and recategorize when category definitions change, ensuring tags remain accurate and up-to-date.
    • Compliance Monitoring: The Tag category policy identifies CIs missing categories and marks them as non-compliant to help with remediation.
    • Integration with Service Mapping: Uses the CI tag category [svctagcategories] and CI tag key [svctagnames] tables from Service Mapping Plus (version 1.16.3 or later), requiring this installation for full functionality.
    • Domain Separation Support: Supports domain-specific tag management by adding categories to the global domain for non-domain-separated instances or to each leaf domain for domain-separated instances, ensuring proper domain-level organization.

    Practical Considerations for ServiceNow Customers

    • Ensure Service Mapping Plus version 1.16.3 or later is installed to access full Tag Categorization capabilities.
    • Utilize the ability to customize tag categories and keys to tailor tagging structures to your organization's needs.
    • Leverage the compliance marking feature to identify and remediate incomplete tagging, improving data governance and reporting quality.
    • Understand domain separation implications for tag categorization to maintain proper access and organization across domains.
    • Use the daily scheduled jobs or manual triggers to keep tag categorizations current after any updates or changes.

    By automatically grouping similar tag keys into predefined categories, Tag Categorization streamlines the management of configuration items (CIs) and cloud resources while promoting clear and consistent tagging practices.

    Tag categorization requirements

    Note:

    The Tag Categorization feature in Tag Governance leverages the CI tag category [svc_tag_categories] and the CI tag key [svc_tag_names] tables in Service Mapping. Full access to these tables requires installation of the version 1.16.3 or later of Service Mapping Plus. Without it, access to these tables might be limited, affecting your ability to recategorize tags, modify tag definitions, or fully use the feature. For more information, see Install Service Mapping Plus.

    Tag Categorization overview

    Tag Categorization helps streamline and improve the accuracy of tag management by providing preconfigured categories to help you group tags for your CIs. A daily scheduled job categorizes newly added tags and maps any unrecognized tag keys to the appropriate category. For more information about the predefined tag categories, see Components installed with Tag Governance.

    You can modify the tag category definitions, create your own categories, or add additional tag keys as needed. For more information, see Modify tag category information for Tag Categorization.

    The Tag category policy confirms that all categories are properly mapped and up-to-date. It retrieves records and checks for category mappings to identify any missing categories. CIs that are missing a category are marked as non-compliant, which helps you address and remediate any tag category issues.

    The system uses the sn_itom_tag.recategorization_required property to determine whether recategorization is needed. By default, this property is set to false, but when a change to a category occurs, a business rule sets the property to true, indicating that recategorization is needed. A daily scheduled job then checks this property and if it is set to true, begins the recategorization process. This process automatically updates the tag mappings within 24 hours of the change, but you can also initiate recategorization to apply the changes immediately. All changes and updates are stored in the CI tag category table.

    Tag Categorization and domain separation

    Tag Categorization supports domain-specific management. If an instance isn’t domain-separated, the categories are added to the global domain. For domain-separated instances, the categories are added to each leaf domain. When you access or manage tags, the system gets domain information from the CI and adds tag mappings to the matching category in the appropriate domain. For general information about domain separation with Tag Governance, see Domain separation and Tag Governance.