0
2.0.9
Australia Patch 6
Standalone Application
The ServiceNow Data Catalog gives you one place to discover, search, and understand all your data assets—whether they live in your data warehouse, BI platform, or ServiceNow instance. Connect to your data sources automatically, build a shared business language with your team, and visualize how your data flows across systems. Start governing your data today.
Built within Workflow Data Fabric, this new catalog integrates natively with the ServiceNow AI Platform capabilities you already rely on, such as AI-driven insights, workflows, and process automation. Find, trust, and govern your data assets, whether they live in ServiceNow or beyond, by leveraging this unified solution for end-to-end data governance.
Unified Data Asset Discovery
- Search across ServiceNow and external data sources with filtering and faceted navigation
- Find the data you need fast, wherever it lives
- Utilize the Catalog Discovery agent with Otto
Data Asset Details & Context
- View schema, ownership, descriptions, and tags in one place
- Understand what data you have, where it lives, who owns it, and how it's used
Business Glossary
- Define business terms and link them directly to technical assets
- Create a shared language across your organization
- Bulk edit glossary terms
Data Visualization for Lineage & Relationships
- Visualize lineage and context across systems with Graph Explorer
- Navigate your catalog within the graph experience - preview nodes without leaving the view
- Understand dependencies at a glance
- Column-level lineage - full upstream and downstream data lineage flow
Multi-Source Connectivity
- Connect and collect metadata from 17+ sources including ServiceNow, Amazon S3, Azure Data Factory, BigQuery, Databricks, dbt Cloud, Fivetran, SQL Server, MongoDB, MySQL, Oracle, PostgreSQL, Power BI, Redshift, Snowflake, Teradata, Tableau and more
- Unified Connect experience for managing all collectors and connections from the admin console
- Schedule on-demand collection run via ServiceNow hosted collectors or on-prem using MID Server
- New
- Rich text, image embed and other content options now available in multiline fields (e.g. description, status message)
- Bulk import/export of Glossary terms to perform faster glossary building and editing
- Run collectors via ServiceNow hosted environment
- New lineage Ttransform nodes now display transformations and processing steps in your lineage diagram with enhanced visualizations. Interact with transform nodes to view additional details about what data transformations occur at each step, helping you understand your data flow more clearly.
- NewCollectors: Salesforce and SAP HANA
- Changed
- Updated catalog "shopping cart" component to improve adding assets from the details page
- Lineage graph now load progressively by level, reducing the risk of timeouts when viewing large graphs. The system displays lineage in stages, allowing you to explore relationships without waiting for the entire graph to load, which improves overall experience and performance.
- ServiceNow Collector: now harvests table and columns descriptions, parent tables inherit fields of child tables
- Fixed
- Back button in "shopping cart" now retains user's search and filter options
Not applicable for this application version.
ServiceNow Data Catalog requirements:
- ServiceNow instance versioned to the Australia family release on Patch 6 or later
- AI Search must be enabled to facilitate advanced search capabilities and integration with the Data Catalog.
- Now Assist must be enabled to leverage AI-powered features for enhanced user experience and automation.
- Collectors
- Collectors can run in a ServiceNow-hosted environment or on-prem via MID Server. Customers wanting to run on-prem should configure a dedicated MID Server with approximately 8GB of JVM memory to ensure optimal performance. The exact memory allocation may vary based on specific customer requirements, and detailed guidance for sizing can be found in the MID Server documentation.
- Collectors require active network connectivity to each configured data source endpoint.
- Credentials: Each collector requires appropriate service account credentials with read access to the respective source system's metadata APIs or system catalogs.