INC-202480 · Issue 711699
Resolved report filter section freeze
Resolved in Pega Version 8.7.2
When opening a report with a count column, changing the order of one of the report columns resulted in the report freezing and requiring the report to be closed and re-run. This was traced to a double filter popup appearing that did not close after the column sorting, which happened if the report definition was configured as a summary with an aggregated column such as "Count” combined with a "Do not display group headings" setting on the Report Viewer tab. To resolve this, a new step has been added in the Activity pzPopulateSortOrder to call the pzCancelFilterLogicChanges activity.
INC-217655 · Issue 723564
Resolved validation check freeze for Dynamic Layout Group
Resolved in Pega Version 8.6.5
After creating a multi-step form where step 1 had a Dynamic Layout Group(tabbed) that used form fields configured with validations, clicking next with empty/invalid values in the form intermittently caused the screen to freeze and a javascript exception was logged. This was traced to a missed use case related to templates in the childNode, and has been resolved by adding the necessary safe checks in lgtemplate and lgcelltemplate.
INC-164631 · Issue 641441
Updated Ajax container close to resolve intermittent portal freeze
Resolved in Pega Version 8.4.5
The portal was intermittently freezing after the "+" icon was clicked to create a new case from the Create menu. This was traced to the Ajax container not closing after creation of the create modal, and has been resolved.
INC-208199 · Issue 706446
Added input null check to resolve loading error
Resolved in Pega Version 8.7.2
The application was freezing while loading if action was taken on the controls while a page level message was visible. This has been resolved by adding an additional null check for input before calling the focus API.
INC-157357 · Issue 636711
Hazelcast remote execution not called from synchronized context
Resolved in Pega Version 8.4.5
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-160379 · Issue 633675
Closed case preview display corrected
Resolved in Pega Version 8.4.5
Hovering over the Preview of a closed case in Cosmos User Portal was showing as blank instead of displaying the details, and clicking on it caused the screen to freeze. The case preview of an open case worked as expected, as did opening the preview of a closed case after looking at the preview of an open case. This was traced to an error in the HTML code for the anchor tag in the pyOperatorInfo control, and has been corrected.
SR-C82480 · Issue 421488
Column Headers properly aligned after expand/collapse of Tree Grids
Resolved in Pega Version 8.1.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 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.