INC-187617 · Issue 692543
Added API for Pega Call Team websocket reconnect
Resolved in Pega Version 8.7.1
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-188029 · Issue 691097
Rich Text Editor will pause until instance is ready for interaction
Resolved in Pega Version 8.7.1
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 674104
Localization added for FilterUILabel
Resolved in Pega Version 8.7.1
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-189748 · Issue 694737
Added API for Pega Call Team websocket reconnect
Resolved in Pega Version 8.7.1
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-189748 · Issue 701458
Websocket disconnect code logged
Resolved in Pega Version 8.7.1
An update has been added which will log the websocket disconnect code for additional diagnostic information.
INC-190609 · Issue 681324
Added null check for routeToParent in Mashup
Resolved in Pega Version 8.7.1
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 695488
Save works on Ajax container without Dynamic container
Resolved in Pega Version 8.7.1
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-191160 · Issue 685378
Empty caption value not shown in dropdown list
Resolved in Pega Version 8.7.1
An update has been made to template_dropdown to restrict an empty value from being added to the list.
INC-191785 · Issue 680930
Edit Validate Rule works after mobile section collapse
Resolved in Pega Version 8.7.1
It was possible to collapse a section of the UI on the mobile app and then proceed to the next page without entering valid data. This has been resolved by updating the validation condition to handle the mobile sections edit validate rule correctly.
INC-192813 · Issue 684735
Corrected unexpected page refresh
Resolved in Pega Version 8.7.1
When a value was changed in a section where the source of the section was defined as a property, the page refreshed without any announcement and focus was disrupted. Investigation showed this happened when using paragraph control where an anchor tag was used without any Name attribute. An update has been made to explicitly set the gFocusElement property after the processAdditionalFields activity to resolve this issue. Because the Name attribute is needed to query the particular element from the DOM to focus back, there were also intermittent issues when using the Microsoft Edge browser with Windows OS even after adding Name in the paragraph control link. A setTimeout has been added before focusing the element to resolve this.