Skip to content
Mint Service Desk Documentation centre

Configuration Tree

Build approval rules from users, roles, line managers and AND/OR operators. Set the number or percentage of decisions needed to approve or reject a ticket.

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.