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.