update-set-workflow

Update Set Workflow for ServiceNow

Update Sets are MANDATORY for tracking changes in ServiceNow development. Without an Update Set, changes are not tracked and cannot be deployed to other instances.

This is also enforced: configuration writes are blocked at the tool layer while no update set is active for the session. When you hit that block, ask the user whether to capture the work in a named update set, then call snow_ensure_active_update_set({ name }) once and retry. Only if the user explicitly declines tracking, re-issue the call once with __skipUpdateSet: true — the choice is remembered for the rest of the session.

Before ANY Development

ALWAYS create or ensure an Update Set is active before making changes:

// Step 1: Check current Update Set
var current = await snow_update_set_query({ action: "current" })

// Step 2: If no Update Set or using Default, create one
if (!current || current.name === "Default") {
  await snow_update_set_manage({
    action: "create",
    name: "Feature: [Descriptive Name]",
    description: "What and why this change is being made",
  })
}

// Step 3: Now safe to make changes
// All changes will be tracked!

// Step 4: When done, complete the Update Set
await snow_update_set_manage({
  action: "complete",
  update_set_id: current.sys_id,
})

Update Set Naming Conventions

Update Set Lifecycle

1. In Progress - Active, receiving changes
2. Complete - Ready for export/promotion
3. Ignore - Changes won't be promoted (use for experiments)