INC-119669 · Issue 562588
Special character handling added to filters for table sourced with parameterized RD
Resolved in Pega Version 8.1.9
Filters were not working on a table when sourced with a report definition which accepted a parameter value containing special characters (Eg: S&P). This has been resolved by using StringUtils.reversibleCrossScriptingFilter in the pzGetGridColUniqueValues activity to allow filters to contain special characters.
INC-145810 · Issue 599463
BIX log shows correct corrupted BLOB pzInskey
Resolved in Pega Version 8.1.9
An update has ben made to ensure the correct inskey is shown in the BIX logs for a corrupted BLOB.
SR-D90400 · Issue 563187
Explicit parent added for descendants in subreport to correct summary
Resolved in Pega Version 8.1.9
When using a Report Definition with a Summarize column and a subreport with join class, it was not considering implementation class work objects. As a result, the prepared values were only partially computed. This was traced to the SubReport in SetQuery not having reference to a parent for the descendants classes, and has been resolved by explicitly setting the parent value.
INC-160190 · Issue 658124
Logic updated to allow page property and declare index with the same name
Resolved in Pega Version 8.5.5
A Property which was in a page list which in turn was embedded in a Page was not visible in the Report Browser. This was traced to the two properties sharing the same name, and was caused by a check which ensured only entries with unique names were added. In order to support this configuration, logic has been added to pzAddPropListForClass_TreeGrid such that if a page property and declare index share the same name, they are both added to the tree grid.
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.