Skip to main content

Updating and patching Pega Infinity

Suggest edit
Updated on April 12, 2022

To keep your Pega Infinity software current, update to the latest releases of Pega Platform and your Pega applications or apply a patch to your existing software. Update to take advantage of the latest features, capabilities, and security and bug fixes or apply a patch to address important security and reliability improvements.

Pega Platform version naming conventions

Pega patches and updates use semantic versioning, where the part of the version number that is incremented communicates the significance of the change. The version number, in the format XX-YY-ZZ, defines the major version (XX), minor version (YY), and patch version (ZZ), for example, 8.6.1.

Software versions are defined as follows:

  • Major versions include significant features that might cause compatibility issues with earlier releases.
  • Minor versions include enhancements or incremental updates.
  • Patch versions include small changes such as bug fixes.
Pega Platform release naming convention
Pega Platform release naming convention

Patches

Patches provided by Pega within a release stream are cumulative, meaning all fixes from earlier patches in the same release stream are included in the current patch. For example, fixes made in Pega Infinity release 8.4.4 are carried forward to release 8.4.5. The latest Pega software patch is always the most stable release available in its release stream.

See the following documents for more information:

Updates

Update to the latest version of Pega Platform to apply new features, capabilities, and all available fixes to existing functionality that are backwards compatible.

For updates of Pega Infinity release 8.4.2 or later to release 8.5.1 or later for Pega Cloud services, and for on-premises updates on Tomcat and PostgreSQL, you experience near-zero downtime. The latest update process enhancements include improved monitoring to prevent issues and rolling updates and procedures that maintain high availability so that you can continue to work on your applications during the update.

In addition, for Pega Cloud services updates, you can perform a Go-NoGo decision of your live system (production) environment update, which gives you the option to abandon your update.

If you update from Pega Infinity release 8.4.1 or earlier, or if you update from Pega Infinity release 8.4.2 or later in on-premises environments other than Tomcat and PostgreSQL, you experience as little downtime as possible.

The following table contains a list of documents with information about your update scenario:

Pega Infinity update scenarios and related documentation

Pega Infinity ReleaseEnvironmentRelated documentation
8.4.2 or laterPega Cloud servicesPega Cloud update process for Pega Infinity release 8.4.2 and later
8.4.1 or earlierPega Cloud servicesPega Cloud update process for Pega Infinity release 8.4.1 and earlier
8.4.2 or later for Tomcat and PostgreSQLOn premisesOn-premises update process for Pega Infinity release 8.4.2 and later for Tomcat and PostgreSQL
8.4.2 on all other databases and application serversOn premisesOn-premises update process for Pega Infinity release 8.4.2 and later for other application servers and databases
8.4.1 and earlierOn premisesOn-premises update process for Pega Infinity release 8.4.1 and earlier
  • Pega software maintenance and Extended Support

    Pegasystems understands that security, privacy, and compliance are top of mind issues for all organizations. We are committed to ensuring our products meet or exceed rigorous global security and privacy standards, so you can rest assured your data is safe. Pegasystems expects all clients to stay current because of the important security and reliability improvements delivered with each new release.

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us