Sourcing request and approvals help

[IssacR]

I am implementing HAM for the first time and am looking for advice and best practice tips for utilizing sourcing task and approvals for our catalog items. There are some items that require approval from certain groups and other items from other groups. The issue I face is what is the best way to define these approvals on an item by item basis when the sourcing task is created once the Request itself is approved.

For example, a user requests Item A and Item B in one REQ. Item A needs approval from Group A and Item B needs approval from Group B & C. I can easily ask for approvals in flow designer but these approvals are triggered AFTER the sourcing task is created because the parent REQ is approved. Any suggestions?

[Singh Manish]

Hello @IssacR ,

Is it possible to assign validation on Req item, If user approve Req item A then they can proceed and cancel for other Req item 'B' if user reject.
I wanted to more about the flow which you are trying to implement.

Thank you.

[IssacR]

Thank you for the response Singh. I'm trying to implement a flow for standard hardware asset requests. Basically, a computer will need approval from Asset Management, CIO and the users manager, while the CIO will not need to approve a request for a keyboard or mouse. 

We can setup approvals on the item with no issue but the workflow for each item is not triggered until the parent Request is approved, which is also what triggers the sourcing task.

[DavidWallace1]

What I have done in the past is to create a custom report/dashboard widget for the warehouse team (who action the sourcing tasks), so that they don't see the sourcing task until after the parent request is approved. It just prevents them from going and processing the sourcing task before the approval, and so if the approval gets denied having wasted effort.

It is a weird situation caused by the sourcing task being on the parent request rather than there being one on each request item.