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.

SR-B3980 · Issue 282061

Scrollbar added for Microsoft Internet Explorer 11 window sizing overflow

Resolved in Pega Version 7.3

In Microsoft Internet Explorer 11, reducing the screen width caused grid data to overflow onto the tree navigation menu. This has been resolved with the addition of scrollbars to the Action area to handle overflowing content.

SR-B39878 · Issue 299678

Fixed encoding of colon for exported report title

Resolved in Pega Version 7.3

A file exported using Chrome or Mozilla displayed %3A instead of Underscore (_) when replacing a colon in the title. This was an error in the encoding, and has been fixed.

SR-B40038 · Issue 298378

Column alignment with filter icon fixed for Chrome and IE

Resolved in Pega Version 7.3

When a grid was configured with filtering and 'Freeze Grid Header' option was enabled, at runtime the column header did not align as expected with the filter icon when using Chrome or IE. In IE, the anchor element for filter icon needs to have height set to render properly. In Chrome, the oflowDiv gets a height which caused the problem. To resolve the issue, the addHeightToFilterIcon function in ui_grid JS has been modified to consider freeze header cases.

SR-B40177 · Issue 297056

Resolved harness error after using pagination 'load more'

Resolved in Pega Version 7.3

After using the Pagination 'load more' option and clicking on any of the newly loaded items, a blank harness was opened. This was traced to missing change tracking data for the newly loaded rows, and has been corrected.

SR-B40310 · Issue 299601

Offline sync fixed for post-processing Question shape

Resolved in Pega Version 7.3

The post-processing activity of a Question shape was not skipped when 'only execute post processing on client' was checked on the case type rule. A 'when' condition has been added for the post processing activity of Question Flow to fix this.

SR-B40310 · Issue 299855

Offline sync fixed for post-processing Question shape

Resolved in Pega Version 7.3

The post-processing activity of a Question shape was not skipped when 'only execute post processing on client' was checked on the case type rule. A 'when' condition has been added for the post processing activity of Question Flow to fix this.

SR-B4047 · Issue 276127

Fixed intermittent drag and drop failure in List to List with IE

Resolved in Pega Version 7.3

After double-clicking an item in Internet Explorer to move it from left to right in 'List to List' control, the drag and drop functionality intermittently stopped working. This was due to the listeners being removed after double clicking or scrolling and again clicking, and code has been added to reattach the event listeners.

SR-B40783 · Issue 297484

Fixed value focus for percentage control in repeat grid

Resolved in Pega Version 7.3

When configuring percentage control with integer type property inside the Repeat Grid, the field displayed the Case ID and some text instead of the value when focus was out. This was due to an empty string being passed, and has been corrected.

SR-B41140 · Issue 300825

Fixed column alignment in progressive repeat grid

Resolved in Pega Version 7.3

The scrollhead th was generated even when there was no scrollbar for a fixed header grid, causing the column alignment of records in a repeat grid with Progressive pagination that contained one or two rows to become progressively more disaligned from the column headers. The problem did not appear if the actual number of rows was equal to the page size. To fix this, the system has been updated to not generate the scrollhead th when the number of rows is less than the page size of the grid.

SR-B41602 · Issue 300653

Filter conditions made case-insensitive for displaying column filters

Resolved in Pega Version 7.3

The filter comparator/operator dropdown was displaying different options for the same property when adding a filter for a column as opposed to dragging a property from the Data Explorer. This was caused by the dropdown logic using a case-sensitive string comparison to examine the data type of the column or filter, and has been fixed by setting the dropdown logic to ignore case when comparing the data type of the filter to determine which options are shown.

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