SR-B26257 · Issue 288790
Fixed SMA broken item requeue
Resolved in Pega Version 7.3
When attempting to requeue a broken item using the SMA, the requeue failed with an error about Attribute Based Access Control. This was traced to the API passing a thread object that did not have any executable associated with it; the system will now create a new executable instance if the getThread().retrieveContext() is null.
SR-B2709 · Issue 276670
Fixed OOM exception during DL import on JVM
Resolved in Pega Version 7.3
An OOM exception was generated during DL import on JVM when the DL being deployed had an very large number of hotfixes relating to CarDirectories. This was traced to each directory deployment creating a new instance of JarLoaderTool to internally build the cache (VersionedJdbcJarReader) which was then never cleared from the Mbean cache. This has been corrected by adding a check to release memory.
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-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-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.