Conga Approvals offers the ability to set up approval processes not currently supported by Salesforce. This gives you more flexibility and visibility into approval process configuration, helping overall compliance.
Approval steps assign approval requests to users and define the chain of approval for a particular approval process. Each approval step specifies the attributes a record must have to advance to that approval step, the user who can approve requests for those records, and whether to allow backup assignees of the approver to approve the requests. Regardless of process complexity, when anyone in the process rejects an item, the entire process is considered rejected.
Configuring multiple approval processes reduces number of approval steps and criteria the system must execute. Use multiple approval processes for region-based, business-unit-based, or channel-based approval variations. When configuring multiple approval processes, define mutually exclusive process entry criteria so that only one process is selected for a given primary object instance.
Approval rule entry criteria
Specify minimum approval conditions in approval rule entry criteria for subprocess or child process steps to avoid evaluating all approval rule entries every time.
Approval required check
Shows users whether approval is needed for headers or line items without executing the entire approval process. Provides a mechanism to avoid approval process evaluation in many scenarios.
Types of approval steps and when do I use them?
Standard: This is the existing method for creating header-level approval steps.
Subprocess: Use this to select approval rules associated with the approval process's header-level context object. The assignee types are derived from the approval rule. Create a subprocess when you have multiple approvers for a set of criteria instead of defining multiple standard steps for each criterion.
Child Process: Use this to select approval rules associated with child objects of the approval process's header-level context object, for example, to define an approval process for proposal and proposal line items. The assignee types are derived from the approval rule. Use a child process instead of a subprocess and standard step type when you want to populate the approval request with the child object line items to be approved, such as proposal line items.
It's best to use conditional criteria instead of approval dimensions and an approval matrix when creating approval rules and processes.