INC-139966 · Issue 606844
JAWS announces popup error message
Resolved in Pega Version 8.4.4
When a form is submitted without giving value to required field, a browser pop up appears. The expected behavior is that the screen reader (JAWS) should move the focus to the field that has error and read the error message However, JAWS was not announcing the error "Value cannot be blank". This was traced to a scenario where if pega.u.d.fieldErrorType === "ERRORTEXT" is true, the class on the span within the error div will be set to "inputSpans", and this resulted in the return of an empty array for document.querySelectorAll("span.iconError.dynamic-icon-error"). To resolve this, support has been added for the "inputSpans" class.
INC-141302 · Issue 614993
UI automation script documentation update
Resolved in Pega Version 8.4.4
To provide a more consistent experience, explanatory comments in the code for UI automation scripts have been removed.
INC-141387 · Issue 612826
Autocomplete/autopopulate in table works properly with keyboard
Resolved in Pega Version 8.4.4
When two autocompletes in a table (two separate columns) were sourced by different properties within the same data-page, clicking to select a “reason-code” in the first autocomplete column correctly populated the corresponding “reason description” in the second column autocomplete. However, when using configured keyboard presses on the auto complete with post value and data transform actions (enter-key, tab-key, and on change), selecting from the auto-complete list and pressing enter or tab to select the item populated the second column as expected but the first column auto-complete showed the selected code for a moment and then was cleared. This as traced to the associated property set value executing after all associated properties setvalue actions were completed, and has been resolved.
INC-141451 · Issue 601141
Radio button helper text is localized
Resolved in Pega Version 8.4.4
The localized value from content was not being served for helper text in a radio button group. This has been resolved by adding the necessary localization support to the button template.
INC-142066 · Issue 600046
Dirty confirmation alert added for standalone Ajax container
Resolved in Pega Version 8.4.4
In the Pega CS interaction portal, an interaction could be launched to create a service in the Ajax container. If the same service was opened from the search results or the worklist, however, it was not prompted with the dirty popup message to save or discard the changes. This was a missed use case for a standalone Ajax Container, and has been resolved by adding a check to evaluate whether the document has an Ajax Container so the proper dirty state handling will be called.
INC-142214 · Issue 601790
Null Checks added for Null Dereference
Resolved in Pega Version 8.4.4
Null checks have been added to CSSAsJson and to the activeValue variable, which is used for the checked attribute generation.
INC-142557 · Issue 600532
Accessibility added to Recents
Resolved in Pega Version 8.4.4
Under all recent items, the work object was not opened when using the keyboard and the focus was on the work object. Clicking with the mouse worked. Investigation showed that on pressing the enter key, actions were not triggered because the action string was not on the same SPAN tag (but in child node). This has been resolved with an update to add tabindex on the same span where action-string is added. In addition, accessibility was not enabled on the out-of-the-box Recents table because the work object elements in the table used a formatted text control; this has been updated to use a link control which will enable the accessibility feature while using keyboard navigation.
INC-142557 · Issue 600529
Accessibility added to Recents
Resolved in Pega Version 8.4.4
Under all recent items, the work object was not opened when using the keyboard and the focus was on the work object. Clicking with the mouse worked. Investigation showed that on pressing the enter key, actions were not triggered because the action string was not on the same SPAN tag (but in child node). This has been resolved with an update to add tabindex on the same span where action-string is added. In addition, accessibility was not enabled on the out-of-the-box Recents table because the work object elements in the table used a formatted text control; this has been updated to use a link control which will enable the accessibility feature while using keyboard navigation.
INC-142564 · Issue 598698
Resolved issue with opening case in review mode
Resolved in Pega Version 8.4.4
After upgrade, using the Open in Review button from the Dashboard to view a case that the user did not have work entitlements on opened the case as expected, but the screen then immediately refreshed and redirected to the home screen. This was traced to the button configuration having an incorrect action set, with cancel action and then OpenWorkByHandle, and h as been resolved by updating the open in review button to remove the cancel action.
INC-143310 · Issue 601206
Added scrolling for fixed size modal with buttons offscreen
Resolved in Pega Version 8.4.4
After upgrade, the modal format "Large Fixed" for the Modal Dialog in a local action was not working as expected when the screen was reduced in size. It as not possible to scroll down the modal dialog, and the "cancel" and "submit" buttons were no longer available. In standard modal, the cancel and submit buttons are always shown in the view port. When the modal is fixed format, the width and height of the modal are set to a fixed size. In that case, if the window is resized it is not possible to navigate to cancel and submit buttons that are offscreen. To resolve this, scroll has been added to allow accessing the cancel and submit buttons in case of fixed size modal that does not fit the window.