SR-D87019 · Issue 561909
Required attribute of the layout label considered for displaying "*" on the button
Resolved in Pega Version 8.4.2
After upgrade, radio buttons with a “required” when condition did not have that condition triggered. This was traced to validation only being applied to the first row when using a repeating dynamic layout. Because of this, if the first row 'when' rule is false and subsequent rows 'when' rule is true, the validationType='' attribute is stamped for all rows as first row when rule is false. To resolve this, logic updates have been made which will stamp a button's required attribute for showing the '*' symbol based on the required attribute of the layout label.
SR-D87203 · Issue 550996
Required field accessibility improved
Resolved in Pega Version 8.4.2
In some instances, there is no non-visual indicator that a field is required. Because the asterisk character is commonly ignored by screen readers, the attribute or should be used so that non-sighted users have explicit information about the required status of the field. To enable this, when client-side validations are disabled on the harness and clientValidation attributes are absent, the system will run an additional check so that aria-required is added.
SR-D89242 · Issue 555590
Corrected layout refresh for grid state page
Resolved in Pega Version 8.4.2
When the condition builder had an empty row, on submit an error was displayed as expected. However, attempting to delete the empty row resulted in an exception. Investigation showed that the layout refresh was causing the grid state page to get deleted upon submission of the modal. This has been resolved.
SR-D89672 · Issue 550527
Custom error label styles work for 'required'
Resolved in Pega Version 8.4.2
When using the default 'required' error message, the class "labelError" is added when the required field is empty. However, when the default 'required' is replaced by a custom error message, a UI error was seen because the class "labelError" was not added when the field was empty. This was traced to an error in the non-template to template code transform, and has been resolved by updating webwb_pzpega_ui_dlcelltemplate_js to add the labelError class based on the presence of an error message.
SR-D90711 · Issue 553092
Portal harness maintained when opening email link
Resolved in Pega Version 8.4.2
When an email link was opened (pxOpenAssignmentLink), the portal harness was replaced with the case Perform harness. This has been resolved by ensuring the 'flex' CSS class is added for the portal harness div when using pyMobileSnapStart and a top navigation portal.
SR-D91344 · Issue 560628
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-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.