Contents Now Platform Capabilities Previous Topic Next Topic Workflow update set migration use case - subflow dependency (failure) Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share 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. User A selects Update Set C. User A checks out Workflow A. User A adds a subflow called Workflow B to Workflow A.Assume that Workflow B was previously published, but has not been migrated to the production instance. User A publishes Workflow A.A customer update set record is added to Update Set C 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.Notably absent from Update Set C is the subflow called Workflow B. Workflow B was published before User A selected Update Set C.User A completes Update Set C and migrates it to the production instance.Update Set C commits with warnings.Workflow A is invoked on the production instance with the following results:Workflow A fails the runtime validation check and is prevented from running on the production system. The system adds to the workflow context a workflow log entry detailing the cause of the failure, notably the absence of a dependent workflow.To learn more about the validation checks on workflow dependencies and update sets see ValidateUpdateSetDependencies. On this page Send Feedback Previous Topic Next Topic
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. User A selects Update Set C. User A checks out Workflow A. User A adds a subflow called Workflow B to Workflow A.Assume that Workflow B was previously published, but has not been migrated to the production instance. User A publishes Workflow A.A customer update set record is added to Update Set C 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.Notably absent from Update Set C is the subflow called Workflow B. Workflow B was published before User A selected Update Set C.User A completes Update Set C and migrates it to the production instance.Update Set C commits with warnings.Workflow A is invoked on the production instance with the following results:Workflow A fails the runtime validation check and is prevented from running on the production system. The system adds to the workflow context a workflow log entry detailing the cause of the failure, notably the absence of a dependent workflow.To learn more about the validation checks on workflow dependencies and update sets see ValidateUpdateSetDependencies.
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. User A selects Update Set C. User A checks out Workflow A. User A adds a subflow called Workflow B to Workflow A.Assume that Workflow B was previously published, but has not been migrated to the production instance. User A publishes Workflow A.A customer update set record is added to Update Set C 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.Notably absent from Update Set C is the subflow called Workflow B. Workflow B was published before User A selected Update Set C.User A completes Update Set C and migrates it to the production instance.Update Set C commits with warnings.Workflow A is invoked on the production instance with the following results:Workflow A fails the runtime validation check and is prevented from running on the production system. The system adds to the workflow context a workflow log entry detailing the cause of the failure, notably the absence of a dependent workflow.To learn more about the validation checks on workflow dependencies and update sets see ValidateUpdateSetDependencies.
