INC-197358 · Issue 695309
Resolved finish assignment screen freeze
Resolved in Pega Version 8.6.3
In some assignments of several flows, when the processing was done (finish assignment) the screen only displayed the loading logo. The only way to proceed was by refreshing the browser. The browser console showed the error "Uncaught TypeError: Cannot read properties of null (reading 'undefined') at setTargetValuesSuccess (expression_calculation_1480665478.js!!.js:1) at k". The error did not occur when using Live UI privileges. This has been resolved by updating the expression calculation.
INC-197410 · Issue 690218
Handling added for invalid numeric range
Resolved in Pega Version 8.6.3
When filtering the range in number column with value as “1000000” , the validation message appeared as "1000000 : This results in an invalid numeric range". This has been resolved with an update to use Data-value to get the non-formatted value for decimal.
INC-197481 · Issue 695585
Accessibility improved for blank field errors in non-auto generated controls
Resolved in Pega Version 8.6.3
When using non-auto generated controls, leaving an edit field blank causes an error message informing that the value cannot be blank. An accessibility issue was seen where this error text was not part of the field label or description, preventing it from being announced by screen readers (NVDA or JAWS) when focus is on the field. This has been corrected by adding aria-describedby in non-template textarea.
INC-198021 · Issue 686632
Corrected blank areas on maximized view
Resolved in Pega Version 8.6.3
A blank section was displayed when maximizing the reply screen. Investigation showed that when the editor was inside a positioned container with overflow hidden and the editor had a scrollbar with its body height greater than the document, the scrollIntoView would scroll to grey spaces which were originally hidden by overflow. This has been resolved by commenting out scrollintoview, since it is not necessary and scroll position/cursor will be retained without it.
INC-198133 · Issue 693111
Data-test-id generated for table header
Resolved in Pega Version 8.6.3
After adding a table to the layout and putting labels on the table headers, the data-test-ids were not displayed in the generated DOM. This was traced to an issue where the test ID was not generated for the table headers, and has been resolved by updating GenerateCellContent to add data-test-id in markup.
INC-198484 · Issue 689006
Tab error message localized
Resolved in Pega Version 8.6.3
Localization has been added for the message that is shown at a tab when a section in tabbed layout contains errors.
INC-198601 · Issue 695498
Autocomplete value retained post refresh
Resolved in Pega Version 8.6.3
After update, including an autocomplete control in the UI configured as 'on change refresh this section' resulted in the selected value getting removed from the list after being selected. Investigation showed this could happen in a customized environment if Selected Autocomplete and associated Autocomplete fields had Refresh section configured. While removing the refresh conditions resolved the condition, this has been addressed by adding handling for this use case.
INC-198958 · Issue 691676
Scroll bar appears consistently
Resolved in Pega Version 8.6.3
The scroll bar was not consistently appearing beside the menus containing vertical overflow. This has been resolved by setting the correct max-height on the menu all the time.
INC-199043 · Issue 697069
Preview link aligned under item
Resolved in Pega Version 8.6.3
The preview option was not showing below the link control configured to open the case, but instead was displayed elsewhere on the page. This was traced to changes made in Google Chrome v.93+, and has been corrected by changing the perspective to none instead of 0 so the link is displayed in the expected location.
INC-199496 · Issue 690006
Corrected quotation mark handling for multi select
Resolved in Pega Version 8.6.3
After defining a source for multi select where the selectable list contained double quoted text, for example: Testing for "Double Quotes", the double quotes were converted to single quotes in the selection list. This caused the value Testing for "Double Quotes" to be displayed as Testing for 'Double Quotes'. This has been corrected.