How-to Guides · LessonBy Sneha I, ServiceNow Trainer, 8 yrs · Published · ServiceNow · all levels
Build a catalog variable set
Create a variable set once and use it across catalog items without copy and paste.
Quick answer
Create a variable set once and use it across catalog items without copy and paste.
Key takeaways
- Variable sets carry their own policies and scripts
- Stable variable names keep flows and reports working
- One purpose per set keeps reuse clean
- A change affects every item that includes it
Plan the block
Identify variables that repeat across items, for example requester details, cost centre and delivery location. Those belong in a single variable set that every relevant item includes.
Build it
Create the variable set, add the variables with stable names, and add any catalog client scripts or catalog UI policies inside the set so behaviour travels with it. That last part is what most people miss and why copied blocks drift apart.
Use it well
Keep the set focused.
- One purpose per set, do not build a set of everything
- Name variables predictably so flows and reports can rely on them
- Test on two different items, behaviour sometimes depends on item context
- Version carefully, a change affects every item that includes the set
Practice challenge
+0 XPStreak ×0
Question 1 of 2
What travels with a variable set besides variables?
Frequently asked questions
Can a set be conditional?
Yes, variable sets support conditions so the block only appears when relevant.
What breaks when I rename a variable?
Flows, reports and any script that references the name. Renaming is a coordinated change, not a cosmetic one.