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-137352 · Issue 583664
Mobile app improvements for poor connectivity conditions
Resolved in Pega Version 8.5.1
When the mobile app was used in areas with poor data network connectivity, the screen was freezing or a number of sync errors were seen. Improvements have been made in the processing and wait conditions to smooth the functions when connectivity is intermittent.
INC-136057 · Issue 587164
Modal dialog close for date/time works as expected
Resolved in Pega Version 8.5.1
When a date/time property was used in a modal screenflow in Google Chrome, changing the date property on the pop up calendar and then clicking the modal close caused the screen to freeze. This was caused by the plf.handleModalClose() being called a second time for a container close event that was not available in window.event. This has been resolved.
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.