Setting Approval at sc_request instead of sc_req_item

[Brian Hofmeiste]

Hello all,

I'm trying to set approvals at the sc_request level instead of sc_req_item.  At a high level I understand I just create a workflow that triggers on the sc_request table but all examples I've seen are evaluating if approval is needed based on price.  We don't care about price so much.  When creating the catalog item we'd like to specify which ones require manager approval and which ones don't.  How do you achieve this?

Brian

[RaghavSh]

If you dont want the price, you can remove that from the workflow on sc_request and add or edit the approval activity.

The only problem here is that the workflow you attach on catalog item works at RITM level, so you cant have a different  request workflow for every catalog item.

If your requirement is such, that all your requests will require same set of approvals (dynamic or static) you can go ahead with it.

[Brian Hofmeiste]

Let me get give you exact scenario.  

1. We have a catalog item called "Get Travel account" which requires manager approval
2. We have a catalog item called "Get Credit card" which requires manager approval
3. We have a catalog item called "Get security badge" which does NOT require manager approval.

Using these catalog items independently works fine.  But when i group them in to an order guide the manager gets two separate approval requests, 1 for travel and 1 for credit card.  This seems redundant and unncecessary so I was trying to remote the approval workflows from the catalog item workflows and place the approval flow one level higher - at the Request.  The only issue with this is that I need to check if any of catalog items in the order guide will require a manager approval.  That is where I'm getting stuck.