Flow should be created for each OrderGuide or Catalog item?

[KazukiM]

I'm planning to use OrderGuide to provide multiple catalog items in succession to a user.

Q1.

A flow is associated with 1 catalog item , is this correct?

Q2.
Should I use "cascading variables" to pass data between catalog items?

Or should I get the contents of other requested items from the "Request" associated with the requested item?

[Ankur Bawiskar · Accepted solution]

@KazukiM 

responses inline

Q1.

A flow is associated with 1 catalog item , is this correct? -> correct, but single flow can handle multiple catalog items as well but it will become tedious to maintain

Q2.
Should I use "cascading variables" to pass data between catalog items? - Using "cascading variables" is a common and effective way to pass data between catalog items in an Order Guide. Cascading variables allow values entered in the initial order form to be passed to equivalent variables in the ordered catalog items.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ankur Bawiskar · Accepted solution]

@KazukiM 

responses inline

Q1.

A flow is associated with 1 catalog item , is this correct? -> correct, but single flow can handle multiple catalog items as well but it will become tedious to maintain

Q2.
Should I use "cascading variables" to pass data between catalog items? - Using "cascading variables" is a common and effective way to pass data between catalog items in an Order Guide. Cascading variables allow values entered in the initial order form to be passed to equivalent variables in the ordered catalog items.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Mark Manders · Accepted solution]

1. yes

2. all variables that are for more than one item (like 'requested for') can be set through cascading variables. If you check on the request, you will see that you are missing information. Variables are stored on the ritm. The request is just a parent to combine all. Your logic is on the ritm (and/or tasks).

[Sanjay191]

Hello @KazukiM 

The provided statement suggests that cascading variables should be used for reusability and efficient handling of multiple catalog items in ServiceNow. Here's a breakdown of the statement:

1. Cascading Variables:
   These are variables that depend on the values of other variables in a catalog item. They create a logical flow where one variable's selection determines the options or behavior of subsequent variables. For example, selecting a department can filter available teams dynamically.

2. Reusability:
   By defining cascading variables properly, you can use them across multiple catalog items. This approach reduces redundancy, simplifies maintenance, and ensures consistency.

3. Flow Association:
   The flow (or workflow) attached to a catalog item should be designed to execute only when triggered by that specific catalog item, not others. This ensures that flows remain relevant and efficient, avoiding unintended execution on unrelated catalog items.
   
   Please Use the cascading variables and if one flow attach with one catalog it executes that not others that associate with order guide . you need to create separate flow for the each cat Items
   
   
   If my answer has helped with your question, please mark my answer as accepted solution and give a thumb up.
   Thank You