ServiceNow Deployment

Quick start

Update Set naming convention:

[App Name] - [Story ID] - [Brief Description]

Example:
ITIL - STORY-1234 - Add approval routing for high-priority incidents

Batching strategy (parent/child pattern):

Parent Update Set (orchestrates order)
├── Child Update Set 1 (dependencies)
├── Child Update Set 2 (main logic)
└── Child Update Set 3 (cleanup)

Deployment process

1. •Capture phase: Select only objects needed; use filters to exclude system changes
2. •Preview phase: Resolve all errors:
   • •Accept Remote: Keep target system changes
   • •Skip: Ignore conflicting source changes
3. •Commit phase: Only after preview succeeds
4. •Verify phase: Test functionality on target instance

Critical rules

Best practices

• •Keep Update Sets focused (one feature per set)
• •Document customizations in the Description field
• •Test on sub-production before production
• •Create parent sets for new applications
• •Version track all custom objects
• •Backup production before large deployments

Reference

For capture lists, what moves vs what stays, and batching patterns, see BEST_PRACTICES.md