approval

shamsuddinm
Tera Contributor

I’m working on a requirement where the Assigned To user completes their work on the RITM, and then changes the State to "Pending Closure Approval".
At this point, a Flow needs to trigger and send an approval request to the Assigned To user’s manager.

1 ACCEPTED SOLUTION

Matthew_13
Mega Sage

Hi Buddy,

Here’s the straightforward way to do it:

  1. Build a Flow on the RITM

  • Table: Requested Item (sc_req_item)

  • Trigger: Record Updated

  • Condition: State changes to “Pending Closure Approval”

  1. Grab the manager

  • The manager is on the Assigned To user record:

    • Assigned to → Manager

  • In Flow, you can usually dot-walk it directly. If not, do a quick Look Up Record on sys_user using assigned_to and pull the manager field.

  1. Send the approval

  • Use Ask for Approval

    • Record: the RITM

    • Approver: Assigned To’s Manager

  • Then branch on the result:

    • Approved → move the RITM to the next “closed/complete” state

    • Rejected → move it back to “in progress / needs rework” and notify the assignee

One important thing so it doesn’t spam approvals:

  • Before you request approval, add a check for an existing approval for that RITM (requested/active). If one exists, don’t create another.

Thats basically it: trigger on the state change, pull assigned_to.manager, create the approval, then handle approved/rejected.

 

@shamsuddinm - Please mark Accepted Solution and Thumbs Up if you found Helpful!

MJG

View solution in original post

2 REPLIES 2

Matthew_13
Mega Sage

Hi Buddy,

Here’s the straightforward way to do it:

  1. Build a Flow on the RITM

  • Table: Requested Item (sc_req_item)

  • Trigger: Record Updated

  • Condition: State changes to “Pending Closure Approval”

  1. Grab the manager

  • The manager is on the Assigned To user record:

    • Assigned to → Manager

  • In Flow, you can usually dot-walk it directly. If not, do a quick Look Up Record on sys_user using assigned_to and pull the manager field.

  1. Send the approval

  • Use Ask for Approval

    • Record: the RITM

    • Approver: Assigned To’s Manager

  • Then branch on the result:

    • Approved → move the RITM to the next “closed/complete” state

    • Rejected → move it back to “in progress / needs rework” and notify the assignee

One important thing so it doesn’t spam approvals:

  • Before you request approval, add a check for an existing approval for that RITM (requested/active). If one exists, don’t create another.

Thats basically it: trigger on the state change, pull assigned_to.manager, create the approval, then handle approved/rejected.

 

@shamsuddinm - Please mark Accepted Solution and Thumbs Up if you found Helpful!

MJG

shamsuddinm_0-1769263800697.png

In this flow, after the approval is rejected, the RITM correctly moves back to Work in Progress. However, when it is sent again for approval, and the approver approves it, the RITM state does not change to Closed Complete as expected.