Create Your First Workflow

This guide walks through the process of creating a simple Blueprint workflow.

The goal of this workflow is to:

1. Retrieve labour entries from a field system
2. Transform those records into canonical structures
3. Push the aligned records into a financial system

Step 1: Define the Blueprint

Blueprints are defined as ordered sequences of steps.

Each step performs a specific operation using a workflow verb.

Example structure:

1. FETCH labour entries
2. TRANSFORM records
3. PUSH aligned records

This structure ensures that data flows through a predictable pipeline.

Step 2: Retrieve Data From a System

The first step typically retrieves data from an external system.

Example:

FETCH → assignar.site_diaries

This step retrieves site diary records containing labour entries.

The adapter responsible for the Assignar system handles:

• authentication
• API communication
• response normalization

The result is stored in the pipeline context.

Step 3: Transform the Data

External system records often need normalization before they can be used elsewhere.

A transformation step converts those records into canonical constructs.

Example:

TRANSFORM → extract_labour_entries

This step converts raw site diary records into structured LabourEntry constructs.

Each record now includes fields such as:

• worker
• project
• date
• hours
• cost category

Step 4: Apply Governance Checks

Before data is written to downstream systems, governance rules may be applied.

Example governance checks include:

• validating project identifiers
• verifying worker mappings
• enforcing cost category rules

This ensures that incorrect data does not propagate across systems.

Step 5: Write Records to the Target System

Once records are validated and transformed, they can be written to the target system.

Example:

PUSH → business_central.project_ledger

The Business Central adapter handles:

• API authentication
• entity mapping
• transaction handling

This step records the aligned project costs inside the ERP.

Step 6: Observe the Workflow Execution

Each workflow run is tracked by the runtime.

Execution metadata includes:

• BlueprintRun identifier
• step execution results
• execution time
• system responses

This allows teams to monitor system behavior and diagnose failures.

What Happens Next

Once the first workflow is running, teams typically expand the pipeline.

Common next workflows include:

• scheduled labour ingestion
• payroll reconciliation
• variance detection pipelines
• document indexing workflows

Over time, these workflows form the operational backbone of system alignment.

Summary

A typical workflow follows this pattern:

FETCH
Retrieve records from an external system.

TRANSFORM
Convert records into canonical constructs.

GOVERN
Validate and enforce policy rules.

PUSH
Write aligned data into downstream systems.

By structuring system interaction in this way, Demiton ensures that enterprise systems behave predictably across complex operational environments.

---