Configure approval request via email
This functionality is intended to approve or reject the ticket request through email, without the need of the manager to be logged.
Before getting started
In order to configure the email in the ticket, it is necessary to:
Pre-register the user and the group;
Configure the parameters 33 and 370 according to the guidelines of the system-related parametrization rules;
Make sure to know how to design the request approval flow via email registered. In this flow, there should be the "Approval" task and the design for sending the email, registering the template with the "Waiting Approval" template attached, and the e-mail server must be configured with all the parameters for email parameterization rules.
âš Attention!
Ticket approval via email is only possible with the following browsers configured as default: Mozilla Firefox, Google Chrome, and Microsoft Edge from version 42.17134.1.0.
Procedure
- Access the functionality through the main menu Workflow > Flow Design;
- Select the request approval flow and click on "Edit";
- Click on the Diagram tab;
- In the request approval flow, click on the connector "Send Message - email" icon and then on the small gray box next to the connector to configure it;
- Register, in the Identification tab, the name and email template to be used;
- Configure, in the Recipient tab, the type of recipients (group/user) of the email to be sent (the system does not search the recipients via "Expression").
Configure the email approval notification
- Access the functionality through the menu System > Settings > Email template;
- Paste the email template available in HTML in the attachment, in the Text field and verify the following guidelines:
- href="{TOKEN(serviceRequestIncident, ${IDSERVICEREQUEST}, VIEW, 50)};
- serviceRequestIncident = Interface directing: this field cannot be changed by the user;
- ${IDSERVICEREQUEST} = Key to increment the number of the service request: this field cannot be changed by the user;
- VIEW - calls the command to open the request: this field cannot be changed by the user;
- MM (50) - Token expiration time in Minutes: this field can be changed by the user;
- Click on "Save".