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.
INC-189844 · Issue 673736
Scroll bar appears consistently
Resolved in Pega Version 8.6.3
The scroll bar was not consistently appearing beside the menus containing vertical overflow. This has been resolved by setting the correct max-height on the menu all the time.
INC-189935 · Issue 684505
Drag and Drop works as expected on mobile
Resolved in Pega Version 8.6.3
After opening a case assignment on a mobile device and selecting an option on the correct fields to make the drag and drop section visible, dragging the object vertically the caused the entire page to scroll up and down. Horizontal dragging worked as expected. This has been corrected.
INC-190609 · Issue 681325
Added null check for routeToParent in Mashup
Resolved in Pega Version 8.6.3
After update, mashup was loading in a different context. This has been resolved by adding a null check in routeToParent in webwb_pega_desktop_support.
INC-190708 · Issue 688134
Save works on Ajax container without Dynamic container
Resolved in Pega Version 8.6.3
After opening a work object and making changes to a required field, pressing the save button did not give any visual indication that the save was performed. Hitting cancel generated a dirty pop up saying changes will be discarded, indicating no save was done. When an Ajax container is configured without a Dynamic Container, all the content is rendered inside a fieldset tag instead of a form tag. While performing the save, the API was looking for the form element in the document and could not find any, and the save failed. This has been resolved by updating the submitWhenFail() API to handle both fieldset and form elements in the dom.
INC-190847 · Issue 676678
Preview link aligned under item
Resolved in Pega Version 8.6.3
The preview option was not showing below the link control configured to open the case, but instead was displayed elsewhere on the page. This was traced to changes made in Google Chrome v.93+, and has been corrected by changing the perspective to none instead of 0 so the link is displayed in the expected location.
INC-190901 · Issue 683842
Corrected datetime placeholder handling
Resolved in Pega Version 8.6.3
On desktop, date fields values selected were displayed in placeholder color instead of the black color. Date fields placeholders were not displayed in the offline mobile app. Before the refresh section call happened, the date selected color for the datetime input was black since the placeholder class was being removed from the span tag after selecting the date. After the refresh section calls, the Span tag which was generated for date time control was being appended with the placeholder class, which was an incorrect behavior. To resolve this, a check has been added which will only add the placeholder class if the datetime inputvalue is empty.