INC-187015 · Issue 678383
Listener implementation updated for closing modal dialog popup
Resolved in Pega Version 8.6.3
It was not possible to close the popup window in a local action when using a flow in a modal dialog action in Cosmos. This was traced to a missed use case for closing a modal dialog opened from a tertiary container, and has been resolved by updating the listener implementation in the ModalFlowTemplate.
INC-187617 · Issue 692544
Added API for Pega Call Team websocket reconnect
Resolved in Pega Version 8.6.3
When a call came in, the operator was not able to pick it up due to the popup only containing a reconnect section. This has been resolved by adding the disconnectAndReconnect API which will be used by Pega Call Team if the websocket reconnect limit exceeds 5.
INC-188001 · Issue 672777
Security enhanced for SmartTips
Resolved in Pega Version 8.6.3
Cross-site scripting protections have been updated for SmartTips.
INC-188029 · Issue 691102
Rich Text Editor will pause until instance is ready for interaction
Resolved in Pega Version 8.6.3
Outbound email was intermittently appearing blank creating replies using pyReply section. This was traced to the Rich Text Editor not loading completely before the interaction, and has been resolved by adding a brief pause that will temporarily disable the Rich Text Editor until the instance is ready.
INC-188212 · Issue 674105
Localization added for FilterUILabel
Resolved in Pega Version 8.6.3
Filter values were not rendered in French for French users for Case Status in all the grids. This has been resolved by updating the localization values in the pzFilterUiLabel control.
INC-188299 · Issue 677732
Focus corrected for dynamic layout in mobile
Resolved in Pega Version 8.6.3
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-188605 · Issue 673598
Missing property added for permission check on CanPerformAssignment Go button
Resolved in Pega Version 8.6.3
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.
INC-189047 · Issue 674760
Session timeout adjusted for use with Apple Safari
Resolved in Pega Version 8.6.3
A configured browser session logout timer was not working with the Apple Safari browser. This was traced to browser-specific handling for self.location.href and has been resolved by adjusting the logic and moving it inside a setTimeout to improve cross-browser compatibility.
INC-189214 · Issue 675960
Improved backwards compatibility for sendmail notifications
Resolved in Pega Version 8.6.3
After upgrading from Pega 7 to Pega 8, sendmail notifications were not working for email addresses that included the to-form "Lastname, Firstname'. This was caused by a difference in handling within the activity "@baseclass.SendEmailNotification", and has been resolved by shifting the reliance to InternetAddress.parse for validating and splitting email addresses in order to handle special characters, commas, and semi colons in display name.
INC-189748 · Issue 694739
Added API for Pega Call Team websocket reconnect
Resolved in Pega Version 8.6.3
When a call came in, the operator was not able to pick it up due to the popup only containing a reconnect section. This has been resolved by adding the disconnectAndReconnect API which will be used by Pega Call Team if the websocket reconnect limit exceeds 5.