INC-140205 · Issue 595661
Safe check added for first element focus on inline table edit
Resolved in Pega Version 8.6
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-140289 · Issue 589004
Check added to preserve clipboard pages for pop-up
Resolved in Pega Version 8.6
Many properties were missing in the clipboard after launching an ImageViewer. This was traced to the clipboard pages being deleted in the pop-up mode, and has been resolved by adding a check to not delete pages in case of pop-up opened from top navigation case.
INC-140848 · Issue 596460
Button row correctly added for click on exception list
Resolved in Pega Version 8.6
After upgrade, clicking on an exception list button in the mobile app was not adding a row to an existing Page List 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 598130
Updated Cosmos confirm notification visibility conditions
Resolved in Pega Version 8.6
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-141302 · Issue 614992
UI automation script documentation update
Resolved in Pega Version 8.6
To provide a more consistent experience, explanatory comments in the code for UI automation scripts have been removed.
INC-141387 · Issue 612825
Autocomplete/autopopulate in table works properly with keyboard
Resolved in Pega Version 8.6
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 595435
Radio button helper text is localized
Resolved in Pega Version 8.6
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 596066
Tooltip option for Label control visible
Resolved in Pega Version 8.6
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-142034 · Issue 596084
Tab moves to next field after autocomplete
Resolved in Pega Version 8.6
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.
INC-142066 · Issue 600044
Dirty confirmation alert added for standalone Ajax container
Resolved in Pega Version 8.6
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.