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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-D44857 · Issue 510735

Node level data page now specifies tenant name in MT environments

Resolved in Pega Version 8.4

In order to address a requestor contention between different tenants during the load of node level data page in multi-tenant environments, an enhancement has been added that will specify the tenant name in the data page name. This will improve performance by allowing different tenants to have different locks, ensuring the process of data page loading on one tenant will not make another tenant wait for the loading of the same data page. Additional debug and trace logging has also been added to provide more information related to declarative rule cache management.

SR-D44878 · Issue 510732

Node level data page now specifies tenant name in MT environments

Resolved in Pega Version 8.4

In order to address a requestor contention between different tenants during the load of node level data page in multi-tenant environments, an enhancement has been added that will specify the tenant name in the data page name. This will improve performance by allowing different tenants to have different locks, ensuring the process of data page loading on one tenant will not make another tenant wait for the loading of the same data page. Additional debug and trace logging has also been added to provide more information related to declarative rule cache management.

SR-D45622 · Issue 521662

Sorting on Grid works with declare expression property

Resolved in Pega Version 8.4

If a property with a declare expression was used in a column, the sorting on that column was not working. This was traced to reference errors when Grid used the engine API pega.sortPageList to sort the page list / data page, and has been corrected.

SR-D47752 · Issue 513752

Resolved Assembly time error for findPage signatures with two arguments

Resolved in Pega Version 8.4

Due to the introduction of IL assembly, an Assembly time error was generated after upgrade when saving a 'when' rule that had a page with the same name defined in both Parameters and Pages & Classes. To resolve this, if the system is generating PegaAPI#findPage or PegaAPI#findPageWithException and passing a null as the second argument, then it will be cast as a String. This will ensure the compiler will not become confused as to the type of null when there are multiple findPage signatures with two arguments.

SR-D48960 · Issue 517880

Exception stack trace will be included as comments in generated assembly code

Resolved in Pega Version 8.4

When there is an exception during assembly time, that original exception message is assembled in the generated code. To improve the process of finding the the root cause by examining the original exception stack, the system has been updated to insert the original exception stack trace into the generated code as comments.

SR-D50016 · Issue 515904

Exception stack trace will be included as comments in generated assembly code

Resolved in Pega Version 8.4

When there is an exception during assembly time, that original exception message is assembled in the generated code. To improve the process of finding the the root cause by examining the original exception stack, the system has been updated to insert the original exception stack trace into the generated code as comments.

SR-D50528 · Issue 514133

Exception stack trace will be included as comments in generated assembly code

Resolved in Pega Version 8.4

When there is an exception during assembly time, that original exception message is assembled in the generated code. To improve the process of finding the the root cause by examining the original exception stack, the system has been updated to insert the original exception stack trace into the generated code as comments.

SR-D51536 · Issue 515067

Holdability flag set on connection for using MS SQL in Designer Studio

Resolved in Pega Version 8.4

Static assembler was not working from Designer Studio, displaying the error "com.microsoft.sqlserver.jdbc.SQLServerException: SQL Server supports holdability at the connection level only. Use the connection.setHoldability() method." Investigation showed that ApplicationAssembly.getResultSetForQuery explicitly sets the holdability flag on the prepared statement, and this issue has been resolved by updating the system to set the holdability flag on connection as well.

SR-D51725 · Issue 516468

DSS added to rpevent logging of sensitive data used as input during async batch task processing

Resolved in Pega Version 8.4

When running Async Batch Task Processing, the whole set of inputs was logged when an error occurred during ADP load. Because this might result in sensitive data such as SSN, DOB, IDs, etc, being included in the debugging output, a DSS has now been added which when set will avoid printing any sensitive information in the log.

SR-D53253 · Issue 515309

Versioning information removed from Universal SMA

Resolved in Pega Version 8.4

To clarify that Universal SMA is compatible with Pega 7.4 and all below versions, the repository name has been changed to remove the versioning number so it is listed as only "Universal SMA".

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