A workflow is a collection of operations that is used as a tool to help segregate different parts of the project. By grouping operations together in a workflow, you may find it more convenient to organize process flows in a logical manner.
Workflows cannot be executed; only the operations within them can be executed. If a workflow is configured such that one operation leads to the chain execution of all other options in a workflow, you can effectively run all operations in the workflow.
You can also execute individual operations within workflows, which may lead to execution of operations in the same or other workflows. That is, if any operations are upstream of other operations in an operation chain, within or outside the workflow, the downstream operations will be kicked off accordingly. In this way, you can effectively run all operations within a project.
Workflow Deployment This page describes how to deploy workflows or selected project components to the Jitterbit Harmony cloud. Once all components that an operation is dependent on are deployed, those operations can be executed.
Workflow Dependencies and Deletion Viewing the dependencies of a workflow lists the other project components that the workflow is dependent on. As project components cannot be dependent on a workflow themselves, workflows can be deleted without consideration of dependencies.
Workflow Validity Workflows must be valid in order to be deployed. This page covers how to identify invalid workflows and view the validation errors associated with them, as well as how to resolve validation errors.