INC-184104 · Issue 682355
Cosmos Report Browser list updates during current session
Resolved in Pega Version 8.5.6
The Cosmos Report Browser list section was using a cached list of reports that did not update to reflect created or deleted reports until after logout and new login. This has been resolved by adding the pzInvalidateRBDataPages activity for harness initialization to update the reports list during the current session.
INC-184109 · Issue 671192
Handling updated for customDateTime formatting
Resolved in Pega Version 8.5.6
When a feature date was entered, for example as 2021/07/29 12:00:00 AM, changing any other property caused the time to be off by 4 hours and display as 2021/07/28 08:00:00 PM. Investigation showed this was caused by the parameters being passed in an incorrect order while calling pega.ui.Formatter.formatDateTime() in combination with customTimeZone, and has been resolved.
INC-185563 · Issue 670845
"Manage content" dialog box tab index is consistent
Resolved in Pega Version 8.5.6
The tab ordering for the "Manage content" (document upload) dialog box was not consistent. This has been resolved by updating pzModalTemplate to list the submit, cancel, etc, buttons in a consistent order.
INC-185782 · Issue 675528
Tab Names correctly displayed in Ajax Container
Resolved in Pega Version 8.5.6
After configuring Action Set with an Ajax container to open a harness and then configuring the same harness name for multiple action items, the first open happened as expected but the following action items were not opening properly and were still pointing to the old tab instead of showing the new tab names. This was traced to actionMetadata.Name not having the correct value, and has been resolved by explicitly updating the tabName value in the "Display" action with the needed actionMetadata.Name.
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.