Workflow update set migration use case - simple

Create a new workflow with no dependencies and then migrate the workflow in an update set.

  1. User A selects Update Set A.
  2. User A creates a new workflow called Workflow A.
  3. User A publishes Workflow A.

    A customer update set record is added to Update Set A containing an XML payload, including the published Workflow A and all activity dependencies. The XML payload also contains the workflow input variables associated with the workflow.

  4. User A completes Update Set A and migrates it to the production instance.
  5. Update Set A commits successfully.
  6. Workflow A works as expected.