Hi Maarten,

We can just do Preview on your Correspondence template rule from Actions to get an idea of actual email view. That would be the same view embedded in email body and sent as an actual email.

Will this help ?

We can also download the correspondence email from case attachments to see how actually it looks, but this is after sending. 

or do you have any specific requirement to preview the email within Pega before you send to email recipient and looking for a way?

Let us know.

Hello,

I think your requirement is this "If i choose a template and put text in the RTE (.pyBody) then i do not have a view how the actual email will look."

So you want your end user to see the content before sending the emails ! Am i correct ?

Few approaches you can try .

1. Use a button called preview and ask user to click the button to see the content. Thru that button you can call the modified pybody via a harness to show it to user how it is going to look .

2. Otherwise, before using sendEmailCorrespondance , use a dummy flowaction where you use the corr template and allow users to modify the content if required. Then you can use the sendemailcorr flowaction again to show the content and subsequently perform the action. 

I dint try any of them so not sure whether that will help you to meet your requirement or not.

On a different note, I do believe that when your users are modifying the content of a template via RTE at runtime, it is more of WYSIWYG that means "what you see is what you get" so there should not be a mismatch for which they need to first review it and then send. Just a thought. Others can comment.