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.

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.

Improved security after hiding SQL values

Valid from Pega Version 8.6

In Pega Platform™ version 8.6, the default value of the showSQLInList dynamic system setting changes to FALSE, which suppresses the visibility of the SQL values in the Clipboard tool. With this setting disabled, when you run a report definition the clipboard does not display sensitive values in the pxSQLStatementPre and pxSQLStatementPost properties, which makes your system less vulnerable. If you want to display the values, in the .prconfig file, set the prconfig/security/showSQLInListPage/default to TRUE.

Additional connection pool parameters for JDBC URL external databases

Valid from Pega Version 8.6

For improved external JDBC URL database connection performance, Pega Platform™ now supports multiple Hikari connection pool parameters directly in the Data-Admin-DB-Name rule. Previously, Pega Platform supported a limited number of connection pool parameters to optimize your database connection using dynamic system settings (DSS). Now you can optimize your JDBC URL connection pool sizing to meet your traffic requirements through additional parameters without switching rules. Additional parameters include client-request parameters to maximize the connectivity to your external databases.

For more information, see Creating and updating external database instances with JDBC URLs.

Upgrade impact

During an upgrade to Pega Infinity™ release 8.6 and later, clients who previously specified their JDBC URL connection parameters through dynamic system settings (DSS) or prconfig file must delete the corresponding DSS or prconfig elements immediately after upgrade. The old parameters that you previously specified through DSS or the prconfig file override the equivalent parameters that you specified in the JDBC URL rule after your upgrade.

For more information about deleting your previous DSS or prconfig elements, see Deleting dynamic system setting connection parameters and Deleting connection parameters in the prconfig file.

Enhanced PEGA0104 alert

Valid from Pega Version 8.6

The PEGA0104 alert now includes the thread pool size, a list of activities that are waiting in the queue for a thread to become available, and details on how long it took to capture the thread dump.  By default, the alert also includes the thread dump.  You can disable the inclusion of the thread dump by changing the related configuration option. 

For more information, see PEGA0104 alert: Background tasks have exceeded a threshold time when attempting to acquire a thread from pool or executor.

New alert for job scheduler activity that exceeds a time threshold

Valid from Pega Version 8.6

Pega Platform™ now saves the PEGA0130 alert in the performance alert log at the time that a scheduled job exceeds the configured threshold value. To identify performance issues with long-running processes, you can monitor the log for the alert while the job scheduler runs.

The alert is enabled by default. You can change the default threshold value or disable the alert in dynamic system settings.

For more information, see PEGA0130 alert: Current Job Scheduler run is taking too long.

Data model inheritance does not depend on ruleset context

Valid from Pega Version 8.6

Search and Reporting Service (SRS) in Pega Platform™ 8.6 now provides an improved method of synchronizing data model by distinct users. In applications built on earlier versions of Pega Platform, some users might encounter difficulties in indexing data. Now, the data model that the system sends to SRS does not depend on access privileges. With this enhancement, each user of your application is eligible to synchronize data.

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.

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