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.

INC-127591 · Issue 564817

isAuthenticated checks trimmed for Performance Improvement

Resolved in Pega Version 8.3.4

In order to improve performance, a duplicate check of pxIsRepositoryAuthenticated has been removed from the Function Rule.

INC-127859 · Issue 564618

Email image retrieval switched to Lazy Load

Resolved in Pega Version 8.3.4

In email, multiple images being loaded at once resulted in a performance impact. To resolve this, the fetching of inline images has been modified to use Lazy Load optimization which will retrieve file content from S3 storage on a need basis.

INC-127891 · Issue 564725

Added check for redirects when getting images from S3

Resolved in Pega Version 8.3.4

When retrieving images from S3 storage, a 303 redirect status response code was shown. Investigation showed that using a public URL caused the redirects, and this has been resolved by adding an AG hash while fetching images via an activity.

INC-132866 · Issue 583775

Email images correctly displayed in interaction

Resolved in Pega Version 8.3.4

If the email listener was configured with "Embed data for inline images into HTML" turned on, images were not displayed. If configured with that setting turned off, images were displayed and additionally added as attachments to the interaction, which is not desired behavior. This has been resolved by adding a 'when' rule to pyPostEmailContent which will not let inline images be displayed as attachments in the interaction case UI.

INC-133026 · Issue 578279

Updated Pulse email attachment handling

Resolved in Pega Version 8.3.4

After updating from 8.3.2 to 8.3.3, the Audit Trail displayed the entire contents of an email. In some instances, attaching a .txt file caused the file extension to be displayed twice. This was due to pyNote being used to create email file posts, and has been resolved by updating the implementation to use pyEmail instead of pyNote. Backward compatibility has been ensured by still considering pyNote for older emails and changing when emails open.

INC-136264 · Issue 582471

Chatbot text starts scroll at top of answer

Resolved in Pega Version 8.3.4

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.

SR-D87412 · Issue 563226

Support added for multi-language email parsing

Resolved in Pega Version 8.3.4

Parsing an email body for different languages was causing performance issues. To resolve this, an enhancement has been added to support email IVA in seven languages; to use this, override the Work-Channel-Triage.pyParseReplyMail activity and add the required languages in the given parameter.

SR-D93031 · Issue 555675

Calendar fields maintained after refresh

Resolved in Pega Version 8.3.4

Calendar fields were not displaying in PegaChat after the browser was refreshed. This has been resolved.

INC-133026 · Issue 578278

Updated Pulse email attachment handling

Resolved in Pega Version 8.4.3

After updating from 8.3.2 to 8.3.3, the Audit Trail displayed the entire contents of an email. In some instances, attaching a .txt file caused the file extension to be displayed twice. This was due to pyNote being used to create email file posts, and has been resolved by updating the implementation to use pyEmail instead of pyNote. Backward compatibility has been ensured by still considering pyNote for older emails and changing when emails open.

INC-136264 · Issue 582470

Chatbot text starts scroll at top of answer

Resolved in Pega Version 8.4.3

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.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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