Pega Infinity patch frequently asked questions
Ensure that you are on the latest patch of Pega Infinity to take advantage of the latest security and reliability improvements that are delivered with each new release. See the following list of frequently asked questions about the Pega Infinity patch process.
How often are patches released?
Patches are released on an ongoing basis starting the month after a GA release. The schedule may be adjusted based on the severity and nature of any reported issues.
Pega will release patches for a minor release for up to 18 months following the GA date. For more information, see Pega software maintenance and extended support policy.
What will the patch releases contain?
Patch releases are cumulative and include the full Pega Platform distribution, plus all the fixes made up to that date. The Pega patch process uses scripts to either apply only the changes between Pega Platform releases or to install or upgrade Pega Platform using the distribution package. For example:
- 8.4.0 is the original Pega Platform release
- 8.4.1 will contain the Pega Platform release plus any fixes since the release
- 8.4.2 will contain Pega Platform and fixes of version 8.4.1 plus any fixes since that release
- 8.4.3 will contain Pega Platform and fixes of version 8.4.2 plus any fixes since that release
For example, if you apply the Pega Platform version 8.4.2 patch to a system on which Pega Platform version 8.4.0 is installed, the patch process applies only the changes between Pega Platform versions 8.4.2 and 8.4.0 to your system. If you install Pega Platform version 8.4.2 on the system, your system gets Pega Platform version 8.4.0 and includes all the newer rule fixes introduced in Pega Platform versions 8.4.1 and 8.4.2.
How do clients get the patch release?Patch releases are available through Pega Digital Software Delivery.
How do I install a patch release?
If you upgrade on Pega Cloud, Pega automatically applies patch releases to all of the environments in your subscription during the maintenance periods you have scheduled. Depending on the version of Pega Platform running, you should review the patch appropriate article to ensure you understand the process:
If you apply on-premises patches: Patch releases are available through Pega Digital Software Delivery. To apply a patch to your existing system, use the appropriate guide for your system:
Has the process for reporting issues changed?
No, the process for reporting Pega Platform form issues has not changed. You will continue to report issues and request changes through the standard service request (SR) process.
Will hotfixes be provided?
Hotfixes will be provided at the discretion of Pega in extremely rare and exceptional situations (such as production down or security vulnerability). Going forward, fixes will be delivered through the patch release process.
You must be on the latest patch version before a hotfix can be applied.
Does the patch release process apply to Pega applications?
At this time, while most applications continue to follow the existing hotfix process, Pega Customer Service and Pega Sales Automation now support patches and may include enhancements when Pega deems such fixes cannot wait until the next minor application release.
For details of application fixes that are included in application patches, see Pega Cloud patches include latest CRM application patches. Pega Platform patch releases will be tested for compatibility with the latest GA version of Pega applications.
How is the patch process different for on-premises and Pega Cloud clients?
For Pega Cloud patches, the Cloud operations team proactively installs patch versions for you. For more information, see Pega Cloud proactive patch program frequently asked questions. If you apply patches on-premises, you will request the software through traditional channels and update your system.
What is the responsibility model for testing Pega software patches?
The Pega patch process includes thorough regression testing to ensure backwards compatibility with the previous patch release. It is your responsibility to review the list of "Resolved Issues" to identify smoke and sanity testing protocols specific to your implemented application. In addition, you should plan for the routine testing of critical functionality to ensure that applying the patch does not disrupt your business process. Pega recommends implementing an automated testing pipeline to reduce testing cycle times (for example, Pega Scenario Testing.).
Perform sanity testing when you want to check the effect of a specific fix or change. After you verify the change, you then test the functionality that the change might have affected. For example, you perform sanity tests if you want to verify a resolved issue.
Perform smoke testing to verify that a wide range of critical features works properly. With smoke testing, you check which critical features the change might have affected, over a wide range of critical features, to verify that they still work correctly.
You can do sanity and smoke testing at the same time. Sanity testing is more focused and scope-restricted, often done manually. You can run smoke testing with significant automation.
Where can I find details about the bug fixes included in each patch?
Patch release notes will be published to Pega Community and include a cumulative list of bugs that were fixed inclusive of prior patch releases for a minor release. Resolved issue notes will not be included in release media.
Where can I find information about what patch version is available?
For a list of currently available patches, see Pega Platform Patch Releases - Resolved issues download.
Where can I find the patch release cadence?
Patches will be released monthly starting the month after a GA release. The schedule is subject to change based on resources and other requirements. For more information, see Pega Infinity patch calendar.