Skip to main content
circle-square
Outline Circle
square-square
Little Circle
square-square
Little Circle

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 SR ID number 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-147654 · Issue 642188

Updates to displaying embedded images in cases

Resolved in Pega Version 8.5.4

Sending an email with an embedded image to the email ID associated with the email listener successfully created the interaction case, but the embedded image was not displayed when the case was opened from the work-basket. A rule-not found exception was seen in the tracer for pyGetImageDisplay, the rule responsible for displaying the images in the ET pane. Investigation showed that when URLObfuscation was turned on, the decryption of the URL was not successful because "&" had been encoded to '& amp;'. This has been resolved by calling the activity pyGetImageForDisplay using URLMapping instead. An additional issue was seen with displaying images in the email interaction pane where the additional empty new lines moved the image outside the intended place. This was traced to a customization for the reply area which used the pyHighlightedMessage property and converted newlines to br tags even in HTML mode. To resolve this, pyHighlightedMessage has ben modified to convert newlines to br tags only if the mode is plain text.

INC-157214 · Issue 631599

Mentioned user in Pulse appears correctly

Resolved in Pega Version 8.5.4

When loading user names while using the "@" functionality in a Pulse post, adding or tagging the operator/user in Pulse by entering each letter brought up the list, but when using copy/paste it was not possible to select the desired value from the user.Suggestions list of operators/users. If by chance the user name was selected from the suggested list, the operator ID was added instead of the full name. This has been resolved.

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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us