Architect track
Upgrades & operations
Two families a year, without the drama.
2 sections · 11 entries
Upgrade runbook
The rhythm mature teams repeat every release family.
- PlanRead release notes for your path, check plugin and Store app compatibility.
- Clone & upgrade sub-prodFresh clone of prod, upgrade it, capture timing.
- Review skipped recordsDecide per skipped record: keep yours, revert to OOB, or merge.
- RegressionRun ATF suites plus a short manual smoke test of critical journeys.
- PromoteCarry skipped-record fixes as an update set; upgrade prod in the agreed window.
- HypercareWatch the system log, slow queries and integration failures for a week.
Operations habits
Keep the instance healthy between upgrades.
- ✦Stay current. Fewer customizations = smaller skipped list = cheaper upgrades.
- ✦Weekly health. Review slow queries, failed scheduled jobs, email errors and integration logs.
- ✦Log hygiene. Remove gs.info noise from prod code; use properties to switch debug logging on.
- ✦Clean up. Deactivate unused business rules, client scripts and notifications each quarter.
- ✦Document. Every custom component has an owner, purpose and link to its design note.
Nothing on this page matches. Try the search on the hub.
Snippets are provided as-is under the MIT licence, without warranty. Test in a sub-production instance first. ServiceNow is a trademark of ServiceNow, Inc.; this page is independent and not affiliated with or endorsed by ServiceNow.