Input variable movement use case - two input variables An existing workflow already contains two input variables. User A checks out the workflow. User A adds two input variables.ServiceNow adds to the current update set one customer update record for each new variable.The current workflow now has 4 input variables: the two that were present prior to check out and the two new ones. User A publishes the workflow.There are now three related customer update records: two for new variables, and one for the published workflow. The XML payload of the new workflow version now includes all input variable database entries. So while the two original input variables do not have individual customer update records, all four variables are migrated to the local instance with the payload of the newly published workflow version. Verify variables included in a specific workflow. User A completes the update set. Adding Input Variables - SuccessUser A migrates and commits the update set to a local instance where the original workflow version had previously been committed. The two existing input variables are already present because of the earlier version.The system adds the two new input variables when the user commits the update set.The system preserves the two legacy input variables on the instance receiving the update set. The update set does not overwrite these variables.The new published workflow version uses all four variables.The user tests the new workflow version and it runs as expected. Verify variables included in a specific workflow Follow the steps in this page to verify the variables that are included in a specific workflow. Navigate to System Update Sets > Local Update Sets. Select the active update set. Select the customer update entry for the workflow. View the XML Payload. Search for the name of one of the columns or search for var_dictionary. There is one var_dictionary entry for each input variable.