E-Mail Templates: Difference between revisions

From Accelerator for SageCRM
No edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 5: Line 5:
[[File:mailtemplate3.jpg]]
[[File:mailtemplate3.jpg]]


This opens a dialog for you to choose a record. If you have the taskpane open this provides a context for merges this data with the template.
This opens a dialog for you to choose a record. If you have the taskpane open this provides a context for merges and so reconciles the data with the template.
 
The templates you see are entity specific. So if you have the task pane with a case then it will only show templates setup for cases.  


[[File:mailtemplate1.jpg]]
[[File:mailtemplate1.jpg]]
Line 14: Line 16:


Clicking the item in the list or USE in the preview will insert the template into the Compose window and close the dialog.
Clicking the item in the list or USE in the preview will insert the template into the Compose window and close the dialog.
---
NOTE: merge fields must all be in lowercase
EG
  #Comp_Name#
will NOT work and you must use
  #comp_name#
----
The view used to get the merge data is
  vsummaryENTITYNAME
EG
  vsummaryCase
So if you require fields from say, the "Address" table, this view must be updated to include this.

Latest revision as of 10:30, 8 May 2026

The "Email Templates" dialog will allow users to search for email templates stored in CRM and download (and optionally merge) the templates and attachments into the email.

This appears in the email compose window.

This opens a dialog for you to choose a record. If you have the taskpane open this provides a context for merges and so reconciles the data with the template.

The templates you see are entity specific. So if you have the task pane with a case then it will only show templates setup for cases.

You can preview the email template also

Clicking the item in the list or USE in the preview will insert the template into the Compose window and close the dialog.

---

NOTE: merge fields must all be in lowercase

EG

 #Comp_Name#

will NOT work and you must use

 #comp_name#

The view used to get the merge data is

  vsummaryENTITYNAME

EG

 vsummaryCase

So if you require fields from say, the "Address" table, this view must be updated to include this.