INC-192582 · Issue 682390
Drilldown report opening made consistent
Resolved in Pega Version 8.7
After launching the user portal for a hybrid app on the system and going to Reports --> Case Volume report, drilling down in the report and clicking on an entry opened it in a new tab, but going to Actions --> Refresh and performing the same action opened it in the same tab. This has been resolved by refreshing the entire pzReportDisplay section to retrigger the JS found in pzRDWinTitle which replaces the drilldown functions.
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.
INC-195827 · Issue 687211
Accessibility improved for filter pop-up buttons
Resolved in Pega Version 8.7
JAWS was not reading the buttons on the filters pop-up for a report in report browser. This has been resolved by adding helper text for the cancel button of pzReportConfigApplyCancel and for the Search icon of the pzAvailableValues.
INC-197610 · Issue 688003
Dataflow with report definition source repaired
Resolved in Pega Version 8.7
After update, data flows using a report definition dataset as source were throwing a null pointer exception. This was traced to previous work done around retry handling for Oracle queries where there were issues identifying the correct column types; that previous work has been reverted to resolve this null pointer exception, and further work will be done to refine the solution to the Oracle CLOB DatabaseException.
INC-197953 · Issue 686254
Execution class parameter handling updated for scheduled reports
Resolved in Pega Version 8.7
The schedule was picking the wrong class to execute a report, choosing the report top class/current application class instead of the expected shortcut class mentioned in the report class of the schedule. This has been resolved by updating the parameter handling in the pzRunScheduleShortcut activity.
INC-185824 · Issue 676630
Corrected filtered column list sorting in Report Browser
Resolved in Pega Version 8.6.5
Sorting was not working in Report Browser for a column list when a filter category was selected. This has been resolved by modifying the pzReportListSort activity to set the correct parameters in step-1 and setting pzSetCategoryParam to retain the sortTitle parameter in step 1 with an added step -2 to call the pzReportListSort activity.
INC-205464 · Issue 721607
Performance improvements for KYC query
Resolved in Pega Version 8.6.5
The GetApplicationKYCTypes report definition was exceeding the default maximum elapsed time of 30 seconds, causing all cases which were part of the due diligence milestone in Client Lifecycle Management framework to be auto-completed. This has been resolved by improving the KYC Items query logic by removing mergeJoin and adding HashJoin Hints.
INC-210837 · Issue 707179
DateTime property correctly formatted in Report Editor
Resolved in Pega Version 8.6.5
When a list report was created via the Report Editor, dragging and dropping a date time property which was embedded inside another page and choosing the format as Date and Time resulted in the property taking pxTextInput instead of pxDateTime. This has been resolved by updating the pzMergeAutoGenForProp activity to get the correct class name for embedded page properties.
INC-211590 · Issue 711018
Auto-complete and calendar popover alignment corrected
Resolved in Pega Version 8.6.5
An issue with the container alignment of the auto-complete and calendar dropdown popovers has been resolved by removing styling in the pyReportEditorStyling .css which was causing the issue.
INC-212157 · Issue 721532
Report filter values correctly displayed
Resolved in Pega Version 8.6.5
The data page name was being displayed in report filters instead of actual values. This was traced to a missing step in the activity pzResolveCopyFilters which was needed to get the data page values in the report filter prompt, and has been resolved.