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.
SR-D90459 · Issue 552661
Improved handling for attachments not using UTF-8 encoding
Resolved in Pega Version 8.2.7
When an email was received that used a charset encoding other than UTF-8, special characters in the HTML body were not displayed and instead the replacement character was shown. To resolve this, the system will read the encoding from the email rather than use the meta tag, and will add the attachment's HTML encoding information in Data-WorkAttach-File so that the same can be used to process and display the original HTML properly.
SR-D92688 · Issue 551340
Optional feature to improve pxETReport performance
Resolved in Pega Version 8.2.7
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.
INC-120326 · Issue 564435
Landing page refresh modified to avoid frequent reloads
Resolved in Pega Version 8.2.7
Approximately every two weeks, clients were able to login but it was not possible to work as the landing page refreshed constantly until all of the nodes were rebooted and the issue was cleared. Investigation indicated the frequent reloads were related to the cacheing of the operator details, and this has been resolved by updating the datapage reload strategy based on 'when' so frequent reloads will be avoided.
SR-D68572 · Issue 543003
Added check for duplicate attachment names with S3
Resolved in Pega Version 8.2.7
S3 Storage does not allow duplicate file names, but the AttachContent function was allowing duplicate file attachments. Due to this, the sync was failing to attach on the server and the message was never communicated to the client. This has been resolved by adding a check for duplicate file names when the storage is repository.
SR-D77580 · Issue 550093
Corrected Survey button refresh issue
Resolved in Pega Version 8.2.7
After implementing a Pega Survey question page with dynamic / reflexive questions (Answer to Question 1 determines Question 2 and so on) where every answer pick caused a refresh, picking various radio buttons quickly caused an unexpected busy indicator. Investigation showed that on click, both refresh section and run activity were executed asynchronously, triggering the property mapping refresh before answers were clicked. To correct this, the clearSelection function call in pzsurvey_ui_userscript JS file has been modified, and questionPageName has an added 'if' condition.
SR-D81500 · Issue 554903
Uploading Pulse attachments made more robust
Resolved in Pega Version 8.2.7
Upon uploading a file in the Pulse section for a case created in the Case Worker portal, the error message "File <filename> doesn't exist or is empty" appeared. This was traced to using a third-party repository when the network was slow, and has been resolved by instituting the use of callbacks/timeintervals to execute a particular function call only after getting proper results.