Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-B1495 · Issue 273198

Workaround to resolve HP NonStopDB column label bug

Resolved in Pega Version 7.3

Using HP Non Stop DB as an external DB with Type 4 driver caused Connect-SQL with Browse to generate the error "UNKNOWN_COLUMN_0: Column number 0 has an invalid name errors in clipboard" but still return the data. This was traced to a bug in the HP driver that caused the getColumnLabel() to be returned as empty, and the system has been updated to return the Column Name when Column Label is null or empty to overcome this.

SR-B15101 · Issue 296224

Logic added to convert UTC Date for REST clipboard mapping

Resolved in Pega Version 7.3

An error was generated while mapping UTC format Date fields to the clipboard in REST. This was traced to the DateTime properties in the JSON response not being converted to Pega-supported datetime format, and the necessary parsing logic has been added.

SR-B15138 · Issue 285032

RUF and listener updates made to support new version of Bouncy Castle

Resolved in Pega Version 7.3

Compatibility issues were found with Bouncy Castle 1.49 and newer versions of WebLogic. In order to proceed with updating Bouncy Castle to the latest version, the SendEmailMessage RUF in Pega-IntegrationEngine and Pega-Procom has been modified to adhere to the newer Bouncy Castle APIs, and the email listener has been updated. The logic related to Rule utility function compilation has been changed to only to consider the top version of a library.

SR-B15143 · Issue 285148

Garbage Collector access fixed in Logging screen

Resolved in Pega Version 7.3

SMA Garbage Collector information was not available under Logging and Tracing due to a naming error; this has been fixed.

SR-B154 · Issue 272522

Performance improvements for TableInformation queries

Resolved in Pega Version 7.3

System performance has been improved by caching and reusing the out-of-the-box query results used by TableInformation Cache to get the list of columns for a given table.

SR-B154 · Issue 290493

Performance improvements for TableInformation queries

Resolved in Pega Version 7.3

System performance has been improved by caching and reusing the out-of-the-box query results used by TableInformation Cache to get the list of columns for a given table.

SR-B15456 · Issue 285110

Cassandra encryption enhancements

Resolved in Pega Version 7.3

An enhancement has been added to support encryption of Cassandra internode and client/server connections through the addition of Pega Platform command line properties. These allow specification of encryption properties such as keystones and use of properties to generate corresponding settings in the cassandra.yaml configuration file and initialize the datastax driver with SSL enabled if encryption is required.

SR-B15456 · Issue 286718

Cassandra encryption enhancements

Resolved in Pega Version 7.3

An enhancement has been added to support encryption of Cassandra internode and client/server connections through the addition of Pega Platform command line properties. These allow specification of encryption properties such as keystones and use of properties to generate corresponding settings in the cassandra.yaml configuration file and initialize the datastax driver with SSL enabled if encryption is required.

SR-B15463 · Issue 287079

New Application operator mapping refinements

Resolved in Pega Version 7.3

When using the New Application Creation wizard, the newly created operators were unexpectedly mapped to the same access group even though the access groups contained different roles. This has been corrected with changes in the pxPrepareApplicationDemoUsers and pxPrepareClonedAccessGroup activities to set transient properties for the original access group name as well as for use in lookup by demonstration users.

SR-B15497 · Issue 286469

Styling corrected for last row in tree grid sourced from RD

Resolved in Pega Version 7.3

Tree grids sourced from report definitions had their last row set to the class "grandTotal" instead of "gridRow", causing them to get incorrect styling. This was caused by a missed cleanup for this use case when removing the GrandTotal class from support in RD, and has been fixed.

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