Conga Approvals offers the ability to set up approval processes that Salesforce does not support. It enables you to configure approval processes with greater flexibility and visibility, helping in overall compliance.

Approval steps assign approval requests to various 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 their complexity, when anyone in the process rejects an item, the entire process is considered rejected.

To modify an approval process, you can quickly navigate between pages in the approval process setup menus using the navigation chevrons. These chevrons speed navigation to specific approval properties to edit them. They also eliminate the need to start from the beginning and traverse all the way through to find the page you want to edit and save.

Performance and Scalability

Multiple Approval Processes

Configuring multiple approval processes reduces number of approval steps and criteria the system must execute. Use multiple approval processes when you have region-based, business-unit-based, or channel-based approval variations.

To configure 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 CriteriaSpecify minimum approval conditions for sub-process or child process steps to avoid re-evaluating all approval rule entries at each step.
Approval Required CheckGives users visibility into whether approval is required for header or line items without executing the entire approval process. Provides a mechanism to avoid approval process evaluation for many scenarios.

Types of Approval Steps and When to Use Them

  • Standard: This is the existing method for creating header-level approval steps.
  • Sub Process: Use this to select approval rules associated with an approval process's header-level context object. The assignee types are derived from the approval rule. Create a sub-process 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, such as when you want to define an approval process for a proposal and proposal line items. Assignee types are derived from the approval rule. Use a child process instead of a sub-process or standard step type to populate the Approval request with child object line items to be approved, such as proposal line items.

It's best to use conditional criteria instead of approval dimensions or an approval matrix when creating approval rules and processes.