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-127684 · Issue 194461

Fixed Microsoft Internet Explorer 9 freeze with grid row numbering

Resolved in Pega Version 7.1.8

Attempting to Wrap Up an interaction after viewing a section using a repeat grid with row numbering ON using Microsoft Internet Explorer 9 was causing a browser freeze. This was traced to an API issue where the incorrect frame handling was called for the grid, and has been updated.

INC-157357 · Issue 636712

Hazelcast remote execution not called from synchronized context

Resolved in Pega Version 8.6.1

After navigating to the Admin Studio portal to view the nodes, the portal was temporarily freezing. Investigation of the thread dump revealed this was caused by a DDS pulse sending a remote execution call to all nodes to update logger settings even though the site was not using DDS. This has been resolved by updating the system to avoid calling Hazelcast remote execution from a synchronized context.

INC-180233 · Issue 660579

Offline.Rulecache UI module capacity increased

Resolved in Pega Version 8.6.1

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