SR-D39302 · Issue 507982
Report name in tab uses localization
Resolved in Pega Version 8.4
After creating a field value with field name as pyCaption to localize the report definition name, the title in the report definition tab was not translated. This was traced to Step 1 of the activity displayReport using an old localization function, and has been resolved by changing the localization of document title to use pyCaption.
SR-D27687 · Issue 500054
Mashup Export to Excel works on first use
Resolved in Pega Version 8.4
If a report was opened from Mashup and exported to Excel, only one record was given regardless of the actual size of the report. If the mashup main page was refreshed, the open and export process worked correctly. This has been corrected by adding a call to pzSetQueryDefaults in pzRDExportWrapper when the requestor is initialized for Mashup.
SR-D47414 · Issue 513078
"Use null if empty" checkbox honored for GetSelectValues
Resolved in Pega Version 8.4
When Report Definition rule uses parameters as a value for filter criteria, a moderate performance warning was generated: ''Some of your filters are using a parameter with the "Use null if empty" option NOT selected. Please ensure that you do pass the parameter. Otherwise, the filter will be dropped entirely and execution of the report will result in very poor performance. If you do not want this behavior, select the "Use null if empty" option.'' When the "Use null if empty" checkbox was selected as suggested, the "Select values" button gave an empty list of possible values. This was traced to refactoring work done on Select Values which changed it to be backed by a Report Definition and Grid instead of a List View: the option was intended to be only temporarily disabled, but was missed. To correct this, the activity pzGetSelectValues has been updated to honor the checkbox and appropriately disable the "Use null if empty" option on the selected filter on the temporary copy of the report definition before it is executed.
SR-D42159 · Issue 508941
Large report pagination should use "Previous and Next only"
Resolved in Pega Version 8.4
Some Report Definitions were getting timed out or facing gateway exceptions, primarily due to high time consumed by the database Queries. Investigation showed the total result count process appeared to stop at the configured pyMaxRecords value as long as it was nonzero. This indicated the issue was related to changes made to fix the inaccurate behavior of the "Last" button in the responsive paginator which included removing logic that set pyMaxRecords to anything other than zero. To resolve this issue, those pagination changes have been reverted. The "Last" button should not be used when the paging mode is set to Numeric: in the case of large reports, the paging option should be set to "Previous and Next only".
SR-D37737 · Issue 509375
Export to Excel can run in the background when called from the filelistener
Resolved in Pega Version 8.4
When calling the pzRDExportWrapper activity from a filelistener and passing reportRunMode as “background” with a given fileLocation parameter, a popup appeared to save the file in the local directory instead of the expected behavior of saving it to the provided location in the background. Investigation showed that ReportExportHandler.java was not checking for the reportRunMode parameter and instead always exporting to the browser for download and then immediately deleting the file. This has been corrected.
SR-D50787 · Issue 520485
Excel time values will default to server datetime if operator time zone is null
Resolved in Pega Version 8.4
After upgrade, a scheduled report that contained a column using pxDateTime that was supposed to use EST instead used GMT when run and exported to Excel. This has been resolved with an update that will default to using the time zone of the server If the time zone of the operator is empty or null.
SR-D27622 · Issue 498771
Export to Excel updated to pass custom time format
Resolved in Pega Version 8.4
When running a report definition the date fields showed the proper date and time, but when exporting to Excel the time showed as the 12:00:00 AM default. Investigation showed that when using edit columns to get the date/time in a specified format and the Data Access tab “Ignore formatting when exporting to excel” option was not enabled, the BasicDateTimeReportUIField class's getFormattedValue method was using the column's reported type to decide whether the clipboard values would be parsed as date+time or date only. This has been resolved by updating the export function.
SR-D30272 · Issue 499440
Primary page paramter explictly set to resolve fix/edit Scheduled Tasks issue
Resolved in Pega Version 8.4
After upgrade, the top section of report details was getting blanked out when using the Reporting | Components | Scheduled Task to open a report and "update" it to fix issues. This was an unintended side effect of updating the Review harness to display the Perform harness when clicking Update, which was done to correct an earlier issue with UI validations when using the out of the box schedule report functionality. To resolve this, pxScheduleTaskWrapper has been updated to explicitly set the parameter page according to the primary page's values when not in the report browser.
SR-D50569 · Issue 515437
Primary page paramter explictly set to resolve fix/edit Scheduled Tasks issue
Resolved in Pega Version 8.4
After upgrade, the top section of report details was getting blanked out when using the Reporting | Components | Scheduled Task to open a report and "update" it to fix issues. This was an unintended side effect of updating the Review harness to display the Perform harness when clicking Update, which was done to correct an earlier issue with UI validations when using the out of the box schedule report functionality. To resolve this, pxScheduleTaskWrapper has been updated to explicitly set the parameter page according to the primary page's values when not in the report browser.
SR-D39601 · Issue 509519
RRDisplaySection made available to assist Edge compatibility
Resolved in Pega Version 8.4
When the Pega Platform was being used with Microsoft Internet Explorer Compatibility Mode ON, it was not possible to use the select filter gadget due to a browser compatibility issue: enabling the filter condition for the report definition caused the SelectValues button to stick in loading mode when clicked. Changing the Microsoft Internet Explorer Document Mode for Harness pzRRDisplaySection to IE=Edge corrected the issue, but the rule was final. To resolve this, the pzRRDisplaySection has been made available to allow override for customers still using IE.