INC-139849 · Issue 598127
Sorting icon visible for table in Cosmos on Google Chrome
Resolved in Pega Version 8.5.2
Tables were not showing any sort icon / indicator in the column header when using the Cosmos Theme in Google Chrome. This was only occurring in apps created with the Cosmos theme, and was caused by the sort icon for a non-optimized table using display flex, resulting in the position of the icon being displaced. This was a missed use case of having a non-optimized table in Cosmos, and has been resolved by removing the non-optimized-related CSS code.
INC-139966 · Issue 606841
JAWS announces popup error message
Resolved in Pega Version 8.5.2
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-140140 · Issue 595670
Multi Select populates values for Page group
Resolved in Pega Version 8.5.2
The Multi Select control was not populating values when Page group was chosen as a source. This has been resolved by updating control_multiselect and pzgetACdata to support page group source.
INC-140205 · Issue 595662
Safe check added for first element focus on inline table edit
Resolved in Pega Version 8.5.2
When moving the scrollbar when performing an inline edit of a hierarchical table, releasing the scrollbar caused it to move to the top of the table. This would continue until a refresh was performed. To resolve this, a safe check for focus first element method has been added.
INC-140848 · Issue 596461
Button row correctly added for click on exception list
Resolved in Pega Version 8.5.2
After upgrade, clicking on an exception list button in the mobile app was not adding a row to an existing PageList as expected. Investigation showed that pega.u.d.refreshSection was not executing correctly from RunScript, which was traced to a missed use case for handling an empty repeating dynamic layer in this scenario. This has been corrected.
INC-141099 · Issue 598131
Updated Cosmos confirm notification visibility conditions
Resolved in Pega Version 8.5.2
After routing an assignment to different operator, the current operator was still seeing the Go button in Cosmos for processing the assignment. Clicking on the button resulted in an error. To resolve this, the confirm notification section reload has been moved to a different context, and the visibility conditions have been updated to handle more use cases.
INC-141451 · Issue 601140
Radio button helper text is localized
Resolved in Pega Version 8.5.2
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-141499 · Issue 596067
Tooltip option for Label control visible
Resolved in Pega Version 8.5.2
After upgrade, the Tooltip option for the Label control in grids/tables was missing. Labels which had a tooltip before upgrade were working, but new fields could not add a tooltip. This was traced to a check for 'Run visibility condition on client' condition, and this has been removed for tooltip layout to resolve the issue.
INC-141789 · Issue 601052
PD4ML upgraded
Resolved in Pega Version 8.5.2
After upgrade, a functionality to generate letters in PDF format had an image size discrepancy between portrait and landscape mode. Investigation showed that the physical dimensions were not preserved by PD4ML v4.0.6; this has ben resolved by upgrading PD4ML to 4.0.9fx1.
INC-142034 · Issue 596086
Tab moves to next field after autocomplete
Resolved in Pega Version 8.5.2
After entering the value on an autocomplete field, it took two presses of the Tab key to move to the next field. Investigation showed that on autocomplete keydown of the tab key, there was an event preventing the expected default behavior. This has been resolved.