Skip Navigation LinksALVAO 10.1Index of Windows and CommandsALVAO AdminManageService DeskProcessesWorkflowRequest statusBehaviorMessage template for approvers Skip Navigation Links. Skip Navigation Links Skip Navigation Links.


Change ALVAO version
Change language

Message template for approvers

In this window you can define the template of the message for approvers for the current request approval status.

Options:

  • Use default template – select if you want to use the default message template.
  • Use custom template – select if you want to define a custom template.
    • Restore default – restores the default message template.
    • Insert variable – from the drop-down box, select a variable you want to insert in the message template.
Note:
The notification to approvers is formatted according to the notification style settings.
Tip:
To display selected text in bold, insert it between the "<b>" and "</b>" tags.

You can use the following variables in the message for approvers:

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 tag 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$] The request tag as a link to the request.
[$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$] The service phone number.
[$TicketSolverEmail$] The solver's e-mail.
[$TicketSolverName$] The solver's name.
[$TicketSolverPhone$] The solver's phone number.
[$TicketSolverEmail$] The solver's e-mail.
[$TicketSolverName$] The solver's name.
[$TicketSolverPhone$] The solver's phone number.
[$TicketTitle$] Request URL in ALVAO WebApp.
[$TicketUrl$] Request URL in ALVAO WebApp.
[$tHdTicketCust.ColumnName$] The request's custom item whose column in the database is ColumnName. Only items available for the specific process are shown in the drop-down list of variables.

 

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