Message template for approvers

This window allows you to define the template of the message for approvers for the edited request approval status. This message is sent to approvers to inform them that the approval process has been initiated. It also appears on the request approval/rejection form and in the request log in approval start events.

Options:

Use the default template – a default message template is used that is common to all processes and request statuses.

Note:
If the system design of the default template does not suit you, you can edit it in the database by using the SQL script.
Use custom template – a custom template is used that is defined only for the modified request status. Edit the message template in the text box. The resulting report should tell the approver of what is specifically subject to approval, i.e. what he/she should approve or reject in the request (e.g. the requester's initial application, solution proposal, final implementation, etc.).

Tip:
The text that you want to display in bold in the message mark with <b> and </b> marks in the template, e.g. <b>Important:</b>.
- Reset to default – overwrites the current content of the text field with the default template.
- Insert variable – from the drop-down box, select a variable you want to insert in the template to the current cursor position.

You can use the following variables in the template:

Variable	Description
[$ApprovalByForm$]	The Approve or reject button which opens the form for approving or rejecting a request. This button will only be inserted in notifications for approvers. If used together with the [$ApprovalByEmail$] variable, the name of the button will be Approve or reject on the web.
[$ApprovalByEmail$]	The Approve and Reject buttons for approving by e-mail. These are two buttons that will only be inserted in notifications for approvers. If used together with the [$ApprovalByForm$] variable, the names of the buttons will be Approve by e-mail and Reject by e-mail.
[$ApprovalStepExpirationTime$]	The expiration date of the current approval step.
[$ApprovalStepCurrentApprovers$]	A list of current approvers with their e-mail addresses, listed as "Name <e-mail address>". Individual approvers are searated with semicolons.
[$CommentForApprover$]	Comments for approvers. In the place of this tag there will be a comment that can be typed by the user if the approval process is launched manually. If the approval process is launched automatically, the variable will be replaced with "-".
[$TicketID$]	Request number
[$MessageForRequester$]	A message for the requester typed by the solver (operator) when the request is resolved, including images and attachments. This variable can only be used for approving in the Resolved status.
[$TicketMessageTag$]	Request tag, e.g. T45412HD.
[$TicketMessageTagLink$]	A request tag as a link to the request page in ALVAO WebApp.
[$OriginalMessage$]	The request creating report including images and attachments.
[$OriginalMessageSubject$]	The subject of the request creating report.
[$TicketProcess$]	Process name
[$TicketRequesterEmail$]	The requester's e-mail
[$TicketRequesterName$]	The requester's name
[$TicketRequesterPhone$]	The requester's phone number
[$TicketService$]	The path to the request service including the whole path in the objects tree, e.g. IT/Terminals/Request for a new computer.
[$TicketServicePhone$]	Service phone number
[$TicketSolverEmail$]	The solver's e-mail
[$TicketSolverName$]	The solver's name
[$TicketSolverPhone$]	The solver's phone number
[$TicketTitle$]	Request name
[$TicketUrl$]	Request page URL in ALVAO WebApp
[$tHdTicketCust.ColumnName$]	Custom request item where ColumnName represents the name of the relevant column in the tHdTicketCust table. The variables drop-down menu only lists the items that are assigned to the edited process.

Note:

The notification to approvers is formatted according to the notification style settings.

Did not find what you were looking for? Ask our technical support team.