INC-186072 · Issue 677408
Updated ClientDynamicData HTML Rule
Resolved in Pega Version 8.5.6
After upgrading from Pega 7 to Pega 8, attempting to open an assignment on the staging environment showed a blank page. This was traced to the system trying to open a declare expression of "PegaComm-" class, and has been resolved by updating the pzClientDynamicData HTML Rule handling for the top level page and enabling the expression calculation checkbox in the Advanced tab of the pyCaseManger7 harness.
INC-186466 · Issue 670290
Style selector workaround added for Internet Explorer 11
Resolved in Pega Version 8.5.6
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-187196 · Issue 680747
Resolved Ajax popup alert for optimized iOS table
Resolved in Pega Version 8.5.6
When using an application on iOS with a section that contained at least 3 tables with 'optimize code allow' set to true, refreshing caused the error "AJAX request failed. Reason: communication failure" to be displayed. This has been resolved by adding an update which will skip the alert for the pzBuildFilterIcon activity when triggered from pzpega_ui_template_grid_helpers.
INC-187617 · Issue 692542
Added API for Pega Call Team websocket reconnect
Resolved in Pega Version 8.5.6
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 672776
Security enhanced for SmartTips
Resolved in Pega Version 8.5.6
Cross-site scripting protections have been updated for SmartTips.
INC-188029 · Issue 691101
Rich Text Editor will pause until instance is ready for interaction
Resolved in Pega Version 8.5.6
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 674103
Localization added for FilterUILabel
Resolved in Pega Version 8.5.6
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-189047 · Issue 674758
Session timeout adjusted for use with Apple Safari
Resolved in Pega Version 8.5.6
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 675958
Improved backwards compatibility for sendmail notifications
Resolved in Pega Version 8.5.6
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-189670 · Issue 688142
Dirty dialog harness handling updated for mobile
Resolved in Pega Version 8.5.6
A button configured with an "OnClick"->"Cancel" action presented the pyIsDirtyCheckConfirm modal when changes were made, but clicking the "OK" button then closed the modal and the mobile application displayed a blank screen that was only resolved by restarting the application. This has been resolved by ensuring the harnessID has been stamped on the dirty dialog.