Input variable movement
concept brazil Updated Sep 10, 2026 1 min read c_InputVariableMovement.md
You can add input variables to existing workflows and add them to update sets.
When you submit the new variables, an entry is made into the current update set that reflects the addition of a variable to the Variables [var_dictionary] table. Unlike the workflow version that only writes to the update set when the workflow is published, the variables write individual update entries into the currently selected update set immediately upon submission.
- Input variable movement use case - two input variables
An existing workflow already contains two input variables. - Input variable removal
Deleting workflow input variables, like insert and update actions, creates a customer update record in a user's current update set. - Avoiding duplicate workflows
Update sets manage the published state of all versions of a workflow prior to committing the workflow version on a local instance.
Parent Topic:Workflow administration
30 lines · 2.0 KB
--- title: Input variable movement description: You can add input variables to existing workflows and add them to update sets. locale: en-US canonical_url: https://www.servicenow.com/docs/r/build-workflows/legacy-workflow/c\_InputVariableMovement.html release: brazil product: Legacy Workflow classification: legacy-workflow topic_type: concept last_updated: "2026-09-10" reading_time_minutes: 1 breadcrumb: [Workflow administration, Classic Workflow, Build workflows] --- # Input variable movement You can add input variables to existing workflows and add them to update sets. When you submit the new variables, an entry is made into the current update set that reflects the addition of a variable to the Variables \[var\_dictionary\] table. Unlike the workflow version that only writes to the update set when the workflow is published, the variables write individual update entries into the currently selected update set immediately upon submission. - **[Input variable movement use case - two input variables](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/build-workflows/legacy-workflow/r_InptVrblMvmntTwo.md)** An existing workflow already contains two input variables. - **[Input variable removal](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/build-workflows/legacy-workflow/c_InputVariableRemoval.md)** Deleting workflow input variables, like insert and update actions, creates a customer update record in a user's current update set. - **[Avoiding duplicate workflows](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/build-workflows/legacy-workflow/c_AvoidingDuplicateWorkflows.md)** Update sets manage the published state of all versions of a workflow prior to committing the workflow version on a local instance. **Parent Topic:**[Workflow administration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/build-workflows/legacy-workflow/c_WorkflowAdministration.md)
| title | Input variable movement |
| description | You can add input variables to existing workflows and add them to update sets. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/build-workflows/legacy-workflow/c\_InputVariableMovement.html |
| release | brazil |
| product | Legacy Workflow |
| classification | legacy-workflow |
| topic_type | concept |
| last_updated | 2026-09-10 |
| reading_time_minutes | 1 |
| breadcrumb | Workflow administrationClassic WorkflowBuild workflows |