SR-D39302 · Issue 507980
Report name in tab uses localization
Resolved in Pega Version 8.3.1
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-D39601 · Issue 509517
RRDisplaySection made available to assist Edge compatibility
Resolved in Pega Version 8.3.1
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 Microsoft Internet Explorer =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 Microsoft Internet Explorer .
SR-D40599 · Issue 508279
Handlign added for Japanese half-space character during DB query
Resolved in Pega Version 8.3.1
After creating a Report Definition based on the Unicode/Japanese text property with summary list, the list was visible from Report viewer but any full size space used by the summary filter was unintentionally trimmed to half size space. As a result, the database query could not find the item. This has been resolved by modifying the setGroupByInputs API in the pega_report_summary js file to use the unicode space char(\u0020) instead of \s in regex. The Japanese space character will be replaced in the pzDrillDownReport activity step 2 for the query use, and will be set back to the Japanese space character in pyFilterValue.
SR-D42138 · Issue 509288
Fixed white space issues with Previous and Next buttons in multi-page Audit Reports
Resolved in Pega Version 8.3.1
After upgrade, multiple-page Audit Reports in GOC had too much white space between the end of the numbers and the Next Button, and the Previous Button had too much white space between 'Previous' and the start of the numbers. This was traced to a coding error in the pzbase-browser CSS generation that resulted in a space between "div" and "[node_name="pyGridPaginator"]". This has been fixed. Unused webkit selectors have also been removed.
SR-D17306 · Issue 490918
RD pagination expanded to 1500 rows
Resolved in Pega Version 8.3.1
The default pagination enabled on the Report Definition was limiting the results to 50. This has been enhanced to a row limit of 1500 in report definitions pzGetAllPropertiesOfGivenClass.
SR-D37115 · Issue 515838
Onclick handler updated to resolve RD UI issue
Resolved in Pega Version 8.3.2
After modifying the function logic in Report Definition, reopening it in the configuration modal dialogue displayed the function multiple times and it was not possible to open/edit the function. This issue was cosmetic and related to the UI representation of functions: the underlying clipboard page had the correct details regarding the custom logic and functioned as expected. Investigation showed the UI error was related to the onclick handler, and this has been resolved so the system correctly removes the onclick handler when required.
SR-D42095 · Issue 516669
Added validation function to 'apply filters' to handle custom filtering
Resolved in Pega Version 8.3.2
A custom filter section with the "Display custom section inline" checkbox checked and required input fields was not firing validation if the input fields were empty. Switching the focus away from the filter section caused validation to appear saying the filter could not be blank, but "Apply filters" (which is missing validation) was still clickable and the report updated. This has been resolved by adding a validateInput function to the "Apply filters" button of the pega_report_events file.
SR-D48173 · Issue 515338
Resolved hang caused by cancelling report calculation
Resolved in Pega Version 8.3.2
When dragging a calculation into the report editor filter area, clicking X on the cancel modal that appeared caused a JavaScript exception to occur. This exception later prevented the ability to click the "done editing" button on the report. This has been resolved by modifying the pzpega_report_rafpopup.sj -- doRefresh API to pass the correct argument to reload the section API.
SR-D48442 · Issue 514045
ExportMode parameter sent to resolve duplicate rows in Export to Excel
Resolved in Pega Version 8.3.2
On performing Export to Excel for a report definition, duplicate rows were being exported for a column which had a TextAreaWithExpandSmall UI Control. Investigation showed that this control was looking for the exportmode parameter, which was not being sent. This parameter is now being sent.
SR-D50787 · Issue 520483
Excel time values will default to server datetime if operator time zone is null
Resolved in Pega Version 8.3.2
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.