INC-147643 · Issue 605386
Corrected filtering logic for Report Definition with declarative join
Resolved in Pega Version 8.5.2
When using a report definition with declarative join enabled, running the report produced the correct results, but filtering on any other column resulted in all values being shown. This has been resolved by modifying the logic used for pzGetGridColUniqueValues.
INC-147856 · Issue 607132
Description input for new reports restricted to 64 characters
Resolved in Pega Version 8.5.2
After saving a report with a description containing more than 64 characters, trying to delete the same report generated error messages saying the report description exceeds 64 characters. There was no maximum character limit set on the description input when creating/editing/save as a report. The delete modal shows any page-level warnings, so the guard rail warnings show up at that time. This has been resolved by disallowing the creation of a description greater than 64 characters in length.
INC-150054 · Issue 607387
Drilldown works for display of all locks
Resolved in Pega Version 8.5.2
In Developer studio, drilling down from the summary count of all locks to see the actual cases locked gave a generic error screen. This was a missed drilldown use case for List Views during security updates, and has been resolved.
SR-D91660 · Issue 555724
Updated document ID handling for deleting indexes
Resolved in Pega Version 8.5.2
When trying to delete a document for index name "work*", intermittent errors were seen indicating an invalid index name or index does not exist value. This has been resolved by updating the handling for delete by ID.
SR-D35981 · Issue 506381
Column formatting default added to Export to Excel to match Export to PDF
Resolved in Pega Version 8.2.4
After running the pyGetWorkHistory report in Designer Studio, exporting the report to PDF showed the correct data format for the Message Key column while exporting to Excel did not. In the Report Definition UI and in Export to PDF (which use the same logic), when the backing property of a column has no control and the column does not have a format, the control falls back to a "Default" control. The "Default" control localized the string values in the Report Definition UI and Export to PDF, therefore changing the Message Key to be the correct value in those places. The similar logic to explicitly handle the "no control" scenario has now also been added to Export to Excel to resolve this issue.
SR-D39236 · Issue 508454
Corrected viewing of sorted drill-down spreadsheet-style summary reports
Resolved in Pega Version 8.2.4
When using a report with a summarized column and the 'Do not display group headings' grouping option checked, drill down was not working when the report was primarily sorted by default on any column other than the first one. This manifested as either no results returned by the drill down report or an error message related to invalid filter values. This was traced to the unique column ordering logic for non-spreadsheet-style summary reports being applied to the drilldown of spreadsheet-style summary reports due to the logic for creating the drilldown filters using the != operator to compare the spreadsheet flag string to the string constant "true". This previously worked as expected because this string was interned in the engine, but these string internments have since been removed. To correct this, pzPopulateReport has been updated to appropriately recognize spreadhseet-style summary reports as they used to.
SR-D39291 · Issue 508368
Alphabetical sort function restored to Legacy Report Browser
Resolved in Pega Version 8.2.4
When the new report browser was introduced in Pega Platform 8.1 the sorting functionality was changed to sort by update time instead of the previous behavior of sorting alphabetically. This change to the logic behind sorting reports ended up applying not only to the new report browser but to the legacy report browser as well, eliminating the ability to use an alphabetized sort for both. This fix re-adds the functionality to sort reports alphabetically by adding selectable sorting capability to the legacy report browser that enables switching between sorting reports by update time and sorting alphabetically.
SR-D39302 · Issue 507981
Report name in tab uses localization
Resolved in Pega Version 8.2.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-D39601 · Issue 509518
RRDisplaySection made available to assist Edge compatibility
Resolved in Pega Version 8.2.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 Microsoft Internet Explorer.
SR-D40599 · Issue 508280
Handlign added for Japanese half-space character during DB query
Resolved in Pega Version 8.2.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.