SR-B3280 · Issue 279492
Resolved skimming error
Resolved in Pega Version 7.3
Errors were getting thrown on the screen while performing minor ruleset version skimming of one version into a new ruleset version which was higher than the ruleset version mentioned in the application rule. This was due to the target version not having the correct context because the application didn't yet exist or because the operator was not logged into the target context. In order to resolve this, the messages in the page will be cleared before skimming to avoid validation. It is then recommended to log into the new application and use the Application Validation tool to validate the newly created rulesets application.
SR-B35799 · Issue 293251
Alerts modified to correct logged interaction totals
Resolved in Pega Version 7.3
The PEGA0069 alert identifies when a client load of a screen takes longer than the threshold for the alert. A client load can contain multiple server interactions and the PAL for the alert should be the aggregate of all these interactions. However, the calculations for pxTotalReqTime were duplicated in the code for the PEGA0046 and PEGA0069 Alerts, causing incorrect data. This has been fixed.
SR-B35799 · Issue 277230
Alerts modified to correct logged interaction totals
Resolved in Pega Version 7.3
The PEGA0069 alert identifies when a client load of a screen takes longer than the threshold for the alert. A client load can contain multiple server interactions and the PAL for the alert should be the aggregate of all these interactions. However, the calculations for pxTotalReqTime were duplicated in the code for the PEGA0046 and PEGA0069 Alerts, causing incorrect data. This has been fixed.
SR-B35931 · Issue 293471
prpcUtils readme updated for importing to Oracle
Resolved in Pega Version 7.3
The readme regarding importing to an Oracle database has been updated to reflect the current state of prpcUtils.
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.