Approval Process Handling

1. Handling Approval Nodes

• Actions: You can process approval workflow tasks on the workflow details page. Supported actions include Agree, Reject, Reassign, Reply, Withdraw Approval, Retrieve, Discuss, Add Signatory, and Mark as Read (button visibility may vary based on user roles).
  • Agree: The “Agree” button is displayed in the node configuration, and only the current node approver can click it.
  • Reject: The “Reject” button is displayed in the node configuration, and only the current node approver can click it.
  • Reassign:
    • By default, CRM Admins, Data Owners, and node approvers can reassign tasks.
    • For Data Owners and node approvers: The “Reassign” button is visible only if the “Reassign Approval Flow Approver” permission is enabled under the trigger object’s business function permissions.
    • CRM Admins: Automatically have the “Reassign Approval Flow Approver” permission and can reassign regardless of node configuration.
  • Withdraw:
    • By default, CRM Admins, Data Owners, and workflow initiators can withdraw approvals.
    • The “Withdraw” button must be enabled in the node configuration.
  • Add Signatory: The “Add Signatory” button is displayed in the node configuration, and only the current node approver can click it.
  • Retrieve:
    • The “Retrieve” button is displayed in the node configuration, and only the current node approver can click it.
    • Scenarios where retrieval is not allowed: a. Advanced settings do not enable “Allow Approver to Retrieve for Re-review” or “Allow Approver to Retrieve After Auto-Approved Node.” b. Legacy Opportunities do not support retrieval. c. Current task and previous task involve resubmission. d. No predecessor task (previous node may be the start node). e. Previous task is an Add Signatory node. f. Previous task is a Joint Approval node. g. Previous task is a Sequential Approval node. h. Previous task is a Rejected node. i. Previous task is a Withdrawn node. j. Auto-approval is not enabled, and the previous task was auto-approved. k. Previous task is a Waiting node. l. Previous task is a Subprocess node. m. Current task status is not “In Progress.” n. Current task has already been processed (Joint Approval or Approval). o. Current task approver is not the same as the previous node approver. p. Current task has a form that has been edited. q. Current task is a Parallel node. r. Current task has already been replied to. s. Current task is a Waiting node. t. Current task is a Free Flow task. u. Current task is a Subprocess node. v. Parallel nodes are two sequential collaborative tasks. w. Retrieval to nodes within a parallel node is not allowed.
  • Mark as Read: The “Mark as Read” button is displayed in the node configuration, and only users who are CC’d on the current node can click it.

picture coming soon:

2. Handling Task Collaboration Nodes

• Supported actions include Complete, Reassign, Reply, Withdraw Approval, Discuss, and Add Signatory (button visibility may vary based on user roles).
  • Complete: The “Agree” button is displayed in the node configuration, and only the current node approver can click it.
  • Reassign:
    • By default, CRM Admins, Data Owners, and node approvers can reassign tasks.
    • For Data Owners and node approvers: The “Reassign” button is visible only if the “Reassign Approval Flow Approver” permission is enabled under the trigger object’s business function permissions.
    • CRM Admins: Automatically have the “Reassign Approval Flow Approver” permission and can reassign regardless of node configuration.
  • Add Signatory: The “Add Signatory” button is displayed in the node configuration, and only the current node approver can click it.
  • Withdraw:
    • By default, CRM Admins, Data Owners, and workflow initiators can withdraw approvals.
    • The “Withdraw” button must be enabled in the node configuration.

picture coming soon:

3. Handling Waiting Nodes

• Click Execute Now to skip the waiting period and proceed with the workflow.
• If the current user’s role does not have the “Execute Waiting Node Immediately” permission under business function permissions, the “Execute Now” button will be disabled.
• If a post-action function is configured and fails, users must have either the “Business Function Permissions” or “Ignore Approval Flow Post-Action Errors” permission to click “Ignore” or “Retry.”

picture coming soon:

4. Additional Notes

• Once an approval workflow is completed (e.g., approved and closed, withdrawn, or rejected and closed), it cannot be withdrawn again. To modify data after approval, configure an edit-triggered approval workflow. Editing the data will automatically trigger the applicable workflow.

picture coming soon: