INC-132771 · Issue 584962
MultiSelect properly handles refresh section
Resolved in Pega Version 8.6
On hitting tab or enter on a Multiselect control with "Post value" and "Refresh Section" enabled, focus moved to the header of the page when it refreshed. This has been resolved by updating the 'disable when' expression for "run on client" to better handle the input element used for enabling the controls.
INC-133576 · Issue 590326
Expandable Grid behavior corrected
Resolved in Pega Version 8.6
Expanding any row in master details was collapsing a previously expanded row. This has been corrected.
INC-133923 · Issue 600299
JAWS correctly reads headers of optimized tables
Resolved in Pega Version 8.6
Table column headers were not being read correctly with JAWS2020 and Google Chrome when using the "Tab" key to traverse the headers of an accessibility enabled application (PegaWAI ruleset included) that had an optimized table. This has been resolved by adding enhancements to enable keyboard navigation as per the WCAG standards of grid navigation for optimized tables.
INC-133944 · Issue 586017
Future DateTime Property picks operator time zone
Resolved in Pega Version 8.6
When selecting the DateTime in a property field configured to accept future data input, the input failed validation due to the DateTime field being compared with the System time zone (IST instead of the operator time zone. This has been resolved by adding a condition to honor the operator time zone in isFutureDate validation, and to fall back to the browser time zone if necessary.
INC-133978 · Issue 587699
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.
INC-134634 · Issue 584947
FSM Mobile app correctly starts phone call after closing Google
Resolved in Pega Version 8.6
When two controls were configured in the FSM Mobile app, one for Get Directions and one to handle a phone call, clicking on the phone call control worked correctly when it was used first, but clicking on the Get Directions control and opening and closing Google Maps before clicking on the Phone call control caused the phone call control to not work. Investigation showed that after the Get Directions control was used, the # in the href attribute was automatically prepended with window.location. To resolve this, a check has been added that will compare the attribute with the completely formed {URL}# so that entire window.location will not be prepended.
INC-134891 · Issue 589870
Logoff set to use root context
Resolved in Pega Version 8.6
The thread name was changing from Standard to DSCPA_DemoStudio on click of log-off, resulting in unexpected behavior if the user logged in again. To resolve this, an update has been made to trigger logoff in root context.
INC-134893 · Issue 587170
Added check for localeDb properties in dateTimeUtils
Resolved in Pega Version 8.6
On click of the Approval/Finish assignment submit button, a blank screen appeared and no further progress could be made. This was traced to an issue with the operator locale not being properly set by the html fragments that initialize the locale for use in dateTimeUtils. This has been resolved by adding a check for properties in the localeDb object.
INC-135181 · Issue 597423
Clipboard handling updated to accommodate custom Cosmos portal
Resolved in Pega Version 8.6
After upgrading and moving to Theme-Cosmos, a browser-level refresh on the user portal was not remaining on the same screen that issued the refresh, but rather on the default screen of the user portal. This was traced to a difference in clipboard handling of the Body parameter value for strJSON that was exposed through a customized Cosmos User Portal where Ajax Container was not used but still present in DOM. In order to support this use case, the tab_support file in sendReqToUpdateClipboard method has been updated.
INC-135285 · Issue 586133
ProcessMerge activity handling updated for auto-populate
Resolved in Pega Version 8.6
If a flow action had auto populates and declaratives configured in it, merging back to pyWorkPage in the main page was not working correctly due to the method used for accessing the base page from the flow in a modal thread. This has been resolved by updating the handling for this process.