Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

Addition of Data Access Tab to access control policy condition rules

Valid from Pega Version 8.6

You can now select associations and declarative index classes when creating access control policy condition rules. The Column source field in the policy condition can now accept properties from available associations and indexes. For ease of reference, the selected associations and indexes are available on the new Data Access tab. 

Using the new tab, you can build complex authorization models in which access restrictions for a class depend on the attributes present in the associated and indexed classes, along with the attributes in the current class. For example, a project management application can now separately maintain project lists for each operator and use that information to restrict read/write access to unique projects.

The information available on the new Data Access tab reflects rule form changes, which are similar to the existing functionality of the Report Definition in the Application Data Model. 

 

For more information, see Creating an access control policy condition.

Addition of Servlet Management

Valid from Pega Version 8.6

Pega Platform™ now has Servlet Management in Pega Cloud® Services, which provides a simple and secure way to make changes to Pega Platform servlet definitions.

Servlet Management provides Pega Cloud Service clients with solutions to manage servlet configurations with self-service options. This reduces the cycle time for delivering configuration changes in Pega Cloud Service installations while also improving upgrade reliability

For more information, see Servlet management.

Upgrade impact

Clients with no application servlet customizations will not experience an impact. If you upgrade from Pega Platform version 8.5 or earlier and, prior to the upgrade, the Pega Cloud team provided your application servlet customizations, then following the upgrade, you must manually add, remove, or modify your servlet customizations in your upgraded application using this servlet management landing page in Pega Platform.

What steps are required to update the application to be compatible with this change?

To manually move your pre-upgrade servlet customizations as appropriate or add new ones to your upgraded application using the new servlet management landing page, follow the steps in Adding a servlet.

Cosmos React-UI supports custom authentication

Valid from Pega Version 8.6

Pega Platform™ now supports custom authentication in applications that use Cosmos React-UI. Depending on the needs of your users and the functionality of your application, you might need to write custom authentication schemes to meet specific requirements. 

Clients that use custom authentication in their applications can now take advantage of the Cosmos React-UI.

For more information, see Securing Cosmos React-UI applications.

Integration and security tab now divided into two tabs

Valid from Pega Version 8.6

The Integration and Security tab is now two separate tabs on the Application Definition form: Integration and Security. While the content of these two tabs are related, they function more effectively as separate tabs. The Security tab now includes the Authentication section, so you can add existing authentication services to your Application Definition to more effectively manage the security of your application. 

For more information, see Security tab of the Application Definition.

Enabling security policies now requires current password

Valid from Pega Version 7.1.3

As part of Pega’s initiative to protect against malicious attacks, the change password dialog has been enhanced.  When Security Policies have been enabled for your system, new users or those with expired passwords will now be prompted for both their existing password as well as their desired new password.

For more details, review the Designer Studio > System > Settings > Security Policies landing page.

Designer Studio

Valid from Pega Version 7.1.3

Numerous usability improvements were made for this release. A group of cosmetic, functional, and performance enhancements were also included.

  • Treegrid controls work more quickly in IE9 and IE10.
  • On application ruleforms, the 5.4 "Place Properties on Thread Page" checkbox will work in 7.1.
  • Message error handling has been improved.
  • Log messages have been cleaned up.
  • Connectors may now be used in Data Pages.
  • Move Rules wizard has been enhanced to work in Version 7.1.

SAML single sign-on is easier to configure

Valid from Pega Version 7.4

Implementing SAML single sign-on (SSO) login authentication in your application is now less complex. You can now configure most requirements that used custom activities or Java code in previous releases from the Authentication services form.

For more information, see Creating an authentication service.

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.

Support for templated auto responses during email triaging of interaction cases

Valid from Pega Version 7.4

When you triage an interaction case by email, you can now select a predefined email response to provide feedback to a customer more quickly. The category that is associated with this email determines the type of responses that you can select. You can create an email response template or use an existing template.

For more information, see Defining suggested replies for the Email channel.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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