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-128890 · Issue 565240

Highlighting fixed for rich-text editor with spellcheck

Resolved in Pega Version 8.5.1

In a Rich Text Editor, after turning on spell check and performing some text highlight on certain words and then clicking save, the formatting of the styling format was being applied to the words after the highlighted word. This has been resolved by modifying the regex reSpellChk1 to remove the last span tag instead of the first.

INC-133924 · Issue 581345

Table captions added for accessibility per HTML5

Resolved in Pega Version 8.5.1

In order to add Table captions for accessibility per HTML5 specifications, a new grid caption field has been introduced to add the caption to the table. When caption is specified, the summary attribute won't be generated.

INC-136620 · Issue 583782

Log off timer localization corrected

Resolved in Pega Version 8.5.1

Localization was not working correctly for the log off timer text “Timeout will occur in”. This has been corrected.

INC-140289 · Issue 589003

Check added to preserve clipboard pages for pop-up

Resolved in Pega Version 8.5.1

Many properties were missing in the clipboard after launching an ImageViewer. This was traced to the clipboard pages being deleted in the pop-up mode, and has been resolved by adding a check to not delete pages in case of pop-up opened from top navigation case.

INC-134893 · Issue 587169

Added check for localeDb properties in dateTimeUtils

Resolved in Pega Version 8.5.1

On click of the Approval/Finish assignment submit button, a blank screen appeared and no further progress could be made. This was traced to an issue with the operator locale not being properly set by the html fragments that initialize the locale for use in dateTimeUtils. This has been resolved by adding a check for properties in the localeDb object.

INC-132771 · Issue 584961

Refresh section of MultiSelect properly handles refresh section

Resolved in Pega Version 8.5.1

On hitting tab or enter on a Multiselect control with "Post value" and "Refresh Section" enabled, focus moved to the header of the page when it refreshed. This has been resolved by updating the 'disable when' expression for "run on client" to better handle the input element used for enabling the controls.

INC-134319 · Issue 581733

Row banding matches on optimized and normal tables

Resolved in Pega Version 8.5.1

Optimized table and normal tables had exactly opposite row banding defined. This was caused by the header row being inside the table body tag: the nth-child selector, used to apply row banding, considered the header row as well while applying even/odd row coloring. To resolve this, the nth-child selectors for odd and even rows have been reversed so that the color banding will be in sync between old and new grids.

INC-137168 · Issue 588708

Documentation updated for Ajax container refresh

Resolved in Pega Version 8.5.1

The documentation for adding an Ajax container has been updated to reflect the proper configuration for adding a refresh within the container.

INC-128970 · Issue 583294

Post value in grid works after clicking on modal submit

Resolved in Pega Version 8.5.1

The row submit on the grid of the modal dialogue worked when the value was updated and there was a click outside the grid. However, when the value was auto-populated, after clicking on the submit and going back to edit the value in the grid, the row submit did not work. Investigation showed that when a modal was submitted with some server errors, the system replaced the DOM and a new grid is initialized: since some of the listeners related to grid are attached to body, on submit of modal with server errors, these old listeners were getting fired. To resolve this, a safe check has been added for modalDetailsDiv before accessing it in event listeners.

INC-127719 · Issue 571778

Text area count correct for special characters

Resolved in Pega Version 8.5.1

The text area character count was showing negative numbers when using special characters. This was due to Cross-site scripting encoding that caused the text length to be incremented by 4. To eliminate this, the text length will now be calculated before encoding.

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