INC-188299 · Issue 677731
Focus corrected for dynamic layout in mobile
Resolved in Pega Version 8.7
When any new item was added to a repeating dynamic layout in mobile or if the grid one of the items was expanded, the entire UI refreshed and the focus moved to the top. This has been resolved by adding a check for isMobileFullScreen.
INC-193947 · Issue 684137
Focus corrected for dynamic layout in mobile
Resolved in Pega Version 8.7
When any new item was added to a repeating dynamic layout in mobile or if the grid one of the items was expanded, the entire UI refreshed and the focus moved to the top. This has been resolved by adding a check for isMobileFullScreen.
INC-141099 · Issue 598131
Updated Cosmos confirm notification visibility conditions
Resolved in Pega Version 8.5.2
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-135523 · Issue 590435
Tab panel read meaningfully by screen readers
Resolved in Pega Version 8.5.2
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-171663 · Issue 655245
MashUp dynamic parameters article updated
Resolved in Pega Version 8.7
The documentation for MashUp best practices has been updated to clarify that dynamic parameters sent from the client side using "pega.web.api.setAuthenticationParameters" API will be sent as part of the query parameters and won't be part of the encrypted hash as this hash is generated on the server end while generating the mashup code in the mashup channel.
INC-181089 · Issue 667655
Corrected modal focus on assignment open
Resolved in Pega Version 8.7
After opening an assignment and using keyboard navigation, the focus was not set on the first focusable element as expected. Hitting "TAB" set focus to the second focusable element. This was traced to previous work done on focusing elements under the modal, and this has been resolved by removing the "document.activeElement.blur()" as it is no longer needed.
INC-181089 · Issue 673460
Corrected modal focus on assignment open
Resolved in Pega Version 8.7
After opening an assignment and using keyboard navigation, the focus was not set on the first focusable element as expected. Hitting "TAB" set focus to the second focusable element. This was traced to previous work done on focusing elements under the modal, and this has been resolved by removing the "document.activeElement.blur()" as it is no longer needed.
INC-171121 · Issue 648130
Filter popup persists correctly
Resolved in Pega Version 8.7
When the Apply filter option was selected for a table configured with a page list property as source, the filter popup appeared on the screen but disappeared after 3 to 4 seconds. This has been resolved by enabling the stretch for tabs option in the layout group.
INC-143310 · Issue 601205
Added scrolling for fixed size modal with buttons offscreen
Resolved in Pega Version 8.5.2
After upgrade, the modal format "Large Fixed" for the Modal Dialog in a local action was not working as expected when the screen was reduced in size. It as not possible to scroll down the modal dialog, and the "cancel" and "submit" buttons were no longer available. In standard modal, the cancel and submit buttons are always shown in the view port. When the modal is fixed format, the width and height of the modal are set to a fixed size. In that case, if the window is resized it is not possible to navigate to cancel and submit buttons that are offscreen. To resolve this, scroll has been added to allow accessing the cancel and submit buttons in case of fixed size modal that does not fit the window.
INC-193775 · Issue 686645
Action Sets in Sections working as expected
Resolved in Pega Version 8.7
When adding actions to a table, the action sets were not always saved correctly. Sometimes actions from one actions set were moved to a new action set without any event, which seemed to occur when there were multiple actions defined for each action set. This was traced to the open of the table property panel in the activity Embed-Harness-SectionBody-Grid.pzGridActionSets activity. This activity sets data for the action set display, including setting a “pyKeyCode” property. The “pyKeyCode” property is not set correctly in certain scenarios, causing the selected action/behavior to not be saved correctly. This has been resolved by changing the local param-pzGridActionSets: TempKeyCode to string.