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.
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.