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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

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-123960 · Issue 184251

Error message updated for report 'save as'

Resolved in Pega Version 7.1.8

The error message created when doing a 'Save As' report to a private category has been updated for clarity. Previously, the error generated was "The name you entered is not valid". This has been changed to "The name should start with letter followed by letter or digit or underscore".

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.

SR-123968 · Issue 194580

Added special character handling to Process Modeler

Resolved in Pega Version 7.1.8

After migration, some sites attempting to open flows through Process Modeler saw only the 'loading' message for a long time and then an error was displayed. This was traced to the use of user-input strings containing special characters in the canvas-based rule data, and has been resolved by adding character escaping during the model generation.

SR-123968 · Issue 194306

Added special character handling to Process Modeler

Resolved in Pega Version 7.1.8

After migration, some sites attempting to open flows through Process Modeler saw only the 'loading' message for a long time and then an error was displayed. This was traced to the use of user-input strings containing special characters in the canvas-based rule data, and has been resolved by adding character escaping during the model generation.

SR-123977 · Issue 185468

Optimized regex decision tree for property and when values

Resolved in Pega Version 7.1.8

A regex expression run against long property names was resulting in system slowdown and stuck requestor threads. A similar issue was encountered with When rules. To resolve this, the decision tree has been optimized.

SR-124004 · Issue 186135

Timing improved for delegated strategy rule editing

Resolved in Pega Version 7.1.8

After saving a strategy rule to an unlocked production ruleset and adding that version to My Favorites, it was not possible to checkout the rule. When the refresh/reload button (only button displayed on the rule toolbar) was clicked, a StringIndexOutOfBoundsException message was generated. The root cause was a timing issue due to system slowness that prevented the display of the toolbar icons, and code has been implemented to increase the timeout for 'openRuleINprogress'.

SR-124005 · Issue 185470

Fix inserted for CaseWorker portals using Microsoft Internet Explorer 8

Resolved in Pega Version 7.1.8

CaseWorker portal links to open and interact with cases were not working in the Microsoft Internet Explorer 8 browser. This was caused by the method used to get the dynamic container not being supported by Microsoft Internet Explorer 8, and has been resolved by changing the querySelector to get the proper class names.

SR-124007 · Issue 187210

Added handling for NPEs on mobile devices

Resolved in Pega Version 7.1.8

Answering a questionnaire on a mobile device was generating the error "NullPointer in SafeURL.put()" due to the source element being a radiobutton div and not sending the request for postvalue. This was a missing condition in the initiatepost method of pega_ui_events for handling NPEs on mobile and the system has been modified to correct this.

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