INC-183995 · Issue 673789
Corrected accessibility for action menu button
Resolved in Pega Version 8.7
When using JAWS with Google Chrome or NVDA with Microsoft Edge, the action menu button label was announced twice, as 'Case Action Menu button' and 'Action Menu button', and it required two tab key presses to set focus on the Action menu button from the Follow button. This has been resolved by removing the role type as component/widget and keeping the label as "case wide actions" so that after the focus from the icons, the focus is correctly set on the action buttons.
INC-169203 · Issue 646097
Robotics Desktop Automation correctly runs on subsequent tabs
Resolved in Pega Version 8.7
When using Customer Service (CRM) to call Robotics Desktop Automation (RDA) from a data page, closing the first interaction tab after the RDA automation was completed resulted in the automation not being triggered for the second tab. If the first tab was not closed, the automation on the second worked as expected. Investigation showed the attachOnUnload was unregistering the client actions for all the open tabs and the attachOnLoad was not being called on reload. This has been resolved by updating attachOnLoad so it is now called with InvokeOnReload as 'true' to register client action for the tab in focus.
INC-167611 · Issue 652468
Business users can move dashboard widgets on production portal pages
Resolved in Pega Version 8.7
Business users were not able to use "Edit dashboard" to move dashboard widgets in production portal pages. This was a missed use case of using an operator with different security level, and has been resolved by using the control pzUserDashboardIncludeScript instead of including pzpega_dashboard script directly in the UserPortal harness.
INC-138354 · Issue 594353
Third party cookies reminder added for Mashup in incognito browsers
Resolved in Pega Version 8.5.2
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-195363 · Issue 690043
Accessibility improvements for Cosmos
Resolved in Pega Version 8.7
After update, some UI changes were seen in Cosmos that could impact accessibility. These included the left panel for the portal can be folded, but the arrow/Icon to fold this pane shows only when you hover over with it with the mouse; on the same portal, Submit and Cancel buttons are displayed at the bottom of the screen as a sticky menu over the long form instead of the previous behavior of being at the bottom of the form; and that the sticky menu partially covered the bottom of the form's functionality. These have been resolved by updating the selectors to make the collapsible icon accessible using keyboard and by removing the sticky behavior for the case action area buttons in the perform harness.
INC-136563 · Issue 607418
Tenant Switching updated
Resolved in Pega Version 8.5.2
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-143005 · Issue 596957
Fluid Overlay displays as expected in Firefox
Resolved in Pega Version 8.5.2
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-164012 · Issue 640039
Source edit with formatting resumes process automatically
Resolved in Pega Version 8.7
When opening a paragraph rule and clicking on Actions > checkout out to branch, the rule refreshed and the modal never appeared to allow the selection of a branch on the current application. This was an inadvertent side effect of work done to resume the event queue if it was paused when applying styles, and has been resolved by modifying the work so it resumes the action sequence only when source mode is initialized in the Rich Text Editor.
INC-142214 · Issue 598766
Null Checks added for Null Dereference
Resolved in Pega Version 8.5.2
Null checks have been added to CSSAsJson and to the activeValue variable, which is used for the checked attribute generation.
INC-188605 · Issue 673597
Missing property added for permission check on CanPerformAssignment Go button
Resolved in Pega Version 8.7
With the introduction of the pzCanPerformAssignment When Rule to control the visibility of the Go button in the Assignment lists, the context for checks is now within the D_CaseAssigments Data Page. One of the checks executed by this When Rule is performed by the function @pzCanPerformAssignment() which calls an API to examine the RARO configuration for the Assignment Class in question. When the Read permission is controlled by the canPerform Access When Rule, a function is called which relies on the presence of the .pxRefObjectClass to check the privileges; In the new D_CaseAssignments Data Page the .pxRefObjectClass was not mapped during construction and as such the value for workClass passed to the API method was "" meaning the relevant checks were not executed. This has been resolved by adding the missing property pxRefObjectClass that is needed for execution permission checking.