Skip to main content

Pega Cloud update checklist for Pega Infinity release 8.4.2 and later

Suggest edit
Updated on April 12, 2022

This checklist details the update requirements and actions that are needed during an update of all of your environments with Pega Infinity release 8.4.2 and later. Use this checklist to plan and complete your update process steps and stages, as well as to run your communication with Pega.

Stage 1: Prepare for the update

The software update process requires that you coordinate your efforts with Pega throughout the update process.

Update preparation checklist

StakeholderRequired actions with each stageDate completed
To familiarize with the process, including the update process responsibilities model, review Pega Cloud update process for Pega Infinity release 8.4.2 and later.

To learn about the benefits of keeping current with Pega, read about the latest features, and learn about any features or processes that Pega has identified with update impact, explore the following topics:
To review the standard maintenance procedures and protocols, see Pega Cloud maintenance and types of system updates.

If applicable, run the Pega-provided pre-update checker on your applications to ensure that Pega Infinity seamlessly integrates with your applications. Examples of pre-update checkers include:

For Pega Platform, Pega provides a pre-update checker that identifies the rules that you have customized in your application to understand the impact of the update; you are expected to use the results to retrofit these rules after the update. As a best practice, do not overwrite or customize Pega rules. For more information, see Pega Update Tools.

Maintain a standard, consistent DevOps approach so that you can assess the effect of the latest Pega Platform and Pega application capabilities and plan your new feature adoption strategy across your environments after you update to Pega Infinity. This standardization includes the following structure:
  • Configure your staging environment similar to, but not necessarily the same as, your production environment. This requires that:
    • The rules and data schema Data Definition Language (DDL) are the same as the production rules and data schema DDL.
    • The rules content is identical except for configurations specific to production environments.
    • The staging environment has the appropriate test data; copying production data is not recommended.
  • You must already have a deployment pipeline configured with a minimum number of development, staging, and production environments. You use the pipeline to promote the latest application functionality to your production environments. You use Deployment Manager for your standard deployment pipeline. For details, see Using Deployment Manager for model-driven DevOps.

Review these application development best practices to ensure that your background processing takes only several minutes to complete:

Plan for your update journey in an upcoming sprint. Updates of your production environment are typically verified and completed within two weeks of initiation. During the sprint, do not promote any new application changes to the production environment.

Stage 2: Start the Basic update process

The Basic update process enables you to update your Pega applications to the latest Pega Infinity version with minimum disruption.

In this phase you initiate the update process that provides you with an updated clone of a specified staging environment for 10 business days. You prepare this environment for update testing using test data, test cases, and any operators as needed.

Basic update process checklist

StakeholderRequired actions with each stageDate completed
To begin your update journey, request a Pega software update of your environments in the My Pega Cloud portal. To begin your request, on the Home page, in the Updates tile, click Start, where you are routed to My Support Portal to complete the request. Specify a staging environment you want Pega to clone and then update.

For more information on managing updates in the My Pega Cloud portal, see Upgrades.

For the latest documentation on making requests, see My Support Portal: New Design, Streamlined Features.

If necessary, plan maintenance communication with your application users around your schedule for the update.
After your cloned environment has been provisioned, in the My Pega Cloud portal, on the Home tab, click View details in the Updates tile to view the UAT stage screen, where you can access the Pega-provided URL to the cloned, staging environment.

For more information on managing updates in the My Pega Cloud portal, see Upgrades.

Tip: The updated, staging clone environment name and the URL include "clone".

If you have existing web mashups, create new mashup code on the updated, cloned staging environment. For more information about migrating mashups, see Migrating existing mashups.

Stage 3: Validate the Basic update with user acceptance testing (UAT)

In this stage, you test all applications in your updated, cloned staging environment. You have 10 business days to use that environment to test all applications for functional correctness using automated and manual testing. You should also plan to make any critical changes if recommended as part of the update impact assessment that you complete in Stage 1: Prepare for the update.

This phase does not include adopting features of the new version of the Pega Infinity platform which are done later, during the Feature Adoption phase of the update process.

Basic update validation checklist

StakeholderRequired actions with each stageDate completed
For each application, import the following applicable testing assets into the updated, cloned staging environment:
  • Test operators and access groups
  • Test data and test cases

The clone maintains your application and data from the staging environment with the following exceptions:

While you must ensure that appropriate test data exists in the staging environment, copying production data is not recommended.

For each application, sync selected rules from the production environment to the updated, cloned staging environment. This is only required if a sample of production data or rule configuration is necessary to complete thorough regression testing of the application on the cloned staging environment. For more information, see Syncing rules between the production environment and the updated, cloned, staging environment in Deployment Manager.
If applicable, run the Pega-provided Customer Service post-update checker on your applications to ensure seamless integration. For more information, see Pega Customer Service Update Checker and Checking for rule overrides in Pega Customer Service in Pega Customer Service and Pega Sales Automation Update Guide.
For each application, perform application compatibility testing and validation on the cloned, updated staging environment for up to 10 business days. Ensure you have test coverage for the following Pega capabilities and configurations:
  • Case types
  • User roles
  • Data and integrations
  • Background agents
  • End user portals
  • Web mashups
  • Any other critical functional components

Helpful resources include:

During a 10 day trial period: For each application, make required changes to address issues identified during the testing. The required rules and data changes include addressing critical security-related enhancements, as well as problematic configurations identified by the pre-update assessment tools during Stage 1: Prepare for the update. In later stages of the update process, you promote these changes accordingly, depending on the stage.
Create an update pipeline in Deployment Manager to migrate rules from the updated cloned, staging environment to the production environment for each application. The update pipeline includes two product rules that contain any update fixes and confidence testing assets along with all required data instances to test the application.

For details, see Migrating update fixes to production.

Optionally, if you are migrating existing mashups and want to access them during the production update, create a product rule that contains the mashup and promote it to the production environment. For details, see Migrating existing mashups.

If you are migrating existing web mashups, add them to the application product rule in the update pipeline. For details, see Migrating existing mashups.

Notify Pega that you are ready to proceed with your software update by indicating that you have completed UAT.
  1. In the My Pega Cloud portal, on the Home tab, in the Updates tile, click View Details.
  2. Click UAT Checklist and Approve to enter your tentative schedule for the production update, provide feedback, and check off application testing and update validation as you perform the requirements.
  3. Select the checkboxes for each Basic update validation task to indicate whether you have performed them.
  4. Approve or reject if the clone environment has met your approval for update by clicking the Decision Taken list and selecting Approve or Reject, respectively.
  5. Click Submit.
For more information about managing updates in the My Pega Cloud portal, see Upgrades.

Stage 4: Accept the Basic update of your production environment

In this phase, you have 60 minutes to promote any necessary changes from the updated staging clone to the temporary production URL. You complete your confidence testing and communicate a Go-NoGo (accept or abandon) decision; the production environment is only updated following a go decision.

Note: Pega limits this window to 60 minutes to ensure that rule changes and data from case processing in your application during the update do not severely lengthen the time it takes to complete the migration of rules to the updated database schema.

Basic production update acceptance checklist

StakeholderRequired actions with each stageDate completed
In the My Pega Cloud portal, access the Pega-provided temporary production URL. On the Home tab, in the Updates tile, click View details to access the temporary production URL on the Updates stage screen.

For more information on managing updates in the My Pega Cloud portal, see Upgrades

Tip: This environment name and the URL includes "ephemeral".
Log into your temporary production URL and update the DMReleaseAdmin auth profile and the DMAppAdmin operator passwords to interact with Deployment Manager and complete your Go-NoGo confidence testing. If required, you may have to re-create the profile and operator.

For each application, use Deployment Manager to start a new deployment to promote the following instances from the cloned staging environment to the temporary production environment:

  • The update fixes that you identified during Stage 3: Validate the Basic update using application testing.
  • The confidence testing assets that you created during Stage 3: Validate the Basic update using application testing.
For more information, see Migrating application update changes to non-production environments.
On the temporary production environment, enable the operators that are needed for confidence testing.
Perform the application confidence testing on the temporary production URL. For details, see Understanding confidence testing.
If you have third party mashups embedded in your Pega applications and have a Custom Security Policy (CSP) configured, update the CSP rule by adding the mashup domain as an exception to the content security policy directive. For more information, see Allowing a website as an exception to a content security policy directive.
Indicate approval for the update on production by clicking the Action center banner in the My Pega Cloud portal and providing the relevant information. For details, see Migrating update fixes to production.

For more information on managing updates in the My Pega Cloud portal, see Upgrades.

After your go approval, Pega deletes the temporary production URL and initiates a rolling update of your production environment to the latest version of Pega Infinity.

If you make a No-Go decision, the update does not proceed, the operations engineer contacts you for information about why the update was stopped, and then the engineer reschedules the update.

After the rolling update of the production environment is complete, for each application, you use Deployment Manager to promote the update fixes that you identified during Stage 3: Validate the Basic update using application testing to the production environment. This is required to re-import any of your data instances or schema changes.

For details, see Migrating update fixes to production.

Log in to the production environment in the My Pega Cloud portal and then verify that your application is working as expected. Pega removes the outdated rule schema in your production within seven days of the update.

For more information on managing updates in the My Pega Cloud portal, see Upgrades.

Stage 5: Accept the Basic update of non-production environments

During this stage, Pega updates all non-production environments during your defined maintenance window within seven days of completing the update on the production environment. Non-production environment updates do not include a Go-NoGo approval requirement.

Basic non-production update acceptance checklist

StakeholderRequired actions with each stageDate completed
After every non-production environment update, for each application, import any required rules and data changes discovered during Stage 3: Validate the Basic update using application testing, during application compatibility testing and validation from your updated, cloned staging environment. To promote these changes by using Deployment Manager, review Migrating application update changes to non-production environments.
Log in to each updated, non-production environment in the My Pega Cloud portal and verify that your application is working as expected.

For more information on managing updates in the My Pega Cloud portal, see Upgrades.

Pega removes the outdated rule schema in your non-production environment within seven days of completing all of the non-production environment updates.

Pega also deletes the updated, cloned staging environment within this seven-day window.
Optionally provide feedback about your experience by clicking the Action center banner in the My Pega Cloud portal and providing your comments.

For more information on managing updates in the My Pega Cloud portal, see Upgrades.

Stage 6: Maintain Feature Adoption in your environments

At this point, the Basic update phase is complete and the Feature Adoption phase begins. Use this phase as part of your standard application development life-cycle with which you complete optional post-update steps, verification steps and recommended configuration changes, or adopt new features in your application by using the standard DevOps process.

Feature Adoption checklist

StakeholderRequired actions with each stageDate completed
Review Completing post-update tasks in your Pega industry applications and complete the steps that are relevant to your application.

In your development environment, enable and integrate the new features of the latest release that you identified during Stage 1: Prepare for the update of the update process into each of your relevant applications.

Use your existing deployment pipeline with a minimum number of development, staging, and production environments and use the pipeline to promote the latest application functionality to your production environments. For details, see Configuring pipelines and deploying applications in Deployment Manager.

  • Previous topic Pega Cloud update process for Pega Infinity release 8.4.2 and later
  • Next topic Pega Cloud update process for Pega Infinity release 8.4.1 and earlier
Did you find this content helpful? YesNo

50% found this useful

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