Introducing the Workflow Engine Core

Version 1.0.3

With v1.0.3, the platform gains its foundational workflow automation layer: a state machine engine that manages approval chains, drives process routing, and provides consistent state tracking across every module.

Why a Workflow Engine?

Modern enterprise operations depend on structured, auditable processes — approvals don't happen in a straight line, and business rules change. Previously, each module handled its own ad-hoc process logic, which made it difficult to enforce consistent behaviour, trace decisions, or reconfigure processes without code changes.

The Workflow Engine Core solves this by providing a shared, configurable automation backbone that all modules can build on.

What Was Built

Core State Machine

At the heart of this release is a deterministic state machine. Every workflow instance — whether it's a leave request, an invoice approval, or a contract review — moves through a defined set of states with explicit, validated transitions.

States and transitions are declared in a structured configuration.
Invalid transitions are rejected at the engine level.
Every transition emits an event that can be consumed by other parts of the system.

Approval Chains

Approval chains allow a single workflow to require sign-off from multiple parties in a controlled sequence.

Supports sequential chains (step A must complete before step B begins).
Supports parallel chains (multiple approvers act simultaneously; configurable quorum rules).
Supports conditional routing (the next step is determined by the outcome of the previous one).

Each step in a chain maintains its own state, so partial progress is preserved and individual steps can be retried or escalated independently.

Process Routing

Configurable routing rules determine who handles each step of a workflow. Routing can be based on:

Role or permission group
Organisational hierarchy (e.g. direct manager, department head)
Attribute-based rules (e.g. spend amount determines the required approval tier)
Explicit assignment

State Tracking & Audit Trail

Every state transition is persisted with:

Timestamp of the transition
Identity of the actor (user or automated agent) that triggered it
The previous and new state
Any contextual payload attached to the transition

This makes every workflow instance fully auditable and supports compliance reporting without additional instrumentation.

Cross-Module Availability

The workflow engine is exposed as a shared service layer. All three major platform domains benefit immediately:

Human Resources

Employee onboarding sequences
Leave and absence approvals
Performance review sign-off

Financial Management

Multi-tier expense approvals
Purchase order authorisation
Budget exception handling

Contract Lifecycle Management

Structured review and redline stages
Execution sign-off chains
Renewal and expiry workflows

What Comes Next

This release is intentionally foundational. The engine is live and all modules can integrate against it, but the full set of pre-built workflow templates for each module will ship in upcoming releases. A visual workflow designer for non-technical configuration is also on the roadmap.

Getting Started

If you are building on or integrating with the workflow engine, refer to the API Reference for the workflow state machine endpoints and the Features section for module-specific workflow guides as they become available.