Considerations for Setting Up Enhanced Email | Salesforce
Considerations for Setting Up Enhanced Email
Consider a few tidbits of wisdom before using Enhanced Email, including limitations, details for Email-to-Case customers, and information about working with EmailMessage and Task records.
Available in: Salesforce Classic and Lightning Experience
Available in: Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions
Enhanced Email is automatically enabled for most organizations except those that use Email-to-Case.
If you use Email-to-Case, you can already use custom fields, customized layouts, workflow rules, and triggers with emails without enabling Enhanced Email. Plus, you already use the EmailMessage object to store emails associated with cases. If you want to be able to relate EmailMessage records to other objects (besides cases), then we recommend that you enable Enhanced Email.
With Enhanced Email, your emails are stored using the standard Salesforce object, EmailMessage. This gets you all the usual goodies that come with standard objects, including custom fields, customized layouts, and a better record detail page. To store emails with the EmailMessage object, you must enable Enhanced Email unless your organization uses Email-to-Case, which already uses the EmailMessage object to store emails associated with cases.
With Enhanced Email, emails sent from Salesforce are saved as both EmailMessage records and Task records. However, only the EmailMessage record is shown on the email detail page in the UI.
Even if your organization uses Enhanced Email, emails added from Web-to-Lead, Salesforce for Outlook, and Lightning for Outlook are still only stored as Task records.
You can’t use custom currency fields with the EmailMessage object.
EmailMessage records can have only one record type.
Workflow rules can use EmailMessage records only to update fields on Case records.
Before using Enhanced Email, we recommend that you:
Review triggers and workflow rules that use the EmailMessage object. For EmailMessage records associated with cases, the ParentID field is always populated. With Enhanced Email, you can associated EmailMessage records with other records and the ParentID field may be blank. As a result, you may need to update your triggers and workflow rules to handle email messages with a blank ParentID field.
Review custom business logic that incorporates tasks and emails. We recommend that you:
Recreate any custom Task object fields on the EmailMessage object.
Migrate any Task object triggers to the EmailMessage object.
Test it in a sandbox with any workflows and customizations, including Email-to-Case customizations.