Basic concepts of Workflow
If you just get started, we encourage you to familiarize yourself with the basic concepts of Workflow. These concepts are frequently used in the Workflow documentation.
- Workflow run
- A workflow run is an execution of a workflow. Each workflow run has a unique run number. Workflow runs are displayed in the Run History tab of the Workflow home page or the editing page of a specific workflow. You can stop a workflow run that is in Processing status.
- Task run
- A task run is an execution of a task. Each task run has a unique run number. Task runs are displayed in the Tasks tab of the Workflow home page or the editing page of a specific workflow.
- Swimlane
- Swimlane is the debugging tool that is built in Workflow. With Swimlane, you can view the data payload for a task, adjust configurations, and rerun a workflow run. You start Swimlane from the menu of a task run.
- Workflow data payload
- The actual data that is transferred from one task to another of a workflow. The data payload is organized in JSON objects. A task can read the data payload and append data to it.
- Upstream task
- A workflow is a set of tasks that are run based on configured sequence and logic. It is similar to the flow of water in a river. A task that is run before another task is considered an upstream task to the latter task.
- Downstream task
- Similarly, a task that is run after another task is considered a downstream task to the latter.