INC-135523 · Issue 590436
Tab panel read meaningfully by screen readers
Resolved in Pega Version 8.6
When the tabPanel received focus with accessibility, the entire tab content was read instead of the W3 standard of only reading "Edit ". This has been resolved by ensuring the Tabpanel has the proper aria-labelledby.
INC-135992 · Issue 595355
Corrected Windows attaching file to incorrect case
Resolved in Pega Version 8.6
When using Microsoft Internet Explorer with Windows 10, opening multiple cases in multiple browser tabs and switching between the different cases created a condition where a file might be attached to the wrong case. This has been addressed by updating pzHarnessInlineScripts.
INC-136057 · Issue 587165
Modal dialog close for date/time works as expected
Resolved in Pega Version 8.6
When a date/time property was used in a modal screenflow in Chrome, changing the date property on the pop up calendar and then clicking the modal close caused the screen to freeze. This was caused by the plf.handleModalClose() being called a second time for a container close event that was not available in window.event. This has been resolved.
INC-136563 · Issue 607419
Tenant Switching updated
Resolved in Pega Version 8.6
When working on new “tenant switching” implementations in a multi-tenant environment, the API itself seemed to be working as expected (case details from another tenant were shown correctly in review mode), but clicking on the assignment unexpectedly opened the case in a new window that contained the same review view of the case rather than the perform view. Clicking the assignment link again caused yet another review window to open with the same issue, over and over. This has been resolved by adding a UI-side update to send the requests on proper sub-domain URL instead of using the parent domain, and by ensuring the document threads are properly deleted for multitenant usecases.
INC-136659 · Issue 593768
Template circumstancing works for report definitions
Resolved in Pega Version 8.6
On circumstancing the pyMyCasesReport using the Template option, it always displayed the base report definition instead of the circumstanced one when referenced the same report in the table in section. Because the grid component called two activities 'pxRetrieveReportData' and 'pxRetrieveReportMetadata' to render the table, the step page passed to these activities was from @baseclass. This caused the circumstanced template created in work- class to not get picked up. To resolve this, updates have been made to ensure the step page to the above activities will be of the report definition class.
INC-136793 · Issue 585604
Updates made to display busy indicator correctly in Google Chrome 84
Resolved in Pega Version 8.6
The Pega busy indicator was not displaying correctly in Google Chrome 84 due to changes in that browser. The needed updates have been made to adjust for these changes.
INC-137100 · Issue 604058
Added predictive text handler for Japanese on iOS
Resolved in Pega Version 8.6
The autocomplete function was not working well in MobileView when using Japanese IME on iOS. This has been resolved by adding a new input handler for IOS mobile, which will be triggered when predictive text is selected in mobile.
INC-137168 · Issue 588082
Documentation updated for Ajax container refresh
Resolved in Pega Version 8.6
The documentation for adding an Ajax container has been updated to reflect the proper configuration for adding a refresh within the container.
INC-137276 · Issue 585299
Arrow key navigation updates for layout grid tabs
Resolved in Pega Version 8.6
When a layout grid was configured as Tab mode, the up and down arrows allowed navigation between tabs. This has been modified to meet W3 standards of using left/right arrow keys to navigate between tabs and up/down arrow keys to scroll the page.
INC-137324 · Issue 584918
Corrected tabbing focus when modal flow has 'disable when'
Resolved in Pega Version 8.6
While tabbing through the modal dialog, focus moved to the background screen if there were custom flow action buttons that had a 'disable when' condition. This was caused by the last focusable element being a disabled element, and has been resolved by adding a disabled check in the getLastFocusableElement method that will determine whether element is disabled, and if so it will look for other elements as disabled elements can't be focused.