NiCE CXone Mpower Release Process

The release cycle encompasses the time between the release of the Coming Soon notes and the deployment of the release to the last customer cluster. Coming Soon notes are published 30 days before the deployment of a new release to our beta clusters.

The final Release Notes and online help updates for the new release are published on or shortly before the date of the beta deployment. Deployment to customer clusters begins two weeks after the beta deployment. The release is deployed to customer clusters in groups, with a few clusters receiving the release each week.

The Coming Soon notes for the next release are published near the tail end of the previous release’s deployment cycle.

A diagram of the timeline of Coming Soon publication 30 days before beta deployments, and then customer deployments.

Cumulative and Pipeline Updates

Three kinds of updates are released periodically throughout the release cycle. Cumulative and Pipeline updates occur on separate cadences but occur roughly every three weeks. Hot fixes are also released on an as-needed basis to address critical issues.

Cumulative and Pipeline updates are primarily for bug fixes. However, there can be new features, although they’re rare in all CUs except CU 1. Most often, the features were originally planned to be deployed as part of the major release but due to delays are released separately, although still as part of the overall release cycle.

In the Coming Soon or final Release Notes, features that include the line “This feature will be available later in the release cycle” will be released during an update.

Diagram showing the yearly release cycle of four major releases, each with cumulative and pipeline updates and hotfixes.