Scenario tutorials: start with a business goal
Choose a small scenario with a concrete result. Follow configuration and execution steps, then inspect the target system. Times are reading/operation estimates after prerequisites are ready, excluding external-service installation.
Shared preparation
- Complete the quick start and understand definitions, triggers and instances.
- Use newly created tutorial data/resources. Keep business and platform databases separate; supply your own paths, ports and accounts.
- Use ADMIN for the complete tutorial, including configuration, publication and logs/variables. OPERATOR can execute configured tasks and use applicable controls. Approval also requires allowed-operator membership; see permissions.
- A “copy” in these tutorials means creating a newly named object and entering the same example configuration. The task and job lists do not provide a one-click clone action.
- Execute manually before enabling schedules. Plan idempotency for writes; stopping or retrying does not undo completed effects.
- Clean up only objects created for the tutorial. Keep passwords, tokens and keys in resources/private configuration.
Choose a tutorial
Start with the first group, then choose by business goal. The full order workflow has a separate environment setup page for its data and receiver before the orchestration steps.
Scope identifies the documented version/environment, not proof that every protocol extension or new combined workflow was executed.
Start with one task
| Scenario | What you achieve | Environment | Difficulty / estimate | Scope |
|---|---|---|---|---|
| Run a script and distinguish success, failure and stop | Use four script variants for success, failure, stop and timeout to distinguish trigger acceptance from actual execution results. | Windows PowerShell Worker | Beginner / 10 min | 1.0.0 · Local Worker |
| Query orders and add a data quality gate | Query three orders and use a scalar check to detect an unexpected row count. | PostgreSQL | Beginner / 15 min | 1.0.0 · PostgreSQL |
| Copy an orders file and verify its contents | Copy a CSV to a separate directory and verify contents, hashes and source preservation. | Two dedicated directories | Beginner / 10 min | 1.0.0 · Two dedicated directories |
Move data and connect systems
| Scenario | What you achieve | Environment | Difficulty / estimate | Scope |
|---|---|---|---|---|
| Sync incremental orders with equal-watermark handling | Load three orders, append an order at the same timestamp, and keep reruns idempotent. | Source/target PostgreSQL | Intermediate / 25 min | 1.0.0 · Source/target PostgreSQL |
| Sync two tables and control target names | Synchronize orders and order_items together, checking each mapping and target table. | Source/target PostgreSQL | Intermediate / 20 min | 1.0.0 · Source/target PostgreSQL |
| Call an orders API and extract variables | Pass a date and limit to a read-only API, then extract total and amount for later steps. | Python HTTP example service | Intermediate / 15 min | 1.0.0 · Python HTTP example service |
| Publish three order messages and configure run notifications separately | Verify order messages at a consumer and distinguish them from platform email notifications. | PostgreSQL, Kafka; SMTP for email | Intermediate / 25 min | 1.0.0 · PostgreSQL, Kafka; SMTP for email |
Orchestrate and control a workflow
| Scenario | What you achieve | Environment | Difficulty / estimate | Scope |
|---|---|---|---|---|
| Build parallel joins and conditional routes | Wait for two parallel branches before joining, then choose one route by amount. | Local Worker | Intermediate / 20 min | 1.0.0 · Local Worker |
| Control which child version a parent job uses | Observe a parent's pinned child version and adopt a new version by publishing each level. | Local Worker | Intermediate / 15 min | 1.0.0 · Local Worker |
| Resume a run after an event or approval | Wait for a matching event or designated approval and observe the same instance continue. | DATABASE accounts | Intermediate / 20 min | 1.0.0 · DATABASE accounts |
Deploy, operate and extend
| Scenario | What you achieve | Environment | Difficulty / estimate | Scope |
|---|---|---|---|---|
| Run a remote script over SSH | Produce a message and variable remotely, then check the remote path and execution result. | Independent SSH host | Intermediate / 15 min | 1.0.0 · Independent SSH host |
| Collect monitoring metrics and interpret threshold alarms | Inspect fresh memory metrics and change a tutorial threshold to observe health-state changes. | Monitor Agent | Intermediate / 15 min | 1.0.0 · Monitor Agent |
| Preview schedules and understand missed-run recovery | Inspect timezone/calendar candidates, then compare missed-run policies in a dedicated installation. | An instance you can stop | Intermediate / 25 min | 1.0.0 · An instance you can stop |
| Route by group and limit shared concurrency | Route tasks to matching Workers, then serialize two tasks through one shared permit. | Independent Workers/groups | Advanced / 25 min | 1.0.0 · Independent Workers/groups |
| Deploy a trusted Local JAR and invoke it | Use a minimal protocol-1 extension to emit hello-localjar and rows=3. | Java 21, trusted SPI JAR | Advanced / 25 min | 1.0.0 · Java 21, trusted SPI JAR |
| Transfer configuration to another environment | Import a harmless task into a separate target and inspect disabled state, mappings and execution. | Two independent instances | Intermediate / 20 min | 1.0.0 · Two independent instances |
Complete business workflow
| Scenario | What you achieve | Environment | Difficulty / estimate | Scope |
|---|---|---|---|---|
| Daily order reconciliation and report delivery | Sync 12 orders, validate and reconcile, then deliver a CSV and receipt through direct or approved routing. | PostgreSQL, local HTTP receiver | Intermediate / 45–60 min | 1.0.0 · Normal, failed quality check, approved delivery |
Checking results
Inspect platform states and business outcomes together: row counts, totals, file hashes, API responses, consumed messages or post-approval node states. Each tutorial lists concrete expected values. Interpret intentional failure/stop exercises according to their steps.