Read this article to set up the CC Description in the Approval Process Design.
Follow these steps to understand how the administrator can initiate CC, node CC and end CC when the approval needs to be notified or filed.
The scope of the relevant personnel mainly includes: administrators, CCs and approvers.
The "Operational Flow Description" of this article supports the console including Windows/Mac/iOS/Android/Web.
Step 1: Start a CC
During process design, the administrator can set the CC to set up the CC, and the CC has 6 roles to choose from.
After the sponsor initiates the process, the CC will receive a notification and can view all the CC processes in the list of the “CC” of the approval applet. One process is only copied once.
Step 2: Node CC
During the approval process, if it is necessary to synchronize the approval status of some nodes to other personnel other than the approver, the administrator can add the CC to the intermediate approval node.
The CC person can view all the processes that are copied in the list of the approval applet "CC ME", and one node only copies it once.
By default, you only choose to copy when you agree. After the approval of this node is passed, you will notify the CC person and refuse to send CC. If you do not select CC only when you agree, the CC will be notified when the node ends, regardless of whether the approver agrees or rejects it.
Step 3: End CC
The administrator can set the CC person after the approval is completed. After the approval is passed, the CC will receive the notification.
The administrator can also view all the CC processes in the list of the copy applet "CC", one process is only copied once.
Frequently Asked Questions
3.1 Set the CC file problem
The administrator can set the CC who after the approval is submitted (initiated CC), after the end of the intermediate node (node CC), and after the approval is completed (end CC), the CC cannot operate the process, but will receive Notice.
3.2 Free copying problem
In addition to the above-mentioned CCs that are automatically copied by the administrator, at any point after the approval is initiated, the approver and the sponsor can click CC on the operation bar below the approval details page to copy the approval flow. Give any person.
Completed approvals can also be copied.
3.3 How to define node end problem
After the node approver agrees/rejects, the node ends.
The node approver is handed over to another person, and after the transferee agrees/rejects, the node ends.
The node approver adds the signature. If it is the pre-addition, the node is approved and the node approver agrees/rejects the operation and the node end. If it is post-addition and sign-on, the node approver agrees/rejects after the operation is signed, and the node ends. Note: If the previous signing node refuses and cannot reach the node where the CC is located, it will not be copied.
The node approver rolls back, the retired node re-approves, and the flow goes to the node where the operation is rolled back. After the node approver agrees/rejects, the node ends.