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.

INC-195581 · Issue 691841

Control menu code minified

Resolved in Pega Version 8.5.6

Minification has been turned on for control menus.

INC-195583 · Issue 684839

Flow action modal pop-up closes after submit

Resolved in Pega Version 8.5.6

On clicking Submit button on the modal window, the post action was successfully completed but the buttons froze and the modal window did not close. This was traced to a missing condition in the if loop to handle the needed flow action logic, and has been corrected.

INC-195683 · Issue 687952

Security update for MashUp

Resolved in Pega Version 8.5.6

Cross site scripting protections have been updated for the LoadMashupPage activity and RedirectTo parameter.

INC-196079 · Issue 694397

Repaired shortcut key use in Flow Action default buttons

Resolved in Pega Version 8.5.6

After update, the shortcuts configured on flow action buttons stopped working. The previous version displayed the labels "Save" and "Cancel" on the portal and it was possible to use hotkeys to press the button. The updated system displayed "Sa&ve" and "Cance&l" and the shortcut did not work. This was traced to the encoding performed by the CrossScriptingFilter API, and has been resolved by ensuring the correct text value is retained and displayed for use with the hotkeys.

INC-197410 · Issue 690217

Handling added for invalid numeric range

Resolved in Pega Version 8.5.6

When filtering the range in number column with value as “1000000” , the validation message appeared as "1000000 : This results in an invalid numeric range". This has been resolved with an update to use Data-value to get the non-formatted value for decimal.

INC-197481 · Issue 695583

Accessibility improved for blank field errors in non-auto generated controls

Resolved in Pega Version 8.5.6

When using non-auto generated controls, leaving an edit field blank causes an error message informing that the value cannot be blank. An accessibility issue was seen where this error text was not part of the field label or description, preventing it from being announced by screen readers (NVDA or JAWS) when focus is on the field. This has been corrected by adding aria-describedby in non-template textarea.

INC-198021 · Issue 686631

Corrected blank areas on maximized view

Resolved in Pega Version 8.5.6

A blank section was displayed when maximizing the reply screen. Investigation showed that when the editor was inside a positioned container with overflow hidden and the editor had a scrollbar with its body height greater than the document, the scrollIntoView would scroll to grey spaces which were originally hidden by overflow. This has been resolved by commenting out scrollintoview, since it is not necessary and scroll position/cursor will be retained without it.

INC-198033 · Issue 688688

Updated ctx.recordId as variable handling

Resolved in Pega Version 8.5.6

Attempting to create a case using the Microsoft Internet Explorer 11 browser failed and the browser console log recorded the error "Caught exception: TypeError: Unable to get property 'split' of undefined or null reference". This has been resolved by updating the handling for passing the ctx.recordId as variable.

INC-198316 · Issue 699313

Resolved error in PortalNavigation save

Resolved in Pega Version 8.5.6

An error indicating Rule-UI-Components were either missing or could not be found appeared while using revalidate and save for a PortalNavigation section, though the update completed and worked as expected. This has been resolved by adding validation handling for a section when given a property as the class for the icon source.

INC-198326 · Issue 690316

Tab key menu navigation updated

Resolved in Pega Version 8.5.6

Using the tab key to navigate links in the left menu would intermittently skip links or not appear to advance. This was an unintended side effect of work done to use the tab key to move out of the portal menu and to the next focusable element, and has been resolved by modifying the re-setting tabindex for left navigation so it will anchor on the first element in the menu list for tab traversal.

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