Update set best practices
Quick answer
Update sets carry configuration from dev to test to prod. Keep them clean.
Update sets carry configuration from dev to test to prod. Keep them clean.
- Use a focused update set per feature, not one giant set.
- Set your current update set before you start changing things.
- Watch for and resolve collisions during commit.
- Remember update sets do not carry data, only configuration.
- Back up (export) before committing to production.
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 do update sets NOT carry?
- A. Data records
- B. Business rules
- C. UI policies
Show answer
A. Data records
They move configuration, not data.
When should you set the current update set?
- A. Before making changes
- B. After committing
- C. Never
Show answer
A. Before making changes
Set it first so changes are captured.
Frequently asked questions
What does the term Update set best practices refer to in ServiceNow?
Update sets carry configuration from dev to test to prod. Keep them clean.
What is another point to note about Update set best practices?
Use a focused update set per feature, not one giant set. Set your current update set before you start changing things. Watch for and resolve collisions during commit.