REQ Level Approval Workflow for Order Guide

[suresh_v]

I hope you are doing well.

We are in the process of implementing an Order Guide workflow in ServiceNow, and I would like to gather your inputs to finalize the approval requirements.

Below are the key points of the requirement:
• The Order Guide contains Rulebase 4 catalog items.
• Approval must be handled at the Request (REQ) level, not at the RITM level.
• Approval routing should depend on the Order Guide variable “Associate Type”
If Associate type is select box and dropdown values is -- Company1 & Company2

If based on associate type is selected approvals goes to Company1 -- L1 & Comapny2 -- L2

• The approval process should follow two levels:

• L1 approval → if approved, proceed to L2.
• L2 approval → if approved, all RITMs should proceed to their fulfillment workflows.

[Dr Atul G- LNG]

Hi @suresh_v 

In order to understand this, you need to keep in mind that once the catalog item is submitted, the associated Flow is attached to the RITM.
Whether the approval happens on the REQ or the RITM depends on how the Flow is designed — and that’s expected behaviour by design.

If Associate type is select box and dropdown values is -- Company1 & Company2

If based on associate type is selected approvals goes to Company1 -- L1 & Comapny2 -- L2

You can easily handle this. Use the “Get Variables” action to retrieve the Company value, and then use an If condition to define the approval logic based on that value — completely doable.

[suresh_v]

Hi @Dr Atul G- LNG 

When i created this REQ level workflow based on variable if condition i mentioned and first i mentioned Run script for particular order guide only trigger this approval part.

whenever i raised any catalog item in DEV instance in REQ level asking for approval it is impacted to all catalog items.

[Dr Atul G- LNG]

Hi @suresh_v 

That will work because your approval is configured at the Request (REQ) level, so it is expected.