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.
SR-A1999 · Issue 214345
"Edit in Excel" not supported in Microsoft Internet Explorer 11+
Resolved in Pega Version 7.2
Please note that due to code differences and rendering issues, the "Edit in Excel" option in Listview is not supported in Internet Explorer versions Microsoft Internet Explorer 11 and higher. Attempts to use Microsoft Internet Explorer 11+ for this will result in the messages "Error loading Transfer XML data" and "Error launching PegaRULES import manager". As an alternative, the Data tables landing page offers conversion of existing data tables to the new format.
SR-A1999 · Issue 214460
"Edit in Excel" not supported in Microsoft Internet Explorer 11+
Resolved in Pega Version 7.2
Please note that due to code differences and rendering issues, the "Edit in Excel" option in Listview is not supported in Internet Explorer versions Microsoft Internet Explorer 11 and higher. Attempts to use Microsoft Internet Explorer 11+ for this will result in the messages "Error loading Transfer XML data" and "Error launching PegaRULES import manager". As an alternative, the Data tables landing page offers conversion of existing data tables to the new format.
SR-A2378 · Issue 214518
Added check for missing getFieldValues page in standalone listview
Resolved in Pega Version 7.2
In some installations, executing list view -> getFieldValues as a stand alone generated the error "Failed to find instance @baseclass". This was traced to the "LISTVIEW_getFieldValues" page not being present, and a check has been added to resolve this problem.
SR-A2378 · Issue 210254
Added check for missing getFieldValues page in standalone listview
Resolved in Pega Version 7.2
In some installations, executing list view -> getFieldValues as a stand alone generated the error "Failed to find instance @baseclass". This was traced to the "LISTVIEW_getFieldValues" page not being present, and a check has been added to resolve this problem.
SR-A2378 · Issue 211007
Added check for missing getFieldValues page in standalone listview
Resolved in Pega Version 7.2
In some installations, executing list view -> getFieldValues as a stand alone generated the error "Failed to find instance @baseclass". This was traced to the "LISTVIEW_getFieldValues" page not being present, and a check has been added to resolve this problem.
SR-A4717 · Issue 214606
Added handling for Microsoft Internet Explorer double-submit on enter
Resolved in Pega Version 7.2
When using the Microsoft Internet Explorer browser, List view was throwing an error on submission by pressing 'enter keyboard key' while working as expected when using the submit button. This was traced to an Microsoft Internet Explorer issue that fires the 'onunload' event twice if it is redirected from within the event handler, and has been resolved by applying a flag-based condition check while executing to prevent the second firing.
SR-A5424 · Issue 213337
Check added to handle mismatched property names given in referred page
Resolved in Pega Version 7.2
If a property name was provided in a list criteria by referring page name, it generated type mis-match error even though the property was of the same type. Creating a new RD with same criteria avoided this error, but a check has been added to "Validate_Report_Condition" to determine whether the property is a leaf or page property . If it is a page property, the system will prefix that property with a "." to resolve the mis-match issue.