Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.
Versions
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store
Close

Update set migration example

Log in to subscribe to topics and get notified when content changes.

Update set migration example

It 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.

Consider this example:
  1. Workflow A - Version 1 is migrated and committed to the production instance.
  2. Update Set B is created.
  3. Update Set C is created.
  4. Workflow A - Version 2 is published in Update Set B.

    A customer update record is added to Update Set B with the Version 2 payload.

    A customer update record is added to Update Set B with the Version 1 workflow left unpublished.

  5. Update Set B is completed.
  6. Workflow A - Version 3 is published in Update Set C.

    A customer update record is added to Update Set C with the Version 3 payload.

    A customer update record is added to Update Set C with the Version 2 workflow left unpublished.

  7. Update Set C is completed.
  8. Update Set C is migrated and committed to the production instance.

    Workflow A - Version 1 is set to unpublished.

    Workflow A - Version 2 update is skipped since Update Set B, which contains Version 2, was never migrated.

    Workflow A - Version 3 is committed and becomes the only published version of the workflow.

Feedback