[object Object]

The Washington DC release landed in 2024 and continues to define what’s in production for organizations that have not yet adopted Yokohama or Zurich. The headlines were Now Assist breadth and the new Service Operations Workspace; the operational impact also includes deprecations that bite if planning lags. Skipping past Washington in upgrade planning is fine if you are landing on Zurich; staying on Washington for an extended window means accepting the deprecation timeline.

Now Assist: Across the Platform

Now Assist features expanded across ITSM, CSM, and HRSD in Washington — agent assist summaries, knowledge article generation, and code generation reached GA for most modules. Enablement remained opt-in per module per feature, so adoption could stage. The Washington licensing model preceded the 2026 AI-native reframe, so Now Assist line items were discrete and metered separately; renewals straddling the change need careful reconciliation.

Washington Now Assist GA surfaces:
  ITSM: incident summary, resolution suggest
  CSM: case summary, response draft
  HRSD: case summary, policy article suggest
  Creator: text-to-code (App Engine Studio)
  Virtual Agent: improved NLU

Service Operations Workspace

The new unified console for operations teams combines incident, problem, change, and knowledge into one context. Replaces the older Agent Workspace for operations personas; the new workspace is the strategic surface for operations and the previous Agent Workspace receives only critical fixes. Migration is not automatic — workspace configurations, sidebar layouts, and contextual side panels need explicit setup in the new workspace.

Flow Designer Enhancements

Error handling, subflow governance, and debugging all improved in Washington. The debugger now shows inputs and outputs for every action in a run, which makes diagnosis dramatically easier than the previous “trace by guessing” approach. Subflow versioning gained the ability to pin a flow to a specific subflow version, which prevents the in-flight semantic drift that plagued earlier shared subflows.

// Subflow invocation with explicit version pin
var sf = new sn_fd.FlowAPI.getSubflow('NotifyApprovers', {version: 7});
sf.execute({approvers: approverList, context: ctx});

Deprecations to Plan For

Legacy Workflow Editor support narrows in Washington — Flow Designer is the strategic flow surface and new flow work should target it. UI16 receives accessibility patches and security fixes only; Next Experience is where new feature investment goes. Plan UI strategy accordingly — adopting Next Experience requires explicit migration of workspaces, dashboards, and Service Portal pages, not just an upgrade flag.

Upgrade Order

Sub-prod, then dev, then staging, then production, with ATF pass at each stop. Budget two to four weeks for Washington depending on complexity (custom apps, integrations, scoped artifacts). Do not skip the upgrade tasks dashboard — it surfaces deprecated APIs, changed behaviors, and legacy customizations that need attention before production cutover. Ignoring the dashboard is the most reliable way to encounter post-upgrade incidents.

Common Failure Modes

Production upgrade scheduled for the same week as a major business event — block the calendar window before any upgrade promotion. Custom workflows on the legacy editor never converted — the upgrade succeeds technically and the workflows stop receiving feature updates; convert opportunistically. Workspace customizations not re-tested in Service Operations Workspace — operators discover broken layouts on go-live morning.

What Changed Since Washington

Yokohama (2025) added enterprise-grade controls on Now Assist surfaces and broadened the BYO LLM catalog. Zurich (March 2026) introduced Agentic AI, the AI Control Tower, Build Agent, and Process and Task Mining. Customers planning a multi-release jump should target Zurich rather than Yokohama; the operational shifts compound and Zurich is the version where the agentic story is coherent.

Implementation Sequence

Run the upgrade tasks dashboard early in the planning cycle, not the day before promotion. Triage every deprecation finding — fix, defer with documented timeline, or accept with risk owner. Pilot Service Operations Workspace with one operations team for 30 days before broad rollout. Treat Now Assist enablement as a separate program from the upgrade itself; feature adoption gets buried when bundled with the upgrade.

What to do this week: open the upgrade tasks dashboard for any release you have not yet adopted and read the top deprecation findings; that read sets the realistic timeline for your next upgrade.

[object Object]
Share