Skip to main content

 –

Pega Cloud Services update checklist for Pega Infinity release 8.4.1 and earlier

Suggest edit Updated on September 29, 2021

This checklist details the update requirements and actions required during an update of all of your environments running Pega Infinity version 8.4.1 and earlier. 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 update process requires that you coordinate your efforts with Pega throughout the update process.

Update preparation checklist

Stakeholder Required actions with each stageDate completed
To become familiar with the update process, including the update process responsibilities model, review Pega Cloud Services update process for Pega Infinity release 8.4.1 and earlier.
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:
To review the Pega 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 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 contains the appropriate test data; copying production data is not allowed.
  • 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. Pega Cloud you will use Deployment Manager for you 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 which provides you with an updated clone of a specified staging environment for 30 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, complete a request for 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. Then, on the Clone stage screen, click Create SR, after which your are routed to My Support Portal to complete the request.

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.
On the Home page of the My Pega Cloud portal, 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 in the My Pega Cloud portal.

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

Tip: The updated, staging clone environment name and the URL includes "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 30 days to use it 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:

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

For each application, sync selected rules from the production environment to the updated, 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 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 30 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 in 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 more information about configuring update pipelines, see Configuring update pipelines in Deployment Manager.

Optionally, if you are migrating existing mashups and want to access them during the 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 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, Pega updates your production environment after you prepare the environment for the update. After the update, you must perform any required post-update steps that your application requires.

Basic production update acceptance checklist

StakeholderRequired actions with each stageDate completed
Before the update, perform the following steps which apply on the production environment:
  • For applicable applications running on Pega Platform version 7.3 or earlier software, perform a limited number of pre-update steps in coordination with Pega. Review the software update communication from Pega for guidance. For details, see: Completing pre-update tasks for Pega Marketing 7.4 and earlier running on Pega Cloud.
  • Reschedule any upcoming activities, such as job schedulers, before Pega initiates the update process.
  • If you are updating from Pega Platform version 8.2 or earlier: stop all background processes before Pega initiates the update process and restarts the stopped processes after Pega completes the update process. To complete the pausing and subsequent resuming of these background processes, see Managing background processes during updates and patches.
  • If you are updating from Pega Platform version 8.3 or later: The update process waits up to 30 minutes for any activity that is running in the background to finish its work; if it is not finished after 30 minutes, the background process is terminated.
After the update, perform any of following required steps applicable to your application on the production environment as detailed in the following articles:

For each application, use Deployment Manager to start a new deployment to promote the update fixes that you identified during Stage 3: Validate the Basic update using application testing.

For more information, see Migrating update fixes to production.

Log in to the 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 production within seven days of the update.

Stage 5: Accept a 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.

Basic non-production update process checklist

StakeholderRequired actions with each stageDate completed
Perform any pre-update and post-update tasks on the non-production environments as outlined in Stage 4: Accept a Basic update of your production environment.
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 applicatoin testing, during application compatibility testing and validation from your updated, cloned staging environment. To promote these changes 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 days window.

Optionally provide feedback about your experience by clicking the Action center banner in the My Pega Cloud portal and providing 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 lifecycle with which you complete optional post-update steps, verification steps and recommended configuration changes, or adopting new features in your application 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.

Did you find this content helpful? YesNo

0% found this useful

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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