Approval based on choice table selection

[Cat]

Hi all,

I have a requirement to get 2 approvals based on a selection on a table. Each selection requires two different (named) users to approve it.

How can I get this to work? Generally approvals ask for specific approvers in groups, but that would be right in this case as it depends specifically on what they choose.

Thanks,

Cat

[Ankur Bawiskar]

@Cat 

you can use scripted approval in flow

check this

Scripted Approvals in Flow Designer with Flow Variables 

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Tanushree Maiti]

Hi Cat ,

Here assumption is that your custom lookup table has these 2 fields (e.g u_approver1, u_approver1) that reference the user(sys_user) table.

1. Create the Flow: Trigger the flow on Catalog Item submission.
2. Get Catalog Variables: Fetch the user's selection from the form.
3. Look Up Record: Use the Look Up Record action to find the row in your custom table that matches the user's selection.
4. Ask for Approval: Add the Ask for Approval action.
   • In the Approver field, drag the data pills for u_approver1 and u_approver2 from the Look Up Record step.
   • Set the approval rule to Everyone must approve.

[Sujit Jadhav]

Hello @Cat ,

Recommended Approach: Use Flow Designer

Steps:

1. Trigger

• Table: Your request or target record table
• Trigger condition:
  • On Insert, or
  • On State change (for example, Requested → Awaiting Approval)

---

2. Look up approvers

• Use the “Look Up Records” action
• Table: Approval mapping table (as per requirement)
• Retrieve the approvers based on the selected value on the record

---

3. Create approvals

• Use the “Ask for Approval” action
• Approval type: User
• Approvers:
  • Data.u_approver_1 (example)
  • Data.u_approver_2 (example)

---

4. Approval behavior

Choose the appropriate approval condition:

• All must approve – if both approvers are mandatory
  OR
• Any approver – if a single approval is sufficient

---

5. Post‑approval logic

• If Approved: Proceed to the next step in the process (update state, continue workflow, etc.)
• If Rejected: Update the record state accordingly and notify the requester
  
  

  "If you found my answer helpful, please like and mark it as an "accepted solution". It helps future readers to locate the solution easily and supports the community!"

  Thank You,

  Sujit Jadhav