Using Custom Controllers within Visualforce Email Templates

Visualforce email templates can leverage custom controllers to render highly customized content. To do so, include a custom component in a Visualforce email template that uses that custom controller.

For example, suppose you want to display a list of all accounts beginning with the word “Smith” in an email template. To do this, first write a custom controller that uses a SOSL call to return a list of accounts that begin with “Smith”:

Next, create a custom component named smithAccounts that uses this controller:

Remember that all custom components used in Visualforce email templates must have an access level of global.

Tip

Finally, create a Visualforce email template that includes the smithAccounts component:

Notice that although the relatedToType attribute is required by the emailTemplate component, it does not have any effect on this example. It has the value of "Opportunity" only to show that it can take an object value that is different than the object used in the custom component.

Sharing settings are enforced if your email templates use a standard controller. If your organization-wide default for the user object is set to Private and you need to access user information such as name and email address in your Visualforce email template, you can use a custom component or custom controller with the without sharing keywords.

For information about sharing for the user object, see User Sharing Overview in the Salesforce online help.

Note

Visualforce Developer Guide

Using Custom Controllers within Visualforce Email Templates