Workflows inServiceNoware typically moved between instances usingUpdate Sets. Update Sets serve as a mechanism for capturing customizations and migrating them across different environments, such asDevelopment (Dev) # Test # Production (Prod).
Recording Customizations:
When a workflow is modified or created, its changes are recorded in an Update Set if theUpdate Set is active.
Capturing Related Records:
Workflows consist of multiple components (e.g., activities, conditions, transitions).
Update Sets capture theWorkflow Versionand associatedWorkflow Activities.
Exporting and Importing:
The Update Set containing the workflow is exported from the source instance (e.g., Dev).
It is then imported into the target instance (e.g., Test or Prod).
Commit the Update Set:
After import, the Update Set must be reviewed and committed to apply the changes in the target instance.
B: Workflows are moved using Transform Maps
Incorrect: Transform Maps are used forimporting and mapping datafrom external sources into ServiceNow tables, not for migrating configurations like workflows.
C: Workflows are moved using Application Sets
Incorrect: There is no such thing as "Application Sets" in ServiceNow. However,Applications (Scoped Apps) can be moved usingApplication Repositories (App Repo)orUpdate Sets, but this is different from standard Workflow migration.
D: Workflows cannot be moved between instances
Incorrect: Workflowscanbe moved usingUpdate Sets, and in scoped applications, they can also be packaged with the application.
How Update Sets Work for Workflows?Why Other Options Are Incorrect?
ServiceNow Product Documentation - Update Sets
Update Sets Overview
Moving Customizations Using Update Sets
ServiceNow Workflows
Workflow Management
References from ServiceNow CSA Documentation: