This getting started article will help Administrators to learn about and modify Notification Templates.
For most notification templates, the user must have TDAdmin or Application Administrator access.
For Ticket Survey notification templates, the user must have access to a Ticketing application with a user role that includes "Create and Modify Surveys"
For Project Survey notification templates, the user mist have access to the Projects application and a Global security role that includes "Create and Modify Project Surveys"
Overview
Notifications are important as they enable people are kept up to date with work progress via email delivery. Administrators can configure notification templates that determined the email content and layout for their organization.
Where to Find This
Navigate to Notification Templates following these paths:
- Standard Application Notification Templates
- TDAdmin > Notification Templates > [choose type of template] > [select template]
- Application Specific Notification Templates
- TDAdmin > Applications > [Application Name] > Notification Templates > [select template]
- As an application administrator:
- Work Management > View Applications > [Application Name]
- Select the Gear icon on the right side of the upper menu bar
- Select Admin > Notification Templates > [select template]
Where to Start
Notification Templates exist throughout the system for a variety of applications and components. This allows for custom email templates to be controlled on an action-by-action basis, where each action is limited to the scope of an application. If the custom template is not enabled for a specific action, then the default template will be used for that action.
Template Information by Application or Component
The following notification templates are available for Standard applications.
- Announcements
- Briefcase
- File Check In
- File Check In Requested
- File Comment Added
- File Notification
- File Workflow Completed
- File Workflow Rejected
- File Workflow Routed for Approval
- Expense
- Expense Comment Added
- Expense Status Changed
- Issues
- Issue Comment Added
- Issue Created
- Issue Edited
- Issue Updated
- An issue update refers to a change in an issue's status, e.g., New to In Process.
- Links
- Link Comment Added
- Link Created
- Portfolio Issues
- Issue Comment Added
- Issue Created
- Issue Edited
- Issue Updated
- An issue update refers to a change in an issue's status, e.g., New to In Process.
- Portfolio Risks
- Risk Comment Added
- Risk Created
- Risk Edited
- Risk Updated
- A risk update refers to a change in an risk's status, e.g., New to In Process.
- Projects
- Project Comment Added
- Project Manager Changed
- Project Staffed
- Project Updated
- A project update refers to a change in the project's, health, overall % complete, or status.
- Resource Added to Project
- Resource Removed from Project
- Project Requests
- Request Approved
- Request Comment Added
- Request Declined
- Request Forwarded
- Request Forwarding Completed
- Request Returned to Requestor
- Request Step Responsibility
- Request Submission
- Request Type Changed
- Request Withdrawn
- Resource Added to Request
- Resource Request
- Multiple Resources Assigned to Project
- Resource Assigned to Project
- Resource Assigned to Project Request
- Resource Request Cancelled
- Resource Request Created
- Resource Request Edited
- Risks
- Risk Comment Added
- Risk Created
- Risk Edited
- Risk Updated
- A risk update refers to a change in an risk's status, e.g., New to In Process.
- Tasks
- Task Assigned
- Task Comment Added
- Task Started
- Task Updated
- A project task update refers to a change in an task's % complete, e.g., 0% to 20%.
- Time Report
- Time Report Due
- Time Report Overdue
The following notification templates are available for Client Portal applications.
- Knowledge Base
- Knowledge Base Article Comment Added
- Knowledge Base Article Feedback Added
- Knowledge Base Article Status Changed
The following notification templates are available for Ticketing applications.
For many of the templates there are two versions, Requestor and Ticketing User. The Requestor vs. Ticketing User Ticket Notification Templates article explains when each version is used.
2 Versions - Requestor & Ticketing User
- Ticket Comment Added
- Ticket Created
- Ticket SLA Violation
- Ticket SLA Warning
- Ticket Updated
- A ticket update refers to a change in the ticket's status, e.g., New to In Process.
- Task Comment Added
- Task Updated
- A ticket task update would include a change to the task's overall % complete, e.g., 0% to 20%.
1 Version
- Ticket Moved
- Ticket Workflow Step Assignment
- Ticket Workflow Step Reminder
Surveys are used in the TeamDynamix application suite to retrieve useful client feedback after a project or ticket has been completed. It is important that these survey notifications are consistent with an organization's brand since these emails are client-facing. Custom survey notification templates can be used to style these emails that are prompting clients for feedback.
To view or edit the surveys for a Ticketing Application or Projects:
- Work Management > View Applications > Projects or [Ticketing Application Name]
- Click the “gear” icon in the toolbar.
- Select Surveys from the dropdown.
- Click the name of the survey from the list.
- Select the Request Notification tab.
- Make modifications as needed then save.
To learn more about surveys, see Using Surveys in Ticketing Application and Projects.
Notification Footers
Notification footers allow additional customization for notifications.
Notification footers include a text footer and an HTML footer, which will be included at the bottom of the email. The former is used when plain-text emails are delivered, while the latter is used for HTML-formatted emails. If an HTML-formatted email is being delivered and HTML footer information is not provided, then the text footer information will be used instead. Notification footers can also include a tracking pixel at the bottom of the email. If this is enabled, then a corresponding Read By entry is created for the item in TeamDynamix when the user reads the email.
Template Configuration
When editing a notification template, the available information is encapsulated by Template Tags. This changes on a per-application basis so that only relevant information can be included for an email. These tags can be used to include helpful information for both the email Subject and Body, and are of the format {{FieldName}}
. All available fields for a notification template are present in the Template Tag dropdown. This uses the Mustache markup language, which has documentation available here: http://mustache.github.io/mustache.5.html.
Follow these steps to add a template tag to the Subject or Body fields:
- Place your cursor in the Subject or Body field at the place where the template tag should be inserted.
- Choose the appropriate field in the Insert Template Tag dropdown. It will be inserted where your cursor is.
Template tags can also be used to insert a section of HTML content that only displays when the section tag evaluates to True or a not empty value. A section starts with a tag with a pound sign and ends with one with a slash, as follows:
{{#TemplateTag}} ... snippet ... {{/TemplateTag}}
As an example, the default Project Comment Added Template includes this section, which displays the old status and new status if the Description tag has a value:
{{#Description}}
<!--Description-->
<tr>
<td style="font-size: 17px; font-weight: bold; color: #515A61; padding-top: 10px; border-top: 1px solid #0072C6;">Description
</td>
</tr>
<tr>
<td style="font-size: 16px; padding-top: 0px;">{{{Description}}}
</td>
</tr>
{{/Description}}
Sections can also display when the opposite is true, by switching the pound sign for a caret. The following would include a message that no description is provided if the Description
field is empty:
{{^Description}}
<!--No Description-->
<tr>
<td style="font-size: 17px; font-weight: bold; color: #515A61; padding-top: 10px; border-top: 1px solid #0072C6;">Description
</td>
</tr>
<tr>
<td style="font-size: 16px; padding-top: 0px;">No Description was provided.
</td>
</tr>
{{/Description}}
Custom Attribute Sections
A special type of section is available which allows you to include all the custom attributes on an item. For notifications that support custom attributes, the {{#CustomAttributes}}
section will repeat once for each valid custom attribute on the item. Within this section, you can define how the HTML displays, and can include the attributes' Names and Values using the {{Name}}
and {{Value}}
tags.
A custom attribute will be valid for including in the {{#CustomAttributes}}
section if it:
- Has a value
- Is not a protected custom attribute
- Is marked as Client Visible (for custom attribute types that support this setting)
- Matches the project's current type (for project custom attributes only)
Individual Custom Attributes
Each individual custom attribute is also available as a section, which are available in the Insert Template Tag dropdown. These will insert a section with a tag based on the custom attribute's ID, with the name of the attribute in an HTML comment tag.
{{#Attribute61902}}<!-- AttributeName -->{{Name}}: {{Value}}{{/Attribute61902}}
Inside the custom attribute you can use the same {{Name}}
and {{Value}}
tags to define exactly how you want the attribute to display.
Activating or Deactivating Templates
Activating a Template
Each notification must be Activated before it will be used for notification.
- Open the notification template that you wish to activate
- Click the Activate button at the top.
Deactivating a Template
If a template is deactivated, the default template will be used for this notification.
- Open the notification template that you wish to activate
- Click the Dectivate button at the top.
Changes to the template, including activation, may take up to 5 minutes to take effect. You must first save the template before customizations can be activated.