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.
INC-189748 · Issue 701456
Websocket disconnect code logged
Resolved in Pega Version 8.5.6
An update has been added which will log the websocket disconnect code for additional diagnostic information.
INC-189748 · Issue 694738
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-189935 · Issue 684503
Drag and Drop works as expected on mobile
Resolved in Pega Version 8.5.6
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-190233 · Issue 675484
Production check removed for Get Action Details API
Resolved in Pega Version 8.5.6
After creating an assignment for a case and calling the Get Action Details Applied Assignment API, the name tag for views was not included in the returned JSON. This has been resolved by removing a check for production level.
INC-190708 · Issue 688133
Save works on Ajax container without Dynamic container
Resolved in Pega Version 8.5.6
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-190901 · Issue 683840
Corrected datetime placeholder handling
Resolved in Pega Version 8.5.6
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.
INC-191674 · Issue 681575
Cosmos Stakeholders menu updated to prevent loss of work party change
Resolved in Pega Version 8.5.6
The Stakeholders menu for adding work parties to cases available in Cosmos Utility panel was not saving work party changes as expected when the case was also open for performing assignments. When the assignment was completed, the work parties were reset to the values present when the case was opened. The list of stakeholders is saved as a property in work page. When an assignment is opened there are two threads, and any stakeholder added is then added only in the first thread. Because it was not added in the second thread (acprimary Ajax container - processing assignment) the stakeholder addition was lost due to the second thread overriding the first thread. To resolve this, if an assignment is being processed while trying to open the stakeholders model, an additional modal will be displayed with the following options: - resign from opening stakeholders modal and continue process assignment or, - rresign from processing assignment (all unsaved changes will be discarded) and open stakeholders modal
INC-191785 · Issue 680929
Edit Validate Rule works after mobile section collapse
Resolved in Pega Version 8.5.6
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.