Understanding Workflow Engines: Concepts, Types, Standards, and Components

1 What Is a Workflow Engine

Workflow originated in production organization and office automation, aiming to break work into defined tasks or roles, execute them according to principles, and monitor them to improve efficiency, control processes, and enhance service quality. Computers can automatically pass documents, information, or tasks among participants based on preset rules.

2 Why Use a Workflow Engine

Workflow exists whenever data moves from one task to another, whether structured or unstructured. If data does not flow, there is no workflow.

The main workflow categories are:

Process Workflow : Predictable, repeatable tasks with a fixed data flow, such as leave applications.

Project Workflow : Structured but more flexible paths for a single project, like releasing a new website version.

Case Workflow : Unordered data flow that becomes clear only after large data collection, e.g., insurance claim cases.

Introducing a workflow engine depends on business complexity; complex or frequently changing processes benefit from it, while simple, stable processes may not need one. Core functions include node management, flow control, state control, and process instance management.

3 Common Workflow Comparisons

4 Workflow Standards

Popular engines (Activiti, Camunda, Flowable) follow three major standards:

• BPMN (Business Process Model and Notation): Fixed, focuses on process management.

• CMMN (Case Management Model and Notation): Dynamic, focuses on case management.

• DMN (Decision Model and Notation): Computational, focuses on decision making.

5 Business Process Engine

BPMN defines graphical business process diagrams, reducing the need for custom code. It consists of four basic object types: Flow Objects, Data, Connecting Objects, and Swimlanes.

1. Basic Objects

Flow Objects : Events, Activities, Gateways.

Events include start, intermediate, and end events.

Activities cover tasks and sub‑processes.

Gateways control branching and merging (exclusive, parallel, inclusive, event).

Data : Data Objects, Data Inputs, Data Outputs, Data Stores.

Connecting Objects : Sequence Flow (solid arrow), Message Flow (dashed arrow), Association (dotted line).

Swimlanes : Group elements to show responsibilities of different participants.

2. Process Designer

Designers allow drag‑and‑drop modeling (e.g., bpmnjs). Modern low‑code tools (DingTalk, Yida) provide user‑friendly designers, while enterprise‑level complex processes still benefit from BPMN‑compliant designers.

3. Approval‑Person Selection Strategies

Five strategies are supported: GIVEN_USER (specified approver), GET_BY_FORM_USER (selected in form), GIVEN_ROLE (role‑based approvers), API (fetch via API), TEMPLATE (template‑based).

After setting a strategy, the engine retrieves approvers for each node and sends pending messages through the messaging center.

4. Multi‑User System Integration

The approval center can work with multiple user systems (internal user center, Tower) via RPC or HTTP, automatically distinguishing user contexts.

6 Case Model Engine

CMMN captures unpredictable, case‑driven workflows where tasks may occur in any order, driven by conditions such as order size or VIP status. It suits scenarios like insurance claims or loan planning.

7 Decision Engine

DMN models business decisions and can be invoked as a decision task within BPMN. It decouples decision logic from process code, allowing analysts to focus on rules.

Decision requirements diagrams bridge process models and decision logic, defining tasks, relationships, and preconditions.

8 Form Engine

Form engines provide visual, web‑based form designers that bind to database fields without writing code, enabling rapid creation of admin, HR, procurement, and leave forms. They decouple workflow from business logic, improve efficiency, and support low‑code customization.

Limitations include simplistic UI, need for custom components, and incomplete support for advanced front‑end layouts.

9 Summary

Workflow engines are essential for automating office and business processes such as approvals and service orchestration. They improve efficiency, control, flexibility, and reduce coupling, making them valuable in micro‑service architectures when orchestration, state transitions, or complex routing are required.