SR-A22699 · Issue 248560
RuleServiceFile.parseRecordAtTime and RuleServiceFile.parseByRecordType Timer function corrected
Resolved in Pega Version 7.2.2
The Timer function used in the RuleServiceFile.parseRecordAtTime and RuleServiceFile.parseByRecordType functions was not properly halting when it encountered an exception, causing any subsequent invocation to these methods to start the Timer again. This created errors and incorrect results. The parseRecordAtTime and parseByRecordType methods have now been updated to enclose inbound mapping related stopTiming within a finally block for accuracy.
SR-A87711 · Issue 255629
REST query key maps invalid characters to underscore
Resolved in Pega Version 7.2.2
When creating a REST Service with query key=value pairs that contains keys with dots/periods, the inbound mapping could not handle the keys and failed with an HTTP 500 error. To resolve this, changes have been made in the service API to locate any invalid character (according to ParameterPages) in a key to be mapped and substitute an '_' (underscore) character.
SR-A76677 · Issue 253493
IDP SAML 2.0 schema validation error resolved
Resolved in Pega Version 7.2.2
When generating the Pega SP metadata after importing the Shibboleth IDP metadata, the error "The metadata does not pass the SAML 2.0 schema validation" appeared. This has been resolved by modifying the pzDownloadSPMetadata activity to generate a unique secure random ID prefixed with an underscore.
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-A99521 · Issue 266569
Localization added to DisplayStages
Resolved in Pega Version 7.2.2
Localization has been added to 'Show all steps' and 'Hide Steps' in pxDisplayStages.
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.