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.
SR-D40599 · Issue 508281
Handlign added for Japanese half-space character during database query
Resolved in Pega Version 8.4
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-D42095 · Issue 516671
Added validation function to 'apply filters' to handle custom filtering
Resolved in Pega Version 8.4
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-D42138 · Issue 509289
Fixed white space issues with Previous and Next buttons in multi-page Audit Reports
Resolved in Pega Version 8.4
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-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-D42403 · Issue 507707
Additional language options added to Language Wizard dropdown
Resolved in Pega Version 8.4
An enhancement has been added to the “select a language” dropdown in the Language Wizard that extends the available options to include Latin American Spanish (es_XL), Brazilian Portuguese (pt_BR), and Korean (ko_KR).
SR-D43788 · Issue 512544
Corrected Last Added By values for reports created in report browser
Resolved in Pega Version 8.4
After creating a report using report browsers in the case manager portal, opening that report definition rule in Designer Studio showed the person's name who created the pydeafult report instead of the expected values for Last added by(Operator ID & Name) and Last Moved by (Operator ID & Name,Date). This has been resolved by adding steps to pzRRSaveAs which will fix the history details when making a new report in the report browser.
SR-D45653 · Issue 515248
Corrected textarea formatting issue for Excel
Resolved in Pega Version 8.4
The TextAreaWithExpandSmall control was causing incorrect formatting in the generated Excel for a text area due to using "reportMode" with value of "excel" instead of the proper "Excel". This has been corrected.
SR-D46535 · Issue 512848
Accessibility label added to RBShortcuts7 report browser search field
Resolved in Pega Version 8.4
In order to improve accessibility, a hidden label has been added to the Search field in the pzRBShortcuts7 report browser for use by a screen reader.
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.