An Update Set in ServiceNow is a mechanism for capturing and migrating customizations and configurations from one instance to another (e.g., Development → Test → Production).
What is Captured in an Update Set?Update Sets record configuration changes, such as:✅ Tables & Database Schema Changes (e.g., new tables, modified fields)✅ Form Layout & UI Changes (e.g., changes in form views, UI policies)✅ Schedules (e.g., Scheduled Jobs, Business Rules with scheduled actions)✅ Client Scripts (e.g., JavaScript running on the client side)✅ Business Rules, UI Actions, UI Policies✅ Workflows, Script Includes, ACLs (Access Control Rules)✅ Email Notifications, Dictionary Entries, Application Menus
What is NOT Captured in an Update Set?❌ Data Records (e.g., Incident, Change Request, CMDB data)❌ Group Memberships & User Data❌ System Properties (some properties may require manual migration)❌ Attachments & Scheduled Reports
B. Changes made to tables, forms, views, and fields ❌ (Incorrect)
Views and Fields are part of UI changes, but schedules and client scripts are also included in Update Sets, making Option A more complete.
C. Changes made to tables, forms, Business Rules, and data records ❌ (Incorrect)
Data records (actual table entries like incidents or change requests) are NOT captured in Update Sets.
D. Changes made to tables, forms, groups, and configuration items (CIs) ❌ (Incorrect)
Groups and CIs (CMDB data) are considered data and are NOT included in Update Sets.
Instead, CIs should be migrated using Import Sets or CMDB data export/import.
Why Other Options Are Incorrect?
Understanding Update Sets
What Gets Captured in Update Sets?
References from ServiceNow CSA Documentation: