Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Pega Customer Service and Pega Call Patch Release Notes

Updated on August 12, 2022
Patch Release Notes

This book describes the changes for Pega Customer Service and Pega Call patch releases. For information about changes in major and minor releases, select the appropriate product version on the Pega Customer Service and Pega Call product pages and refer to the release notes.

To view the anticipated releases dates for upcoming Pega Customer Service and Pega Call patches, see the Pega Infinity patch calendar.


These patch release notes include all issues resolved across patch releases. For each issue, a reference number is provided, and the prefix of the reference number indicates the issue type. You can use the reference number of an issue in your related conversations with Pega Support.

The release notes include the following issue types:

Customer-reported incidents. For example, INC-183895.
Support requests, which were used instead of incidents in older patches. For example, SR-D79601.
Pega-identified issues. They might or might not be related to customer-reported incidents. For example, ISSUE 654263 (which might also be written as just 654263).
Sustenance engineering activities. For example, SE-60265.

Starting Q2 2021, all customer-reported issues are logged as INCs. You can view INCs that you logged in the My Support Portal. INCs logged by other Pega customers, and all other issue types (SR, ISSUE, and SE), are available in Pega internal tracking systems, in addition to these patch release notes.

For more information about application patch releases, see Application patch releases.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us