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-B97043 · Issue 343211

Custom default attributes shown on offer

Resolved in Pega Version 7.4

Custom default values passed in the proposition form were not reflected when the the function pxLoadPropositionAttribute was called. This was caused by the initial value property not being transferred from the form to the caller of pxLoadPropositionAttribute function, and has been fixed.

SR-C7742 · Issue 349877

Proper cleanup for leftover clipboard pages after sync

Resolved in Pega Version 7.4

When the stateful sync requestor has finished, all pages that are replaced on the next sync should be removed. Several pages were found to not be cleaned up as expected, and this has now been corrected.

SR-C8899 · Issue 349868

ABAC exception handling added

Resolved in Pega Version 7.4

After creating an access control policy and access control policy condition on a data class that shows in the Data Explorer, defining the condition such that it was always false and then clicking on the class on which the policy was just defined generated an error. If the policy was withdrawn and then clicked on again, it appeared as expected. This was reproducible only when ABAC was enabled, and handling for an exception generated in this scenario has been added.

SR-B65434 · Issue 334578

Oracle table metadata performance improvements

Resolved in Pega Version 7.4

Performance improvements have been added for Oracle table metadata queries.

SR-B74189 · Issue 334576

Oracle table metadata performance improvements

Resolved in Pega Version 7.4

Performance improvements have been added for Oracle table metadata queries.

SR-B76468 · Issue 336009

Oracle table metadata performance improvements

Resolved in Pega Version 7.4

Performance improvements have been added for Oracle table metadata queries.

SR-B76989 · Issue 327639

Informational text added to "No suitable driver" error message

Resolved in Pega Version 7.4

After configuring Pega to connect to an external database using Data-Admin-DB-Name with a JDBC URL configuration that had the appropriate jar for the driver in the application server classpath, unexpected behaviors were seen. The first time the Test Connectivity button was clicked, a "No suitable driver found" error appeared. The second click ran the test as expected. This confusion was related to an undocumented enhancement: because adding a new database JDBC driver in Pega may require configuration to get the driver class loaded to the classpath, the 'No suitable driver' exception was enhanced with the configuration required to get the JDBC driver loaded at the next restart. In order to avoid confusion, informational text will now appear as part of the "No suitable driver" error message to explain this.

SR-B82933 · Issue 333921

SQL queries constructed to stay below 1000 limit

Resolved in Pega Version 7.4

A very large SQL query referencing a large number of history classes was generating an SQL syntax error exception due to exceeding the maximum number of expressions in a list (1000). In order to support large queries, the SystemManagementUtils.generateWhereINClause function will now construct queries that stay below that limit per single query.

SR-B86451 · Issue 334135

SQL queries constructed to stay below 1000 limit

Resolved in Pega Version 7.4

A very large SQL query referencing a large number of history classes was generating an SQL syntax error exception due to exceeding the maximum number of expressions in a list (1000). In order to support large queries, the SystemManagementUtils.generateWhereINClause function will now construct queries that stay below that limit per single query.

SR-B89556 · Issue 341256

fixed exception for relaystate with more than 128 characters with DB2

Resolved in Pega Version 7.4

In IDP initiated SSO, an SQL error was generated when using DB2 and the relaystate contained more than 128 characters. This was caused by DB2 validating the column length of the 'where' clause column, and those column bytes exceeding the declared length of 128. This 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