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.

Text area field supports rich text

Valid from Pega Version 7.2.1

You can now configure a text area field on a form to collect plain or rich text from users at run time. By customizing the way that users provide information, you can create cases that display data in different formats and styles.

For more information about the supported options for text area fields, see:

New URL field type on forms

Valid from Pega Version 7.2.1

You can now add a URL field to a form to display a link at run time. By using this field type, you can integrate a case with external resources, such as documents and web pages.

For more information about the URL field type, see:

Improved performance in Process Modeler

Valid from Pega Version 7.2.1

Process Modeler has been enhanced to be faster, more responsive, and easier to use. Opening a canvas is 10 to 35 times faster on flows with 200 shapes.

Enhancements include:

  • Smart guides to help you align shapes
  • New cursors that indicate what you can and cannot do
  • A WYSIWYG display when you move shapes
  • Real-time preview when you swap swimlanes
  • A visible grid when grid snapping is on
  • Actual shapes are dragged instead of a silhouette of the shape
  • Shapes are highlighted in real time when you draw over a selection of many shapes
  • Right-click menu for controlling shape distribution and alignment
  • Keyboard shortcuts
  • Combined panning and zooming
  • Swimlanes pick up shapes when you move a swimlane over them

Keyboard shortcuts added to Process Modeler

Valid from Pega Version 7.2.1

Keyboard shortcuts have been added to the Process Modeler. These shortcuts make the creation of flows easier and more efficient.

For more information, see Process Modeler keyboard shortcuts.

New notifications for case types

Valid from Pega Version 7.2.1

You can now enable email and push notifications for a case type to communicate an event, such as an expired service-level agreement, to users in your application. By calling attention to assignments in a case that require action, you can help users to resolve cases faster.

Assignments in upgraded flows automatically inherit the notification policy that is defined by the case type unless you provide a custom notification activity or explicitly disable notifications in the Assignment shape.

For more information, see: Case notifications.

Adjust case urgency in Case Designer

Valid from Pega Version 7.2.1

You can now provide an urgency when configuring the goal and deadline for a case type in Case Designer. By increasing the urgency of a case that has an expired service-level agreement, you can call attention to unresolved work in your application.

For more information, see Setting goals and deadlines for a case type.

Support for advanced validation conditions for fields on a form

Valid from Pega Version 7.2.1

You can now create complex conditions to validate fields on a form to ensure that a step proceeds only when user input meets expected values. Use the AND and OR operators inside conditions so that the conditions can reference more than one field.

For more information, see Advanced validation conditions for fields on a form.

Pega Survey documentation refers to deprecated field

Valid from Pega Version 7.2.1

The documentation for Pega® Survey refers to the Answer Layout field on the Complex Question form, but this field is no longer supported. For more information about the question layout formats that Pega Survey supports, see Pega Survey.

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.

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