SR-123642 · Issue 187841
Resolved MultiSelectList control issues for Microsoft Internet Explorer 9+
Resolved in Pega Version 7.1.8
The MultiSelectList control was no longer working for Microsoft Internet Explorer 9+. When a user attempted to select one or multiple items in the MultiSelectList control, the values were not captured when going to the next screen and a JavaScript exception was thrown. This was due to an API change in newer versions of the Internet Explorer (Microsoft Internet Explorer) browser. Microsoft Internet Explorer is following a more strict standard about how the createElement function is used, which caused the JS error to be thrown, and the system has been updated to resolve this issue.
SR-123678 · Issue 185155
Resolved issue with duplicate thread creation
Resolved in Pega Version 7.1.8
In Designer Studio, a new thread was created on every click of New Item in the recent list. This was due to the contentID generated not being passed at the document launch time, and the APIs have been updated.
SR-123686 · Issue 184976
Properly resolved HTML tags in ListView
Resolved in Pega Version 7.1.8
If any HTML tags such as were used inside the Full Description of ListView, the tags are were not being resolved and were instead displayed as-is. This was caused by how the XSS filter affected the way the tags were reference when returned to the browser, and has been fixed.
SR-123741 · Issue 186119
Collapsible header text updated for accessibility
Resolved in Pega Version 7.1.8
When a UI layout/section used a collapsible header, JAWS read the field values "Click to expand" and "Click to collapse." Using the word "Click" is not optimal for accessibility, and this field has been changed to "Disclose contents" and "Hide contents."
SR-123750 · Issue 189489
Smoothed multiple portal tabs handling
Resolved in Pega Version 7.1.8
After opening the Case Manager developer portal, if a user portal was opened in a second tab using the 'Switch Portal' option shown in operator menu, returning to the developer portal tab caused that tab to be refreshed and the user portal tab to close. Previously, attempting to open a second portal session in a tab of the same window resulted in a 'Multiple sessions running' error. This limitation was removed in Pega 7.x. However, in this case the 'ShowDesktop' activity could not determine the 'ThreadName' parameter and defaulted to the 'Standard' thread and this change caused the refresh. The logic for determining the thread name has been updated to remove this issue.
SR-123785 · Issue 184291
"Required" checkboxes now working properly with Firefox
Resolved in Pega Version 7.1.8
When using Firefox, putting focus on a field which has "Required" checkbox checked and clicking "Enter" button caused the flow to ignore the checkbox and move forward without showing any error on the screen. This was an issue with the browser not supporting the event prevention code, and the system has been updated to ensure expected behavior.
SR-123809 · Issue 185686
Report schedule icon display fixed for SQL
Resolved in Pega Version 7.1.8
When disabling then re-enabling the task for a scheduled report through the report browser, the icon that indicates whether the report is scheduled will sometimes not show. That is, the report is actually scheduled, and will run at the appointed time, but there will be no icon in the report browser to show that it is scheduled. The SQL query to retrieve the list of scheduled reports was being generated incorrectly for certain databases (e.g., MS SQLServer). Therefore the rescheduled reports were omitted from the list, and no icon would be displayed for them. To resolve this, the custom getcontent activity 'pxgetRRContentForRB' has been inserted.
SR-123820 · Issue 185192
Fixed truncated custom datetime in RD
Resolved in Pega Version 7.1.8
If a report was created on work objects that used a property of type DateTime in Report definition output, custom datetime settings were truncated. This was a problem with the grid implementation where the modified GenerateGridHTML. "D" was set always to propTypeForFormatting even for DateTime. It has bene fixed.
SR-123911 · Issue 189019
Changed timing for retrieving autocomplete values after modifications
Resolved in Pega Version 7.1.8
When AutoComplete controls is used to populate Data, a wrong value was sometimes getting populated in the AutoComplete. The issue was due to the delay in change tracking request after the request is complete, causing it to take values from the server before the changes were committed. This has been corrected.
SR-123911 · Issue 192195
Changed timing for retrieving autocomplete values after modifications
Resolved in Pega Version 7.1.8
When AutoComplete controls is used to populate Data, a wrong value was sometimes getting populated in the AutoComplete. The issue was due to the delay in change tracking request after the request is complete, causing it to take values from the server before the changes were committed. This has been corrected.