Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

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.

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.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us