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.

Support for advanced validation of embedded and referenced data

Valid from Pega Version 8.5

To help you define validation conditions for a broader range of use case scenarios, Pega Platform™ now supports stage entry validation for embedded fields in the form of a validation matrix. You can now define validation conditions for both field groups and field group lists, and easily navigate between them. You can also select any fields and when conditions while building a condition for both field-level and stage-level validation.

For more information, see Validating field values for stage entry.

Complete email and notification approval in App Studio

Valid from Pega Version 8.5

App Studio now supports complete email approval configuration directly in the Case Designer. Email approval settings now include composing a new message or selecting a template, saving templates to a library for future reuse, and adding attachments to an email. Additionally, you can now send the approval as a push notification to mobile users. With full configuration of email approval in App Studio, you save time and create unique and personalized email messages and push notifications in a no-code, intuitive way. 

For more information, see Obtain approvals from email and push notifications from App Studio (8.5), Requesting approval by email and push notification.

Business logic routing of approval steps

Valid from Pega Version 8.5

Pega Platform™ now supports routing of approval steps by applying business logic, in both App Studio and Dev Studio. Business logic uses a set of conditions to determine the most appropriate worker to approve a case by routing the approval based on defined conditions. For example, in a loan request case, the application can route the approval step to a manager if the importance of the case is set to high. For greater accuracy, business logic can also use skill set, availability, and workload to determine the appropriate worker. With business logic routing, you increase work efficiency and speed up case resolution.

For more information, see Determine a relevant case approver by using business logic (8.5), Requesting approval from users.

Default Create stage in a case life cycle

Valid from Pega Version 8.5

Pega Platform™ now adds a default Create stage to a case life cycle every time you create a new case type, both in App Studio and Dev Studio. The default Create stage includes a view that users interact with to provide initial data before case processing begins. Consequently, you can now easily locate the view to make any necessary changes. In the background, the Create stage makes a case type independent from the starting process, which removes relevant advanced configurations and makes application development faster.

For more information, see Capture initial data faster with the default Create stage (8.5), The Create stage.

Case Manager option for searching only attachments

Valid from Pega Version 7.2

Case Manager search now has an option to search only case attachments. When you search attachments, a new column in the search results displays a paperclip icon with the number of attachments that match the search string. You can click the number to display a list of matching attachments for the selected case.

The Declarative Network display is now cross-browser compatible

Valid from Pega Version 7.2

The Declarative Network display can now be displayed on all browsers.

Label changes to field types in Case Designer

Valid from Pega Version 7.2

The following field types have been renamed in Case Designer to be consistent with Data Designer and other areas of the Pega 7 Platform.

Label in previous versionsLabel in Pega 7.2
TextText (single line)
Text (multiple lines)Text (paragraph)
Check boxBoolean
Date and timeDate & time
DateDate only
Drop downPicklist
Number (integer)Integer
Number (decimal)Decimal

Users who upgrade from versions prior to Pega 7.2 do not have to take any action because the label changes are cosmetic and do not affect the underlying controls or property types that support form building.

For more information about the field types that you can use when building a form, see Storage and display of single-value fields.

New Pulse gadgets for developers

Valid from Pega Version 7.2

Pulse for the Pega 7 Platform provides two new gadgets: pxContextFeed and pxActivityFeed.

The pxContextFeed gadget is a section that you can integrate with your application. Users can use this gadget to communicate with other users by creating and sharing posts within a given context. You can also customize the gadget or build your own Pulse interface by using a number of APIs.

The pxActivityFeed gadget aggregates all the activity feeds for the cases that a user follows without requiring that individual cases for posts be viewed.

For more information, see the help topic Pulse gadgets and custom APIs.

New Pulse gadget for users

Valid from Pega Version 7.2

You can use Pulse to communicate and collaborate with other users. For example, in Pulse you can post messages, share files, select cases for which you want to receive emails, search for content, and view an activity feed in your dashboard that aggregates your Pulse posts.

For more information, see Pulse for social collaboration.

New types of steps in a process

Valid from Pega Version 7.2

You can add assignments, subprocesses, and preconfigured steps to a process in Case Designer. By using these new step types, you can quickly enhance your case life cycle and identify opportunities for reuse. This change also delivers a more consistent experience to users who are working in Case Designer and Process Modeler.

For more information, see Steps in the life cycle of a case.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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