Operations 10 min read

Comprehensive Guide to the Workflow System: Frameworks, Features, and Process Design

This guide details the workflow system’s underlying frameworks, functional modules, process design operations, form customization, deployment procedures, and task management features, providing a comprehensive overview for developers and administrators to effectively implement and maintain business processes.

Top Architect
Top Architect
Top Architect
Comprehensive Guide to the Workflow System: Frameworks, Features, and Process Design

The system is built on a collection of frameworks including SpringBoot 2.3.7.RELEASE (web framework), Mybatis-Plus 3.5.2 (ORM), sa-token 1.35.0.RC (authentication), Hutool 5.8.4 (utility), knife4j 2.0.7 (API docs), spring-file-storage 0.7.0 (file upload), tlog 1.5.1 (logging), easypoi 4.2.0 (Excel import/export), MinIO 8.4.3 (file storage), and xx-job 2.4.0 (distributed scheduling).

The feature list covers system settings (route synchronization, menu authorization, member management, role and department management, data dictionary, parameter configuration, etc.), workflow management (approval, delegation, form design, deployment, and deletion), and various task operations such as agreement, rejection, rollback, and forwarding.

Process design allows users to add new processes by filling basic information, view process diagrams and data via separate tabs, edit existing designs, and open the visual designer to construct workflows using drag‑and‑drop nodes.

The visual designer consists of four main panels: a drag panel with node models (Start, Task, Custom, Decision, Fork, Join, End, SubProcess), a canvas supporting zoom, drag, move, connect, edit node/edge, and right‑click menus, an attribute panel for editing node or edge properties, and a control panel offering zoom, fit, undo/redo, clear, view, import, highlight, and save functions.

Form design supports both custom‑coded Vue forms and metadata‑driven forms generated from JSON; it includes form attributes, field addition, ordering, editing, deletion, and saving, with a preview mode for metadata forms.

Deployment actions enable users to deploy a new version of a process or redeploy to overwrite the latest version, while deletion removes the design without affecting already deployed instances.

Process definitions store workflow engine files, showing fields such as display name, unique code, category, version (auto‑incremented on deployment), and status (enabled/disabled); they can be viewed, enabled/disabled, or deleted.

Users can initiate processes via the "Apply" button, which presents a form specific to each workflow, and manage their own initiated, pending, completed, and copied tasks, with detailed views of forms, diagrams, and approval records.

Task handling includes approval actions (agree, reject, rollback, forward), withdrawal of in‑progress tasks, and delegation to other users; the interface differentiates between normal and countersign tasks, providing appropriate submission options.

The documentation also provides links to the backend and frontend source code, a demo address, and default credentials (admin/123456) for further exploration.

backendfrontendoperationsWorkflowSpringBootprocess design
Top Architect
Written by

Top Architect

Top Architect focuses on sharing practical architecture knowledge, covering enterprise, system, website, large‑scale distributed, and high‑availability architectures, plus architecture adjustments using internet technologies. We welcome idea‑driven, sharing‑oriented architects to exchange and learn together.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.