SR-D91656 · Issue 556864
Close button added to runtime exception error message display for non-tabbed layout
Resolved in Pega Version 8.4.2
While running the case through manager/user portal, a runtime exception caused the screen to reload with a GeneralFail harness to show the error and the stacktrace through the section GeneralFailDetails. Since the tabbed layout was not supported, it was not possible to close or cancel this case / case-id. This has been resolved by adding a close button to close the exception window.
SR-D91783 · Issue 556370
Corrected undefined class error during browser refresh
Resolved in Pega Version 8.4.2
After enabling a Report left navigation link for the CaseWorker portal, the browser refresh after opening a report from Report landing page was throwing the exception "Problem invoking function: pega_processengine_workutilities.pzHasAccessToWorkPool--(String), Undefined class "ReportBrowser"". This was a missed refresh usecase for ReportDefinition action in SPA portals after SPA was modified to use a separate thread for inner harness, and has been resolved by adding a condition to ensure the reportDefinition action also executes the displayOnPage action on browser refresh.
SR-D92571 · Issue 553117
Corrected ReportBrowser refresh section
Resolved in Pega Version 8.4.2
After bringing up the popup menu on a report shortcut in the report viewer and then dismissing it, the gear icon on the shortcuts in the upper section of the report browser stopped responding. This has been resolved by updating the system to refresh the pyReportBrowserInner section instead of pyReportBrowserAll.
SR-D92913 · Issue 553905
Aria-collapsed replaced with aria-expanded to improve accessibility
Resolved in Pega Version 8.4.2
Previously, the system used the aria-collapsed attribute for the left and right navigation toggling. In order to improve accessibility, this attribute has been changed to aria-expanded and the value will be set to true/false accordingly.
SR-D94331 · Issue 561970
Resolved PageCannotBeSerializedForPassivationException in logs
Resolved in Pega Version 8.4.2
The exception "One or more properties could not be serialized during passivation and have therefore been lost. They will not be available on activation. Please ensure that all property data is Serializable" was observed in the logs. Investigation showed there was an HTML fragment in 'pzGridOpenAction' that was adding non-serializable properties to the clip board. This did not cause a functional issue, but has been resolved by modifying the way the system obtains and reuses the class definition.
SR-D94700 · Issue 556020
Report group headers localized
Resolved in Pega Version 8.4.2
Localization has been added to report group headers.
SR-D95367 · Issue 560742
Expanded debug logging for exception blocks
Resolved in Pega Version 8.4.2
In order to enhance debugging, logging has been expanded to capture more detail on exception blocks.
SR-D95419 · Issue 563397
Updated Multiselect control behavior for incorrect value
Resolved in Pega Version 8.4.2
After upgrade, a difference in behavior was seen. Previously, when a user entered an incorrect value in a multi-select where the required field was checked and then clicked anywhere outside of the field, the value would erase before displaying the message "Value cannot be blank”. After upgrade, the value was not erased when the message was displayed, causing confusion. This has been resolved by adding logic which will determine the correct message to display, such as "Value cannot be blank" or "Please select a Valid Value".
SR-D96224 · Issue 556782
Validation error messages correctly cleared
Resolved in Pega Version 8.4.2
The error message on a checkbox field, radio button, or text area with a on-change post value was persisting even after the correct input was provided. This occurred when the area had a caption, and was due to an additional wrapper span that caused the error div to be the span's sibling instead of the span itself. In the post value success, the system checked whether the error div was present in the area's parent, i.e. span, and when no div was returned the error msg was not removed. It was possible to add an action 'Refresh this section' on change as a workaround, but this has been corrected by updating the system so that Instead of checking the error div in src.parentNode, it will access the correct parentNode using 'closest' and check for the error div.
SR-D96754 · Issue 560220
Column filtering corrected for Microsoft Internet Explorer 11 AJAX containers
Resolved in Pega Version 8.4.2
Column Filtering was failing when used in tables inside an AJAX container in Microsoft Internet Explorer 11. This was due to the filter popover close method changing the visibility of the popover and triggering a context switch, and has been resolved by setting the flag pega.ctxmgr.skipContextSwitching to true before changing the visibility.