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-138354 · Issue 594355

Third party cookies reminder added for Mashup in incognito browsers

Resolved in Pega Version 8.6

When working in incognito/private browser windows, attempting to use Mashup displayed a message indicating login credentials were not recognized ("Unknown password and/or username"). This was due to recent changes originating with the browsers regarding blocking third-party cookies which are necessary for Mashup to run. For informational purposes, a new API has been added which will check for the PegaRules cookie; if the cookie is not present, the message "Third party cookies must be enabled for Mashup to function." will be displayed. This message may be customized by configuring the setting "pega.web.config.xCookiesDisabled" with the required message.

INC-138672 · Issue 593280

Corrected size of Session Timer modal window

Resolved in Pega Version 8.6

The session timer modal dialog window did not have the correct height. This has been resolved by increasing the height of the logoff timer modal dialog from 210 to 236 in the desktop_showTimeoutLogoffDialog method of the pega_desktop_appcontrollerlite.js file.

INC-138701 · Issue 596611

Multi Select populates values for Page group

Resolved in Pega Version 8.6

Multi Select populates values for Page groupThe Multi Select control was not populating values when Page group was chosen as a source. This has been resolved by updating control_multiselect and pzgetACdata to support page group source.

INC-138709 · Issue 591325

Removed empty space in harness error messages

Resolved in Pega Version 8.6

After changing the display option for the validation error message to top of the harness, the message was displayed along with empty white space. This gap was caused by a hidden error table which had display set as "block", and the display has been resolved by changing the display to "none".

INC-138803 · Issue 591925

Mouse event Cross site scripting updates

Resolved in Pega Version 8.6

Cross site scripting protections have been added to mouse event attributes.

INC-138877 · Issue 589534

Filter range decimals persist for German locale

Resolved in Pega Version 8.6

When using German localization, filtering values in Dashboard caused the entered decimal value range (13.00 - 50.55) to lose the separator and become a whole number (1300 - 5055). This has been corrected.

INC-138886 · Issue 589301

Animated modals correctly trigger refresh conditions

Resolved in Pega Version 8.6

In the client application, a list of tasks can be selected by the user to act on. Clicking on any action opens a modal to work on the task. Once that task is complete, the modal is closed automatically, and the task list is updated to show the next task. The task list section has a refresh condition that triggers when D_Reload.pxUpdateDateTime changes (that timestamp is updated when a task is completed inside the modal). However, after upgrade the task list was no longer updating correctly. This was traced to the animation being performed as an asynchronous task: by the time it was executed, the dom element was not present and the refresh section was not getting triggered. This has been resolved.

INC-138968 · Issue 594169

ARIA landmarks added to put dynamic layout in tab order

Resolved in Pega Version 8.6

As part of W3 accessibility specifications, ARIA landmarks have been added to dynamic layouts to direct tabbing focus. If the role type is "landmark" or "document", tabindex=-1 will be added, and for component widgets tabindex=0 will be added unless it is a non-focusable element like Alert, log etc.

INC-139023 · Issue 591164

Tab will exit portal side menu

Resolved in Pega Version 8.6

It is expected that the Tab key will take users out of the portal menu and to the next focusable element, but on the side navigation menu both tab and arrow keys moved to the next menu item. This caused users to have to navigate the entire menu. The correct behavior was seen for the Navigation rule when called from an Action (for example on the button). This was traced to the system using tabindex as "0" for every element in the menu, and the tabs code has been updated to exit out of the menu bar when pressed.

INC-139086 · Issue 597145

"Show next error" correctly displayed on user portal

Resolved in Pega Version 8.6

In the Case Worker user portal, the Show Next Error link was not shown when the layout group had a validate rule in the flow action. The same configuration worked as expected in Case Manager. This was a missed use case, and has been resolved.

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