SR-B90177 · Issue 337875
Removed extra spaces in attached note
Resolved in Pega Version 7.4
After attaching a note, extra line spaces were seen in the note. This has been fixed.
SR-B91572 · Issue 339656
Email addresses passed intact
Resolved in Pega Version 7.4
When sending correspondence with a Bcc recipient, the Bcc recipient Email ID had the last letter removed in "populateRecipients". This has been fixed, and additional checks have been added for the other address fields as well.
SR-B91999 · Issue 340444
Smart email reply error fixed
Resolved in Pega Version 7.4
An exception was generated when attempting to reply in SmartEmail. This was traced to different APIs conflicting and overriding the address setting process, and the system has been modified to correct this.
SR-B91999 · Issue 336429
Smart email reply error fixed
Resolved in Pega Version 7.4
An exception was generated when attempting to reply in SmartEmail. This was traced to different APIs conflicting and overriding the address setting process, and the system has been modified to correct this.
SR-C2673 · Issue 344715
Email addresses passed intact
Resolved in Pega Version 7.4
When sending correspondence with a Bcc recipient, the Bcc recipient Email ID had the last letter removed in "populateRecipients". This has been fixed, and additional checks have been added for the other address fields as well.
SR-B69751 · Issue 325146
Resolved button select error in PegaSurvey
Resolved in Pega Version 7.4
In Pega Survey, the 'Simple Question' with 'Answer mode' of 'RadioButtons' was not working properly: selecting one radio option via mouse click caused another radio option to be selected after the buttons were clicked multiple times. This was traced to legacy code which required an extra refresh in SurveyScripts for a Survey smart shape. This code has now been removed as it is not required in QuestionScripts.
SR-B14783 · Issue 291708
Added image retrieval support to correspondence rule
Resolved in Pega Version 7.4
If images were present in the correspondence rule used to send emails, no images were visible in the emails sent out from Pega after restart. This was traced to 'SendEmailNotification' using the 'StaticContentUtilsImpl.getResolvedFile(String)' engine API to fetch the Image bytes, which did not have the necessary support to fetch 'Data-Content-Image' content. This has been added.
SR-B74711 · Issue 328307
Added image retrieval support to correspondence rule
Resolved in Pega Version 7.4
If images were present in the correspondence rule used to send emails, no images were visible in the emails sent out from Pega after restart. This was traced to 'SendEmailNotification' using the 'StaticContentUtilsImpl.getResolvedFile(String)' engine API to fetch the Image bytes, which did not have the necessary support to fetch 'Data-Content-Image' content. This has been added.
SR-B84855 · Issue 339079
Clarification on DSN Thread Topic parsing
Resolved in Pega Version 7.4
The PDN article regarding parsing DSN emails incorrectly stated that "If the message triggers a DSN, the Thread-Topic value is still intact. You can map the value from this header to a utility named parseThreadTopicHeader in the Message Header section on the Request tab. Be sure to specify the pyInboundEmail page property in the Map To Key field." In actuality, the Thread topic is not intact for all domains; it depends on the email provider. If the thread topic is not present in the DSN mail header, custom logic will need to be added in the email service activity rule to get it from the mail content.
INC-102005 · Issue 556731
Child case ID prefix preserved
Resolved in Pega Version 8.4.2
When configuring a case as a child case in App Studio, the case ID prefix was cleared out of the field on the Settings tab for the case type. Investigation showed that when the child case was added to the parent case in App studio, pzaddcasetypetoapp was called but the parent activities did not pass the CaseID parameter of the child case type. This caused the CaseID prefix of the child to be null and displayed as blank in the Settings and Application. This has been corrected by ensuring the system will get and set the parameter value.