SR-B36418 · Issue 293162
More descriptive error message for RAP import
Resolved in Pega Version 7.3
In order to clarify that Schema migration does not support importing a table with the same name as an existing view or a view with the same name as an existing table, the code has been updated to throw a more descriptive exception.
SR-B36743 · Issue 293937
BLOB data save performance improved
Resolved in Pega Version 7.3
In an installation with many large work objects, performance issues were seen when saving a BLOB. This was due to the BLOB still saving data for properties that had been removed, and has been resolved through better tracking of orphan entries of list type properties like string list and java object list.
SR-B37139 · Issue 294520
Installation guide updated to reflect that ADM is supported on MS SQL.
Resolved in Pega Version 7.3
The installation guide has been updated to reflect that ADM is now supported on MS SQL server.
SR-B39528 · Issue 303228
Node startup modified to support very large clusters
Resolved in Pega Version 7.3
Node startup was failing if the cluster had more than 50 nodes. This issue was caused by the query to the "pr_sys_statusnodes" table only returning 50 records; this limitation has been removed.
SR-B40657 · Issue 298764
Clarified database privileges to start Pega
Resolved in Pega Version 7.3
The documentation has been updated for clarity regarding database privileges for start up. The text "Pegasystems recommends that you create an Admin user separate from the Base user; however, if you opt for a single Base user, grant these permissions to the Base user" has been modified to read: "Pegasystems recommends that you create an Admin user separate from the Base user; however, if you opt for a single Base user, grant the Base user both sets of privileges listed above."
SR-B41874 · Issue 301766
View parsing regex fixed for union statements
Resolved in Pega Version 7.3
While importing jar file through import out-of-the-box, generated SQL Scripts from the manual option system had scripts which were already present in the Database. This was caused by the view parsing regex not handling UNION statements, and has been corrected.
SR-B42911 · Issue 301591
Tomcat config documentation clarification
Resolved in Pega Version 7.3
The documentation for using Tomcat has been updated for clarity. Step 2b of 'Configuring Tomcat by editing the context.xml file' indicates that configuration of the Admin datasource is optional (which it is), but steps 3 and 4, which use this datasource, were not labeled as conditional on 2b. As a result, those opting not to use the admin datasource believed those settings needed to be added. In the new text for steps 3 and 4, the clarification "For dual-user configurations only, insert..." has been added.
SR-B43415 · Issue 299493
Upgrade does not exit when encountering corrupt ruleset name
Resolved in Pega Version 7.3
In order to avoid upgrade failures caused by an application rule existing without a version (corrupted data), handling has been added so that the upgrade will not fail if it encounters an application rule without either a name or version.
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