SR-B11379 · Issue 281867
Backwards compatibility added for imported RDs to ensure Export to PDF option given
Resolved in Pega Version 7.3
After upgrade, the Export to PDF option was not visible under actions. This occurred when the Report Definition exported from an earlier version did not contain the property "pyUI.pyUserInteractions.pyShowDataOnly" in the rule XML, causing the 'when' rule pzShowExportToPDFLink to be evaluated to false. To correct this, the pzUpgradeOnOpen Data-transform has been modified to create the pyShowDataOnly property and assign it to false if it was not present or if the value is empty/null so the Export option will appear as expected.
SR-B11675 · Issue 284417
Cursor correctly changes to hand in Report Wizard popup
Resolved in Pega Version 7.3
The hand icon was not displaying as expected when the cursor was placed on the Search icon in the "Report Wizard" pop up window. This has been fixed.
SR-B11776 · Issue 289458
Report results populating as expected for tree grid
Resolved in Pega Version 7.3
Report definition results were not populated in the tree grid structure but were populated in the spread sheet structure. This was caused by a difference in handling for formatting a column with empty values, and has been changed.
SR-B12581 · Issue 282710
Documentation correction for setupDatabase.properties naming
Resolved in Pega Version 7.3
The install, upgrade, and update guides on the PDN referring to the setupDatabase.properties file properties gave erroneous name formats for the schema name properties. All instances in the documentation referring to pega.rules.schema have been changed to the correct format of rules.schema.name, and all instances of pega.data.schema have been changed to the correct format of data.schema.name.
SR-B12714 · Issue 294429
String comparison logic updated for complex property references
Resolved in Pega Version 7.3
Running a report that has a single page property (.Address.pyCountry) generated an error and the report shows no results. It worked correctly if the column is removed or a filter was added on instances that have .Address.pyCountry not null. This was an issue related to string comparisons, and has been resolved by updating the logic for parsing of complex references in UDFs.
SR-B12850 · Issue 283836
SMA Garbage Collector landing page updated to work with updated browsers
Resolved in Pega Version 7.3
SMA's Garbage Collector landing page was not working correctly on the latest versions of Chrome and other browsers due to the document.all JavaScript function being deprecated. The code has been updated to correct this.
SR-B13016 · Issue 284134
Report title shows for exported Excel; display report label name reverted
Resolved in Pega Version 7.3
Exported Excel reports were not showing the report title if the "display report filters" checkbox was unchecked in the RD rule. If the box was checked, the report title turned up in the Excel sheet, but the report UI showed an unnecessary blue bar if none of the filter criteria were set to be displayed as per business needs. The missing report title was traced to an error in the "display report filters" checkbox, and has been fixed. Additionally, the 'display report header' label in the pzReportViewerUserActions section had been recently modified to read 'display report filters', which was misleading - that change has been reverted.
SR-B13020 · Issue 283559
Upgrade App Schema generates unique index name IDs
Resolved in Pega Version 7.3
Upgrade Schema index was not incrementing the system-generated index name properly, resulting in duplicate names and a failure to execute new recommendations. This was an issue with duplicate indexes being generated through the UpgradeApplicationSchema Landing Page when the hash truncation matched indexes incorrectly. This has been resolved by using both the table name and the index name to ensure unique IDs.
SR-B13020 · Issue 283078
Upgrade App Schema generates unique index name IDs
Resolved in Pega Version 7.3
Upgrade Schema index was not incrementing the system-generated index name properly, resulting in duplicate names and a failure to execute new recommendations. This was an issue with duplicate indexes being generated through the UpgradeApplicationSchema Landing Page when the hash truncation matched indexes incorrectly. This has been resolved by using both the table name and the index name to ensure unique IDs.
SR-B13606 · Issue 287616
Angle brackets escaped for RD drill down
Resolved in Pega Version 7.3
In a report definition with drill down, if the column parameter had a value that used the wrong parameter was getting passed in Query. This was due to the characters getting converted into their HTML equivalent < and >., and the character escaping has been corrected to resolve this.