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. The last version of a workflow committed as an Insert or Update using an update set becomes the currently published version, regardless of the publishing sequence for the workflow versions. Commit a workflow in an update setFollow the steps in this page to commit a workflow in an update set.Update set migration exampleIt is not possible to have multiple published versions as a result of update set commits. However, this does not eliminate risk, and care should be taken when migrating update sets.Update set migration riskUpdate Set B is migrated and committed to the production instance.
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. The last version of a workflow committed as an Insert or Update using an update set becomes the currently published version, regardless of the publishing sequence for the workflow versions. Commit a workflow in an update setFollow the steps in this page to commit a workflow in an update set.Update set migration exampleIt is not possible to have multiple published versions as a result of update set commits. However, this does not eliminate risk, and care should be taken when migrating update sets.Update set migration riskUpdate Set B is migrated and committed to the production instance.
