The purpose of this use case is to add email attachments on the fly to outbound dispatches.
In this scenario, you will learn how to send transactional emails with individual and/or personalized attachments. The attachments will not be pre-uploaded on the Transactional messaging server: instead they will be generated on the fly.
When you capture customer interactions or details, you may need to send this information back to the customer at the end of the process, for example in a PDF file attached to an email.
Below are the main steps of this scenario:
In this scenario, the attachments are not pre-created, but added on the fly to the outbound emails, which offers the following benefits:
To avoid performance issues, images included in emails cannot exceed 100 KB. This limit, set by default, can be changed from the
NmsDelivery_MaxDownloadedImageSize option. However, Adobe strongly recommends to avoid large images in your email deliveries.
Adobe also recommends to limit the size and number of attached files. By default, you can only add one file as an attachment to an email. This threshold can be configured from the
Learn more in the list of Campaign Classic options.
Before implementing this scenario, read carefully the guidelines below:
To avoid performance issue, it is recommended not to include more than one attachment per email. The recommended threshold can be configured from the list of Campaign Classic options.
The diagram below shows the different steps when implementing this scenario:
To add an email attachment on the fly to a transactional message, follow the steps below:
Start by designing your attachment. For more on this, see this section.
This allows you to have the files attached to an email, even if they are not hosted on the execution instance.
You can send emails via a SOAP message trigger. In the SOAP call, there is a URL parameter (attachmentURL).
For more information on SOAP requests, see Event description.
When designing your email, click Attachment.
In the Attachment definition screen, enter the SOAP attachment parameter:
<%= rtEvent.ctx.attachmentUrl %>
When the message is processed, the system will get the file from the remote location (third-party server) and attach it to the individual message.
Since this parameter can be a variable, it should accept the fully formed remote URL variable of your file, sent via the SOAP call.