I. Methods for dealing with unusual situations such as no members within the approval and processing steps, and termination

1. Configure exception handling rules in advance

In the case of no members within the approval and processing steps or upon termination, the approval process is allowed to proceed continuously. The administrator can set the handling methods for such situations in the approval rule settings.
(1) Methods for handling exceptions at the approver step:
When there is no member, it is possible to set “Auto-approve” or “Transfer to a designated person for handling”. If the designated member is also abnormal, it will be automatically approved.
When a member resigns, it supports setting “Remind the administrator to conduct manual handover” or “Automatically hand over to a designated person”. If the designated member also resigns, the administrator will be reminded to conduct manual handover.
(2) Methods for handling exceptions at the handler step:
When there is no member, it is possible to set “Auto-approve” or “Transfer to a designated person for handling”. If the designated member is also abnormal, it will be automatically approved.
When a member resigns, it supports setting “Remind the administrator to conduct manual handover” or “Automatically hand over to a designated person”. If the designated member also resigns, the administrator will be reminded to conduct manual handover.

Note: The configured exception handling rule will be triggered only when an exception occurs in nodes not yet gone through.

For example, for an approval process (A>B>C>D) where node B is under approval, the exception handling rule will be triggered if C or D resigns at this moment, but will not be triggered if B resigns.
Paths:

In the Admin Console, go to “App Management” -> “Approvals”, select a template to enter its details page, click “Rule Settings”, and select an option under “Exception Handling”.

In the WeCom app, go to “Workspace” -> “Approvals” -> “Management” -> “Document Template Management”, select a template, tap “Edit” -> “Rules” -> “Exception Handling”.

2. One-click handover after resignation or permission changes of employees

When an employee leaves the company or their permissions change, admins can log in to the admin console, choose “App Management” -> “Approvals” -> “Approval Handover”, and then hand over the approval documents and processes owned by the employee to others.
Note: If any approval application has not been transferred to the employee during handover, this application will not be regarded as their assets to be handed over. In this case, hand over the application again after it has been transferred to the employee.
For approval handover, only the processes where the roles configured in the approval/cc nodes are “designated members” can be searched. The handover is not supported for other roles (department heads, direct supervisors, designated tags, etc.).

II. Department head was skipped for leave approval

1. This condition may occur when the applicant modified the approver themself, since permissions to modify the approver are not disabled.
2. If department head has been set as an approver node but no department head exists, no approver will be displayed on the WeCom app. In this case, the approval node will be handled based on the exception handling rule configured.
3. If the approver configured does not match any approver in Contacts, check whether a tag named “Superior” has been configured as the approver.

III. Approver/CC recipient of an approval form does not match that configured by admins

1. This condition may occur when the applicant modified the approver or CC recipient themself, since permissions to modify the approver/CC recipient are not disabled.

2. This condition may also occur when admins modify approver settings after the applicant submitted the approval form.
3. Another possible reason is that the applicant hit “Approval Conditions“. The applicant hit approval process B while the admin thought process A should be used.