Workflow movement with update sets The system tracks workflows in update sets differently than other records because workflow information is stored across multiple tables. Changes made to a workflow version are not added to the update set until the workflow is published, at which point the entire workflow is added into the update set. Update sets store workflows as a single Workflow [wf_workflow] record and only retain the latest version with the update type of Workflow. Workflow update set migration use case - simpleCreate a new workflow with no dependencies and then migrate the workflow in an update set. Workflow update set migration use case - subflow dependency (success)Successfully edit and migrate an existing workflow and its dependent subflow.Workflow update set migration use case - subflow dependency (failure)Edit and migrate an existing workflow from a test instance to a production instance that fails to run on the production instance because of a missing dependent subflow.Workflow update set migration use case - subflow dependency (risk)Multiple users migrate a workflow from a test instance to a production instance without proper coordination. This use case can succeed, but only when each user understands the dependencies and properly migrates the dependent parts of the workflow to the new instance.Input variable movementYou can add input variables to existing workflows and add them to update sets.