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.

INC-227736 · Issue 744475

Added polling lock to handle CDK Key rotation issues

Resolved in Pega Version 8.8

An error was generated when attempting to open existing encrypted contacts created in the Sales Automation application. This was traced to multiple nodes generating CDKs simultaneously, leading to a race condition, and has been resolved by refactoring the CDK generation code so it will acquire a lock when polling the database to avoid a race condition.

INC-227769 · Issue 731726

ReloadHarness security updated

Resolved in Pega Version 8.8

Security handling has been updated for ReloadHarness to ensure proper CSRF validation.

INC-228169 · Issue 729003

Login error messages updated

Resolved in Pega Version 8.8

Exception response messages have been updated in order to improve security around attempts to bypass operator authentication.

INC-232970 · Issue 742011

Security update for MashUp

Resolved in Pega Version 8.8

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

INC-178831 · Issue 680984

Ensured correct context for multi-select

Resolved in Pega Version 8.8

When using multi-select controls, there was an intermittent issue with selecting values using a mouse click. Using the tab key worked as expected. This was traced to the focus being event triggered multiple times so pega.ctx.dom returned undefined values in the second call.This has been resolved by focusing the target element before creation of capsule to ensure the context remains the same.

INC-180100 · Issue 699838

Scrollbar persists for multiselect

Resolved in Pega Version 8.8

Selecting more than 20 values in the multiselect control caused the scrollbar to disappear. This has been resolved by removing a custom popover height calculation.

INC-183966 · Issue 676560

Corrected duplicated select file label reading

Resolved in Pega Version 8.8

When using a screen reader, the select file button label was announced twice on focus. Investigation showed this was caused by the helper text and tooltip having the same content which sounded like a duplicate reading. To resolve this, the text is now differentiated.

INC-183996 · Issue 669645

Step name given heading level for better accessibility

Resolved in Pega Version 8.8

When using the JAWS shortcut for navigating through headings, the Step name was not announced as expected. This was due to the Step name not containing the necessary code for a heading, and has been resolved.

INC-184307 · Issue 673228

Improved accessibility for overflow menu tab

Resolved in Pega Version 8.8

When a tabbled layout group has more tabs than will fit horizontally on the screen, icons appear to the left and right of the visible tabs to scroll through the available tabs along with a drop down list to select from all available tabs. Running the accessibility tool generated an error message for the down arrow button on the right. This was traced to a set tabindex 0 for unfocusable items, and has been resolved by adding tabindex="-1" for the overflow menu.

INC-186072 · Issue 677409

Updated ClientDynamicData HTML Rule

Resolved in Pega Version 8.8

After upgrading from Pega 7 to Pega 8, attempting to open an assignment on the staging environment showed a blank page. This was traced to the system trying to open a declare expression of "PegaComm-" class, and has been resolved by updating the pzClientDynamicData HTML Rule handling for the top level page and enabling the expression calculation checkbox in the Advanced tab of the pyCaseManger7 harness.

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