I. What is a Handler

A handler can only confirm handling and cannot reject an approval form.
The role of a handler is applicable in scenarios such as reimbursement and payment, where the cashier receives the documents and proceeds with the payment. In this case, the handler only needs to perform and submit the handling results without the need to approve or reject the request. When the approval process reaches the handler node, the handler will receive a notification for pending handling. Upon receiving the documents, the handler can submit handling comments and confirm the action as required on the approval form details page.

II. Configure Handlers

1.Operation Path

In the Admin Console, admins can choose “App Management” -> “Approvals”, and then click an approval template to enter its details page. On the “Rule Settings” tab, click “Setting” of “Approval process” to enter the process settings page, and then click the plus sign (+) to add a handler node in an appropriate position.

2.Configure/Modify a Handler Node

There are multiple types of handler nodes, and the assigned handlers will vary for each type.
a) Specified members
Admins can specify the handlers for this node, and all applicants will have the same handlers at this node.
When multiple members are specified, you can specify “Agree by Anyone”, “Agree by Everyone”, or “Approve in Sequence”.

b) Specified department heads
To use this feature, you need to set heads for departments in Contacts.
You can specify a header at a certain level, and the department head will be automatically set as the handler based on the Contacts settings and the department of the employee.
From bottom to top: Starting from the department head of the applicant, the application goes from the department of the lower level to that of the higher one. A head of Level 3 is higher than that of Level 2.
From top to bottom: Starting from the head of top department, the application goes from department of the higher level to that of the lower one. A head of Level 2 is higher than that of Level 3.
If there are multiple heads at the same level, the handling will be based on the “Agree by Everyone” or “Agree by Anyone” setting.

c) Specified tag
To use this feature, you need to set tags in Contacts.
After a tag is specified, all members within that tag will be assigned as handlers by default. You can select “Agree by Anyone” or “Agree by Everyone”.

d) Applicant
The handler for the node is the applicant themselves.

e) Selected by Applicant
The applicant can select the handler for the node when submitting an application.
Unlimited: The applicant can select any member they can view in the Contacts as a handler.
Specified Scope: The applicant can only select handlers from a specific group of members.
Single-Select: The applicant can only select one member as the handler.
Multi-Select: The applicant can select multiple members as the handlers, where the application will be handled based on the configured method (“Agree by Anyone”, “Agree by Everyone”, or “Approve in Sequence”).

f) Linked member control
The members required to be provided in the template control can be linked as handlers of the node. If the applicant selects a member in the template control, the member will also be set as a handler for this approval node.

3.Methods for addressing member exceptions in the handler node

In the Admin Console, admins can go to “App Management” -> “Approvals”, click an approval template -> “Rule Settings”, and set the exception handling methods in the handler node under “Exception Handling”.

The following methods are supported:

• When no handler is available: You can set it to automatically approve or assign it to a specified person.
• When the handler has left the company: You can set it to remind the admin for manual handover or automatically assign it to a specified person.
  
  Admins can also enable handling comments in the approval settings. Once it is enabled, the handlers are required to provide comments when submitting the handling results.