InServiceNow, anUpdate Setis a mechanism used tocapture customizationsmade in an instance andmove them to another instance(e.g., from development to production). However, certain elements arenot included in an Update Set by default.
Homepages (A) –Correct
Homepages are stored asuser-specific or global content, and they are not included in update sets by default.
To migrate them, you need tomanually export/importthem or use thesys_portal_page_settable.
Data (B) –Correct
Update Setsdo not include actual data, such as incident records, user records, or CMDB data.
Onlyconfiguration changes(like fields, forms, and workflows) are captured.
Data migration must be handled separately usingData Export or Integration methods.
Published Workflows (C) –Correct
Once a workflow ispublished, it is stored as a runtime instance and not automatically included in an Update Set.
To capture it, you mustmanually updatethe workflow before moving it in an Update Set.
Report Definitions (H) –Correct
Reports and their configurations are not automatically included in Update Sets.
You mustmanually include themby marking them as "Captured in Update Set."
D. Business Rules(Captured in Update Sets)
E. Schedules(Captured in Update Sets)
F. Database changes(Captured in Update Sets)
G. Related Lists(Captured in Update Sets)
I. Scheduled Jobs(Captured in Update Sets)
J. Client Scripts(Captured in Update Sets)
K. Views(Captured in Update Sets)
ServiceNow Update Sets Overview:https://docs.servicenow.com/en-US/bundle/utah-application-development/page/build/system-update-sets/concept/c_UpdateSets.html
ServiceNow Update Set Best Practices:https://docs.servicenow.com/en-US/bundle/utah-application-development/page/build/system-update-sets/concept/update-set-best-practices.html
Items NOT Included in Update Sets (By Default):Items That ARE Included in Update Sets (By Default):Official References from Certified System Administrator (CSA) Documentation:
