INC-166120 · Issue 657054
Parameter added to prevent name localization in Dev Studio Reports
Resolved in Pega Version 8.5.5
Running the DataTableEditorReport against a customer table translated names that matched localized values, such as "Mr. Block" became "Mr. Sperren" when the locale was set to de_DE even though the property was marked as "Do not localize" in UI Controls in the report definition filter. To resolve this, the parameter 'pyskiplocalization' has been added for use in the RRFilters_logic and while displaying the select Values popup.
INC-174756 · Issue 650538
Queue processor correctly moves items to Broken Items
Resolved in Pega Version 8.5.5
When an exception occurred while Queue Processor processed an item, he queue item was not moved to Broken Items. The error " inconsistent datatypes: expected - got CLOB DatabaseException caused by prior exception" was generated. This has been resolved by modifying the NativeSQL builder and NativeSQLBatchExecutor to allow the batch of queries to be retried. Additional changes were also added for Oracle databases to identify the correct column types.
INC-175622 · Issue 652277
Screen reader announces report names
Resolved in Pega Version 8.5.5
An update has been made to pyReportBrowserItem to ensure names of the reports on the report browser are read correctly.
INC-175797 · Issue 662049
Date/time filter works in source column
Resolved in Pega Version 8.5.5
The date/time filter was not working in the Source column for a report definition. This was traced to "pxCreateDateTime" resolving and storing the pyDataType in the report as "DATE TIME". While "DATE TIME" is an acceptable data type it was not supported by pzGridSortPaginate and thus the filter did not work. This was a missed use case, and has been resolved by updating pzGridSortPaginate to check the dataType as both "datetime" and "date time".
INC-176158 · Issue 664346
Max number of rows setting properly honored
Resolved in Pega Version 8.5.5
The setting for the maximum number of rows to retrieve was still used in a report definition even when it was disabled. This was traced to the report definition being sourced from a data page and having pagination enabled, and has been resolved by updating the handling for this use case.
INC-176205 · Issue 655937
Secure shared link generation added to scheduled reports
Resolved in Pega Version 8.5.5
When a scheduled report with a link was sent in email, clicking the link displayed an access denied message. To support this use, logic has been added to pytaskoutputprocessor in the pega-scheduledtask-reporting and pega-scheduledtask classes that will create a secure encrypted URL using the PublicLinkURL function.
INC-176385 · Issue 657669
Corrected blank lines for hidden report filter criteria
Resolved in Pega Version 8.5.5
When the report browser had five filter criteria for a report and only the last two were made visible due to conditions, three blank lines were shown above the visible filters. This was traced to the Report Definition column filter showing the grid row as empty space when "Filter Not Visible in Viewer" was selected, and has been resolved by adding an inline style to PzPromptGrid.
INC-179362 · Issue 658630
Display limitation removed for scheduled reports
Resolved in Pega Version 8.5.5
When looking at Configure >> Reports >> Scheduled Reports only 50 reports were shown across two pages instead of all of the reports retrieved by pzGetScheduledTask. This was a limitation set in pyScheduledTasksGadget, and has been removed.
INC-181394 · Issue 662099
Handling added to avoid incorrect manifest count
Resolved in Pega Version 8.5.5
Extracted Record counts in the manifest file were incorrect if any updates were made during the extraction process. This has been resolved by modifying the code to prevent the issue.
INC-182375 · Issue 664342
Report filter description correctly displayed
Resolved in Pega Version 8.5.5
When a function alias was used in the filter of a report definition without the caption and with some value assigned, the FilterName was not getting displayed when the report was run. This has been resolved by updating RRFilters_Logic.