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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

INC-136206 · Issue 584327

Handling added for Japanese characters in filename during Safari file upload

Resolved in Pega Version 8.5.1

When using the Safari browser, uploading a file containing Japanese characters resulted in an error message indicating the file was not found afterwards. This was caused by Safari not encoding the flename in the Form Data/Query String as part of the request for file upload, resulting in the filename not being decoded properly. To resolve this, a function named pzBrowserIsSafari has been added to check the browser, and if it is Safari, the system will normalize the filename.

INC-139074 · Issue 587811

Email handling security updated

Resolved in Pega Version 8.5.1

Cross-site scripting protections have been enhanced for email activities.

SR-D98224 · Issue 580594

Updated endpoint Cross-site scripting protection

Resolved in Pega Version 8.5.1

Cross-site scripting security has been updated for Endpoints in Display activities.

INC-134709 · Issue 579438

Updated endpoint Cross-site scripting protection

Resolved in Pega Version 8.5.1

Cross-site scripting security has been updated for Endpoints in Display activities.

INC-136264 · Issue 582472

Chatbot text starts scroll at top of answer

Resolved in Pega Version 8.5.1

In order to present an improved interface for customers interfacing with chatbots, the code has been updated so that the recipient's chat scroll will remain at the top of an answer that would scroll off the screen.

INC-139018 · Issue 587715

Rules updated to handle Outlook change that displayed multiple/duplicate email responses

Resolved in Pega Version 8.5.1

In Pega Email Triage case, all the replies were displayed along with the original email body, meaning for each and every reply, Pega showed the original email body and duplicated the data. This was traced to an update made by Microsoft in the Selector function of Outlook Windows, and has been resolved by updating the rules 'PyExtractLatestReplyFromHTML' and 'pyRichTextEmailHistorySelector' to work with this change.

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