Patch release best practices
Patches in on-premises systems
Patching only applies the necessary delta changes from your current patch version to bring the system up-to-date, which reduces installation time by over 40%.
Starting with Pega Platform™ 8.3.x patches, the installation is seamless with minimal disruption to client systems.
For more information about applying a patch, see Applying the latest on-premises patch.
Proactive patches and releases for Pega Cloud environments
A major benefit for Pega Cloud® Services clients is that Pega controls the deployment process for any new patches or minor releases. Clients can also participate in Pega's proactive patch program to ensure that they always receive the latest and greatest Pega Platform versions.
Some benefits of the proactive patching program include:
- Zero-downtime patching in client-defined maintenance window
- Improved overall application stability and security with the latest bug fixes
- Improved application value with the adoption of the latest capabilities
- Short release cycles and full compatibility through testing in a provided test environment
For more information about the Pega Cloud proactive patch process, see Pega Cloud proactive patch program frequently asked questions.
Route-to-live and testing guidelines
Zero-downtime patch process automation
By fully automating the zero-downtime patch process, clients can adopt the patches as soon as they become available.
Patch the lower environments first, and then, after verifying that everything works as expected, continue to the next environment.
Perform sanity or smoke testing at a minimum.
Review the Resolved Issues on Pega Community and test specific areas that require revalidation.
For more information about testing, see Performing regression testing on applications.
Check your knowledge with the following interaction.