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-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.

SR-B90273 · Issue 339015

Corrected assembler SQLSyntax error

Resolved in Pega Version 7.4

If an install was done with the --assembler=true option, certain generated SQLs weren't schema qualified. This resulted in a 'table not found' error and the install failed. This has been resolved by correcting the class identifier references in the cache.

SR-B94098 · Issue 341926

Oracle table metadata performance improvements

Resolved in Pega Version 7.4

Performance improvements have been added for Oracle table metadata queries.

SR-B95455 · Issue 341826

Fixed merge statement generation for long column names

Resolved in Pega Version 7.4

When the merge was generated for a column that had a long name, the generated SQL referred to the column name as a whole in one location and as a truncated name in another. This caused the query to fail. To resolve this, names will not be truncated in the case of PostgreSQL in merge statements.

SR-C11036 · Issue 353252

Extract ruleform DB schema type persists

Resolved in Pega Version 7.4

After an update was installed to enable generation to Database schema on Pega Cloud, the Extract ruleform changed automatically from 'Database Schema' output format to 'XML' even after save or check-in. Any ruleform changes were not getting persisted and always reverted to XML. . This was a missed use case in saving the BIX rule from UI, and has been corrected by resetting the output format when it is PegaCloud and the output format is schema.

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