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.

SR-B31778 · Issue 294184

First column name displays in tree grid

Resolved in Pega Version 7.3

The first column name was not appearing in the tree grid using the freeze header configuration. This has been fixed.

SR-B31778 · Issue 290725

First column name displays in tree grid

Resolved in Pega Version 7.3

The first column name was not appearing in the tree grid using the freeze header configuration. This 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-B31778 · Issue 301431

Fixed tree grid column alignments for Internet Explorer/ Chrome

Resolved in Pega Version 7.3

When using freeze headers with fill 100% width, Internet Explorer and Chrome showed alignment issues between the header and content columns in a tree grid. This was caused by a missing semicolon in the inline style of left grid header for tree grid, which has been fixed.

INC-180233 · Issue 660577

Offline.Rulecache UI module capacity increased

Resolved in Pega Version 8.4.6

Clicking the save button on a modal window caused the application to freeze and all the buttons were disabled. This was traced to the pega.offline.rulecache UI module having a default hard limit of 500 rules. Once the hard limit was reached, the system intermittently silently refused caching additional rules depending on the amount of rules packaged or the order in which the rules are loaded to the cache. To resolve this, the system has been updated to only log a console warning once the maximum threshold is reached, allowing the application to operate normally and at the time inform about the potential impact of having too many rules in memory.

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