Pega continuously makes new features available to you so that you can incrementally and rapidly deliver value to your customers using the latest capabilities, feature enhancements, performance improvements, and security fixes.
If you opt in to receive our latest capabilities, you will see accelerated returns on investment, increased productivity, lowered costs through automation, and increased revenue growth. Pega Cloud services delivers software updates to your environments as part of its standard maintenance policy defined in Pega Cloud maintenance and types of system updates.
To accelerate the time-to-value and pave the path to your digital transformation, Pega Cloud services maintains an update process that helps you stay current in a predictable and consistent manner from release to release. Pega is committed to the highest software update quality so that you can experience as little downtime during update as possible. After you complete an update to Pega Infinity, you should always consider updating to the latest software to ensure that you can take advantage of the latest features and capabilities to maximize your investment in Pega.
To get started right away with a checklist of your responsibilities to complete an update from Pega Infinity release 8.4.1 or earlier, see Pega Cloud Services update checklist for Pega Infinity release 8.4.1 and earlier.
To prepare for the update process, review the following articles:
- For details about the latest Pega Infinity changes with which you can maximize your Pega software investment, see What's New in Pega Technology.
- For general details about how Pega keeps you current, see Updating and patching Pega Infinity.
- For information about planning and preparing for Pega Platform software patches in Pega Cloud services environments, see:
The information provided in this document is for planning purposes and is subject to change at the discretion of Pegasystems Inc.
Planning considerations for updates of Pega Infinity release 8.4.1 and earlier
Pega collaborates with you and helps you plan and structure your update approach. Pega encourages you to assess and decide on when you adopt new features and functionality available in Pega Infinity. Pega is committed to the highest software update quality so that you experience an automated update with less downtime and fewer post-update steps than earlier versions of Pega Platform. Pega uses the following feature development standards to ensure it seamlessly integrates with applications that are guardrail compliant:
- Backwards compatibility for Pega Platform and Pega application software changes, ensuring trouble-free software updates.
- Fewer required post-update steps in most Pega software applications. The update process includes a post-update, feature adoption phase for completing mandatory and optional post-update steps, recommended configuration changes, verification steps, or for adopting new features in your application.
- Identification of new features or performance improvements with a potential for update impact. To see the changes with known update impact, see Pega Platform changes with update impact.
- Development of analytical tools with which you can assess the update impact
on your application to ensure that it is ready for an update. Examples
- Pre-Upgrade Check for Pega Customer Decision Hub
- Pega Customer Service Update Checker
- Pega Sales Automation Update Checker
For Pega Platform, Pega provides a pre-update tool that identifies the rules that you have customized in your application to understand the impact of the update; your 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.
For any software update to Pega Infinity, Pega uses a two-phased software update process, so that you can adopt the latest performance and security improvements without affecting your existing Pega applications. This two-phased life cycle approach provides flexibility to your adoption of the latest features and enhancements in the latest version into your Pega application:
- Basic update
- Updates Pega Infinity rules to the latest version, with minimum disruption. Typically the Basic update phase take you about four weeks to complete. This phase allows you to make any necessary application changes to ensure functional correctness and update compliance. You can adopt the latest performance and security improvements and can test existing functionality using your current testing processes.
- Feature adoption
- After the Basic update is complete, you use this phase to take advantage of the latest Pega Infinity and application features using your standard DevOps process.
This phased approach requires that you maintain a standard, consistent DevOps approach so that they can assess the effect of the latest Pega PlatformPega Platform and Pega application capabilities and plan your new feature adoption strategy across your environments following your Pega Infinity update. This standardization includes the following structure:
- You configure your staging environment similar to, but not necessarily the
same as, your production environment. This requires that:
- The rules and data schema DDL are the same as the production rules and data schema DDL.
- The rules content is identical except for production environment specific configurations.
- There is appropriate test data in the Staging environment; copying production data is not allowed.
- You must already use a 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. You use Deployment Manager for your standard deployment pipeline. For details, see Using Deployment Manager for model-driven DevOps.
- Pega Cloud does not support modifying the production level of any environment. If you modified the default production level of your environment, it will be reset during the update process. For details, see Specifying the production level.
The Pega Cloud update experience
Pega uses a standardized software update process that provides you with an updated, cloned staging environment for a 30-day trial period. On this cloned environment, you test by using existing test suites, which minimizes efforts and shortens the update life cycle environments. You must schedule the provisioning of this cloned environments when initiating your update through the My Pega Cloud portal. After your cloned environment has been provisioned, you can access the Pega-provided URL to the cloned, staging environment. On the Home tab, in the Updates tile, click View details. The UAT stage screen displays the cloned, staging environment URL.
The standard Pega Cloud software update process integrates the latest Pega automation technology to support seamless adoption of the latest Pega Infinity features and improvements across environments using your development pipeline.
The following limitations and expected behaviors within your environments apply but are not limited to a your software update experience:
- During the environment updates, you experience environment downtime, during which time you cannot access Pega applications. Pega Cloud services makes a reasonable effort to minimize this downtime.
- Any data saved to the database before the update process is never lost during the update process. Throughout the Pega Cloud services software update process, Pega does not use the Pega application sample data.
- User sessions are not persisted: active users might be logged off during the environment restart.
- Reschedule any upcoming activities, such as job schedulers, before Pega initiates the update process.
- If you update from Pega Platform version 8.2 or earlier: stop all background processes before Pega initiates the update process and restart the stopped processes after Pegasystems, Inc. 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 update 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 the activity is not finished after 30 minutes, the background process is terminated. Review these application development best practices to ensure that your background processing takes only several minutes to complete:
- Existing mashups must be migrated; beginning in Pega Platform 8.5.1, Pega Web
Mashups include a channel ID in the mashup code for validation with your
mashup server. Create new mashup code on your updated, cloned environment
running release 8.5.1 or later so the mashup rule form includes a Mashup
channelID that is automatically included in your application testing rule in
your update pipeline. To create a new mashup, see Creating a mashup. Be sure to
update existing website configurations with the new mashup code.
For more information about migrating mashups, see Migrating existing mashups.
In addition, you must migrate your existing mashups; beginning in Pega Platform 8.5.1, Pega Web Mashups include a channel ID in the mashup code for validation with your mashup server. Create new mashup code on your updated, cloned environment running release 8.5.1 so the mashup rule form includes a Mashup channelID that is automatically included in your application testing rule in your update pipeline. To create a new mashup, see Creating a mashup. Be sure to update existing website configurations with the new mashup code.
Details of the new Pega Cloud services software update process
The Pega Cloud services major software update process requires that Pega and you coordinate your efforts throughout the update process. After Pega receives your request for an update to Pega Infinity, the process phases are broken into discrete steps based on the responsibility model:
- Pega clones a staging environment identified by
you in your update request and updates this cloned environment to the latest
Pega Platform and application software. This update
includes all the declared cumulative patches and critical hotfixes as defined in
Pega maintenance and types of system updates. The clone maintains
the application and data from the staging environment with the following
- Decision data store (DDS) datasets are not copied. For details, see "Pega Cloud cloning limitations in Pega Customer Decision Hub environments" in the feature adoption guide that is relevant for your update path:
- Kafka data sets are not copied; custom or internal queue processors automatically start on the cloned environment; and new topics are created in Kafka on first use. For details, see "Pega Cloud cloning limitations for stream data sets and environment stream tiers" in the feature adoption guide that is relevant for your update path:
- Archived data, case attachments, and SFTP data, because these are maintained in the Pega Cloud File storage repository and the cloned environment gets its own, new repository. To configure archiving on the cloned environment, see Improving performance by archiving cases; to configure file listeners on the cloned environment, see Configure a file listener associated with a storage repository.
- In Deployment Manager, your migrate rules from the updated cloned, staging environment to the production environment for each application using an update pipeline. 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 Configuring update pipelines in Deployment Manager.
- You perform application compatibility testing and validation on the cloned staging environment for up to 30 days, when they can make any changes or fixes necessary to verify expected application functionality while using the new version of Pega Infinity. Within this period, you complete your regression testing and then indicate your readiness to consent to update your production environment. During this testing phase, you can complete your regression testing on the updated, cloned staging environment. Helpful resources include:
- You perform any of the following steps that apply on the production
- For applicable applications that run Pega Platform version 7.3.x or earlier, perform a limited number of pre-update steps in coordination with Pegasystems, Inc. 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 Pegasystems, Inc. initiates the update process.
- If you update from Pega Platform version 8.2 or earlier: Stop all background processes before Pegasystems, Inc. initiates the update process and restart 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 update 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 the activity is not finished after 30 minutes, the background process is terminated.
- Pega updates your respective production environment during your standard maintenance window.
- You perform any of the following required steps that apply to your applications
on the production environment as detailed in the following articles:
- Post-update tasks following Pega Platform updates (8.x to 8.y) in Pega Cloud Services environments
- Post-update tasks following Pega Platform updates (7.x to 8.x) in Pega Cloud Services environments
- Completing post-update tasks in your industry applications
After completing required post-update steps in your application, you use Deployment Manager to promote the the update fixes identified during Step 3. see For details, see Migrating update fixes to production.
- Pega updates all non-production environments during your defined maintenance window within seven days of completing the update on the production environment.
- You perform any post-update tasks on the non-production environments as outlined in step 6. You now import any update fixes discovered as part of step 3 to all non-production environments by using Deployment Manager to promote these changes. For details, review Migrating application update changes to non-production environments.
- Pega removes the outdated rule schema in each updated environment seven days after completing the update.
- Pega deletes the updated, cloned staging environment within seven days of completing all of the live environment updates.
At this point, the Basic update phase is complete and the Feature Adoption phase begins. Use the second phase for completing post-update steps, verification steps and recommended configuration changes, or adopting new features in your application using your standard DevOps process.
During the Pega Cloud services software update process, Pega responsibilities include the following actions:
- Manage communications about updates, scheduling, and required consents
throughout the software update process as defined in the maintenance
policies and procedures. This includes notifying you:
- Five days in advance, as well as four hours prior to the software update process.
- When the software update process is initiated.
- When the software update process completed.
- Perform the software update within the standard maintenance window that you defined during the Pega Cloud services onboarding process.
- Coordinate any required pre-update steps if you are updating from Pega Platform version 7.3.x or earlier.
- Perform required infrastructure updates, clone the staging environment, update the software, and complete a post-update health check.
- Document any issue that was discovered during the cloning and update of the staging environment.
- Work with you when necessary, by using service requests, to resolve any update issues.
- Remove the outdated rule schema in each updated environment within seven days of completing the update.
- Delete the updated, cloned staging environment within seven days of completing all of the live environment updates.
Pega reserves the right to remove the cloned environment any time after the 30-day evaluation period in order to free up Pega Cloud services resources.
During the Pega Cloud services software update process, your responsibilities include the following actions:
- Complete a request for Pega software update of your environments in My Pega Cloud. 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. You must schedule the provisioning of this cloned environments when initiating your update through My Pega Cloud. You must initiate a software update with a minimal advance notice of five business days. My Support Portal: New Design, Streamlined Features.
- Run the application update assessment tools provided by Pega to identify potential issues in the application that are not compliant with the new version of Pega Infinity.
- Perform and document required post-update fixes on your updated, cloned staging environment and on your updated environments.