SR-A692 · Issue 205611
Resolved duplicate portal open when using Microsoft Internet Explorer 11
Resolved in Pega Version 7.1.9
When using Microsoft Internet Explorer 11, trying to access the My Group tab in the links 'Manage Operator Schedules and Profiles' was not displaying the screen correctly on click of any operator or workbasket and an extra portal window was opened. This was a browser-specific dynamic container issue where the lack of an explicit type=button declaration was causing a form submit that triggered a main page refresh. That declaration has been added.
SR-A734 · Issue 205406
Added null clipboard check for Recently Resolved report
Resolved in Pega Version 7.1.9
While running the Recently resolved report, a null ContentPage caused an NPE and prevented the output of the report. This has been resolved by adding a null check for the clipboard page.
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.
SR-A4489 · Issue 214635
Corrected filter application error in SQL generation
Resolved in Pega Version 7.2
If a report definition containing class joins used a grid repeat with filtering enabled, selecting a filter value from the pick list for any column did not apply the filter. Examination of the SQL revealed a flaw in the generated query that caused an incorrect order of evaluation of AND and OR operators in the WHERE clause, and this has been corrected.