1. Project Overview

A domestically developed Java workflow engine based on SpringBoot and Vue, featuring a decoupled frontend and backend architecture.

The workflow engine provides digital implementation of organizational and institutional workflow management rules and internal business processes. Externally, it offers automated third-party business integration, API connectivity, and algorithm-driven capabilities. In addition to providing the underlying execution engine, it fully considers global transparent monitoring, security protection, and localization requirements. It is a practical solution for internal workflow management and business process automation driven by algorithms.

2. Open Source License

Licensed under GPL-3.0

3. Screenshots

Workflow Engine Screenshots

Task Management Screenshots

Workbench Screenshots

4. Feature Overview

Logical Architecture Diagram

1. The workflow engine mainly consists of Task Configuration and the Workbench. Task Configuration is designed for operations personnel to configure workflows, while the Workbench is designed for users to interact with and use the system.
2. The workflow engine requires role and position configurations in the Digital Foundation; otherwise, it cannot operate.
3. The workflow engine supports not only traditional OA scenarios but also integration with and management of external business systems, algorithms, APIs, and agents.

Functional Architecture Diagram

1. The workbench's functionality and interface are configured through Task Management.

2. Task Management features are divided into three categories: workflows, forms, and configuration items.

3. Form Management handles database table structure mapping and design, supported by a drag-and-drop form engine.

4. Workflow Management covers workflow design, deployment, and monitoring, supported by a drag-and-drop workflow engine.

5. API Management supports integrating third-party APIs into workflow nodes and workflow paths.

6. Link Management supports binding third-party application entry points to job positions.

7. Document templates and red-header document templates require third-party plugin integration before they can be used.

Deployment Architecture Diagram

1. The workflow engine supports deployment and scaling through microservices, distributed architecture, and containerization.

2. The workflow engine requires additional servers for document preview services.

3. The workflow engine depends on the Digital Foundation and its Single Sign-On service.

4. In a domestic IT innovation environment, a standalone workflow engine can easily support 500 users on a virtual machine with 4 CPU cores and 8 GB of memory (historical data must be archived annually).

5. Tech Stack

Backend Technology Stack

Sequence number	Dependency	Version
1	Spring Boot	2.7.10
2	SpringDataJPA	2.7.10
3	SpringDataRedis	2.7.10
4	SpringKafka	2.8.11
5	nacos	2.2.1
6	druid	1.2.16
7	Jackson	2.13.5
8	javers	6.13.0
9	lombok	1.18.26
10	logback	1.2.11
11	flowable	6.8.0

Frontend Technology Stack

Sequence number	Dependency	Version
1	vue	3.3.2
2	vite2	2.9.13
3	vue-router	4.0.13
4	pinia	2.0.11
5	axios	0.24.0
6	typescript	4.5.4
7	core-js	3.20.1
8	element-plus	2.2.29
9	sass	1.58.0
10	animate.css	4.1.1
11	vxe-table	4.3.5
12	echarts	5.3.2
13	svgo	1.3.2
14	lodash	4.17.21

Middleware Selection

Sequence number	Tools	Version
1	JDK	11
2	Tomcat	9.0+
3	Kafka	2.6+
4	filezilla server	1.7+

Database Selection

Sequence number	Tools	Version
1	Mysql	5.7 / 8.0+
2	Redis	6.2+
3	elasticsearch	7.9+