INC-186466 · Issue 670292
Style selector workaround added for Internet Explorer 11
Resolved in Pega Version 8.7
When using UI-Kit 15.0.1 with Microsoft Internet Explorer 11, the responsive behavior of the left navigator was not working as expected, it was not possible to Customize/Style the File Path control completely, and the AutoComplete control and Date Time Controls had a blue border on hover/focus. This was traced to the styles not being correctly selected because they contained the selector "focus-within" which is not supported in this browser. This has been resolved by adding focus-within separately so Internet Explorer will ignore the selector.
INC-187039 · Issue 678865
Handling added for decoding file names containing umlauts
Resolved in Pega Version 8.7
Two issues were seen with file names that contained an umlaut: When sending file with an umlaut in the name via PegaCHAT, the error "Failed to load resource: the server responded with a status of 404 (404)" appeared on the Client side and a preview was generated. On the Agent side, the message was sent but attempting to open it resulted in an error that the file did not exist. This was traced to the unescape javascript API returning the wrong decoded values if the encoded value of an umlaut character was sent, and has been resolved by adding a safe check to avoid a malformed URI. Second, an image was not displayed in the Rich Text Editor if the image name contained the ä or Ä character in it. Investigation showed the activity parameters were being changed when it was invoked from the script. If the file name sent was "aysnÄ1626292145235.png" it was encoded to "aysn%C3%841626292145235.png" as expected, but when the parameter was passed to the Activity the value further changed to "aysn%C3%83%C2%841626292145235.png", causing the file open failure because the names did not match. To resolve this, code has been added which will correctly decode the encoded values of umlaut characters.
INC-187082 · Issue 668973
PDF generation corrected
Resolved in Pega Version 8.7
Issues with PDF generation have been resolved by upgrading the PD4ML libraries to version 4.0.9fx5.
INC-187378 · Issue 670550
Scrolling fixed for moving rows in tables
Resolved in Pega Version 8.7
After update from Pega 8.4 to Pega 8.6, attempting to move a row on the top to bottom was not working correctly due to the scroll being limited. Moving an item higher worked as expected. Investigation showed if the container format of the grid was None a condition was setting the scroll to top even if it was being scrolled down, and this has been resolved by getting the gridOffsetTop value from the closest table tag and increasing the setInterval time to achieve smooth scroll behavior.
INC-188001 · Issue 672775
Security enhanced for SmartTips
Resolved in Pega Version 8.7
Cross-site scripting protections have been updated for SmartTips.
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-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.
INC-189047 · Issue 674759
Session timeout adjusted for use with Apple Safari
Resolved in Pega Version 8.7
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 675959
Improved backwards compatibility for sendmail notifications
Resolved in Pega Version 8.7
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-189935 · Issue 684504
Drag and Drop works as expected on mobile
Resolved in Pega Version 8.7
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.