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-126361 · Issue 189663

Case Designer modified to counter Microsoft Internet Explorer 8 UI override

Resolved in Pega Version 7.1.8

While working in the Stages & Processes tab using the Microsoft Internet Explorer 8 browser, it was not possible to view or modify the step and details and some buttons were not working. This was due to the display of auto complete being overridden with the browser's UI styles z-index. To create the proper behavior, the Case-Designer-styles CSS has been modified to add a Pega-specific z-index for process entry in Microsoft Internet Explorer 8.

SR-126460 · Issue 190738

Corrected persistent highlighting of work object

Resolved in Pega Version 7.1.8

If a work object was opened from the following button in the left panel, that particular WO opened but remained highlighted in blue even after other selections were made. This was caused by a configuration issue where the pyFavorites section was refreshed if the FollowUnFollow count changed, but if there was a Mixin as the Background for Row focus and Row Selection cases the text would remain highlighted until there was another change in the FollowUnFollow count. In order to resolve this, "Use default background for this format" will be enabled by default.

SR-126546 · Issue 194655

Additional out-of-the-box controls marked for accessibility

Resolved in Pega Version 7.1.8

The following out-of-the-box controls have now been marked as accessible: UI Controls: - pxButton - pxHidden - pxDisplaytext

SR-126546 · Issue 200724

Clipboard message method updated to improve performance

Resolved in Pega Version 7.1.8

Occurrences of ClipboardPage#getMessagesAll have been replaced with ClipboardPage#getMessageCountAll to improve performance.

SR-126576 · Issue 189461

RTE font change behavior smoothed

Resolved in Pega Version 7.1.8

If text present in the RTE was selected and the font family changed, the selected text was getting unselected and cursor was moving out. This has been fixed by modifying cmd_fontName and _selectNode to retain the selection of content in the RTE after changing the font name.

SR-126621 · Issue 193287

Localization added for on-click harness tab

Resolved in Pega Version 7.1.8

Localization was not working for the label of a tab containing a harness which was opened by a button. This was was due to the field value not being used for the tab name when it is configured as an on click action for a button, and localization has been added for tabName when the navigation rule is configured as showharness.

SR-126649 · Issue 193881

Documentation updated for column layout controls focus

Resolved in Pega Version 7.1.8

The documentation for column layouts has been updated to clarify that controls in a column layout main region receive focus before controls in the sidebar region receive focus. This is important for understanding the tab order on the page for accessibility users.

SR-126649 · Issue 192252

Documentation updated for column layout controls focus

Resolved in Pega Version 7.1.8

The documentation for column layouts has been updated to clarify that controls in a column layout main region receive focus before controls in the sidebar region receive focus. This is important for understanding the tab order on the page for accessibility users.

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.

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