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-142930 · Issue 600770
Email history will be stripped from case replies
Resolved in Pega Version 8.4.4
When sending an email reply to a case, the entire email history (all previous emails in the email chain) was attached to the case as part of the reply.To resolve this, updates have been made so the system will strip history only when it's a follow-up mail. In addition, an issue with duplicate attachments has been corrected, and attachments from trailing mail will not be copied to a new post.
INC-143320 · Issue 602282
Support added for email addresses with hyphen in domain name
Resolved in Pega Version 8.4.4
When attempting to enter a email with a hyphen '-' in the domain part of an email ID ([email protected]), the reply button was getting disabled. This was caused by the regex validation implemented in the "pzValidateEmailAddress" (Work-Channel-Triage-Email) standard activity not covering all the possible cases. To resolve this, regex has been changed to instead use a platform-provided rule to ValidateEmailAddress.
INC-145425 · Issue 600774
New email template added to include full message history
Resolved in Pega Version 8.4.4
Whenever a reply was sent from the email triage case, the outbound email sent only the actual reply along with the original email and latest reply only, skipping all remaining replies from email. For example, if there were 5 replies from case, replying 5th time generated an outbound email that contained only 5th reply (actual / current), original reply (which created the service case) and the latest reply (reply 4 in this case) and skipped reply 1 and reply 2. To resolve this, a new Outlook-style template has been added for use in replies that will include all of the previous exchanges.
INC-146544 · Issue 604495
Updated handling for unexpected character set in non-UTF-8 email
Resolved in Pega Version 8.4.4
After upgrade, the listener properly created a case from an email, but the space character was being replaced by ? in the inbound emails. Investigation showed the messages did not appear properly in the UI if the email was sent using any encoding other than Unicode (UTF-8) and it had a special character set. To resolve this, the system will remove the attachment type which includes the charset.
INC-149667 · Issue 610053
Email Triage properly maps attachments to case
Resolved in Pega Version 8.4.4
Attachments from emails coming in via the Email channel were not being attached as expected to both the Email Triage case and the case generated from that. Instead, attachments were only being added to the triage case. This was traced to the pyAttachments property not being properly updated for attachment to the generated case, and has been resolved.
INC-150367 · Issue 606030
Double quotes escaped in entity mapping
Resolved in Pega Version 8.4.4
A usecase where the BOTS created the triage cases from the emails and pushed it to the Workgroup had an intermittent problem where the screen would freeze and no actions could be performed. perform any action on the same. Investigation showed this occurred when the entity text contained double quotes which is caused JSON to break on the client side. This generated an exception during rendering, and other onload scripts failed on load and blocked the entire thread. To resolve this, the system will now avoid the JSON break by escaping double quotes in entity mapping.