---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Input variable movement

# Input variable movement {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

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://servicenow-prod.fluidtopics.net/mR_raqQ7OHzfT7tuWQMJhQ#r_InptVrblMvmntTwo)**   
  An existing workflow already contains two input variables.
* **[Input variable removal](https://servicenow-prod.fluidtopics.net/bjEpBEzALBqYtfF~JzB1Zg#c_InputVariableRemoval)**   
  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://servicenow-prod.fluidtopics.net/1y0g1JrY4WVDGT_RGjs_qw#c_AvoidingDuplicateWorkflows)**   
  Update sets manage the published state of all versions of a workflow prior to committing the workflow version on a local instance.