Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-123636 · Issue 184161

Trojan horse protection auto-enabled

Resolved in Pega Version 7.1.8

The authentication/trojanhorseprotection previously defaulted to NEVER, creating a security vulnerability. The trojanhorseprotection setting now defaults to external.

SR-123636 · Issue 181701

Trojan horse protection auto-enabled

Resolved in Pega Version 7.1.8

The authentication/trojanhorseprotection previously defaulted to NEVER, creating a security vulnerability. The trojanhorseprotection setting now defaults to external.

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-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-123945 · Issue 185036

Corrected symbol handling in ToolTips

Resolved in Pega Version 7.1.8

In the ToolTips, the '@' character was being replaced with '@'. This was an issue with the character being parsed instead of being treated as literal text, and has been fixed.

SR-123945 · Issue 186241

Corrected symbol handling in ToolTips

Resolved in Pega Version 7.1.8

In the ToolTips, the '@' character was being replaced with '@'. This was an issue with the character being parsed instead of being treated as literal text, and has been fixed.

SR-123961 · Issue 184528

New Stylesheets save to harness correctly

Resolved in Pega Version 7.1.8

Stylesheets added to the StyleSheetName pageList were not getting saved in Harness rule. This was traced to the process not updating the primary page on clipboard, and has been corrected.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us