Email template details

This table shows the required fields and configuration options for completing email template details:

Field Description
Preferred Email Language

Specify the role whose language you want to use. For example, if you select Manager, then the Manager's locale is used to determine the language for the template file. This field is not required.

If you leave this field blank, the organization's base data is used.

Note: This field is only available if Dynamic Embedded Text (DET) is used.
To

Select the variables representing the email or addresses of the people to whom the email will be sent.

Right-click in the field, click Variables, and select the variable representing the email address of the recipient. The variable that you select shows in curly braces.

For example, {ManagerEmail}. Separate multiple email addresses or email variables with commas.

Note: In any email address field on the template, you can also specify an actual email address.
CC, BCC

Select the variables representing the email addresses of the people to whom the email is copied.

For example, {ResourceEmail}. Separate multiple email addresses or email variables with commas.
From Specify the email address of the sender. This can be a generic system email address. Alternatively, you can right-click in the field, click Variables, and select the variable representing the email address of the sender.

For example, {RequesterEmail}

.
Subject Specify the subject of the email. You can right-click the field and select Variables for any text to be substituted.

For example, {ResourcePreferredFullName} – Requests Time Off.
Body

Provide the text of the email. Use variable text for any text that you want substituted. To select variable text and show the list of valid variables, click {A} in the formatting toolbar.

For example, {ResourceFullName}has requested Time Off of {Hours} hours on {TimeOffDate}.

Note: This is an RTF field with formatting options.

The variables that are prefaced with the word Old can be used in email templates for update actions. You can include the values that were there before the update and what they were changed to. The Old variables store the values from before the update. The variables that are not prefaced with Old can be used to show what the fields were changed to.

For example, {ResourceFullName}has changed their time off request date from {OldTimeOffDate} to {TimeOffDate}, and the hours from {OldHours} to {Hours}.