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.

All tabs are accessible on delegated rule forms

Valid from Pega Version 7.1.1

Delegates can now access all tabs in a delegated rule form.

You can continue to customize the development experience for delegated users, such as line managers, who may not require the full set of rule form options. For example, you can prevent users from adding new nodes on the Decision Tree form or using the expression builder on the Map Value form. All users, including delegated users, can remove these restrictions if they hold a rule-editing privilege.

For more details on this process and a list of commonly delegated rules, see How to delegate a rule.

Compare rule versions in a rule form

Valid from Pega Version 7.2.2

You can now compare different versions of rules from the Actions menu when you work within a rule form instead of using the Rule Compare utility. You can inspect changes that were made between versions directly on the rule form, make updates, and save any changes to the rule form.

For more information, see Rule version comparison within a rule form.

View all nodes in a cluster from the Cluster Management landing page

Valid from Pega Version 7.2.2

Use the Cluster Management page to view information for all of the available nodes in a cluster. To view the nodes, click Designer Studio > System > Operations > Cluster Management. To access detailed information about a single node, click Actions.

For more information, see System Operations.

Logic-based assignment routing

Valid from Pega Version 7.2.2

You can now define business logic that controls when and by whom an assignment is processed in a case. By routing assignments to a specific user or group of users, you can help ensure that cases are resolved faster.

For more information, see Logic-based assignment routing.

Support for additional rule types for PegaUnit test cases

Valid from Pega Version 7.2.2

To compare the expected results with the results that are returned by running a rule, you can now create PegaUnit test cases for the following rule types:

  • Activities
  • Data transforms
  • Strategies
  • Decision trees
  • Decision tables

After you unit test these rules, you can convert them to test cases and configure assertions on the test cases. You can also set up the clipboard with data before tests are run, and clean up the clipboard after tests are run.

For more information, see PegaUnit testing.

Page assertions are supported for PegaUnit test cases

Valid from Pega Version 7.2.2

You can now create page assertions for PegaUnit test cases. Because data transforms and activities can create or remove pages, you can configure page assertions to determine whether a page exists after you run PegaUnit test cases.

For more information, see Configuring page assertions.

New Automated Testing landing page

Valid from Pega Version 7.2.2

The new Automated Testing landing page displays all the PegaUnit test cases in your application. You can use it to quickly access, run, and view results of tests. In addition, if you have the AutomatedTesting privilege enabled, you can switch to the Automated Unit Testing landing page to access rules that are supported by both PegaUnit testing and Automated Unit Testing, such as activities.

For more information, refer to Automated Testing landing page.

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