DEV Community: Nayan Patel

ServiceNow Zurich Release: Highlighted New Features

Nayan Patel — Sat, 14 Feb 2026 01:28:26 +0000

ServiceNow Zurich Release: Highlighted New Features You Should Know About
The ServiceNow Zurich release marks a major milestone for the Now Platform, combining powerful AI, better developer tools, and improved user experiences into one upgrade. Whether you are an architect, admin, or business stakeholder, Zurich focuses on three themes: scalability, intelligence, and usability.

If you are planning an upgrade or just want a quick overview, this blog walks through the key highlighted features and points you directly to the official ServiceNow documentation.

Start Here: Official ServiceNow Zurich Resources
Before diving into the details, bookmark these core Zurich links:

Zurich family release notes (all products):
https://www.servicenow.com/docs/r/release-notes/family-release-notes.html

New features and products in Zurich (cumulative feature summary):
https://www.servicenow.com/docs/r/release-notes/rn-summary-new-features.html

Release notes summaries for Zurich features (by application area):
https://www.servicenow.com/docs/bundle/zurich-release-notes/page/release-notes/release-notes-summaries.html

Zurich release highlights (high‑level business outcomes):
https://www.servicenow.com/docs/r/release-notes/release-highlights.html

Learn about the Zurich release (AI Platform focus):
https://www.servicenow.com/docs/bundle/zurich-release-notes/page/release-notes/concept/rn-learn-landing-page.html

These pages act as your single source of truth for deeper, product-specific information.

AI Everywhere: Now Assist and the ServiceNow AI Platform AI is at the heart of the Zurich release. The Now Platform AI capabilities expand significantly, with Now Assist reaching across more products and use cases.

Key AI and Now Assist highlights:

ServiceNow AI Platform Zurich Release
The latest AI capabilities, including agentic playbooks, enhanced process mining, and expanded AI-powered workflows, are summarized here:
https://www.servicenow.com/platform/latest-release.html

Now Assist across workflows and products
The “New features and products in Zurich” page lists Now Assist variants for ITSM, CSM, HRSD, SPM, Security, Asset Management, and many industry solutions (for example, Now Assist for ITSM, CSM, HR, SPM, SAM, FSM, and more).

You can browse the full Now Assist coverage in the table on:
https://www.servicenow.com/docs/r/release-notes/rn-summary-new-features.html

Smarter AI interactions
Blogs summarizing Zurich call out improvements like multilingual support, richer context in recommendations, voice input, and AI-assisted email responses.

A concise overview of how these AI enhancements drive faster development and better decisions is available in the Zurich highlights:
https://www.servicenow.com/docs/r/release-notes/release-highlights.html

For customers, this means AI assistance is no longer confined to a few modules; it becomes a platform-wide capability embedded into daily work.

Developer Experience: Sandboxes, Studio, and Automation Zurich is a big release for developers and system administrators, with strong emphasis on safer experimentation and faster delivery.

Core areas to explore:

New features and products in Zurich – Developer & Platform
The cumulative new-features page includes items such as ServiceNow IDE, ServiceNow SDK, ServiceNow Studio enhancements, and Creator-focused capabilities.

See:
https://www.servicenow.com/docs/r/release-notes/rn-summary-new-features.html

Developer sandboxes and ReleaseOps
Community and partner blogs highlight developer sandboxes and ReleaseOps as key features, enabling safer development, structured release pipelines, and better governance.

High-level outcomes tied to faster app development and deployment are captured here:
https://www.servicenow.com/docs/r/release-notes/release-highlights.html

Flow Designer and Workflow Studio improvements
Zurich introduces enhancements like reusable triggers, better flow debugging, and AI-generated descriptions for flows, all aimed at simplifying complex automation.

The Release Notes Summaries page lets you drill down into Flow Designer and Process Automation Designer updates:
https://www.servicenow.com/docs/bundle/zurich-release-notes/page/release-notes/release-notes-summaries.html

If your team builds on App Engine or extends ITSM/CSM with custom apps, Zurich’s developer tooling can significantly reduce time to value.

Workflow Data Fabric and Integration Integration and data orchestration are another flagship theme in Zurich. ServiceNow introduces and expands features that connect workflows to external data platforms without heavy data movement.

Highlights:

Workflow Data Fabric
Partner blogs describe Workflow Data Fabric as a way to connect tools like Snowflake, Databricks, Oracle, and others so that workflows can use data in place.

You can find the official positioning and benefits as part of the Zurich highlights page:
https://www.servicenow.com/docs/r/release-notes/release-highlights.html

IntegrationHub and external event triggers
Zurich brings stronger IntegrationHub capabilities (such as PowerShell v6+ support, SOAP security, improved troubleshooting) and external event/webhook triggers for flows.

Detailed feature lists are available in the Zurich release notes and summaries:
https://www.servicenow.com/docs/r/release-notes/family-release-notes.html

These capabilities help enterprises build end‑to‑end automation spanning IT, business apps, and analytical platforms.

User Experience, Accessibility, and Analytics Zurich also refines how users interact with the platform, from dark mode to in-depth UX analytics.

Standout UX features:

Dark mode and new themes
Blogs highlight the introduction of a Coral theme and dark mode for Studio and builders, helping reduce eye strain and modernize the overall experience.

Theme Builder enhancements are listed in the Zurich feature summary:
https://www.servicenow.com/docs/r/release-notes/rn-summary-new-features.html

User Experience Analytics (UXA)
Zurich adds a UX Analytics dashboard that gives admins insight into how users interact with the platform and where friction occurs.

You can locate UX-related features via the Release Notes Summaries:
https://www.servicenow.com/docs/bundle/zurich-release-notes/page/release-notes/release-notes-summaries.html

Performance Analyzer
A Performance Analyzer “waterfall” view lets you trace execution sequences and identify bottlenecks in pages and experiences.

This supports the Zurich outcome of “improved visibility and control over workflows”:
https://www.servicenow.com/docs/r/release-notes/release-highlights.html

Together, these changes help platform owners continuously improve usability based on hard data, not just anecdotal feedback.

Industry and Product-Specific Enhancements Beyond the platform itself, Zurich brings many new and enhanced applications across industries and domains.

A few examples:

Industry solutions and SPM
The cumulative new-features page lists numerous industry and Strategic Portfolio Management (SPM) capabilities, including updates for telecommunications, financial services, and manufacturing.

Browse them by product area here:
https://www.servicenow.com/docs/bundle/zurich-release-notes/page/release-notes/release-notes-summaries.html

Security, Observability, and Vault
New and enhanced features appear for ServiceNow Vault, Service Observability, Service Operations Workspace, and related security and resilience products.

The high-level security and platform overview remains in the Zurich highlights:
https://www.servicenow.com/docs/r/release-notes/release-highlights.html

Asset Management and ITAM
There are dedicated “What’s new in Zurich” resources for Software Asset Management, Hardware Asset Management, and ITAM for Financial Services.

These are linked from the official ITAM webcast description:
https://www.youtube.com/watch?v=mO__h2ickdM

If your organization uses domain-specific modules, it is worth exploring each product’s Zurich release notes to uncover targeted value.

How to Move Forward with Zurich
To get the most out of the Zurich release:

Start from the Zurich release highlights for an outcome-focused view:
https://www.servicenow.com/docs/r/release-notes/release-highlights.html

Use the family release notes and summary of new features to drill down into products you own today:
https://www.servicenow.com/docs/r/release-notes/family-release-notes.html

https://www.servicenow.com/docs/r/release-notes/rn-summary-new-features.html

Share this blog (or adapt it) with your IT leaders, product owners, and developers to align on which Zurich features to prioritize in your upgrade plan.

Streamlining ITSM with Automated Change Risk, Policy Gates, and Release Orchestration

Nayan Patel — Sun, 08 Feb 2026 17:56:09 +0000

Streamlining ITSM with Automated Change Risk, Policy Gates, and Release Orchestration in ServiceNow

Change is where IT either earns trust—or loses it. Traditional change management often drowns in spreadsheets, manual CAB reviews, and subjective risk calls that slow delivery without reliably reducing incidents. The framework described in “Automated Change Risk, Policy Gates, and Release Orchestration: A ServiceNow‑Based Framework for IT Service Management” shows how to turn ServiceNow into an intelligent control layer that automates risk scoring, enforces policy gates, and orchestrates releases end‑to‑end.[2][1]

Why manual change management fails modern IT

Most IT organizations still rely on human-driven assessment and ad‑hoc approvals for changes, even though their environments are highly dynamic and integrated. The referenced framework highlights several pain points that many ServiceNow customers will recognize.[2]

• Risk scoring is inconsistent, often based on subjective fields or free‑text justifications.[2]
• CAB time is dominated by low‑risk, routine changes while genuinely risky changes slip through with limited scrutiny.[2]
• Release coordination across teams, environments, and tools is fragmented, leading to misaligned deployments and avoidable incidents.[4][2]

The core argument is simple: if your ITSM platform already holds configuration, change, incident, and dependency data, it should also drive automated change risk and release decisions.[5][2]

The ServiceNow-based change risk model

The proposed ServiceNow-based framework starts with a structured change risk model that uses data already present in the platform and CMDB.[5][2]

• Inputs include CI criticality, historical incident density for affected services, change type, timing windows, and dependency complexity.[5][2]
• These inputs feed a rule-based or algorithmic risk engine that calculates a normalized change risk score (for example, Low, Medium, High, Critical).[2]
• Risk categories drive downstream behavior—such as required approvals, mandatory test evidence, or blackout enforcement—without manual recalculation for every change.[5][2]

By encoding this model inside ServiceNow (via Flow Designer, business rules, or decision tables), organizations can move from opinion-driven reviews to consistent, data-backed risk outcomes.[5][2]

Policy-driven approval gates, not just CAB meetings

Instead of treating CAB as a single weekly meeting, the framework introduces policy gates that automatically enforce governance conditions at key points in the change lifecycle.[6][2]

• Pre-submission gates verify that the change has complete metadata, mapped CIs, and a defined implementation and backout plan.[2]
• Pre-approval gates ensure that risk thresholds are respected; for example, High-risk changes must have successful test evidence attached or they cannot progress.[6][2]
• Pre-deployment gates enforce environment readiness, freeze windows, and conflict checks against other scheduled changes impacting the same services.[6][2]

These gates are expressed as ServiceNow policies and flows, so the platform automatically blocks or routes changes that violate governance, instead of relying on humans to catch issues during meetings.[6][2]

Release orchestration as a ServiceNow “control plane”

The paper positions ServiceNow not just as a ticketing system, but as a control plane that orchestrates releases across CI/CD tools, deployment pipelines, and operations processes.[4][2]

• Change records become the authoritative container for risk, approvals, and deployment metadata.[2]
• Orchestration flows integrate with external tools (such as CI/CD pipelines or deployment engines) using APIs, webhooks, and integration hubs.[4][2]
• When gates are satisfied, ServiceNow can automatically trigger or allow deployments; when conditions fail, it can halt or roll back according to pre‑defined policies.[4][2]

This design allows IT leaders to maintain governance and auditability in ServiceNow while keeping technical teams in their preferred build and deployment tools.[4][2]

Practical implementation patterns in ServiceNow

Translating the framework into a live ServiceNow implementation requires a few key building blocks discussed in the article.[2]

• Risk scoring engine: Implemented via decision tables or scripts that evaluate CI attributes, historical incidents, change category, and timing to produce a risk score.[5][2]
• Policy gates as flows: Built with Flow Designer or workflow engine, each gate checks specific conditions (risk level, test status, approvals, blackout windows) and either progresses or blocks the change.[6][2]
• Integration hooks: Use IntegrationHub spokes or custom REST APIs to connect ServiceNow changes with pipeline tools so that risk status and approvals directly control deployments.[4][2]
• Dashboards and reporting: Build dashboards showing change risk distribution, gate failure reasons, and post-deployment incident impact to continuously refine the model.[5][2]

The paper emphasizes iterating on the model using real production data, rather than attempting to design a perfect risk engine from day one.[2]

Benefits observed and expected outcomes

Although every organization’s baseline is different, the article outlines several expected benefits from adopting this ServiceNow-based framework for automated change risk and release orchestration.[5][2]

• Reduced change-related incidents by prioritizing scrutiny on truly high-risk changes and enforcing evidence-driven approvals.[5][2]
• Faster lead time for routine or low-risk changes, as policy gates automatically approve or streamline paths without waiting for CAB.[2]
• Improved auditability and compliance, since every risk decision and gate outcome is logged in the change record and can be reported for regulators or internal auditors.[5][2]
• Better collaboration between Dev, Ops, and Risk teams by treating ServiceNow as the shared source of truth for change risk and release status.[4][2]

These outcomes align with broader industry findings about automation and DevOps convergence in ITSM environments.[4][5]

How this complements ATF and automated testing

While the article’s main focus is governance, risk, and release orchestration, it naturally complements ServiceNow Automated Test Framework (ATF) and other automated testing approaches.[7][2]

• Automated change risk policies can require successful ATF test suites as pre-approval gates for certain risk tiers.[7][2]
• Release flows can trigger ATF regression suites as part of deployment pipelines and use the results to promote or block changes.[7][2]
• Over time, test results and incident patterns can feed back into the risk engine, improving risk scoring accuracy for specific services or change types.[7][2]

Together, ATF for technical regression and the ServiceNow-based risk and orchestration framework provide a holistic control system for safe, fast change.[7][2]

Getting started in your own instance

If you want to experiment with this approach in your ServiceNow environment, the article suggests starting small and evolving.[2]

Define a minimal risk model (for example, Low/Medium/High based on CI criticality and change type) and encode it in a decision table.[2]
Implement one or two policy gates (such as requiring test evidence for High-risk changes) using Flow Designer.[2]
Integrate with a single CI/CD or deployment tool and use ServiceNow change status to control a basic deployment flow.[4][2]
Measure outcomes (incidents, lead time, gate failure reasons) and refine both the risk model and the gates over subsequent releases.[5][2]

By progressively maturing these capabilities, ServiceNow can evolve from a passive system of record into an active engine for safe, automated change.[5][2]

⁂

https://www.servicenow.com/community/developer-forum/automated-change-risk-policy-gates-and-release-orchestration/m-p/3480894
https://www.academia.edu/161755706/Automated_Change_Risk_Policy_Gates_and_Release_Orchestration_A_ServiceNow_Based_Framework_for_IT_Service_Management
Patel, Nayan. “Reliability-Centered Automation Testing for the ServiceNow Platform with Automated Test Framework (ATF.” Scientific Research Publishing, vol. Vol.17, no. No.1, 2026, pp. 77–89.
https://sarcouncil.com/download-article/SJMD-267-2025-530-538.pdf
https://rast-journal.org/index.php/RAST/article/download/29/29
https://www.servicenow.com/community/expert-services-forum/streamlining-itsm-with-automated-change-risk-policy-gates-and/td-p/3477938
https://www.scirp.org/journal/paperinformation?paperid=149299
https://www.youtube.com/watch?v=xTyYKW9C2Fg
https://www.ijisrt.com/assets/upload/files/IJISRT26JAN689.pdf
https://www.youtube.com/watch?v=bjCkgK0tahE
https://www.servicenow.com/community/champions-community-forum/how-to-make-servicenow-automated-test-framework-atf-truly/m-p/3480198