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-D47414 · Issue 513077
"Use null if empty" checkbox honored for GetSelectValues
Resolved in Pega Version 8.2.5
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.
SR-D42159 · Issue 508940
Large report pagination should use "Previous and Next only"
Resolved in Pega Version 8.2.5
Some Report Definitions were getting timed out or facing gateway exceptions, primarily due to high time consumed by the DB 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-D36372 · Issue 504746
Force order added to inner join when running a Rules Resolution filter
Resolved in Pega Version 8.2.4
After upgrade, D_getResolvedWorkStatuses was not loading properly due to a Report Definition that used a Filter by Rule Resolution option timing out on the SQL Server. When the Filter by Rule Resolution option is selected in RD, it will generate a rule resolution query with an inner join which can cause a time out on the SQL Server while it tries to find out the join order for tables with multiple joins. To resolve this, the SQL server will provide a Force order, merge inner join hint option by way of an added DSS reporting/useForceOrderHint. Additionally, reporting/useMergeHintForRRquery should be set on Pega-Reporting to set things up for using the Merge Inner join hint in the query.
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.
INC-182375 · Issue 664344
Report filter description correctly displayed
Resolved in Pega Version 8.7
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.
INC-176158 · Issue 664348
Max number of rows setting properly honored
Resolved in Pega Version 8.7
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 655938
Secure shared link generation added to scheduled reports
Resolved in Pega Version 8.7
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.
SR-D33832 · Issue 503957
Configurability added to SLA Timeliness to allow either 0 or NULL for Unqualified records
Resolved in Pega Version 8.2.4
When using a Report Definition where the count (aggregate function) was used for both the WithinSLA and Past Deadline columns, the correct value was not getting displayed. The correct value was displayed when the sum function was used instead of the count function, but clicking 'value' returned all values despite what value was displayed on the screen. This was a behavior change related to performing a drill down action on a report definition. As per the older behavior, drill down relies on a specific value (NULL) to determine whether a record is a candidate to be shown in the drill down report. From 7.2.1 forward, drilldown relies on value 0 instead of NULL to make the average summarize function work properly, which led to a change in behavior when used with other summarize functions like sum and count. To resolve this, SLA Timeliness related RAFs have been modified to conditionally return either 0 or NULL for Unqualified records based on a DASS config.
INC-192769 · Issue 683001
Removed incorrect role from accessible filter logic
Resolved in Pega Version 8.7
When using JAWS, tabbing out from Close(X) and setting focus on the "filter by" section resulted in JAWS reading out "use arrows to move". This was not an available action, and has been resolved by removing role="listitem" from the RRFilters_logic.