Manage FireFlow email templates
FireFlow sends emails to users upon various events in the change request lifecycle.
This topic describes how to manage the templates used for each type of email.
FireFlow email templates
This template... |
Is used to send emails to... |
And is used when... |
---|---|---|
Transaction |
Change request owners
|
A reply is written for an item in a change request's history. A comment is written for an item in a change request's history. A change request's owner is changed. |
Correspondence |
Requestors |
A reply is written for an item in a change request's history. |
Resolved |
Requestors |
A change request is resolved. |
Autoreply |
Requestors |
A new change request is created. |
Notify External System Ticket Close |
An external Change Management System (CMS) |
A change request is resolved. |
If desired, you can modify these templates.
Note: Other templates appear in the FireFlow interface; however, they are not used for FireFlow emails and should therefore be ignored.
Note: It is possible to customize which events trigger email sending and to whom the emails are sent. For further information, contact AlgoSec.
Modify email templates
Do the following:
- Log in to FireFlow for configuration purposes. For details, see Log in for configuration purposes.
-
In the main menu, click Advanced Configuration.
The Advanced Configuration page is displayed.
-
Click Global.
The Admin/Global configuration page is displayed.
-
Click Email Templates.
The Modify email templates page is displayed.
-
Click on the name of the desired template.
The Modify email template Autoreply page is displayed.
-
In the Content field, type the template's content.
You can use variables in the template. For a list of popular variables and their explanations, see Email Template Variables (see Email template variables).
Note: Do not modify the Name and Description fields.
Note: The email template variables that include Perl code (appearing in curly braces {}) are subject to Perl syntax.
-
To reset the template to its default settings, click Reset.
-
Click Update.
Email template variables
The change request ID number. For example, 364.
The change request subject. For example: Need to open device ports for project Armageddon.
The change request status. For example: plan
The requestor's email address. For example: [email protected]
The change request owner's username. For example: ned.netop
The change request in XML format (a flat ticket). For examples, see Flat Ticket Examples.
The change request in XML format (a flat ticket) with initial plan and/or work order information included.
Note: Initial plan and work order information are only included in the flat ticket when they are enabled.
For details, see Configure inclusion of work details in flat tickets and See Configure inclusion of work details in flat tickets.
For more details, see Flat Ticket Examples.
The URL at which the change request is displayed.
Note: To enable links, see Configuring Link URLs to FireFlow pages.
For example: https://fireflow-demo.algosec.com/FireFlow/Ticket/Display.html?id=136
The date and time at which the email is sent.
For example: Mon Nov 17 16:58:44 2008