Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

Improved processing of correspondence details

Valid from Pega Version 8.6

When you send correspondence, the system now does not update the pxSendDateTime property on the pxCorrSummary work page that belongs to pyWorkPage. In previous versions of Pega Platform™, after sending correspondence, the update of the pxSendDateTime property could cause errors when working with an application at run time. To prevent such issues, Pega Platform now includes a pyEnableCorrSummary when rule that, by default, is set to false. If your business scenario requires updating the pxCorrSummary work page, set the when rule value to true.

For more information, see:

Support for picklists with parameterized data pages in App Studio in Cosmos React UI

Valid from Pega Version 8.6

You can now use data pages with parameters to populate a property of the picklist type with filtered results in App Studio. For example, in a survey case type, you can use a parameterized data page to configure cascading drop-down controls in which the values in a secondary drop-down list are based on the value that the user selects in the primary drop-down list. With dynamically-sourced picklists, you get greater flexibility in configuring picklists, and users see more accurate values.

For more information, see link Dropdown control Properties — General tab.

Questionnaires available in App Studio

Valid from Pega Version 8.6

App Studio now supports authoring questionnaires, which in previous releases of Pega Platform™ were known as surveys. You can create questionnaires, add question pages, and populate the pages with questions of different types so that you can collect the exact data that your business processes require. For more efficient data management and reuse, data objects from a data model now store answers to questions, instead of autogenerated properties. For example, when a customer provides a date of birth in a questionnaire, and your application stores the date as a data object, you can conveniently reuse that data object in related cases. For greater flexibility, both standard Pega Platform and Cosmos React applications support questionnaires, however, some question types are unavailable in Cosmos React.

For more information, see:

Remote case types in App Studio

Valid from Pega Version 8.6

App Studio now supports remote case types for applications that you build on Cosmos React. With remote case types, you can create a case type inside one application, and then work on cases based on this case type in another, remote application. As a result, users can perform work from multiple applications on one screen without the need to switch between applications, which results in increased efficiency and faster case resolution.

For more information, see:

Support for calling a data transform from a case life cycle in App Studio and initializing data at case creation

Valid from Pega Version 8.6

You can now call a data transform from a case life cycle in a low-code way in App Studio. For example, when a customer wants to order the same product again, your application can reuse the shipping information from their previous order. Additionally, by configuring data initialization for a case type, you can prepopulate fields at case creation. For example, an application for a delivery service can apply the customer's preferred delivery options when a new case starts. These enhancements save time for developers because the system can initialize data and prepopulate fields in a case by reusing existing logic, and for customers, who do not need to manually enter their details every time.

For more information, see Calling a data transform from a case and Initializing data at case creation.

Data propagation for questionnaires in case types

Valid from Pega Version 8.6

Pega Platform™ now provides a tool to prepopulate answers in a questionnaire that runs in a case by propagating data from a parent case. At run time, specified questions in a questionnaire that users complete as part of case processing, can display answers by using information that users already provided in the parent case. As a result, you speed up the development of your application and help users process cases and complete questionnaires faster.

For more information, see:

Case outcome predictions in case types

Valid from Pega Version 8.6

Pega Platform™ introduces the use of machine learning and AI in Case Designer. You can now use predictions in case types, both in App Studio and Dev Studio. By using predictions, your application can predict various outcomes, such as the possibility of reaching a positive or negative case resolution, so that you can prioritize work, route cases according to risk, or optimize the case flow in other ways. You can use predictions when you create conditions in the condition builder, for example, when you define a business logic for routing assignments. 

For more information, see:

Virtual questions deprecated in 8.6

Valid from Pega Version 8.6

Following the improvements in Pega Intelligent Virtual Assistant (IVA), the creation of virtual questions is now deprecated and planned for removal. To avoid additional effort during updates to future releases, do not use deprecated features. For optimal application performance and efficient development of conversation processes, you now collect information from users by using the Ask a question smart shape.

For more information, see Adding a case type conversation process for a conversational channel and Asking a question in a case.

Case Management

Valid from Pega Version 7.1.3

This release had a focus on extending key capabilities to improve the ease of configuration based on early adopter feedback.  Improvements were made in run-time performance, especially in high volume situations with complex case configurations.  A series of cosmetic changes and fixes are included.

  • The Wait shape now supports dynamic references.
  • Issues were addressed with the CreatePDF and the CascadingApproval Smartshapes.
  • Attachments have been improved.
  • Issues with the Create Case Type functionality were addressed.
  • The Pega Pulse functionality has been improved, including its performance.
  • When auditing a work item, History is now the default tab.

Service levels for case stages

Valid from Pega Version 7.1.5

Service levels are available for stages in stage-based case management applications.

The service level starts when a case enters a stage and stops when it exits. The service level is defined in the Service level for stage field on the "Stage Configuration" dialog, which is accessed on the Case Designer Stages and Processes tab.


Alternatively, you can add a stage service level on the case type record's Stages tab.

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