Build a catalog variable set
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
Want to learn this properly?
Our live, instructor-led ServiceNow Training covers this hands-on, with real projects and a certification path.
Check your understanding
What travels with a variable set besides variables?
- A. Nothing
- B. Its catalog client scripts and UI policies
- C. The workflow
- D. The category
Show answer
B. Its catalog client scripts and UI policies
Behaviour defined inside the set is reused with it.
Why keep variable names stable?
- A. Performance
- B. Flows and reports reference them
- C. Storage
- D. Licensing
Show answer
B. Flows and reports reference them
Downstream automation and reporting depend on the names.