Skip to main content

Approval

1. Node Function​

If the workflow involves approval, then you can use the approval node. It allows setting up multi-person approvals, supports consensus/sign-off approval methods, and supports settings such as approval redirection, approval comments by the approver, and handwritten signatures by the approver.

2. Node Settings​

  • Add an approval node to the process
  • Select the object to be approved
  • Set the approver
  • Methods of approval when there are multiple approvers
  • Set the operation permissions of the approver during approval
  • Set branch processes for different approval results

2.1 Add an Approval Node to the Process​

2.2 Select the Object to be Approved​

The approval object, i.e., which record data to approve, needs to be selected from the nodes in the process.

2.3 Set the Approver​

The approver can be set to custom or hierarchical departmental approval:

Custom: As shown in the figure, click add at the approver to select from members/departments/positions in the organization. The approver can be a single individual or multiple individuals.

Hierarchical Departmental Approval: Starting point: The direct department head of the specified member Endpoint: The department head of the member's superior department approves, supporting up to 20 levels to meet the approval process requirements of multi-level organizations.

Optional: Only the main department head needs to approve If not selected: Then all corresponding level department heads belonging to the initiator's departments need to approve together

2.4 Methods of Approval When There are Multiple Approvers​

When there are multiple approvers, the approval method can support multiple sign-offs and consensus.

2.4.1 Sign-off, One Person's Approval or Rejection is Sufficient​

Whoever processes the approval (approval or rejection) first, their decision is executed. Once the first person's approval result is obtained, other members need not approve anymore.

2.4.2 Consensus, All Approvers Must Approve​

Approval: Only after all approvers approve, it is considered approved. Rejection: If any one person rejects, it is considered rejected.

2.4.3 Consensus, Only One Approver's Approval is Needed, Rejection Requires Unanimity​

Approval: Whenever anyone chooses to approve, it is considered approved. Rejection: Rejection by one person does not count as rejection, only when everyone rejects is the node considered rejected. If the first person chooses to reject, it is not yet over, if the second person chooses to approve at this level, then the approval is considered passed. Only when everyone rejects unanimously, is this step considered rejected.

2.5 Set the Operation Permissions of the Approver During Approval​

2.5.1 Allow Redirection​

That is, the current approver transfers the approval authority to someone else for approval. If the approval process is A>B>C, and if A redirects to D, then it becomes A>D>B>C.

2.5.2 Allow Additional Signatures​

If you are unable to make a decision, or need someone else to assist in decision-making, you can use the additional signature function. The additional signature method is divided into after approval additional signature and before approval additional signature. For example: The original approval process is A > B > C,

  • If A chooses after approval additional signature for D, then the final process is A > D > B > C;
  • If A chooses before approval additional signature for D, then D will approve and then let A approve again. The final process is A > D > A > B > C

When we have selected allow additional signatures, allow redirection, you can see the button in the approval workflow message interface, approval result … as shown below

2.5.3 Set to Fill in Approval Comments​

Once selected, the approver needs to fill in approval comments when operating the corresponding approval result.

2.5.4 Set to Add Handwritten Signature During Approval Processing​

Once selected, the approver needs to add a handwritten signature (using the mouse on the WEB end) when operating the corresponding approval result.

2.5.6 Operation Permissions for the Approval Object​

You can also set which fields the approver can view/edit or must fill in for the approval object

2.6 Set Branch Processes for Different Approval Results​

Finally, after we have set up the approval node, we can process a branch process for the approval result. The branch node in the process node is needed for this.

First, add the branch node after the approval node Then you can choose a type of branch For example, branching by approval result, which is to process two results of approval and disapproval, and then you can continue to set the process after the result.

3. Independent Approval​

Once selected, it does not allow the approver to process approvals in batches