Approvals
Mint Service Desk 3.4.2 user manual.
Basic Information
Approvals let designated users accept or reject tickets in the Pending Approval status according to rules configured by an administrator. The ticket remains locked for editing until the configured approval or rejection conditions are met.
The administrator defines decision rules and decision-makers, creates a Pending Approval status for the ticket type and assigns the configuration to that status. The administrator also configures notifications for the start of the process and for positive and negative decisions. An agent or customer can then create a ticket of that type. When the agent moves it to Pending Approval, the ticket is locked. Decision-makers accept or reject it; once the configured voting conditions are met, it changes to Accept or Reject and is unlocked. Designated users receive the configured notifications, and ticket history records each decision.
Once the process is complete for a given application, the same Pending Approval status cannot be set again.
To configure approvals, complete the following steps as an administrator:
1. Create a configuration in the Approvals tab.
2. Add a status of type Pending Approval in Tickets > Statuses and assign the configuration to it.
3. Configure notifications for the approval process.
The process of moving to Pending Approval status and decision-making takes place in the Agent and Customer profile and is described in the last part of this section.
Use the menu on the left to open a section.
Approvals Tab
Related articles
Configuration Tree
In the Approvals tab, administrators define decision rules using users, agent roles and logical operators (AND, OR). Assign the configuration to a status of type Pending Approval for the relevant ticket type. Specify how many users, or what percentage of a role’s users, must approve or reject the ticket. The ticket remains locked for editing until the configured decision conditions are met.
Important: Incorrect logical conditions can prevent any decision and leave the ticket locked. If your business process permits it, add a user, such as the CEO, who can make a decision alone in exceptional cases.
Upon accessing the tab, a table of configurations appears with the columns: Name, Description, and an Action column containing buttons to delete the selected configuration.
In the upper-right corner of the table, there is a panel containing a search field and buttons for Add Configuration, Search by, and Set Column Properties.
Clicking the Add Configuration button opens a modal with the following fields:
- Name - the configuration’s name (required, must be unique)
- Description - a short description of the configuration
- Approval conditions - a required section where you build the logic structure, starting with a single Operator field.
Available operators
The default branch structure starts with operator field:
here you can choose AND or OR
Operator AND – this means that all conditions must be met/approved.
Example:
In the example above, the users First Agent, Second Agent, and Third Agent must all give a positive decision for the process status to be approved. If any of them issues a negative decision, the status will be marked as rejected.
Operator OR – this means that one or more of the conditions must be met/approved. The number or percentage of required conditions is determined by the Approval Rule setting. Similarly, the number or percentage of negative decisions needed to reject the process is set in the Reject Rule.
Example:
In the example above, it is set that three agents must give a positive decision for the process to be approved (Approval Rule set to 3). Conversely, the process will be rejected after one negative decision (Reject Rule set to 1).
Decision-makers and nested conditions
- operator: a nested AND or OR operator.
- user: a selected agent or customer.
- role: a selected agent role.
- to be selected: the agent chooses the decision-maker when a Pending Approval status is selected in ticket details.
- line manager: the manager of the user in the ticket’s Customer field. Users can set a manager in their profile. An administrator can also set it, and an agent with user-management permission can set it for a customer.
After choosing operator, click PLUS icon to open modal with additional options
Here we can choose: another Operator, USER, ROLE, To Be Selected and Line Manager
User: choose an agent or customer to participate in the decision process.
Role: select the agent role to involve in the decision process. Approval Rule sets the number or percentage of users in that role whose positive decisions are required. Reject Rule sets the number or percentage of negative decisions required to reject the ticket.
Example:
In this example, 50% of the Service Desk Agent role’s users must approve the ticket. It is rejected if 30% give a negative decision.
To be selected - selecting this option allows the agent to choose in ticket details the user (Agent or Customer) who will be the decision maker for this configuration branch. Only one ‘To be selected’ option can be selected per configuration. The possibility for the agent to select the user appears when the Pending Approval status is selected in the application with an assigned configuration containing the ‘To be selected’ option.
Example:
The administrator creates the following configuration.
Two users participate: First Agent and a user selected by the agent.
Next, the administrator assigns this configuration to a new status of type Pending Approval. In this example, the status is named To Be Selected. In Tickets > Statuses, select Pending Approval in Type, choose the rule in Select approval configuration, and set Select status after approve and Select status after reject. See Configure an approval status for the complete procedure.
The agent starts the approval process by selecting To Be Selected in ticket details.
A selection window opens.
The agent selects an Agent or Customer to participate in the decision process.
Line manager: include the manager of the user in the ticket’s Customer field in the decision process.
See Set or change a line manager in the user profile for the steps, permissions and examples.
Drag And Drop
Drag a user or branch to another position while creating an approval configuration.
For example, you want to move First Agent from first branch to second:
Click and hold left mouse button at Second Agent and move it to second branch:
You can do the same with whole branch - for example, you want to put second operator AND to first. Click and hold left mouse button on first AND and drag it to place you want:
Advanced Structures
The Approvals module supports nested decision logic. The example below combines nested operators with an alternative decision by the CEO.
In this configuration, a ticket can receive an Approval or Reject decision through three paths:
If none of the configured branches can produce an Approval or Reject decision, you can ask the CEO to decide.
Deleting Configuration
An administrator can delete a configuration only when it is not assigned to a status. If it is still assigned, a message identifies the status and its location.
In this example, the configuration is used in Tickets > Statuses, under the Complaints ticket type and the Decision status.
Statuses
Related articles
Configuration
An administrator can create statuses of type ‘Pending approval’ and assign a configuration prepared in the Approvals tab. For each status, choose where the ticket moves after approval and after rejection. You can name the status freely and create several Pending Approval statuses using the same or different configurations.
The general status fields are described in Ticket statuses. The procedure below explains the fields specific to approvals.
Creating an approval status
Open Tickets > Statuses and select the ticket type, such as Complaints.
The existing statuses for that ticket type appear.
Click Add New, enter the display name in Value, and select Pending Approval in Type. The name identifies the status in tickets; the type enables the approval settings.
Decision rule and outcome statuses
Selecting the Pending Approval type reveals the fields for the approval configuration and the two outcome statuses:
Select approval configuration: choose the decision rule prepared in the Approvals tab. This rule determines who decides and how the decisions are combined.
Select status after approve: choose the status assigned to the ticket when the configured approval conditions are met.
Select status after reject: choose the status assigned to the ticket when the configured rejection conditions are met.
Click Save after selecting the configuration and outcome statuses. The new status is then available in tickets.
Important: If you want to use new, custom statuses in the Select status after approve and Select status after reject fields during configuration, you must configure and save them before adding the Pending Approval status.
Example
To use custom statuses named Approved and Rejected with a Pending Approval status:
First create Approved and Rejected with the type Closed, then click Save.
Now create the Pending Approval status. The new statuses are available in the outcome lists.
Configuration Change
The administrator can change the saved configuration in the Select approval configuration field to another configuration. The exceptions are those configurations that include To Be Selected and Line Manager in the decision tree - such configurations will then be greyed out and not selectable.
If tickets already use this status, existing decisions carry over to the new configuration only when their decision-makers also participate in it.
Example
A ticket in Pending Approval requires decisions from Agent 1 and Agent 2. After Agent 2 decides, the administrator changes the configuration to require Agent 2 and Agent 3. Agent 2 does not need to decide again: their existing decision carries over. If the configuration changes several times, only decisions from the configuration immediately before the latest change are carried over.
Deleting Statuses
Deleting an approval outcome status clears the corresponding Select status after approve or Select status after reject field. Select a replacement before saving; otherwise, the system highlights the required field and prevents the save.
Example
The Pending Approval status uses Approve and Reject as its outcome statuses.
After Reject is deleted, saving highlights Select status after reject. Select a replacement status to continue.
Deleting the Pending Approval status
The administrator can delete any status of type Pending Approval. After deleting, all tickets on that status are moved to the status that has been set before in the Select status after reject field.
Notifications
Events and recipients
Configure notifications for approval events as described in notification configuration. The approval-specific events are:
- Ticket begining approval process - the moment when the Agent transfers the ticket to the Pending Approval type status
- Ticket approve - the moment when a positive decision is issued for a ticket
- Ticket reject - the moment when a negative decision is issued for an application
Choose users, roles or other recipients. Select Approvers to notify only the users participating in the ticket’s assigned approval configuration.
Use snippets to insert system fields in notification content. {{ApprovalLastRejectJustification}} inserts the reason from the negative decision that caused the ticket to be rejected.
Example
Create a System notification that tells approval participants why a ticket was rejected.
Open Tickets > Notifications and click PLUS. Enter a Name and mark the notification Active.
In Events, select Ticket reject.
In Receivers, select Approvers.
In Channels, select System.
Select the language.
Click plus to add the language, then Edit. Enter a Title and use the scissors icon to add {{TicketNumber}}:
Select the snippet to insert in Title.
Enter the message in Template for: system and add {{ApprovalLastRejectJustification}}.
Click Create.
The notification is saved.
When the ticket is rejected, participating agents receive a notification in Activity.
Click the notification to open the ticket, then click the bell icon:
The notification shows the full rejection reason.
Agent/Customer Profile
Agents move tickets to Pending Approval, issue decisions when they participate in the configuration and, where needed, assign Line Managers to Customers. These actions are available in the Approvals tab and ticket details.
Customers issue decisions only when they participate in the approval configuration.
Related articles
Approvals Tab
Agents and Customers can open Approvals from the sidebar to manage their approval requests and decisions.
The tab consists of three views:
- My Requests
- To Approve
- History
Management of the views is similar to that on the Dashboard tab, so we can add and sort columns, search for tickets via Search by field, sort columns and reset the settings to default with the Clear Filters button. There is also an approval counter on the sidebar which notifies an agent that there are approval tickets awaiting for his decision.
My Requests
My Requests shows tickets awaiting an Approve or Reject decision where you are assigned in the “Customer” field. The view refreshes automatically after a decision on a listed ticket.
To Approve
To Approve lists tickets awaiting your decision.
The table of tickets refreshes automatically both when new ticket for a user’s decision appears in the system and when the user has made a decision (the notification then disappears from this tab). This view also has the option of selecting tickets. Once they have been selected, two buttons appear (Approve/Reject) with which the user makes his decision.
After clicking on the Approve button, a confirmation message appears
When the Reject button is clicked, a modal appears with the reason for the rejection. Providing the reason is required to perform the action.
If a ticket is rejected as a result of a negative decision by a user, the reason for the rejection of this user is presented in the details of the relevant ticket in the section marked below
In addition, the content of the reason for rejection also appears in the article field in ticket details
History
History lists tickets on which you have made a decision. It includes the optional My decision and My justification columns.
Add these columns using Set column properties in the upper right corner.
The columns show your decision and, for a rejection, the reason entered in the Justification window.
Ticket Details
Manage approval actions directly from ticket details.
Changing the ticket status to Pending Approval
The agent transfers the ticket to Pending Approval status by changing the status in the section below:
Select a Pending Approval status from the dropdown menu.
Once the status is changed, the ticket becomes greyed out and read-only.
Approval panel in the ticket details
If the Agent is involved in the decision-making process, an additional panel appears in the section below with the option to accept or reject. The panel disappears once the Agent has made a decision
Approver history
During the approval process, after selecting the To Approve status, you can continuously view all users involved in the approval process and the complete approval configuration. This includes both users who have not yet made a decision and those who have already approved or rejected the ticket.
Once a decision has been made, the complete approval history remains available in the ticket details.
Information about the reason for rejection
If a ticket has been rejected, the section below shows the reason for rejection given by the last rejecting user
Ticket history
Ticket history records users’ decisions, rejection reasons and the final decision for the ticket.