Characteristics | Approval process | Review process |
Execute on | Record creation and edit. | Applies to all records that enter the CRM system. |
Modules | Standard and custom | Standard and custom |
Entity (records or fields) for approval | A record is considered for the approval process. | Fields of a record will be considered for review. |
Field level approval/rejection | Not allowed | Allowed. Individual fields can be set for review process. Each field should be approved/rejected by the reviewer. |
Layout specific | No | Yes. You can configure review processes for each layout. |
Who can be selected as approvers or reviewers? |
|
|
How many approvers or reviewers are allowed? | Multiple | Multiple |
Approval needed from all approvers or reviewers? | Depends on the configuration. Configure whether the record should be approved by:
| No. Records can be reviewed by any reviewer. It is not mandatory for all the reviewers to mark a record as approved or rejected. Anyone can review the record. |
No. of approvers/reviewers allowed | Maximum 10 | Maximum 5 |
Notification upon record submission | System generated email notification is sent only to the record approver. | A notification will be sent both to the record submitter and the reviewer only if notification is configured while setting up the review process. |
Action for the approver/reviewer | Task can be assigned to the approver that they need to perform upon approving a record | Action cannot be assigned to a reviewer |
Action on approval/review of a record (based on configuration) | Following actions will take place upon approval of a record:
| Notification can be sent to the record submitter, reviewer, and CRM administrators once the record is reviewed and approved. |
Actions on rejection of a record (based on configuration) | Below actions will take place automatically upon rejection of a record:
| Notification can be sent to the record submitter, reviewer, and CRM administrators once the record is rejected. |
Reason for rejection | Approver can enter a reason before rejecting a record. | Following pre-defined reasons can be configured:
You can configure custom reasons too. |
Resubmission | Can be resubmitted | Can be resubmitted
|
Criteria for record entry | Can be configured | Can be configured |
Records outside of criteria | Will not be considered for approval | Can be assigned to a user for review |
Timeline for completion of approval | No set timeline | Can define the number of days in which the review should be completed. |
SLA escalation | Cannot be configured | Can be configured. The chosen user will be sent a notification after the review completion time exceeds. |
Delegate records to other users | Yes. Can delegate a record to another user for approval | No. Cannot delegate a record to another user. |
Process reordering | Yes | Yes |
Reports | No | Yes. Following predefined reports are available:
|
Deletion of process | Yes. The records awaiting for approval will be locked and the approver has to approve them. | Yes, only if there are no records waiting for review. |
Deactivation of process | Yes. The records waiting for approval would be locked. They can be approved or rejected from the list view. | Yes. The records waiting for review can be:
|
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
You are currently viewing the help pages of Qntrl’s earlier version. Click here to view our latest version—Qntrl 3.0's help articles.