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.
INC-142214 · Issue 598765
Null Checks added for Null Dereference
Resolved in Pega Version 8.6
Null checks have been added to CSSAsJson and to the activeValue variable, which is used for the checked attribute generation.
INC-142452 · Issue 595039
Resolved error in personalized table
Resolved in Pega Version 8.6
After creating a section and adding a table, checking the personalization option in the table properties and clicking refresh caused the UI to become unresponsive. This was traced to a missing check in the template that was needed before accessing the busy indicator, and has been resolved.
INC-142557 · Issue 600527
Accessibility added to Recents
Resolved in Pega Version 8.6
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 598696
Resolved issue with opening case in review mode
Resolved in Pega Version 8.6
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-142589 · Issue 595490
Corrected tooltip evaluation for multiselect
Resolved in Pega Version 8.6
After adding help text for a multiselect help icon with overlay on hover field, the value was not being sourced. Changing to a different type of help text or control type worked as expected. This was due to an error in case sensitivity, using pyToolTip when it should have been pyTooltip, and has been corrected.
INC-142714 · Issue 596555
Recent Cases from different applications available to open
Resolved in Pega Version 8.6
An enhancement has been added which will allow opening other application assignments in the Recent Cases section of the current application when the user has access to multiple applications.
INC-143005 · Issue 596955
Fluid Overlay displays as expected in Firefox
Resolved in Pega Version 8.6
After upgrade, using the Overlay format "Fluid" to perform the screening matches task in CLM using Firefox had an overlay that covered the entire screen but was missing the scrollbar to manage the content. This has been resolved by adding changes to support dynamic content (with scrollbar) for center overlay.
INC-143260 · Issue 599302
Overlapping columns fixed in ReportViewer
Resolved in Pega Version 8.6
When Report Viewer was used for Report Definition, displaying it on dashboard columns resulted in columns that overlapped each other. This was traced to a resize issue related to the scrolling checkbox and has been resolved.