SR-B80438 · Issue 343243
Unauthenticated requestor timeout customizable
Resolved in Pega Version 7.4
An enhancement has been added to provide a new customizable configuration switch for the unauthenticated requestors timeout value, i.e. the short lived requestor timeout value. Previously, this defaulted to one minute.
SR-B91029 · Issue 342265
hbase config enhancement
Resolved in Pega Version 7.4
In order to support a customization, the hbase configuration has been enhanced to not only accept values from the UI, but also from various levels of Pega setup including prconfig.xml, hbase-site.xml, and dynamic system settings.
SR-B91029 · Issue 342841
hbase config enhancement
Resolved in Pega Version 7.4
In order to support a customization, the hbase configuration has been enhanced to not only accept values from the UI, but also from various levels of Pega setup including prconfig.xml, hbase-site.xml, and dynamic system settings.
SR-B92192 · Issue 342143
Unauthenticated requestor timeout customizable
Resolved in Pega Version 7.4
An enhancement has been added to provide a new customizable configuration switch for the unauthenticated requestors timeout value, i.e. the short lived requestor timeout value. Previously, this defaulted to one minute.
SR-C8717 · Issue 350603
hbase config enhancement
Resolved in Pega Version 7.4
In order to support a customization, the hbase configuration has been enhanced to not only accept values from the UI, but also from various levels of Pega setup including prconfig.xml, hbase-site.xml, and dynamic system settings.
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.