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-159836 · Issue 631206

Upgraded Apache UIMA Ruta libraries to resolve memory leak

Resolved in Pega Version 8.6.2

A memory leak issue that resulted in a reboot being needed every few days was traced to the class org.apache.uima.ruta.rule.RuleMatch. This has been resolved by upgrading the Apache UIMA Ruta libraries to v2.8.1.

INC-121435 · Issue 563875

Handling added for null requiredskillcount on assignment

Resolved in Pega Version 8.2.7

If the property pxRequiredSkillCount was blank on an assignment when moved to a workbasket, it was never presented for Get Next Work. To resolve this, handling has been added which will change the null to 0 so the assignment is properly queued.

INC-122149 · Issue 562783

Corrected approval step task message

Resolved in Pega Version 8.2.7

When a case progressed to the approval step, the task name did not properly appear as part of the "Please approve or reject this" message. In another scenario, a portal which supported locale switching was not translating "Please approve or reject this" when the locale was switched, but instead displayed the message in the original language. Investigation traced this to the pzInstructionsForApproval data transform storing the localized field value, causing it to persist inappropriately. This has been resolved.

INC-127077 · Issue 564107

Busy indicator appears when uploading via Select

Resolved in Pega Version 8.2.7

After update, the “loading symbol” (busy indicator) was not appearing while uploading large attachments using the Select button. This was a missed use case in recent changes to related to AsyncUpload, and has been resolved.

SR-D76291 · Issue 547840

Updated retry logic for S3 AddAttachmentFromEmail

Resolved in Pega Version 8.2.7

When using the AddAttachmentFromEmail activity with S3 repositories, performing an obj-save on the data-workattach-file page executes a deferred save while also saving the file into the repository. if the data was inserted into S3 successfully but encountered an issue when saving the related data-work-attach-file page, the system was trying to call the save operation again. This tried to insert the duplicate attachment again to S3, causing an error on that side of the process. To resolve this, the duplicate Obj-Save functionality in AddAttachmentFromMail Activity has been removed.

SR-D92352 · Issue 553616

Completed onChange will reset FileInput value to null

Resolved in Pega Version 8.2.7

When attaching a file using the "Select File" button, it was not possible to attach the same file after deleting it. Re-attaching the file worked as expected when using Drag and Drop. Investigation showed that the onchange event occurred only when the value of an element was changed, so in this case trying to attach the same file did not change the value of the element and did not fire the onchange. To resolve this, the value of FileInput in pzMultiFilePath Control will be set to null at the end of the onChange event so that an onChange event will be triggered next time even if the same file is added.

INC-127591 · Issue 564818

isAuthenticated checks trimmed for Performance Improvement

Resolved in Pega Version 8.2.7

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

INC-127859 · Issue 564619

Email image retrieval switched to Lazy Load

Resolved in Pega Version 8.2.7

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 564726

Added check for redirects when getting images from S3

Resolved in Pega Version 8.2.7

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.

SR-D87412 · Issue 563227

Support added for multi-language email parsing

Resolved in Pega Version 8.2.7

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.

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