Manage transactional emails
We can manage transactional emails by ensuring that email templates exist for each specific transaction type we want to support. Transactional emails are sent using the IBM Marketing Cloud Transact XML message type and transport method.
Before beginning
Procedure
- Deciding how to compose the email content
Emails are composed by using content from either WebSphere Commerce, IBM Marketing Cloud Transact XML, or a combination of the two sources. Deciding how to compose the email content typically depends on the complexity of the email that is being sent.- Creating transactional email templates in IBM Marketing Cloud Transact XML
Create an email template in IBM Marketing Cloud Transact XML so that we can assign content to transactional emails. Complete this task for each specific transaction that we want an email sent for. That is, ensure that a corresponding email template exists in IBM Marketing Cloud Transact XML for each specific transaction type.- Assigning the IBM Marketing Cloud Transact XML message type to its transport method
After you create an email template in IBM Marketing Cloud Transact XML, we can assign the template to a message type to be sent by the IBM Marketing Cloud Transact XML transport method. Complete this task for each IBM Marketing Cloud Transact XML email template created so that we can send emails for each specific transaction. That is, ensure that a corresponding IBM Marketing Cloud Transact XML message type and transport method exists in the WebSphere Commerce Administration Console for each existing IBM Marketing Cloud Transact XML email template.- Creating email message JSP files
Create email message JSP files so that the email content that is composed by the IBM Marketing Cloud Transact XML email template can use its content. The IBM Marketing Cloud Transact XML email template uses personalization name-value pair replacement variables to include content that is provided by the email message JSP on the WebSphere Commerce server.