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-116805 · Issue 175879

Focus highlighting added to sub-tabs when they receive focus

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

Focus highlighting was not appearing around sub-tabs when they received focus. There was a CSS workaround for this, but it has been resolved.

SR-116818 · Issue 167121

Corrected swim lane routing with shapes

Resolved in Pega Version 7.1.7

While using swim lanes, adding shapes into the flow caused unexpected and random behavior of the process modeler including failure to return control to the user after saving. This error was related to routing handling when swim lanes are present, and has been corrected.

SR-116893 · Issue 169075

Corrected browser display errors for large decision tables

Resolved in Pega Version 7.1.7

A browser logic flaw with IE9 caused a condition where large tables would not display the decision table, the 'Show Completeness' button, or the 'Edit in Excel' button if there were more than 500 records. These could be made to be visible with modification to the DecisionTableSizeThreshold and DecisionTableSizeThreshold2 system setting, but the logic has been corrected.

SR-117937 · Issue 173922

Corrected browser display errors for large decision tables

Resolved in Pega Version 7.1.7

A browser logic flaw with IE9 caused a condition where large tables would not display the decision table, the 'Show Completeness' button, or the 'Edit in Excel' button if there were more than 500 records. These could be made to be visible with modification to the DecisionTableSizeThreshold and DecisionTableSizeThreshold2 system setting, but the logic has been corrected.

SR-116899 · Issue 169326

Edit validation displays literal characters

Resolved in Pega Version 7.1.7

If a property with edit-validate defined on it is included in a section with the control TextArea used, an error message is shown on top of the property if the edit validate returns false. However, the error was not shown as literal but rather displayed the encoded characters and was difficult to understand. This was traced to double encoding of characters like ">" in the displayed string, and has been changed so the literal character will appear.

SR-116903 · Issue 167940

Recent Explorer item handling corrected

Resolved in Pega Version 7.1.7

When opening a Scheduled item from Recent Explorer, an incorrect flow was being called and the Review Harness buttons (which are based on flow parameters) were incorrect. This was traced to a missing TaskWrapper activity, and has been corrected. In addition, a process was added to check property as well as parameter in the Review Harness.

SR-116908 · Issue 168347

When rules now display all text fields for function aliases

Resolved in Pega Version 7.1.7

Creating a new Access When rule failed to show the text fields for most available function aliases when a condition was added to the rule. This was an error in the passing of the classname to the function, and has been fixed.

SR-116936 · Issue 167898

Discarded threads set to properly clear on refresh or tab close

Resolved in Pega Version 7.1.7

When the browser was refreshed or an inactive recent tab was closed on the client side, the discarded threads were not getting properly cleared at the server end. To remedy this, the JavaScript has been updated to cleanly remove the threads.

SR-116941 · Issue 168143

Improved performance for sending queued messages

Resolved in Pega Version 7.1.7

LogToSpecifiedAppender was experiencing poor performance in some situations caused by duplicating locking attempts while processing an appender to send queued messages. To improve this, code changes have been made to smooth locking and avoid searching appenders when dynamic appenders are configured.

SR-116950 · Issue 167458

Rule name validation checks relaxed for draft mode

Resolved in Pega Version 7.1.7

In order to facilitate flow design, Decision shape properties will no longer require rule name validation when using Draft Mode.

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