SR-B84765 · Issue 341704
Fixed VirtualList RD content display
Resolved in Pega Version 7.4
When a complex reference with more than 3 levels depth was used in the select fields of report and the complex reference contained an auto-populate page property with its key as one of the properties within the page itself, VirtualList failed to populate featureProperty and no data was displayed. This was traced to two issues: first, the decorateSingleFrame API was trying to fetch the VirtualClipboardProperty from VirtualClipboardPage using a complex reference which resulted in NullPointerException. Because of this exception, featureProperty was not set and the auto-chain was broken. Second, the iteration logic used to iterate through the complex reference was incorrect. These have been fixed.
SR-B84879 · Issue 339472
Circumstanced RD 'save as' works
Resolved in Pega Version 7.4
In portal, it was not possible to use 'save as' on a Report Definition which was circumstanced. This was because performing a save as on a report from the report viewer put the copy in the first unlocked ruleset. If the report was circumstanced, the copy would be also. This can cause errors if the rule would not be valid in the new rule set (for example, the base version of the rule may not be present). In order to allow 'save as', a step has been added to pzRRSaveAS which will remove the circumstance properties from the report definition primary page.
SR-B85544 · Issue 337433
Fixed RD fail for Japanese characters
Resolved in Pega Version 7.4
Report definition was failing when the Class name contained Japanese characters. This was an issue with the use of default encoding (now deprecated) and an update has been made to ensure the use of 'UTF-8' encoding for URLs.
SR-B85885 · Issue 336053
PDF images exported
Resolved in Pega Version 7.4
On adding an image to a report and exporting it, the image was not getting exported to PDF. This was caused by the header section pzDisplayReportSectionForPDF is final, and it has now been made available to extend and modify.
SR-B87507 · Issue 335843
Localization added to Chart messages
Resolved in Pega Version 7.4
Chart messages have been localized in the Cases by Status widget.
SR-B88028 · Issue 342806
RRFilters_Logic localizes Class-join case
Resolved in Pega Version 7.4
In Report definition, Filter properties coming from Class-join (i.e., Prefix) were not getting localized if any specific value was given to the RHS. This was due to missing localization support for the join classes, and has been fixed.
SR-B89083 · Issue 340550
Post-passivation tab switching issue fixed
Resolved in Pega Version 7.4
Tab switching did not work properly after passivation if the following were true: 1) the RD was defined on a framework class and returned data from the implementation class (because of the useImplementation class option available in DataAccess tab) 2) A DataPage sourced from the RD was defined on the framework class and was editable. The error did not occur if the RD did not return implementation results or if the datapage was readonly. This was traced to an Invalid Reference exception during activation of the data page (sourced from RD with use implementation class as true) because the pxObjClass of the results and the pyObjClass of data page were different. This was only seen after passivation because the VL was already constructed in the RD and no expansion was being performed, hiding the issue. To resolve this, the system will avoid overriding the class of the pages the RD populates with the class defined in the definition of the data page.
SR-B89824 · Issue 340831
Fixed Guardrail warning for withdrawn page
Resolved in Pega Version 7.4
A guardrail warning was appearing on data pages with the same name on a different class, even when the earlier version of the data-page was withdrawn. This was caused by an error in the handling of "Filter by rule resolution" in the RD, and has been fixed.
SR-B90290 · Issue 338672
Case mismatch fixed for pyDateSetID
Resolved in Pega Version 7.4
The column name for a property defined in Data-NLP-Report-Summary was pyDateSetID, which did not match exactly the property ID of pyDataSetID. This caused issues with Microsoft SQL Server where property names and column names must match exactly. If the UDF functions are present, this is worked around by reading the value from the BLOB. However, if you are running without UDF functions, attempting to access this property generated an error. This case mismatch has been fixed.
SR-B91127 · Issue 340063
Fixed missing records in exported PDF report
Resolved in Pega Version 7.4
A report record which contained double-quotes (") was not displayed in an exported PDF if it was part of a Summary type report definition. In this case, when the drill down was enabled the ddpath attribute was generated in the markup; because the value contained "" double quotes, the markup became corrupted. To fix this, RRDATASUMMARYSPREADSHEETGENERATION now contains code to disable the drill down while doing the export to PDF.