INC-139156 · Issue 592150
Pasting image lands in correct location
Resolved in Pega Version 8.3.5
When pasting an image in a user story or issue, the image did not land where the cursor was placed in the contents of the issue or story. This was traced to the insert element handling for rich text editor, and has been resolved.
INC-132771 · Issue 584963
Refresh section of MultiSelect properly handles refresh section
Resolved in Pega Version 8.3.5
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-137785 · Issue 589064
Removed unneeded scroll bars on optimized table
Resolved in Pega Version 8.3.5
Horizontal and Vertical scroll bars were seen when using an optimized table in the Case Manager portal even when they were not needed. This was traced to the table having "overflow: auto" set, and has been resolved.
INC-132569 · Issue 595177
Resolved case detail overwrite
Resolved in Pega Version 8.3.5
In the interaction portal, when the same property (dropdown) was used to populate the details of sections in two cases, the first section (email case) details were replaced by the second section (outbound call case) details. Investigation showed that the refresh API was getting the reloadElement in the entire DOM based on the event target name property. To resolve this, updates have been made to use context DOM APIs to get the correct section.
INC-144600 · Issue 599916
Skip links enabled for all users by default
Resolved in Pega Version 8.3.5
In order to improve the UI experience, the isAccessible check for skiplinks has been removed. This allows users to navigate the content of the page using skip links without having to have their access group be set to accessible mode.
INC-142034 · Issue 596085
Tab moves to next field after autocomplete
Resolved in Pega Version 8.3.5
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-135523 · Issue 590437
Tab panel read meaningfully by screen readers
Resolved in Pega Version 8.3.5
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-139023 · Issue 591165
Tab will exit portal side menu
Resolved in Pega Version 8.3.5
It is expected that the Tab key will take users out of the portal menu and to the next focusable element, but on the side navigation menu both tab and arrow keys moved to the next menu item. This caused users to have to navigate the entire menu. The correct behavior was seen for the Navigation rule when called from an Action (for example on the button). This was traced to the system using tabindex as "0" for every element in the menu, and the tabs code has been updated to exit out of the menu bar when pressed.
INC-138354 · Issue 594356
Third party cookies reminder added for Mashup in incognito browsers
Resolved in Pega Version 8.3.5
When working in incognito/private browser windows, attempting to use Mashup displayed a message indicating login credentials were not recognized ("Unknown password and/or username"). This was due to recent changes originating with the browsers regarding blocking third-party cookies which are necessary for Mashup to run. For informational purposes, a new API has been added which will check for the PegaRules cookie; if the cookie is not present, the message "Third party cookies must be enabled for Mashup to function." will be displayed. This message may be customized by configuring the setting "pega.web.config.xCookiesDisabled" with the required message.
INC-133951 · Issue 584148
Try catch added for templated refresh when
Resolved in Pega Version 8.3.5
After configuring a refresh when condition on a dynamic layout triggered by changes on D_worklist.pxResults, a component stack mismatch error was generated if client side UI template is enabled. Without templatization it worked as expected. This has been resolved by adding a try catch block to DynamicLayoutGenerator.java.