Phase 2: Application Upgrade

This content applies only to Cloud environments.

Why upgrade?

One of the most valuable benefits of Pega Cloud Services is that, as part of its standard maintenance policy, Pega performs software upgrades and patches on Pega Cloud client environments. The Pega Cloud software upgrade process supports upgrading to the latest Pega Platform™ software versions and any Pega applications that are running in Pega Cloud Services environments, making sure you are running on the latest Pega software.   For details, see Understanding the Pega Cloud Services software upgrade process.

Upgrading applications

The Pega Upgrade Center on Pega Community consolidates a number of upgrade articles and is a useful resource as you go through the upgrade process.

If you are currently using older versions of Pega applications, there may be legacy products or functionality that has been deprecated or replaced with updated features.  See Remediating as part of the upgrade process for information on these older products and their path to upgrade.

Pega Platform

You must upgrade to the latest version of our Pega Infinity series (version 8.x). To get there, begin by determining your Pega Platform version.  In the bottom right of the Designer Studio, click on PEGA, which displays your version. 

For the purposes of troubleshooting migration errors, it would also be helpful to know the original version in which your Pega application was built.  (This is one of the questions in the Client Cloud Migration Gap Analysis worksheet.)

The Deploy Pega Platform site will provide the appropriate Pega Platform Upgrade Guide for the current version of Pega Platform.

Choose the Upgrade Guide that matches your environment setup, and follow the instructions. 

After your upgrade, be sure to complete any post-upgrade tasks:

Pega Strategic Applications

Beginning with Version 8.1 for Pega Platform, all Pega strategic applications which were built on that platform have version numbers that match the Pega Platform version (example:  “8.2”).  These applications include:

  • Pega Customer Service
  • Pega Sales Automation
  • Pega Marketing
  • Vertical applications (“Pega Customer Service for Healthcare,” etc.)
  • Other applications (Field Service, Warranty, etc.)

For version 7 and earlier, some Pega applications may have had different versioning patterns.  For these older applications, check the Application Definition record to find the version of each of your Pega applications.

Each Pega application version has a version-specific upgrade guide.  From the Pega Application upgrade guides page, choose the appropriate guide(s) for your application(s).

Pega recommends that you review all documents for each interim release of all Pega applications in the stack (for example, Sales Automation for Insurance, Sales Automation, Foundation for Insurance).   You may find the following document types helpful:

Release notes

Provides an overview of changes in a release, which is helpful in determining new functionality, integration, UI changes, deprecated/withdrawn rules.

Upgrade guides

(most available starting with 7.22)

Defines steps that should be conducted from release to release, as well as pre- and post-upgrade steps

Implementation guides

Provides insight into new features/capabilities introduced into each release.

Pega CRM

For Pega Customer Relationship Management (CRM) applications, there are several helpful articles on Pega Community which point to important upgrade information:

Some product changes require user action before upgrading, to ensure a successful upgrade.  Before upgrading any Pega CRM applications, you must review important information about product changes for each release. See Crucial upgrade information for Pega Customer Relationship Management.

Pega Marketing

Depending upon your current version of Pega Marketing, you may need to upgrade to an interim version before you upgrade to the most recent release.  Please see Pega Marketing upgrade paths for details.

Testing your application

It is vital to thoroughly test your application at each major step in this process.  There are a number of different types of tests you can perform, including:

Unit tests

do your rules function as expected?

Smoke tests

simple tests to quickly cover functionality to ensure that the newly-deployed release has worked

Functional tests

does a particular feature work correctly?

End-to-end tests

does the application function correctly overall and do what you want?

You should have a full suite of tests that ensure your entire application is running properly.  Pega provides a number of articles on our testing features:

For an overview of Pega’s testing functionality, see Test Rapidly, part of the Pega Project Delivery Lifecycle.

Pega provides Unit Testing functionality as part of our DevOps functionality, to automate the testing of rules.

For further information on testing Pega applications, please see DevOps and Automated Testing

There is also a Pega Academy course, Delivering a Pega Project, which includes a module on Continuous Testing.

Vulnerability Testing

Pega Cloud Services clients can conduct security assessments for applications on Pega Cloud Services, when such assessments are preauthorized and performed within the guidelines (see referenced article below).  Application-tier vulnerability scanning is allowed when clients need to assess and report on the security of their cloud-delivered applications, client-directed development, and services for internal audit or compliance programs.

For details on guidelines and permission forms for conducting a vulnerability test, see the Vulnerability testing policy for applications on Pega Cloud Services.


Suggest Edit
Did you find this content helpful?

Have a question? Get answers now.

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