SR-B44278 · Issue 302830
MT guide updated for rules blocking/restriction
Resolved in Pega Version 7.3
The MultiTenant guide has been updated to clarify what causes rules to be blocked or restricted and the possible consequences of unrestricting rules.
SR-B48780 · Issue 305215
Oracle/Unix documentation updated with JDBC instructions for urandom instead of random
Resolved in Pega Version 7.3
The Install/Upgrade guides have been updated to reflect that recent changes to Oracle have created the requirement of forcing the JDBC driver to use /dev/urandom instead of /dev/random to improve security as well as connection open and close performance. The guide now recommends customers running Oracle on Unix do one of the following: 1. Update $JAVA_HOME/jre/lib/security/java.security to use securerandom.source=file:/dev/./urandom 2. Set system property -Djava.security.egd=file:///dev/urandom
SR-B8847 · Issue 278000
FCM/FCMR documentation updated
Resolved in Pega Version 7.3
The documentation on the PDN for installing and configuring FCM 7.12 has been updated for FCM and FCMR.
SR-B8898 · Issue 279449
Reference to outdated property removed
Resolved in Pega Version 7.3
When building a system with WebSphere 8.5.5, DB2 10.5fp7 and Java 8, creating the environment and testing the connection on its datasource produced the warning: "DSRA8200W: DataSource Configuration: DSRA8020E: Warning: The property 'progressiveLocators' does not exist.". This was traced to a code fragment left after that property became unsupported which has now been removed.
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.