ServiceNow Best Practices · LessonReviewed by Praveen T, ServiceNow Trainer, 9 yrs · Updated · Published · current release · guidance
ServiceNow Update set best practices
Move configuration between instances without surprises.
Quick answer
Update sets carry configuration, never data, from development through test to production. Set your current update set before changing anything, keep one focused set per feature rather than one giant set, resolve collisions during commit, and export a backup before committing to production. That is what keeping a set clean and simple to review means in practice.
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.