SR-B31818 · Issue 292752
Security update for URL string queries
Resolved in Pega Version 7.3
To ensure sensitive information is not exposed in transit between the client and server via URL query string parameters, pyCaseManager Menu and pzGetUserProfile activity have been updated to avoid passing the user ID as a parameter.
SR-B31825 · Issue 288489
Documentation correction for service-enabled system management
Resolved in Pega Version 7.3
The help file for service-enabled system management has been updated to correct and clarify the full path used for connection properties in conjunction with the --connPropFile argument.
SR-B31876 · Issue 290136
Correspondence logic corrected for party ID
Resolved in Pega Version 7.3
When using the Send Email smart shape to send correspondence to work party, party Roles containing the string "Owner" (such as "AAOwner") caused the correspondence to be sent to the email address of the "Owner" party instead of the "AAOwner" party. This was caused by a logic error in the party list iteration that used 'contains' instead of 'equals', and has been fixed.
SR-B32559 · Issue 301028
New prconfig setting for auto-flipping Oracle optimizer
Resolved in Pega Version 7.3
Severe performance issues were seen while importing a RAP with Oracle 11g and 12c due to an Oracle bug related to SMA queries involving all_constraints. To fix this, the Oracle parameter _optimizer_push_pred_cost_based must be set to false before the execution of the SMA query and set back to true after its execution at the session level. This is not set on the system level since Oracle recommends against it. In order to ease this process, the flag setting can be controlled through the prconfig setting '"database/performance/smaqueryperformanceenabled". This prconfig setting will default to true in order to automatically set/unset the Oracle parameter each time it is needed.
SR-B32559 · Issue 297457
NexFlow requestor performance improvements
Resolved in Pega Version 7.3
The deployment of the Nexflow Application RAP was failing due to a requestor synch timeout if 'includeSynonyms' was enabled on the DB connection. Code updates have been implemented to improve performance to resolve this.
SR-B32559 · Issue 301682
Workaround for Oracle SMA query timeout
Resolved in Pega Version 7.3
A bug in Oracle can cause an SMA query involving all-constraints to take a long time to execute, which in turn can cause RAP/application bundle imports to hang. The workaround for this is to set the Oracle parameter _optimizer_push_pred_cost_based to false before the execution of the SMA query involving all-constraints, then set it back to true after its execution at the session level.
SR-B3263 · Issue 275060
Performance improvements for opening pop up grid dialog box
Resolved in Pega Version 7.3
Performance improvements have been made in opening the pop up dialog box in pzPerformGridAction by executing the copying logic only if the page is read-only.
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-B33088 · Issue 293375
pyGetAttachmentContent modified to access class for new properties
Resolved in Pega Version 7.3
The out-of-the-box properties IsDataPageRefreshed and PxAttachName were generating errors indicating the page contains undefined properties. The issue was with the activity pyGetAttachmentContent. As the properties pxAttachName and pyURL etc. are present in their respective classes and the data page class is Data- the errors were not visible. To correct this, pyGetAttachmentContent has been modified to use Page-Change-Class in the activity to change to the correct class so that properties can be accessed. pzRemoveAttachments and pzRefreshAttachmentList have also been updated to use pyIsDataPageRefreshed (new property created).
SR-B33387 · Issue 298483
Incorporated synchronized timestamp function for addWarning
Resolved in Pega Version 7.3
When the pxWarningCreatedDateTime was the same for two warnings with the same pxWarningName, one of the warnings was not getting justified. To fix this, the addWarning function will use the synchronized timestamp function getCurrentDateTimeUnique() to generate the created time.