Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Salesforce Administrator
hard

How would you implement a tiered approval where the threshold determines the path?

Concrete scenario: Discount Approvals.

  • 0-10% discount: auto-approved, no approval needed.
  • 11-25% discount: Sales Manager approves.
  • 26-50% discount: Sales Manager AND Director approve.
  • 51%+: VP approves.

Implementation options:

Option A — Single Approval Process with conditional steps (Approval Process):

  1. Create one Approval Process on the Opportunity (or Quote) object.
  2. Entry criteria: Discount__c > 10 (skip the process for sub-10% deals).
  3. Step 1: criteria Discount__c > 10 AND Discount__c <= 25 -> Manager approval. If approved, exit (final approval action).
  4. Step 2: criteria Discount__c > 25 AND Discount__c <= 50 -> Director approval. If reached, requires Manager (Step 1) AND Director.
  5. Step 3: criteria Discount__c > 50 -> VP approval, bypassing earlier steps.

Constraint: Approval Processes evaluate steps in order, and each step's criteria gates whether it applies. The "all of steps 1+2+3 for higher tiers" pattern works as long as the criteria are properly chained.

Option B — Flow Orchestration (modern):

Use Flow Orchestration to model the multi-stage approval as a Flow with stages, each stage being a Decision (which tier?) feeding into the appropriate Submit-for-Approval invocations. More flexible: you can branch on any criteria, integrate with chat for notifications, time-out and escalate, all declaratively.

Option C — Custom routing via Flow + Approval Process:

A record-triggered Flow on Opportunity that evaluates the discount and submits to one of three pre-built Approval Processes (small / medium / large discount). Each Approval Process has its own approval ladder. The flow picks the right one. Simpler to maintain than Option A's nested approval steps.

Recommendation:

  • For new builds, use Flow Orchestration (Option B) — it's where Salesforce is investing.
  • For existing orgs already on Approval Processes, keep them and use Option A or C, depending on complexity.
  • Don't try to do it purely in Approval Process steps with elaborate criteria if the logic is non-linear; Flow gives you cleaner branching.

Why this answer works

Architectural question. Tests whether the candidate can compose primitives. Strong answers acknowledge multiple options and pick based on org maturity. Mentioning Flow Orchestration shows current platform awareness.

Follow-ups to expect

Related dictionary terms