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-163198 · Issue 637798

Performance improvements for research path interaction

Resolved in Pega Version 8.7

Research path interaction driver composite loading was taking an excessive amount of time due to RULE-HTML-SECTION @BASECLASS ERRORLIST being called multiple times. This has been resolved by changing the ErrorList Section to guard the getMessagesMapByEntryHandle API call with a condition "if (ClipboardPage.getMessageCountAll > 0)".

INC-163544 · Issue 639301

Accessibility corrected for Cosmos user portal left navigation panel

Resolved in Pega Version 8.7

It was not possible to see the focused control label in the left pane of the Cosmos user portal because it was not expanding when its control received focus from tabbing. Investigation showed the class acting as a polyfill for :focus-within was applied only on the observed element when using Microsoft Explorer 11, and this has been resolved by updating the CSS selectors and ensuring the class is applied to every parent element down the DOM tree.

INC-163644 · Issue 652968

Error message handling added for nested page lists

Resolved in Pega Version 8.7

When a multiselect referring pagelist(x).pagelist2() had an error message, the error was repeated for all pagelist(y).pagelist2() in the UI. This has been resolved by adding error handling for nested page lists by using registerErrorMessages for multiselect errors.

INC-164012 · Issue 640039

Source edit with formatting resumes process automatically

Resolved in Pega Version 8.7

When opening a paragraph rule and clicking on Actions > checkout out to branch, the rule refreshed and the modal never appeared to allow the selection of a branch on the current application. This was an inadvertent side effect of work done to resume the event queue if it was paused when applying styles, and has been resolved by modifying the work so it resumes the action sequence only when source mode is initialized in the Rich Text Editor.

INC-164641 · Issue 649391

Table header aria label updated

Resolved in Pega Version 8.7

In a PegaWAI enabled application with the NVDA screen reader, a table header column which had filtering enabled was read as "Column Name Enter to Filter" on the first focus, but the filter operation did not work on hitting enter. When focus was moved to the second tab, the filter worked as expected. This was traced to an incorrect aria-label in the table header description, and has been resolved.

INC-164775 · Issue 681239

Web page generation security updated

Resolved in Pega Version 8.7

Cross-site scripting protections have been enhanced around web page generation.

INC-164924 · Issue 639022

Serbia added to country codes list

Resolved in Pega Version 8.7

The CountryCode for Serbia (SRB) has been added to the existing country codes.

INC-164979 · Issue 650155

Column values displayed in modify filter of grid

Resolved in Pega Version 8.7

Column values were not displaying in the modify filter after cancelling the ‘due date apply filter’ condition in grid -Go to My Work -> Work Queue -Apply filter condition for Program and Country/region columns. This was traced to the pysymbolic date value being posted after selecting and before applying the filter, and has been resolved.

INC-165277 · Issue 645168

PDF generation corrected

Resolved in Pega Version 8.7

Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.

INC-165964 · Issue 656814

Harness context set for modal dialog on interaction portal

Resolved in Pega Version 8.7

An AddDelete refresh condition on a page list property was not triggering a ReloadSection as expected. This was a special use case in the interaction portal where a modal dialog was opened but the harness context was not set properly, and has been resolved by ensuring the harness context is correct.

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