Difference between revisions of "Email Templates"

From Hornbill
Jump to navigation Jump to search
Line 23: Line 23:
 
:* '''Format'''
 
:* '''Format'''
 
:: Each variable starts with a double opening curly brace (<nowiki>{{</nowiki>) and finishes with a double closing curly brace (<nowiki>}}</nowiki>)
 
:: Each variable starts with a double opening curly brace (<nowiki>{{</nowiki>) and finishes with a double closing curly brace (<nowiki>}}</nowiki>)
:: With the curly braces, the contents can be either just a data field specified by a dot (.) followed by the field name or the data field can be preceded by an available related entity.
+
:: With the curly braces, the contents can be either just a data field specified by a dot (.) followed by the field name (.H_Firstname) or the data field can be preceded by an available related entity (Contact.H_firstname).
  
 
:* '''Letter Case'''
 
:* '''Letter Case'''

Revision as of 19:26, 31 December 2016

Home > Administration > System > Email > Templates

Introduction

Email templates can be used to pre-populate emails with information to create a standard format for outbound emails. Emails may be sent automatically from Business Process Workflows or manually from within an app.

Template List

The list of templates is controlled by the selection of the application that will be using the template along with the entity or business object within that application for which the template will use variables to include information from the entity when an email is sent using that template.

Template Editor

  • Name
The Name provides a reference within the list of Templates.
  • Subject
Contents of the Subject of the email. Both text and variables can be used within this section.
  • Message
The main body of the email. When creating or modifying an email template, the Message area includes a full editor to provide options for fonts and styling within your email.

Variables

Template Variables can be used within the Subject or Message of a template in order to have information that is stored within the related entity, used in the email.

  • Format
Each variable starts with a double opening curly brace ({{) and finishes with a double closing curly brace (}})
With the curly braces, the contents can be either just a data field specified by a dot (.) followed by the field name (.H_Firstname) or the data field can be preceded by an available related entity (Contact.H_firstname).
  • Letter Case
The letter case of the variables will determine the letter case that is used in the email. For example
  • {{.H_firstname}} = John
  • {{.h_firstname}} = john
  • {{.H_FIRSTNAME}} = JOHN