SR-A94024 · Issue 264561
Resolved RTE spellcheck freeze with Microsoft Internet Explorer
Resolved in Pega Version 7.2.2
If spellcheck was invoked on an RTE file in a modal dialog while using Microsoft Internet Explorer , the reload harness was not being correctly triggered and the UI would freeze. This was due to the body event listeners not working in Microsoft Internet Explorer , and code has been added to remove the listener from the document body if the browser is Microsoft Internet Explorer .
SR-A76192 · Issue 254055
Added support for tabbing on fixed size freeze header in grid
Resolved in Pega Version 7.2.2
When a grid was configured with many columns and the Freeze Header checkbox was selected from the presentation tab, clicking the header and pressing tab caused the header to move and lose alignment with the columns below. This was an unexpected use case, and support for tabbing on a Fixed size Freeze header in a grid has been added.
INC-130499 · Issue 581443
Mobile offline nested repeating dynamic layout repaired
Resolved in Pega Version 8.2.8
Attempting to open a repeating dynamic layout while working in mobile offline caused the screen to freeze and an UnmodifiablePropertyException error to be generated. This has been corrected.
SR-C97873 · Issue 437280
Added check to maintain key value when using collapseAllMenu in child navigation menu
Resolved in Pega Version 8.3
After a navigation menu had a child added as reference navigation menu that used the function collapseAllMenus, the screen was freezing if a link was clicked in the added child navigation and a javascript error appeared on the console screen. This was traced to an improper key being set in sessionStorage object in setItem due to the nesting, and has been corrected by adding a check in sessionstorage setitem to maintain the proper key value.
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-141751 · Issue 596137
DragAndDrop attaching large file properly disables 'X'
Resolved in Pega Version 8.2.8
When a large file was attached using the DragAndDrop feature, the 'X' icon/button was not disabled. This made it possible to click 'X' and perform other actions during the upload, which caused the screen to freeze and required a browser refresh to continue the work. This was traced to incomplete work done on large file uploads, and has been resolved by ensuring the busy Indicator shown will be applied to the complete screen to avoid any other actions being performed.
SR-C82480 · Issue 421486
Column Headers properly aligned after expand/collapse of Tree Grids
Resolved in Pega Version 8.3
When using a hierarchical table - tree grid with a configuration that included Width of content-Pixels(Fit Content), a Fixed (pixel) size grid, and Freeze Header, expanding and collapsing back the contents resulted in a misalignment of the column headers. The fixed header implementation makes use of multiple table layouts which have to kept in sync via javascript; this issue has been resolved by rewriting the fixed header implementation to call setHeadersWidth on expand/collapse of a treegrid row.
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.