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.

New achievement badges

Valid from Pega Version 7.2.1

New achievement badges have been added to help you learn about and explore Pega Express.

The new badges are:

  • Configure a new application view
  • Configure a layout
  • Add a chart to a report
  • Set a profile picture
  • Post to Pulse
  • Manage team details
  • Enable push notifications

For more information about badges, see Achievement badges.

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.

Escalation actions removed from case-wide goals and deadlines

Valid from Pega Version 7.2.1

The option to define an escalation action for a case-wide goal and deadline has been removed from Case Designer because the standard actions, Notify assignee and Notify manager, apply to assignments, not cases. You can still define escalation actions for goals and deadlines that apply to an assignment.

For more information, see Defining an escalation action for an assignment.

Deprecation of override rulesets in run-time ruleset lists

Valid from Pega Version 7.2.1

Pega 7.2.1 is the last release where override rulesets can be incorporated in the run-time ruleset list. The ability to create override rulesets was originally deprecated in Pega 7.1. However, any override rulesets that were created in releases prior to Pega 7.1 in the application ruleset lists were still incorporated into the run-time ruleset lists at the appropriate location. In releases after Pega 7.2.1, override rulesets will be ignored and will not be incorporated in the run-time ruleset list. Therefore, it is recommended that you use production rulesets in access groups instead of override rulesets.

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.

Support for advanced conditions on processes in a stage

Valid from Pega Version 7.2.1

You can now configure advanced conditions on a process in a stage to ensure that the process starts only when user input matches 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 conditions on processes in a stage.

MBean Javadocs download file

Valid from Pega Version 7.2.1

The Pega 7 Platform MBean Javadocs are no longer provided in the distribution image; however, you can download the MBeanJMXJavadoc.zip file that was previously provided in the distribution image.

You can also use JConsole, which is included with the Java Development Kit (JDK), to obtain MBean information. The JConsole MBean tab provides attributes, operations, notifications, and other information on all the MBeans that are registered with the MBean server.

Enhanced Expression Builder for certain rule types

Valid from Pega Version 7.2.1

For certain rule types, several enhancements to the Expression Builder help you to efficiently build expressions in a user-friendly environment. Enhancements include:

  • The ability to use single-line or multi-line comments to explain the purpose of the expression.
  • Formatting, such as tab characters and carriage returns, that is preserved the next time you open the Expression Builder after closing it.
  • Real-time validation of expressions so that you receive immediate feedback about the syntax in your expression.
  • The ability to test the input value of a property for a portion or all of the expression.

These enhancements apply to the Expression Builder for the following types of rules:

  • Data Transform
  • When
  • Map Value
  • Decision Tree
  • Decision Table
  • Strategy

For more information, see Expression Builder enhancements for certain rule types.

Support for additional health metrics on the Application Quality landing page

Valid from Pega Version 7.4

On the Application Quality landing page, you can monitor the health of your current application to identify areas that need improvement before deployment. The landing page provides application metrics such as the number of executable rules, the guardrail score, the number of guardrail warnings, the test coverage percentage, and the pass rate of PegaUnit tests. From this landing page, you can also view data for the entire application, for each of its cases, and for rules that are not part of any case type.

For more information, see Application Quality landing page.

View the configuration settings for Pega Platform nodes in Designer Studio

Valid from Pega Version 7.4

On the new Configuration Settings landing page, you can view a list of the configuration settings for a specific node, current or remote, or for an entire cluster. From this landing page you can diagnose settings issues, determine whether settings are loaded correctly, and review the settings' purposes. You can also download the prconfig.xml file for any node in a cluster to modify the settings. The ability to view settings for all nodes in the Cluster from a single landing page makes diagnosing configuration issues across the cluster simpler and easier than logging on to each node individually to view its system settings. For example, if a started agent does not run, you can check if agents are enabled on your system; or if some of your caches are too big, you can check the setting for the cache size. You can also determine if settings are loaded correctly, and identify discrepancies in the settings across the nodes.

For more information, see Viewing the current configuration settings of a node or the whole cluster, Downloading and viewing the prconfig.xml file for a specific node, REST APIs for viewing the configuration settings for Pega Platform.

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