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-127591 · Issue 564820

isAuthenticated checks trimmed for Performance Improvement

Resolved in Pega Version 8.4.2

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

INC-127859 · Issue 564621

Email image retrieval switched to Lazy Load

Resolved in Pega Version 8.4.2

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 564728

Added check for redirects when getting images from S3

Resolved in Pega Version 8.4.2

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-128164 · Issue 567430

Resolved CommitError when trying to send email

Resolved in Pega Version 8.4.2

An error related to email was intermittently encountered while working on a case. This was traced to a local setting for Rule-ObJ class that set a read-only privilege, which appeared to have conflicted with the expected permissions around email template saving. This was an unexpected use case, and has been resolved.

SR-D87188 · Issue 551351

Mentioned user in Pulse correctly converted to hyperlink

Resolved in Pega Version 8.4.2

In the Interaction portal, mentioning a user in Pulse using @ was not converting the name to the user name with hyperlink for Email Interactions. @ mentions were working as as expected in Phone Interactions. This problem was introduced as part of using OWASP to sanitize HTML user input in Rich Text support, and was due to OWASP converting @ to an HTML entity. To resolve this, the @ will be excepted from HTML conversion.

SR-D87412 · Issue 563229

Support added for multi-language email parsing

Resolved in Pega Version 8.4.2

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-D92688 · Issue 551342

Optional feature to improve pxETReport performance

Resolved in Pega Version 8.4.2

Poor performance was seen when using pxETReport. This was caused by the system loading the recent cases widget by looking up all the ET cases within last 30 days, opening each ET case to check if it is from the same pyFrom email address, and then if yes, opening its related service case. On a complex system, this was potentially a slow process. To improve performance, the "Related cases" feature can now be disabled through an overridable 'when' rule.

SR-D93031 · Issue 555677

Calendar fields maintained after refresh

Resolved in Pega Version 8.4.2

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

INC-121460 · Issue 569118

IH Summaries correctly loads aggregated count

Resolved in Pega Version 8.4.2

After the IH Aggregated DataFlow has processed more than 34 million records from an Oracle database, the IH Fact table contained only ~120,000 records. Running a browse on the pxInteractionHistory DS resulted in an infinite loop. Investigation showed that this was caused by the handling of Oracle timestamps: using Pega DateTime in query parameters generated Oracle DATE instead of TIMESTAMP, causing all query parameters to be rounded to the second and interfering with the IH pre-aggregation. This has been resolved by updating the handling.

INC-122180 · Issue 563270

Null check added for Entity Extraction result

Resolved in Pega Version 8.4.2

Training data for an Entity Extraction model was not getting distributed correctly, as per the given % data. This was due to the result of the Entity Extraction result being null, and has been resolved by adding a check that will consider detected types as primary candidate for grouping if the result column is null.

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