Setting Up an Ad Hoc Approval Process in Runtime
You can create and modify an ad hoc approval process in runtime. You can preview and save all approval requests with comments and attachments. You can also configure ad hoc approvers - parallel or sequential. Save and preview them all at the same time on the Preview Submit Approval page. You can preview and submit approvals for complex processes.
To configure ad hoc approvers from runtime
Use Case: Ad Hoc Approval Process for Agreement Approvals
Business Context
Standard rule-based approval processes, like the one built in Use Case: Submission Comments and Attachments for Agreement Approvals, work well for repeatable scenarios. Some situations, however, need an approval path that cannot be predicted in advance. Conga Approvals provides an Ad Hoc Approval Process for this: an administrator activates a separate Ad Hoc process type for an object, and once active, a submitter can use Create Adhoc Process on the Preview & Submit Approvals page to build an entirely custom, one-time approver chain in place of the standard process, before the record is submitted.
Overview
This use case shows how to configure and use an Ad Hoc Approval Process.
This use case assumes that a standard rule-based approval process already exists and is active for the Agreement object, as built in Use Case: Submission Comments and Attachments for Agreement Approvals. The Ad Hoc Approval Process configured here runs alongside that process; it does not replace it. The steps below assume the following configuration already exists and is active:
Approval process: High-Value Agreement Approval (Rule Driven, Agreement, Entry Criteria Total Agreement Value > 200000), Activated.
Persona (Administrator)
| Field | Details |
|---|---|
| Name | Tom Bradley |
| Role | Approvals Administrator, TechNova Solutions |
| Goal | Activate an Ad Hoc Approval Process for the Agreement object so that submitters can manually build a one-time approver chain at runtime for non-standard Agreements. |
Persona (End User)
| Field | Details |
|---|---|
| Name | Claire Thompson |
| Role | Legal Counsel, TechNova Solutions |
| Goal | Create a one-time approval path for a multi-jurisdictional software license agreement that involves regional legal and finance reviewers not included in the standard approval process. |
Scenario
Tom Bradley activates an Ad Hoc Approval Process for the Agreement object. Later, PrimeEdge is finalizing a Software License Agreement that spans the USA, Germany, and India. The standard High-Value Agreement Approval process does not include regional reviewers for cross-border Agreements, so Claire Thompson, Legal Counsel, uses the ad hoc process to add jurisdiction-specific approvers for this one deal, without modifying the standard workflow.
Prerequisites
An active rule-based approval process for the Agreement object already exists in your org, as built in Use Case: Submission Comments and Attachments for Agreement Approvals.- Agreement records that fall outside the standard High-Value Agreement Approval process can still be routed for approval, using a fully custom, one-time chain of approvers built by the submitter at runtime.
- The standard High-Value Agreement Approval process defined in Use Case: Submission Comments and Attachments for Agreement Approvals is not modified — the Ad Hoc Approval Process runs alongside it as a separate process type, used only when a record does not fit the standard path.
