Moving configuration changes between ServiceNow instances (e.g., from Development to Test) involves a strict lifecycle using Update Sets.13 The correct standard operating procedure to apply a remote update set is Retrieve, Preview, Commit.

1. Retrieve (The First Step):

Before you can do anything, the target instance (e.g., Production) must fetch the completed update set from the source instance (e.g., Development).

Action: You connect to the source instance and click 'Retrieve Completed Update Sets.' This pulls the XML file into the sys_remote_update_set table on the target instance. The state becomes Previewed or Loaded.

2. Preview (The Validation Step):

Once retrieved, you must validate the data before committing it to the database.

Action: You select the retrieved update set and click Preview Update Set.

Purpose: This checks for potential conflicts (e.g., trying to update a record that doesn't exist or has been modified locally). You must resolve all errors before proceeding.

3. Commit (The Application Step):

After the preview is successful (no errors), the changes are ready to be written to the system.

Action: Click Commit Update Set.

Result: The system writes the changes to the local tables/database. The Update Set state changes to Committed.

Why the other orders are wrong:

You cannot Preview before you Retrieve (you don't have the file yet).

You should never Commit before Previewing (this skips the safety check for conflicts).

ServiceNow System Update Sets documentation outlines the standard process of transferring update sets: Retrieve completed update sets -> Preview update sets -> Commit update set.