Welcome to another edition of “ServiceNow on Toast,” where we simplify the complexities of ServiceNow for developers and end users alike. Today, we’re exploring the ServiceNow release cycle. This structured approach ensures each update—from new features to patches—is designed to maintain system stability and quality while retaining the flexibility to address issues and enhance functionality promptly.

What is a ServiceNow Release?

ServiceNow organizes its releases into families, each centered around a major feature release. For example, if you’re working within the Washington DC family, this might include Washington DC Patch 1 Hotfix 2. Each family comprises:

• Feature Releases: These are significant updates that introduce new functionalities and improvements to existing features.
• Patch Releases: These focus on resolving problems accumulated to date and generally exclude new features unless they are directly related to the fixes.
• Hotfixes: These are urgent, targeted fixes for specific problems that need immediate resolution and cannot wait for the next patch release.

Each type of release is strategically rolled out to support the platform’s stability and user needs without disrupting existing customizations.

Release Terminology and Types

Understanding the types of releases can help users and developers navigate and plan for upgrades:

• Feature Release: This is the initial release in a family that brings new solutions and significant enhancements. It includes all available fixes to date, focusing on production stability and quality.
• Patch Release: This supports existing functionalities with a collection of all known problem fixes, enhancing system reliability without introducing new features.
• Hotfix: This is a reactive release, providing quick fixes to high-severity problems identified through testing or reported by users. Hotfixes are specific and do not include new features or non-essential updates.

Release Distribution Phases

Feature releases go through two main distribution phases:

1. Phase 1 – Early Access: Users can register for the early release program to gain access to the latest updates within a family. These releases are visible when registered customers request an upgrade on Now Support (HI).
2. Phase 2 – General Availability: Users can request and receive the new release at any time, or be automatically upgraded based on scheduled availability. This phase is open to all customers.

Patches and hotfixes are made available immediately upon release. Hotfixes might be distributed to specific customers under controlled availability, depending on the nature of the issue they address.

Release Cycle Examples

To illustrate, let’s consider the Washington DC family as an example:

• Washington DC Feature Release: Introduces new features along with a collection of fixes.
• Washington DC Patch 1: Builds on the Washington DC release with additional problem fixes.
• Washington DC Patch 1 Hotfix 1: Addresses a specific issue found in WDP1.
• Washington DC Patch 1 Hotfix 2: Fixes a different issue within the same patch, building on previous fixes.

This structure ensures that every subsequent release builds on the previous, maintaining a stable and reliable platform.

Final Thoughts

The ServiceNow release cycle is designed to deliver maximum value and stability to its users. Whether you’re an end-user or a developer, understanding how these releases work helps in planning and taking full advantage of the platform’s capabilities. Remember, with ServiceNow, you’re not just keeping up; you’re staying ahead.

Stay tuned for more insights and guides here at “ServiceNow on Toast,” where we make ServiceNow as easy to understand as enjoying your morning toast!