SR-B31589 · Issue 301671
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-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-B31873 · Issue 298086
Review/Perform harness modifications for scheduled report errors
Resolved in Pega Version 7.3
Scheduled reports would periodically go to Completed state and stop running prematurely. Deleting and then reopening a scheduled report (from recents) caused corruption of scheduled reports that are re-scheduled. This was traced to the Review/Perform harness going in to a corrupt state, and has been corrected by re-building the Review harness as well as some minor changes to the Perform harness to ensure the correct buttons are displayed when deleting a scheduled report and reopening it from the recents list.
SR-B32056 · Issue 299068
CustomFusionChart display fixed for mobile HC
Resolved in Pega Version 7.3
Charts were not loading a second time unless a refresh of that section was forced after switching from one tab to other from the navigation panel on left side. This was an issue with charts created using pzCustomFusionChart erroring out when loaded within a layout group that requires the user to swipe left/right to view them in the hybrid client, 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-B33991 · Issue 292845
Corrected ability to hide filters for Export to PDF
Resolved in Pega Version 7.3
The "Display report filters" check-box was not being honored on export to PDF, causing the filters to always be shown. This has been corrected with an added visibility condition to show or hide a filter section based on the value of .pyDisplayReportHeader, and a check has been added in "RRBodyDiv" HTML rule to show header only when pyDisplayReportHeader is true.