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-126654 · Issue 192199

Context retained for nested grids

Resolved in Pega Version 7.1.8

The base reference was computed incorrectly when RDL is dropped inside a repeating structure, causing local action to be executed in the wrong context. To resolve this, the system has been updated to return null if a RDL row is encountered in getRepeatObject, so that base_ref is calculated from the node where action is invoked.

SR-126679 · Issue 197204

Tree grid alignment resolved for Google Chrome and Firefox

Resolved in Pega Version 7.1.8

When using the Google Chrome and Firefox browsers, tree grid rows were not properly aligned. This was due to legacy code in GenerateGridHTML which was running in quirks and used a different document model in different browsers. The model was no longer necessary due to a change in the generation method, and has been removed.

SR-126679 · Issue 197617

Tree grid alignment resolved for Google Chrome and Firefox

Resolved in Pega Version 7.1.8

When using the Google Chrome and Firefox browsers, tree grid rows were not properly aligned. This was due to legacy code in GenerateGridHTML which was running in quirks and used a different document model in different browsers. The model was no longer necessary due to a change in the generation method, and has been removed.

SR-126730 · Issue 193522

Enabled accessibility for validation errors in modal windows

Resolved in Pega Version 7.1.8

Validation error messages were not being read by the JAWS accessibility function automatically in modal windows. This was due to missing ARIA attributes, and these have been added to the error spans.

SR-126732 · Issue 192781

Corrected button label for JAWS

Resolved in Pega Version 7.1.8

With JAWS accessibility active, when you navigate to a menu button labeled "Other Actions", JAWS says "Menu. To move through items press up or down arrow...O" instead of reading out the title of the button. This was caused by the button being used to show the menu, which added role="menu" to it, and this has been corrected in the button generation RUF.

SR-127644 · Issue 192194

Refresh When' behavior fixed for portal tabs

Resolved in Pega Version 7.1.8

When a 'Refresh When' was active on a portal tab, the system would become unresponsive while trying to refresh it. This was caused by an incorrect element call resulting in a JavaScript error and has been corrected.

SR-128834 · Issue 192690

Corrected dynamic select refresh behavior

Resolved in Pega Version 7.1.8

When a Dynamic select with "OnChange + refresh" was configured, the values in dynamic selects were not retained after a refresh in the Google Chrome and Firefox browsers. This occurred most often when selecting a value for a second dynamic select box caused a refresh and forced the previously selected value to be lost from the first box. The values were reset to "Select.." and the drop values were also not populated. The root cause of this problem was trailing white spaces in the values returned by the service that populated the dynamic select. While Microsoft Internet Explorer automatically trimmed these spaces, Google Chrome and Firefox did not. This has been corrected by trimming results when getting data from xml in the DynamicSelect JavaScript file.

SR-128834 · Issue 193912

Corrected dynamic select refresh behavior

Resolved in Pega Version 7.1.8

When a Dynamic select with "OnChange + refresh" was configured, the values in dynamic selects were not retained after a refresh in the Google Chrome and Firefox browsers. This occurred most often when selecting a value for a second dynamic select box caused a refresh and forced the previously selected value to be lost from the first box. The values were reset to "Select.." and the drop values were also not populated. The root cause of this problem was trailing white spaces in the values returned by the service that populated the dynamic select. While Microsoft Internet Explorer automatically trimmed these spaces, Google Chrome and Firefox did not. This has been corrected by trimming results when getting data from xml in the DynamicSelect JavaScript file.

SR-126107 · Issue 189620

"Previous" button now navigates to correct index

Resolved in Pega Version 7.1.8

After correcting a validation error while enabling buttons in a repeating grid, the "Previous" button was navigating to the wrong index, skipping rows in between instead of displaying details for the immediately previous item. The "Next" button worked correctly. This was caused by an error in success callback where "grid.activeRow" was updated to the wrong index when the rows above were expanded, and has been fixed.

SR-130181 · Issue 201836

Modified Dropdown to return JSON content type for use with ISAM

Resolved in Pega Version 7.1.8

ISAM, a third-party tracking layer, embeds JavaScript code in text/html responses. The Dropdown control was returning JSON but in HTML content type, so sites that use ISAM found that the ISAM JS code was embedded and the Pega JS that parses the JSON response failed to execute. Changes have been made to the wrapper to ensure the desired behavior of Pega returning application/json content type for JSON responses instead of text/html.

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