INC-197358 · Issue 695309
Resolved finish assignment screen freeze
Resolved in Pega Version 8.6.3
In some assignments of several flows, when the processing was done (finish assignment) the screen only displayed the loading logo. The only way to proceed was by refreshing the browser. The browser console showed the error "Uncaught TypeError: Cannot read properties of null (reading 'undefined') at setTargetValuesSuccess (expression_calculation_1480665478.js!!.js:1) at k". The error did not occur when using Live UI privileges. This has been resolved by updating the expression calculation.
INC-202480 · Issue 699082
Resolved report filter section freeze
Resolved in Pega Version 8.6.4
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 706447
bbbAdded input null check to resolve loading error
Resolved in Pega Version 8.6.4
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-D52144 · Issue 515672
When no active document is available on login, first document will be marked active
Resolved in Pega Version 8.2.5
After logging into the user portal, attempting to perform operations like (opening a case/work object, opening reports etc.) caused the browser request to spin or freeze. The only way to recover was to close and re-launch the browser window/session and re-login. This issue occurred when there was an active reportdefinition document before the browser/node crash in the tabless dynamic container(DC) portal. After recovery, the dynamic container did not recreate the report definition document but instead tried to activate the first document in the portal, which in this case was the default harness configured in the Dynamic Container. As it was not yet loaded, exceptions were thrown. To resolve this, when no active document is available, the first document will be marked as the active document.