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.

Privilege required for Recent Explorer

Valid from Pega Version 7.1.1

Users with custom roles defined must add the pxUpdateRecents privilege to see work in the Recent Items Explorer. 

Use standard Developer portal

Valid from Pega Version 7.1.1

Customized versions of the Developer portal rely on legacy components and are not supported.

To avoid backwards compatibility issues, update your access group to point to the standard Developer portal prior to upgrade.

Top-level (named) pages may no longer be classless

Valid from Pega Version 7.1.1

Newly created top-level (named) pages may no longer be classless or have a blank pxObjClass property. This change can affect applications upgrading from versions prior to Pega 7 to the latest version, especially when:

  • Application logic relies on a blank value in the pxObjClass property.
  • An activity assumes a new top-level page is classless and explicitly sets pxObjClass in a Property-Set step.
  • A data transform assumes a new top-level page is classless and explicitly sets pxObjClass using a Set action.

To avoid application failures, remove or update any logic that expects a blank pxObjClass. Where possible, use the new engine API that finds a page by both name and class:

findPageWithException(PageName, ClassName);

Activities and data transforms continue to create a top-level page when one does not exist. The class name is now derived from the Pages and Classes tab.

Pinned classes in Application Explorer

Valid from Pega Version 7.1.6

The Application Explorer now includes a Pinned Classes section. This feature allows you to interact with a customized list of classes without having to explicitly switch context in the explorer.

Ability to deprecate a rule

Valid from Pega Version 7.1.6

You can deprecate any Rule- instance to indicate that it is no longer supported.

Users are warned when they open or reference a deprecated rule instance.

Ability to deprecate a class

Valid from Pega Version 7.1.6

You can deprecate any Rule- class to block users from creating new rule instances.

Users are warned when they open the class rule form or any instance of the class.

Only classes that do not belong to a class group can be deprecated.

Designer Studio responds to deprecated rules

Valid from Pega Version 7.1.6

Deprecated classes and rule instances in Pega- rulesets are excluded from:

  • Search results
  • Application Explorer results
  • Lists launched from the Records Explorer
  • +Create menus

These restrictions do not apply to classes and rule instances deprecated in your application rulesets.

Retired Six R's

Valid from Pega Version 7.1.6

The Designer Studio > Application > Inventory > Six R's landing page has been retired.

Integration landing page updates

Valid from Pega Version 7.1.6

The following features and wizards now launch as landing pages in the Designer Studio:

Designer StudioIntegration > Tools > Wizard cleanup

Designer StudioIntegration > Email > Email Accounts

Designer StudioIntegration > Email > Email Listeners

Restructured Process & Rules landing pages

Valid from Pega Version 7.1.6

The Designer Studio > Process & Rules > Tools landing page menu has been restructured for better navigation and access:

  • The Find Rules by Custom Field wizard now launches as a tab in Designer Studio.
  • A new Find Rules menu item consolidates previous wizards. It launches a single landing page with different search criteria options:

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