In our project, treatments for email campaign are created in Pega. However ,we are not using OOTB capability to send Emails. We have to generate a file which should contain the email body and receiver email address and send it to communication gateway. Communication gateway will be sending email to Customers.
Though Pega provides write to file feature in offer flow, we don't see any option to write email body in file treatment rule.
In Pega 7.x version when we execute a email campaign , email content is generated in pr_data_corr_email(pyBody) table. But in Pega8.4 version it is not doing the same.
The way file extraction works for email (and other channels like it - SMS for example), is that your email sending system (ESP) has an email template that is waiting for mail-merge to be applied and then deliver the email. As such, what you model in Pega are just the personalization fields to be sent to the ESP and not the full content. The content is handled by the ESP via the template and the extra data for personalization comes from Pega. This essentially means you are authoring email outside of Pega. When you author email inside Pega, the expectation is that system will do the merging and delivery as well. As such, there is no direct way to accomplish what you are trying to do because its just not the way things work. You need to choose either to author the email in Pega (and have it to the merging and delivery) or author the email externally and have Pega only send the data to personalize the content that was authored outside.
Hope this helps.
Posted: 3 years ago
Posted: 19 Jun 2020 7:34 EDT
sandeep padala (sandeepsunny)
Senior System Architect
Thank you for your response. Now I understood the concept of File templates and how to use them for SMS and Email.
However, technically speaking we can achieve this requirement on 7.x platform version, as body of email is getting stored in table.
Similarly is there any way we can achieve this in Pega 8.4 ? Reason for trying to achieve this is , pega OOTB supports click and Impression. But the Email sending system does not support this feature in our case.
What is the Email sending system? Does it support SMTP connectivity? If so, instead of file extraction, I'd recommend that Pega executes the delivery via the SMTP connectivity directly and not pass a file over.