Hello ServiceNow Community,
I have a use case where I need to streamline a flow in Flow Designer that handles multiple Service Catalog items, but I'm encountering duplication and complexity due to each catalog item needing separate subflows for processing.
Current Setup:
I have 4 maintain items (Service Catalog forms) in ServiceNow:
- Demand Intake Form
- Application Request Form
- Vendor Onboarding Form
All these forms share some common variables via a global variable set, including a Demand Type field that is used to route the request (e.g., Application Request, Vendor Request, Demand Intake).
When the catalog form is submitted on the service portal, a manual task is created on the requested item where a Demand Manager needs to confirm the Demand Type and route the request down the correct path.
The problem is, currently, each maintain item requires its own variable set and subflows, resulting in duplication of efforts and complexity as each form takes a different path based on its specific variables.
My Goals:
- I need to assign a manual task to the Demand Manager to confirm the Demand Type after submission of any one of these 4 forms.
- Based on the Demand Type confirmation, the flow should branch into the appropriate subflow (Application Request, Vendor Request, Demand Intake).
- I would like to avoid duplicating variable sets and subflows, and instead streamline the process by dynamically routing based on the confirmed demand type.
Questions:
- How can I better structure my flow to avoid duplicating subflows and variable sets for each maintain item, while ensuring that all forms follow the correct process based on the confirmed demand type?
- Is there a more efficient way to dynamically pass variables and execute subflows depending on the demand type, without having to create redundant subflows for each maintain item?
