Skip to main content

Support Article

Images meant to be embedded in emails

SA-35138

Summary



Pega's outbound email features only allow for specifying "attachments" for inclusion for the email messages that are sent out from the Pega application. There is no support for "inline content," so all images in a Correspondence object are packaged as attachments when Pega sends Correspondence as email. Images may fail to appear in the body of outbound Correspondence when the recipient opens the message in their email client. The images that were intended to be part of the message body may appear as attachments to the email message.


Error Messages



No error- e-mail is sent with images as attachments.

Steps to Reproduce

  1. Create an AttachmentPage and try to set the below header on this page:
    1. .pyEmailHeaders(<APPEND>).pyName == "Content-Disposition"
    2. .pyEmailHeaders(<LAST>).pyValue=="inline"
    3. .pyEmailHeaders(<APPEND>).pyName == "Sensitivity"
    4. .pyEmailHeaders(<LAST>).pyValue=="company-confidential"
  2. Trigger an email from the application.


Root Cause

A defect in Pegasystems’ code or rules: Pega's outbound email features only allow for specifying "attachments" for inclusion for email messages that are sent out from the Pega application.


There is no support for "inline content", so all images in a Correspondence object are packaged as attachments when Pega sends Correspondence as email. Images may fail to appear in the body of outbound Correspondence when the recipient opens the message in their email client. The images that were intended to be part of the message body may appear as attachments to the email message.

Resolution




A new PageList property "pyInlineContent" of type "Embed-EmailAttachment" has been added to the preexisting "Data-EmailAttachments" class. The "SendEmailMesage" Rule-Utility-Function has been enhanced to detect when the new "pyInlineContent" property is populated. If the email is HTML formatted, the content in the list will be given a disposition of "inline" and packaged with the HTML body in a message part of type "multipart/related" for proper consumption by email clients. If the email is not an HTML email, the "inline" content will NOT be branded as inline content, so that it appears as an attachment when the email message is opened.

SendEmailNotification in Pega-EventProcessing has been Withdrawn and replaced with a new version of SendEmailNotification which has an updated "prepare" step (#2) that puts the data for images in HTML (Corr) into the new "pyInlineContent" property of the Email Attachments page (if such a page exists), so that SendEmailMesage can process them correctly.

These changes are bundled in HFix-32715.

Perform the following local-change steps:

  1. Apply the Hfix through Hfix Manager.
  2. Open the record, navigate to the "java" tab, and click Generate library, to ensure that the latest version of the SendEmailMessage function will be used by the application.
Suggest Edit

Published March 29, 2017 - Updated October 8, 2020

Did you find this content helpful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us