SR-B44278 · Issue 302830
MT guide updated for rules blocking/restriction
Resolved in Pega Version 7.3
The MultiTenant guide has been updated to clarify what causes rules to be blocked or restricted and the possible consequences of unrestricting rules.
SR-B48780 · Issue 305215
Oracle/Unix documentation updated with JDBC instructions for urandom instead of random
Resolved in Pega Version 7.3
The Install/Upgrade guides have been updated to reflect that recent changes to Oracle have created the requirement of forcing the JDBC driver to use /dev/urandom instead of /dev/random to improve security as well as connection open and close performance. The guide now recommends customers running Oracle on Unix do one of the following: 1. Update $JAVA_HOME/jre/lib/security/java.security to use securerandom.source=file:/dev/./urandom 2. Set system property -Djava.security.egd=file:///dev/urandom
SR-B8847 · Issue 278000
FCM/FCMR documentation updated
Resolved in Pega Version 7.3
The documentation on the PDN for installing and configuring FCM 7.12 has been updated for FCM and FCMR.
SR-B8898 · Issue 279449
Reference to outdated property removed
Resolved in Pega Version 7.3
When building a system with WebSphere 8.5.5, DB2 10.5fp7 and Java 8, creating the environment and testing the connection on its datasource produced the warning: "DSRA8200W: DataSource Configuration: DSRA8020E: Warning: The property 'progressiveLocators' does not exist.". This was traced to a code fragment left after that property became unsupported which has now been removed.
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.