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 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.

Support for data rollback and commit in service-enabled system management

Valid from Pega Version 7.2.1

You can use the service-enabled manage tracked data tool to roll back or commit data that has been imported with the service-enabled import tool.

The service-enabled manage tracked data tool lets you commit imported data or roll back all non-committed data instances to their state immediately prior to when they were imported. The tool only tracks and supports rolling back data instances that do not belong to the PegaRULES database name (Data-Admin-DB-Name).

For more information, see Rolling back and committing tracked data.

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.

Child case queries can be slow after upgrade

Valid from Pega Version 7.2.1

After upgrading, performance might be slow when you run queries on child cases for work tables that existed prior to the upgrade. This issue is often indicated by PEGA0005 (query time exceeded limit) alerts that can be correlated to these queries in the logs. To resolve the issue, add a database index to each of your work tables by using a multicolumn index on the pxCoverInsKey, pxObjClass, and pyStatusWork columns.

For more information, see Performance improvements for child case queries.

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.

Verify ML Readiness error: Upgrades from Pega 7.1.0 through 7.1.8 do not replace nonversioned rules

Valid from Pega Version 7.2

Upgrading from any Pega 7 Platform version between Pega 7.1 and Pega 7.1.8 to Pega 7.2 does not automatically replace nonversioned rules. If you revalidated and saved a Pega 7.1.x rule after the timestamp on the Pega 7.2 version of the rule, upgrading to Pega 7.2 does not overwrite the saved rule. You might see either of the following behaviors:

  • The upgrade fails with the following error message:
    Verify ML Readiness
  • The upgrade succeeds, but you might be unable to open changed rule forms.

If the upgrade fails, see the Pega 7 Platform Upgrade Guide to force the upgrade.

This known issue does not affect Pega 7.1.9. After the upgrade has finished, apply Hotfix 27288. For information about obtaining and applying hotfixes, see Hotfix Manager.

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.

Improved engine startup times

Valid from Pega Version 7.2.1

Performance enhancements in this release decrease engine startup times for new Java virtual machines (JVMs) and improve rule assembly for libraries. JVM startup times are faster because rule utility libraries and functions are no longer generated at startup. For more information, see Extract marker file not created at startup.

Performance improvement to BLOB support in Postgres databases

Valid from Pega Version 7.2.2

New tables that contain BLOB columns now use external storage instead of expanded storage for Postgres databases. This improvement applies to tables that are created during installation, upgrade, or during DDL and schema generation. Using external storage improves database performance.

For more information, see BLOB storage in Postgres databases.

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