Platform teams that run more than one ServiceNow instance lose hours every cycle keeping store applications current: logging in to each instance, opening Application Manager, and clicking through updates one at a time. Updates get skipped, environments drift, and production changes happen without proof from lower environments. Update Center replaces that workflow with one fleet dashboard for administrators and platform owners.
Register each instance once. Update Center scans them all and lists every available update with the detail that matters: summary, release compatibility, dependencies, vendor, release dates, version history, and vendor install blocks with the reason. Update one application, a selection, or everything with Upgrade All — large selections split automatically into right-sized waves that submit themselves as each wave completes, and stalled submissions recover on their own.
The result is measurable: hours of repetitive administration replaced by minutes of review, consistent versions across every environment, and a safe path to production — production stays locked until enabled, versions must be proven on sub-production first, wave size is capped, and every batch records its rollback id. Credentials use Connection & Credential aliases or OAuth 2.0; nothing is stored in application tables.
- update inventory across all your instances, enriched from the app repository
- One-click update for one, selected, or all applications with automatic wave batching
- Production lock, proven-on-sub-prod gate, and wave-size guardrails
- Per-instance progress bars, live install tracking, and automatic recovery of stalled submissions
- Scheduled daily scans; blocked-update detection with vendor reason
- Connection & Credential alias / OAuth 2.0 authentication — no stored passwords
Initial release (1.0.0). Dashboard with scan and repository enrichment; single, selected, or Upgrade All submission with automatic wave batching and queue promotion; production guardrails (production lock, proven-on-sub-production gate, wave-size cap); per-instance progress tracking with automatic recovery of stalled submissions; scheduled daily scan; Connection & Credential alias and OAuth 2.0 authentication; included ATF test suite.
ServiceNow Yokohama or Zurich. Users operating Update Center require the x_omhu_updatecntr.admin role. For each remote managed instance, an account with admin (or sn_cicd.sysadmin) on the target instance, referenced through a Connection & Credential alias or an OAuth 2.0 entity profile. The instance hosting the application can manage itself with no credentials. No additional plugins or licenses are required.
Other Requirements:Outbound HTTPS connectivity from the host instance to each remote managed instance (standard ServiceNow-to-ServiceNow REST). Production instances receive no updates until the administrator enables the allow_prod_updates property. All cross-scope access used by the application is declared in shipped sys_scope_privilege records.