SR-B599 · Issue 270485
Flow Dependency queries performance improvements
Resolved in Pega Version 7.2.2
Case dependency queries executed by PEGA have been tuned to improve system performance when mid flow dependencies are getting fulfilled.
SR-A98702 · Issue 270066
Minor update to help doc for property optimization run time
Resolved in Pega Version 7.2.2
The help file for Property optimization using the Property Optimization tool has been updated with non-critical corrections to the phrasing regarding the length of time that might be required to perform background processing.
SR-A103064 · Issue 270247
Schema Change Tracking query performance improvements
Resolved in Pega Version 7.2.2
A query which was used in Schema Change Tracking (Designer Studio -> System -> Database -> Schema Change Tracking) was causing high CPU usage. This was due to the query having a full table scan which was using Information_schema, and the query has been rewritten for better efficiency.
SR-A88372 · Issue 259463
BIX log now includes BIX version info
Resolved in Pega Version 7.2.2
In order to enable better system tuning, the system has been updated to specify the BIX version in use in the logs. i.e. BIX Version : 7.1.9
SR-A89295 · Issue 258931
Result count option added to Campaigns for performance tuning
Resolved in Pega Version 7.2.2
Slowness was seen when launching and running Field Marketing Campaigns. This was an issue with loading results using pxRetrieveReportData with paging enabled, as it fetched the total result count for each page. To resolve this, an option has been added to pxRetrieveReportData to disable fetching of total result count. This is available as Embed-QueryInputs property of type TrueFalse called 'pyReturnResultCount' when running report using pxRetrieveSearchData's pyReportParamPageName Parameter.
SR-A100537 · Issue 268013
Optimized SQL query execution in multitenant systems
Resolved in Pega Version 7.2.2
SQL Query Execution was taking an excessive amount of time in a multitenant system when trying to retrieve a table which contained a given column and schema. To improve performance, the SQLGeneratorPostgres.getQueryForTablesWithColumn() query has been optimized.
SR-A99595 · Issue 267749
Error message displayed on UI for RAP import failure
Resolved in Pega Version 7.2.2
A build success message appeared after importing a RAP file even though the import process failed and an error was put in the log file. During the import process, the JSR94Client did not delegate any exceptions to the callers. This has been changed.
SR-A95888 · Issue 270679
MSSQL upgrade indexing updated
Resolved in Pega Version 7.2.2
After upgrade, an index was missing. Analysis showed the create index statement was using an include clause to add pzInskey in the index column list, which did not work on MSSQL because the DatabaseMetadata interface for the MSSQL JDBC driver did not return the columns in the INCLUDE list when a call to getIndexInfo was made. This resulted in a mismatch of the column list available in pr_changelog. This has been fixed, and automation has been added to detect this mismatch in the future.
SR-A87670 · Issue 256183
Better handling for external data source in the Upgrade utility
Resolved in Pega Version 7.2.2
An external data source included in the system configuration was being considered in the process of upgrade, resulting in an exception. To fix this, the UpgradeApplicationSchemaUtility has been modified to log errors with a message to rerun "Update Application Schema" from the landing page and then continue.
SR-A24411 · Issue 257220
Fastloader update error handling improved
Resolved in Pega Version 7.2.2
An issue was found where the FastLoader failed when an update to the vw table modified 0 instances. The update.bat script has been modified to better handle encountering data that did not get updated as expected.