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.

Email listener enhancements for faster email processing

Valid from Pega Version 8.4

Enhanced email listeners now process more emails in less time. To increase throughput, you can configure email listeners to process several emails simultaneously, instead of one at a time.

For more information, see Creating an email listener.

Support for data page aggregation

Valid from Pega Version 8.4

You can now aggregate data from multiple sources for faster and easier implementations. With this feature, you can load data pages more easily without using an activity or data transform. 

For more information, see Creating a data page

Case tags for improved case search

Valid from Pega Version 8.4

Pega Platform™ now supports enhanced tagging for case types so that you can search cases by tags. As a result, tagging is more consistent because you can define a set of suggested tags that users can add to their posts and cases. When users search for cases, they can apply several filters, for example, recently added or most frequently used tags.

For more information about tags, see Tagging cases in Dev StudioTagging cases in App Studio.

Improved contracts for implementations

Valid from Pega Version 8.4

For more complete contracts, automations now support embedded pages, default values, and picklists. These enhancements provide a more robust model for inputs and outputs that is easier to update and maintain.

For more information, see Viewing automations.

Enhanced OpenAPI Specification generation

Valid from Pega Version 8.4

To better understand the purpose of your REST API, you can now generate a more complete OpenAPI Specification (OAS) from REST service rules in Pega Platform™. The system uses relevant records to build an accurate schema definition for page and page list outputs, and generate stronger schema type definitions for all inputs, outputs, and fields, such as array or boolean. You can also generate OAS by mapping values to JSON or Clipboard in the request, or mapping values from JSON or Clipboard in the response

For more information, see Service REST rules.

Case notification enhancements

Valid from Pega Version 8.4

Pega Platform™ now supports creating case notifications directly in Case Designer in App Studio and Dev Studio, so that you do not need to create a notification rule first and then provide the rule name in a case. You can speed up and simplify case creation by specifying recipients for each notification, without the need to create a data page for the recipients. Push notifications and email subjects can now also include properties, for example, a case ID or a goal and deadline.

For more information, see Sending event notifications from cases in Dev Studio, Sending event notifications from cases in App Studio.

Improved and simplified field-level auditing

Valid from Pega Version 8.4

To track the progress of your work and maintain the compliance of your cases, both App Studio and Dev Studio now support field-level auditing for case fields. Your application tracks and displays information about user updates to scalar fields, field groups, and field group lists, at any level of your case data model. For example, you can check previous and current field values, the last user to change the values, and the time of their modification. 

For more information, see Track changes in cases with improved field-level auditing (8.4), Enabling field-level auditing in Dev StudioEnabling field-level auditing in App Studio.   

Creation of case documents in a case life cycle

Valid from Pega Version 8.4

To save time and further automate your business processes, Pega Platform™ now supports generating case documents as part of the case life cycle. You can ensure that the documents include all necessary information by first creating a document template in a word processor. When you create a template, you add dynamic tags that your application populates with relevant data unique to each case, for example, the case ID and current date. To make your documentation more meaningful, you can also include attachments.

For more information, see Generate case documents in a case life cycle (8.4)Generating case documents in Dev Studio, Generating case documents in App Studio.

Enhancements to automations for defining Pega API contracts

Valid from Pega Version 8.4

With enhanced automations, you can now pass embedded pages, specify default values for optional input parameters, and define a set of values for inputs by using the picklist or enumerated field types. The new enhancements make your applications easier to define and maintain, and you can now provide callers of Pega APIs with a clear description of the API.

For more information, see Viewing automations.

Pulse configurations in the case type settings

Valid from Pega Version 8.4

In both App Studio and Dev Studio you can now configure Pulse in a simplified and user-friendly way, in the case type settings. Add Pulse posts to cases, define default and add new feed sources, and then customize the Pulse label, all without performing advanced actions, such as configuring sections. You can also define visibility conditions for each post type.

For more information, see Start collaborating faster with simplified Pulse configuration (8.4)Configuring Pulse for case types in Dev StudioConfiguring Pulse for case types in App Studio.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us