INC-153109 · Issue 611354
Validation error messages correctly cleared in nested markup
Resolved in Pega Version 8.4.4
A UI Freeze issue was seen whenever mandatory input was missed and the form was submitted. Continuing was possible after browser refresh, but a new Next>> button appeared. This was an unintended side effect of work done to correctly clear validation messages when areas had captions, and has been resolved by modifying that work so it performs as expected on nested markup.
INC-153152 · Issue 613685
Privilege on table cells updated for non-template mode
Resolved in Pega Version 8.4.4
When using a table sourced from a report definition where certain cells were hidden or shown based on privilege, the configuration worked as expected in regular tables but did not work correctly for optimized tables. This was traced to an issue with image control rendering in non-template mode related to privileges for the image, and has been resolved by updating the pzgenerateicon Rule-Utility-Function.
INC-153415 · Issue 616711
On click outside grid record will be saved
Resolved in Pega Version 8.4.4
When a record was added by copying a previous record, the new record was not saved if there was a click outside the grid. This has been resolved.
INC-153537 · Issue 614847
Corrected popup placement for Microsoft Edge browser
Resolved in Pega Version 8.4.4
Autocomplete, date control and SmartInfo pop-ups were not displayed correctly when using the Edge browser. This was due to Javascript behavior differences with that browser, and has been resolved by updating the system to ignore the scrolltop if browser is Microsoft Edge.
INC-153550 · Issue 614989
Cross-site scripting protection update
Resolved in Pega Version 8.4.4
Cross-site scripting protections have been updated for labels.
INC-153555 · Issue 612228
Validation error messages correctly cleared in nested markup
Resolved in Pega Version 8.4.4
A UI Freeze issue was seen whenever mandatory input was missed and the form was submitted. Continuing was possible after browser refresh, but a new Next>> button appeared. This was an unintended side effect of work done to correctly clear validation messages when areas had captions, and has been resolved by modifying that work so it performs as expected on nested markup.
INC-153721 · Issue 613661
Visual natural labels exposed to JAWS in REST wizard
Resolved in Pega Version 8.4.4
Get/Post/Put/Patch/Delete checkboxes were not properly read by the REST Integration Wizard when when tabbing through the checkboxes with JAWS enabled. When tabbing to each, “Tab – Select this method if it is supported at the endpoint” was read for each checkbox, and no information was given regarding what method each checkbox was for. When any helper text is configured, an aria-label attribute with helpertext message is generated. This aria-label will override any other native labeling mechanism (label - id mechanism), which is this case caused the control label to not be announced. To resolve this, the system will remove the aria-label attribute when helper text is configured and will add the helpertext div ID in aria-describedby for accessibility.
INC-153783 · Issue 612993
Cross-site scripting protection update
Resolved in Pega Version 8.4.4
Cross-site scripting protections have been updated for labels.
INC-154205 · Issue 618735
Corrected wrap text for Cosmos radio buttons
Resolved in Pega Version 8.4.4
When using Cosmos, radio buttons with large labels were displayed with the text overlapping even when wrap text was enabled and the radio button placement was incorrect. This was traced to a height of 32px being set as the default, overriding the wrap text setting, and has been resolved by adding CSS to set the height as auto when wrap text on radio label is used.
INC-154458 · Issue 620211
Calendar picker placement corrected for Ajax container
Resolved in Pega Version 8.4.4
When using inline edit and clicking date picker, the calendar popover was displayed in a blank space away from the position of the date picker. This was due to a popover inside a screenlayout having scrolltop and scrollleft values added to the popover position; in the case of an Ajax container these values resulted in incorrect position of a popover. To resolve this, adding the scrolltop and scrollleft will be bypassed if the element where the popover is attached is inside a Ajax Container.