wehub-resource-sync
a9cd7750f4
CI / unit-test (push) Has been cancelled
CI / detect-changes (push) Has been cancelled
CI / build (push) Has been cancelled
Publish docs via GitHub Pages / Deploy docs (push) Has been cancelled
CI / test-harness (push) Has been cancelled
CI / generate-e2e-matrix (push) Has been cancelled
CI / e2e (push) Has been cancelled
CI / build-ui (push) Has been cancelled
Release Drafter / update_release_draft (push) Has been cancelled
UI v2 Integration CI / E2E (Integration) (push) Has been cancelled
UI v2 CI / Lint, Format & Test (push) Has been cancelled
UI v2 CI / E2E (Mocked) (push) Has been cancelled
932 B
932 B
description
| description |
|---|
| Guided Tutorial — learn Conductor step by step with hands-on labs covering task workers, definitions, and workflows. |
Guided Tutorial
High Level Steps
Generally, these are the steps necessary in order to put Conductor to work for your business workflow:
- Create task worker(s) that poll for scheduled tasks at regular interval
- Create task definitions for these workers and register them.
- Create the workflow definition
Before We Begin
Ensure you have a Conductor instance up and running. This includes both the Server and the UI. We recommend following the Docker Instructions.
Tools
For the purpose of testing and issuing API calls, the following tools are useful
- Linux cURL command
- Postman or similar REST client
Let's Go
We will begin by defining a simple workflow that utilizes System Tasks.