Workflow update set migration use case - subflow dependency (success)

Successfully edit and migrate an existing workflow and its dependent subflow.

  1. User A selects Update Set B.
  2. User A checks out Workflow A.
  3. User A adds a subflow called Workflow B to Workflow A.

    Assume that Workflow B was previously published and migrated to the production instance.

  4. User A publishes Workflow A.

    A customer update set record is added to Update Set B 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.

  5. User A completes Update Set B and migrates it to the production instance.
  6. Update Set B commits successfully.
  7. Workflow A works as expected with Workflow B as a subflow.