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-A2677 · Issue 213336

Updated autocomplete to accept shift-key characters

Resolved in Pega Version 7.2

The autocomplete function was not correctly incorporating keystroke combinations that required the shift key, such as '_' when showing results. This has been fixed.

SR-A4648 · Issue 211547

Updated autocomplete to accept shift-key characters

Resolved in Pega Version 7.2

The autocomplete function was not correctly incorporating keystroke combinations that required the shift key, such as '_' when showing results. This has been fixed.

SR-A6168 · Issue 217424

Updated encoding for "&" in dropdowns using defer load

Resolved in Pega Version 7.2

In case of dropdowns with defer load, options having "&" were being double-encoded and displayed as '&'. The API has been updated to correctly handle the special character.

SR-A6815 · Issue 216299

Updated error message display for local actions

Resolved in Pega Version 7.2

Validation errors present at the harness level on the screen were being cleared with a click on the actions button. This was due to a page context error, and has been corrected.

SR-A6732 · Issue 215512

Updated event listener for Microsoft Internet Explorer to resolve refresh hang

Resolved in Pega Version 7.2

If the out-of-the-box Rich Text Editor had spell check enabled and was configured with an OnChange - Refresh Section, entering text in RTE and doing a spell check changed the focus to outside of the RTE and caused the Microsoft Internet Explorer browser to hang. It was found that a permission denied error was being thrown on the element purge when detaching the event handler of an inaccessible RTE iframe during the section reload. This has been resolved by attaching the event listener using the native addEventListener instead of pega.util.Event.addListener.

SR-A3895 · Issue 211401

Using page passed properly for replace current scenarios of Launch Harness

Resolved in Pega Version 7.2

The using page was not passed properly for replace current scenarios of Launch Harness. To correct this, the pzpega_ui_dynamiccontainer.js and pega_desktop_api.js have been updated to pass the correct page context for doUIAction request.

SR-A3571 · Issue 208170

Validation errors made visible for UI-Kit-7:03-01 ruleset

Resolved in Pega Version 7.2

In a TabbedScreenFlow7, there are flow action with Validate rules configured. When the validation failed, the screen flow stopped proceeding further but no error was displayed to the user if the harness was picked up from UI-Kit-7:03-01 ruleset. This has been corrected.

SR-A7485 · Issue 216800

Visible When Conditions working for buttons in Harness

Resolved in Pega Version 7.2

Due to changes in the condition expression formatting, Visible When Conditions were not working as expected for buttons in the harness after upgrade. A check has been added to evaluate the structure and apply the correct visibility expression.

SR-A7679 · Issue 217201

Wrap text working with accessibility

Resolved in Pega Version 7.2

When accessibility was turned on, the wrap text was not functioning properly due to the handling of white-space:nowrap in iconRequired class. This has been corrected.

SR-A4720 · Issue 212449

Corrected focus for tabbing Ruleset inclusion data entry

Resolved in Pega Version 7.2

Data entry for "RuleSets To Include" was behaving unexpectedly when using keyboard-only input: when a value was entered in the "Minimum Version" text field, pressing TAB on the keyboard shifted focus from the next textbox to the top of the sheet due to a row-refresh added for app context. This 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