Approval Process Handling

1. Handling Approval Nodes

• Operation: You can process approval tasks on the approval process detail page. Supported actions include Agree, Reject, Change Assignee, Reply, Withdraw Approval, Retrieve, Discuss, Add Signer, and Mark as Read (the buttons shown may vary by Role).

• Agree: The node must be configured to show the “Agree” button, and only the current node Assignee can click Agree.

• Reject: The node must be configured to show the “Reject” button, and only the current node Assignee can click Reject.

• Change Assignee:
  • By default, CRM Administrators, Data Owners, and the node Assignee can click Change Assignee.
  • Data Owners and node Assignees: to click Change Assignee they must have the business permission “Change approval process assignee” under the relevant trigger object, and the node must be configured to show the Change Assignee button.
  • CRM Administrators: by default possess the business permission “Change approval process assignee” and can change the assignee regardless of whether the node shows the Change Assignee button.
• Withdraw (撤回):
  • By default, CRM Administrators, Data Owners, and the process Initiator can click Withdraw.
  • The node must be configured to show the Withdraw button.

• Add Signer (前加签): The node must be configured to show the “Pre-Add Signer” button, and only the current node Assignee can click it.

• Retrieve (取回): The node must be configured to show the “Retrieve” button, and only the current node Assignee can click it.
  • Scenarios where Retrieve is not allowed: a. Advanced definition not configured to allow approver retrieve for re-review or allow approver retrieve after automatic-pass nodes for re-review
    b. Legacy Opportunities do not support Retrieve
    c. Current task and previous task have been resubmitted
    d. No prior task (previous node may be the start node)
    e. Previous task was an Add Signer node
    f. Previous task was a Countersign node
    g. Previous task was a Hierarchical Approval node
    h. Previous task was a Rejected-to node
    i. Previous task was a Withdrawn-to node
    j. Auto-pass node not enabled and previous task was an auto-pass node
    k. Previous task was a Waiting node
    l. Previous task was a Subprocess node
    m. Current task status is not In Progress
    n. Current task has already been processed (countersign or approval)
    o. Current task Assignee is not the same as the previous node’s Assignee
    p. Current task has a form and the form has been edited
    q. Current task is a Parallel node
    r. Current task has already received a Reply
    s. Current task is a Waiting node
    t. Current task belongs to a Free-flow process task
    u. Current task is a Subprocess node
    v. Parallel nodes implemented as two sequential collaborative tasks
    w. Retrieve back into nodes inside a Parallel node is not allowed
• Mark as Read: The node must be configured to show the “Mark as Read” button, and only a logged-in user who was CC’d to the current node can click it.

• Agree

2. Handling Collaborative Task Nodes

• Supported actions include Complete, Change Assignee, Reply, Withdraw Approval, Discuss, and Add Signer (buttons may differ by Role).

• Complete: The node must be configured to show the “Agree” button, and only the current node Assignee can click Agree.

• Change Assignee:
  • By default, CRM Administrators, Data Owners, and the node Assignee can click Change Assignee.
  • Data Owners and node Assignees: to click Change Assignee they must have the business permission “Change approval process assignee” under the relevant trigger object, and the node must be configured to show the Change Assignee button.
  • CRM Administrators: by default possess the business permission “Change approval process assignee” and can change the assignee regardless of whether the node shows the Change Assignee button.

• Add Signer (Pre-Add Signer): The node must be configured to show the “Pre-Add Signer” button, and only the current node Assignee can click it.

• Withdraw:
  • By default, CRM Administrators, Data Owners, and the process Initiator can click Withdraw.
  • The node must be configured to show the Withdraw button.

3. Handling Waiting Nodes

• Click Execute Now to skip the wait and continue the process.

• A logged-in user whose Role lacks the business permission “Approval process waiting node execute now” for the current trigger object cannot click Execute Now.

• If a post-action function is configured and it fails, users need either the current trigger object’s business permissions or the “Ignore approval process post-action exceptions” permission to click Ignore or Retry.

4. Additional Notes

• After an approval process completes (for example: Agree and end process, Withdraw process, or Reject and end process), you cannot withdraw it again.
• If you need to adjust data that belongs to a completed approval, configure an approval process triggered on edit; editing the data will then automatically trigger any matching processes.