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-A76252 · Issue 253236
String filter values treated consistently
Resolved in Pega Version 7.2.2
Attempting to schedule a report with a string value in the filter condition caused a parsing error even when the report ran correctly in DesignerStudio. To resolve this and make the behavior consistent, the logic has been updated such that If filter value is string but not a property reference, then do not resolve it.
SR-A85953 · Issue 254446
Fixed Export to Excel
Resolved in Pega Version 7.2.2
Export to Excel from report definition generated the sporadic error "Unable to read file." This was traced to the browser attempting to open the file before it was downloaded, and code has been added to check the browser and handle the download/open appropriately.
SR-A76558 · Issue 253570
Date/time data fixed for sub-report filter
Resolved in Pega Version 7.2.2
It was not possible to select filter value for the sub report date column value in main report filter condition due to the sub report date time column value not being populated correctly. This has been fixed.
SR-A24877 · Issue 250548
Widget title localization corrected
Resolved in Pega Version 7.2.2
Sporadic issues were seen with proper localization for the label of items inside any widget of the widget library. A step has been added to explicitly set the pyDescription fix this.
SR-A76162 · Issue 251024
Widget title localization corrected
Resolved in Pega Version 7.2.2
Sporadic issues were seen with proper localization for the label of items inside any widget of the widget library. A step has been added to explicitly set the pyDescription fix this.
SR-A67716 · Issue 251384
Updated ruleset determination for saving copied reports
Resolved in Pega Version 7.2.2
When a new report was made from a copy, it was not properly assigned to the ruleset it should be saved in (the "design time" ruleset configured on the operators Access Group). Instead, it was residing in the same ruleset as the template report definitions (Pega-Reporting), causing property validations to fail if they were in the subset of rulesets which were in the design time ruleset's stack but not in Pega-Reporting until the report was saved successfully once. This has been fixed by adding a step to Rule-Obj-Report-Definition!pxShowReport that sets the ruleset name and version of a new report to match the Access Group's configured design time ruleset.