RuoYiPlus

Environment Setup

Wed, 24 Jun 2026 00:00:00 +0000

Step One

Write your content here…

Getting Started

Sat, 17 Feb 2024 00:00:00 +0000

Quick Start from Template

Create a site

Configure your new site

Add your content

Publish your site

Your site will automatically publish ~1-5 minutes after you commit (save) changes to files in your GitHub repository.

Let’s customize your new site:

Project Structure Configuration Create content

Business Vision

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

In a nutshell: RuoYiPlus aims to become the leader in “enterprise application infrastructure”, helping software vendors and enterprise IT teams obtain production-grade capabilities at the lowest cost.

What Problems It Solves

Customer Type	Core Pain Point	RuoYiPlus Value
Software Vendors	High cost and long cycle of self-built frameworks	Rapid delivery based on mature framework
Enterprise IT Departments	Purchased products hard to customize	Open-source, controllable, deep customization
System Integrators	Tight project delivery timelines	Modular rapid assembly
SaaS Operators	Complex multi-tenant architecture	Out-of-the-box SaaS architecture

Target Customer Profile

graph TB subgraph "Target Customer Groups" A["Software Vendors"] B["Enterprise IT Departments"] C["System Integrators"] D["SaaS Operators"] end subgraph "Core Pain Points" A1["High cost of self-built frameworks"] B1["Purchased products hard to customize"] C1["Tight project delivery timelines"] D1["Complex multi-tenant architecture"] end subgraph "Our Value" A2["Rapid delivery based on mature framework"] B2["Open-source, controllable, deep customization"] C2["Modular rapid assembly"] D2["Out-of-the-box SaaS architecture"] end A --> A1 --> A2 B --> B1 --> B2 C --> C1 --> C2 D --> D1 --> D2

1. Product Matrix

1.1 Version System

graph TB subgraph "Product Version System" A["Community Edition - Free"] B["Professional Edition - ¥29,800/year"] C["Enterprise Edition - ¥99,800/year"] D["Flagship Edition - ¥199,800/year"] end subgraph "Target Customers" A1["Individual Developers"] B1["SMEs"] C1["Large Enterprises"] D1["Group Enterprises"] end A --> A1 B --> B1 C --> C1 D --> D1

1.2 Feature Comparison

Feature Module	Community	Professional	Enterprise	Flagship
Basic Framework	✅	✅	✅	✅
Enhanced RBAC	✅	✅	✅	✅
SSO Single Sign-On	-	✅	✅	✅
MFA Multi-Factor Auth	-	✅	✅	✅
Unified Audit Center	-	✅	✅	✅
Blockchain Attestation	-	-	✅	✅
Email Middleware	-	✅	✅	✅
Message Notification Center	-	✅	✅	✅
License Authorization	-	-	✅	✅
Multi-Tenant Management	-	-	✅	✅
Data Permission Engine	✅	✅	✅	✅
Sensitive Data Masking	-	✅	✅	✅
Technical Support	Community	Email	7x24	Dedicated Support

2. Business Model

2.1 Licensing Model

graph LR A["User Count"] --> B{"Choose Plan"} B -->|50 Users| C["Basic ¥9,800/year"] B -->|200 Users| D["Standard ¥29,800/year"] B -->|500 Users| E["Advanced ¥59,800/year"] B -->|Unlimited Users| F["Unlimited ¥99,800/year"]

Plan	User Count	Annual Fee	Cost Per User
Basic	50 Users	¥9,800/year	¥196/year
Standard	200 Users	¥29,800/year	¥149/year
Advanced	500 Users	¥59,800/year	¥120/year
Unlimited	Unlimited	¥99,800/year	-

2.2 Module-Based Licensing

Module	Professional	Enterprise
IAM Unified Identity Center	¥8,800/year	¥15,800/year
Audit Compliance Center	¥8,800/year	¥15,800/year
Mail Email Middleware	¥3,800/year	¥6,800/year
Notify Message Center	¥3,800/year	¥6,800/year
License Authorization Management	¥5,800/year	¥9,800/year
Tenant Multi-Tenant Management	¥5,800/year	¥9,800/year

2.3 Service Model

Service Type	Description	Pricing
Technical Support	Issue resolution, bug fixes	¥8,000/year
Custom Development	On-demand feature development	¥1,500/person-day
Training Services	Product training, ops training	¥3,000/person-day
Deployment & Implementation	Production environment deployment	¥5,000/time
Data Migration	Historical data migration	¥10,000/time
Compliance Certification	Information security certification support	¥50,000/time

3. Ecosystem Partnerships

3.1 Partner Ecosystem

graph TB subgraph "Partner Ecosystem" A["ISV Partnership"] B["Integrator Partnership"] C["Cloud Vendor Partnership"] D["Training Partnership"] E["Implementation Partnership"] end subgraph "Partnership Value" A1["Integrated sales commission"] B1["Project collaboration"] C1["Cloud marketplace listing"] D1["Training commission"] E1["Implementation project collaboration"] end A --> A1 B --> B1 C --> C1 D --> D1 E --> E1

3.2 ISV Partnership Model

graph LR A["Partner"] --> B["Joint Solution"] B --> C["Industry Customer Delivery"] C --> D["Sales Commission Model"] D --> A D --> E["RuoYiPlus"]

4. Development Roadmap

4.1 Short-Term Plan

gantt title Development Roadmap dateFormat YYYY-MM-DD section MVP IAM/Audit/Mail Core Features :2024-01-01, 90d section Productization License/Tenant Commercialization :2024-04-01, 90d section Ecosystem Building First Batch of Partners :2024-07-01, 90d section Market Promotion Industry Solutions :2024-10-01, 90d

Phase	Timeline	Goal
MVP	Q1	IAM/Audit/Mail core features
Productization	Q2	License/Tenant commercialization
Ecosystem Building	Q3	First batch of partners
Market Promotion	Q4	Industry solutions

4.2 Medium-to-Long-Term Vision

graph TB subgraph "Medium-to-Long-Term Goals" A["AI Enhancement
Intelligent Q&A, Smart Reports"] B["Microservices
Full microservices architecture"] C["Multi-Cloud Deployment
Cloud-native K8s support"] D["Internationalization
Multi-language, multi-timezone"] end

Phase	Goal
AI Enhancement	Intelligent Q&A, smart reports
Microservices	Full microservices architecture
Multi-Cloud Deployment	Cloud-native K8s support
Internationalization	Multi-language, multi-timezone

5. Success Stories

Case 1: Provincial Government Cloud Platform

graph LR A["A Provincial Government Cloud Operator"] --> B["Needed unified office platform for 200+ bureaus"] B --> C["RuoYiPlus Enterprise + OA Enhancement"] C --> D["100K+ Users"] D --> E["Delivered in 3 months
Saved 5M+ in development costs"]

Case 2: Financial Institution CRM

graph LR A["A City Commercial Bank"] --> B["High compliance requirements
Needed Level 3 Protection certification"] B --> C["RuoYiPlus Flagship
+ CRM Enhancement + Audit"] C --> D["2000+ Users"] D --> E["Passed Level 3 Protection certification
Zero-risk audit compliance"]

Case 3: Manufacturing Group ERP

graph LR A["A Listed Manufacturing Group"] --> B["30+ subsidiaries
Needed data isolation"] B --> C["RuoYiPlus Enterprise
+ Tenant Multi-Tenant"] C --> D["5000+ Users
30+ Tenants"] D --> E["Unified platform + data isolation
60% reduction in ops costs"]

Contact Us

Type	Contact
Pre-Sales Inquiry
Business Cooperation
Channel Partnership
Technical Support

Disclaimer: RuoYiPlus is developed based on the RuoYi-Vue-Pro / Yudao open-source framework, following the original framework’s open-source license. We do not claim ownership of the framework itself, and only provide enterprise-level enhancements and commercial packaging on top of the open-source framework.

Customizing Hugo

Mon, 01 Jan 0001 00:00:00 +0000

View the full docs at

Feature List

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

This is the “capability map” of the entire platform. Before deciding to use RuoYi, you can quickly determine through this list: Are the capabilities you need already built-in? If so, how quickly can you go live?

Total code volume approximately 260,000 lines, covering 19 system features, 17 infrastructure items, and 14 business subsystems.

Feature Panorama

mindmap root((RuoYi-Vue-Pro
Feature Panorama)) System Features User Management Role Management Menu Management Department Management Position Management Tenant Management Dictionary Management Notifications & Announcements Operation Logs Login Logs Sensitive Word Management Infrastructure Code Generator File Service Message Queue Configuration Management WebSocket Service Assurance System Monitoring Business Subsystems BPM Workflow CRM Customer Management ERP Purchase-Sales-Inventory Mall E-Commerce MES Manufacturing Execution WMS Warehouse Management Pay Payment Center AI Large Model IoT Internet of Things IM Instant Messaging

System Features (19 Items)

These are the “standard” capabilities of admin panels — universal features needed by any enterprise system:

Feature	Problem Solved	Typical Scenario
User Management	Manage system login accounts, support CRUD, password reset, status control	Create employee accounts, disable departed employees
Online Users	View currently online users in real-time, support forced logout	Security investigation, account anomaly handling
Role Management	RBAC permission model, roles assigned menu and button permissions	Set “Sales Manager” to only see CRM module
Menu Management	Dynamically configure sidebar menu, support directory/menu/button three levels	Configure menus after adding new business modules
Department Management	Organizational structure tree, support data scope permissions	Beijing branch can only see Beijing data
Position Management	Position dictionary, associated with users	Link positions to salary/approval permissions
Tenant Management	SaaS tenant registration, package assignment, expiration handling	SaaS provider managing multiple enterprise clients
Tenant Packages	Bind different menu permissions for different tenant packages	Basic/Professional/Enterprise edition feature differences
Dictionary Management	Global enumeration value maintenance, shared by frontend and backend	Gender, status, type dropdown options
SMS Management	SMS templates, sending records, channel configuration	Verification codes, notification SMS
Email Management	Email templates, sending records, SMTP configuration	Registration verification, system alerts
Internal Messages	In-system message notifications, read/unread status	Approval notifications, system announcements
Operation Logs	Record every user operation with request parameters and results	Audit tracing, issue investigation
Login Logs	Record login IP, time, result	Security audit, abnormal login detection
Error Code Management	Unified error code definitions, user-friendly prompts	API returns `1002005001` for “User not found”
Notifications & Announcements	System-level announcements, support scheduled publishing	System maintenance notices, company announcements
Sensitive Words	Sensitive word library management and auto-filtering	Content moderation, comment filtering
Application Management	Multi-application configuration, e.g., admin panel + mobile	One system, multiple entry points
Region Management	China administrative division data, province/city/district three levels	Address picker, logistics regions

Infrastructure (17 Items)

These are the underlying capabilities that support business operations:

Capability	Problem Solved	Technical Implementation
Code Generator	One-click CRUD frontend/backend code generation, eliminating repetitive work	Template engine, supports master-child tables, tree tables, uni-app
System API	Online API documentation based on Swagger	Swagger3 + Knife4j
Database Documentation	Auto-generate database table structure docs	Screw
Form Builder	Visual drag-and-drop form design	Low-code form designer
Configuration Management	Dynamic parameter configuration, no restart needed	System parameters + Configuration Center
File Service	Unified file upload/download, multi-cloud storage switching	S3 protocol: MinIO/Alibaba OSS/Tencent COS/Qiniu
WebSocket	Real-time bidirectional communication	Standalone/Cluster dual mode
API Logs	Record API request and response details	Interceptor + async write
MySQL Monitoring	Database connection pool and slow query monitoring	Druid
Redis Monitoring	Redis memory, hit rate, connection monitoring	Built-in monitoring panel
Java Monitoring	JVM memory, threads, GC monitoring	Spring Boot Actuator
Distributed Tracing	Distributed request trace tracking	SkyWalking integration
Log Center	Centralized multi-service log viewing	Log file management
Service Assurance	Distributed locks, idempotency, rate limiting, deduplication	Redisson + custom annotations
Unit Testing	Ensure code quality	JUnit5 + 1121+ test cases

Business Subsystem Overview

Subsystem	Table Count	One-Sentence Description
BPM Workflow	-	Approval process engine, DingTalk-like designer
Pay Payment Center	-	Unified payment/refund/transfer, abstracting channel differences
Report Dashboards	-	Drag-and-drop dashboard design, three reporting engines
Member Center	-	Membership system, VIP levels, points check-in
MP Official Accounts	-	Multi-account management, follower messages, auto-reply
Mall E-Commerce	70+	Complete B2C e-commerce system
CRM Customer Management	20+	Lead → Opportunity → Contract → Collection full process
ERP Purchase-Sales-Inventory	30+	Procurement/sales/inventory/finance integrated
Sale Finance	-	ERP sub-module, receipts/payments/settlements
WMS Warehouse Management	16	General warehouse management
MES Manufacturing Execution	133	Workshop-level manufacturing management
AI Large Model	-	Chat/drawing/knowledge base/workflow
IoT Internet of Things	-	Device management/thing model/rule engine
IM Instant Messaging	16	Private chat/group chat/channels/audio-video

Suitable Users

Java Developers: Have Spring Boot foundation, want to rapidly deliver enterprise-level projects
Small & Medium Teams: Need a foundation covering multiple business scenarios, reducing redundant development
Enterprise IT Departments: Internal digitalization, need mature modules like approval flows, purchase-sales-inventory, CRM
SaaS Providers: Need multi-tenant capabilities and modular architecture to serve multiple customers

Project Structure

Mon, 01 Jan 0001 00:00:00 +0000

Folder Structure

There are 4 main folders for Hugo-based sites:

content/ for your Markdown-formatted content files (homepage, etc.)
- _index.md the homepage (Hugo requires that the homepage and archive pages have an underscore prefix)
assets/
- media/ for your media files (images, videos)
  - icons/custom/ upload any custom SVG icons you want to use
config/_default/ for your site configuration files
- hugo.yaml to configure Hugo (site title, URL, Hugo options, setup per-folder page features)
- module.yaml to install or uninstall Hugo themes and plugins
- params.yaml to configure Hugo Blox options (SEO, analytics, site features)
- menus.yaml to configure your menu links (if the menu is enabled in params.yaml)
- languages.yaml to configure your site’s language or to set language-specific options in a multilingual site
static/uploads/ for any files you want visitors to download, such as a PDF
go.mod sets the version of Hugo themes/plugins which your site uses

Hugo File Naming Convention

Hugo gives us two options to name standard page files: as TITLE/index.md or TITLE.md where TITLE is your page name.

The page name should be lowercase and using hyphens (-) instead of spaces.

Both approaches result in the same output, so you can choose your preferred approach to naming and organizing files. A benefit to the folder-based approach is that all your page’s files (such as images) are self-contained within the page’s folder, so it’s more portable if you wish to share the original Markdown page with someone.

The homepage is a special case as Hugo requires the homepage and listing pages to be named _index.md.

The docs navigation is automatically generated based on the content in the docs/ folder and is sorted alphabetically.

The order of pages can be changed by adding the weight parameter in the front matter of your Markdown files.

In the example below, the example.md page will appear before the test.md page as it has a lower weight:

Page example.md:

---
title: My Example
weight: 1
---

Page test.md:

---
title: My Test
weight: 2
---

Configuration

Mon, 01 Jan 0001 00:00:00 +0000

The configuration of your site can be found in config/_default/.

Full Documentation

See

Links are automatically generated from the structure of your content directory. Simply add a folder to nest a page.

Extra Links

Additional links can be added under the sidebar section of your config/_default/menus.yaml:

menu:
 sidebar:
 - name: "Need help?"
 params:
 type: separator
 weight: 1
 - name: "A page"
 pageRef: "/page-filename-here"
 weight: 2
 - name: "An external link ↗"
 url: "https://hugoblox.com"
 weight: 3

A table of contents is automatically generated from the headings your Markdown file.

It can optionally be disabled by setting toc: false in the front matter of a page:

---
title: My Page
toc: false
---

Report Dashboards & Data Visualization

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

The Report module enables non-technical users to create professional data dashboards. Without writing any frontend code, by dragging and dropping components and configuring data sources, you can generate visual reports and dashboard pages. Suitable for management dashboards, data monitoring, project reporting, and similar scenarios.

In one sentence: Create data dashboards like making a PowerPoint presentation.

Problems Solved

Pain Point	How Report Solves It
Management wants to see data, developers have to write pages each time	Drag-and-drop design, business users can do it themselves
Data display requirements change frequently	Modify dashboard configuration, no deployment needed
Need professional visualization effects	Built-in dozens of chart components and templates
Different scenarios need different reporting engines	Three engines provided, choose as needed

User Roles

graph LR subgraph Roles DESIGNER["Dashboard Designer
Drag-and-drop dashboard configuration
Set up data sources
Publish dashboards"] VIEWER["Viewer (Management/Clients)
View dashboards
Interactively filter data"] end

Three Reporting Engines

graph TB subgraph GoView["Go-View (Recommended)"] G1["Open-source & free"] G2["Vue3 tech stack"] G3["Pure frontend, standalone deployment"] G4["Rich built-in chart components"] end subgraph Jimu["JimuReport"] J1["Not open-source"] J2["Embedded backend"] J3["Supports complex reports"] J4["Chinese-style reports"] end subgraph AJ["AJ-Report"] A1["Open-source"] A2["Under development"] A3["Fully backend-driven"] end

Feature	Go-View	JimuReport	AJ-Report
Open-source	✅	❌	✅
Learning Curve	⭐ Low	⭐⭐ Medium	⭐⭐ Medium
Chart Richness	⭐⭐⭐⭐⭐	⭐⭐⭐⭐	⭐⭐⭐
Complex Reports	⭐⭐⭐	⭐⭐⭐⭐⭐	⭐⭐⭐
Recommended Scenario	General dashboards	Chinese-style complex reports	Backend-driven scenarios

Dashboard Design Process

flowchart LR A["New Dashboard
Choose template or blank"] --> B["Drag Components
Charts/Text/Images/Borders"] B --> C["Configure Data Sources
API / Static Data"] C --> D["Adjust Styles
Layout/Colors/Animations"] D --> E["Preview
Real-time view"] E --> F{Satisfied?} F -->|Yes| G["Publish Dashboard
Generate access link"] F -->|No| B

Built-in Chart Components (Partial)

Line Chart / Bar Chart / Pie Chart / Radar Chart
Data Table / Scrolling Table
Number Flipper
Map (China / Province / City)
Gauge
Word Cloud
Timeline
Border and Decoration Components

Typical Application Scenarios

Scenario	Dashboard Content	Viewers
Sales Dashboard	Today’s sales, order volume, conversion rate, regional ranking	Sales Director, Management
Production Monitoring	Production line status, output, defect rate, equipment OEE	Production Manager, Plant Manager
Operations Dashboard	User growth, activity, retention, revenue trends	Operations Team
Project Reporting	Project progress, milestones, risks, resource usage	Project Stakeholders

Yudao Framework Enhancement Capabilities

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

In a nutshell: On top of Yudao’s native capabilities, RuoYiPlus has made enterprise-level enhancements across 8 major dimensions to the framework infrastructure, giving the framework “out-of-the-box” production-grade capabilities.

What Problems It Solves

Pain Point	Yudao Native	After RuoYiPlus Enhancement
Insufficient data permissions	Dept-level filtering only	User/Role/Post/Dept four layers + field-level
Sensitive information leak risk	No masking mechanism	Annotation-based auto masking
Incomplete operation logs	Basic logging	Intelligent change tracking + risk scoring + blockchain attestation
Lack of API protection	Basic routing	Request signing + rate limiting + circuit breaking
Weak distributed capabilities	None	Distributed transactions + locks + idempotency
Single caching strategy	Redis single layer	Caffeine + Redis multi-level cache
Difficult database scaling	Single database	Read/write separation + sharding + data archiving
Weak monitoring capabilities	None	SkyWalking full-chain tracing + custom metrics

Suitable Users

mindmap root((Suitable Users)) Software Vendors Need authorization management Need commercial infrastructure Enterprise IT Teams Need security compliance Need multi-tenant isolation System Integrators Need rapid delivery Need modular assembly SaaS Operators Need multi-tenant architecture Need billing system

1. Data Permission Engine

1.1 Four-Layer Permission Model

graph LR subgraph "Permission Sources" F["User Permissions
Highest Priority"] G["Role Permissions"] H["Post Permissions"] I["Dept Permissions
Lowest Priority"] F ~~~ G ~~~ H ~~~ I end subgraph "Permission Decision Engine" A["User Request"] --> B["Permission Resolution"] B --> C["Permission Merge"] C --> D["Data Filtering"] D --> E["Level Filtering"] end subgraph "Permission Filtering" J["SQL Filtering"] --> K["Return Results"] end PS["Permission Sources"] --> PDE["Permission Decision Engine"] PDE["Permission Decision Engine"] --> PF["Permission Filtering"] style B fill:#FFA500,color:#fff,font-weight:bold

1.2 Capability Comparison

Capability	Native Support	After Enhancement
Dept-level data filtering	✅	✅
Role-level data filtering	❌	✅
Custom SQL filtering	❌	✅
Field-level permission control	❌	✅
Dynamic data permission rules	❌	✅
Customer level filtering	❌	✅

1.3 Usage

// Role-based data permission: Sales manager sees team data, regional director sees region data
@DataPermission(roles = {"sales_manager", "region_director"})
public class CustomerServiceImpl { }

// Dept-based hierarchical permission
@DataPermission(deptIds = "#{currentUser.deptId}")
public class ReportService { }

// Custom data scope
@DataPermission(scope = "custom", sqlFilter = "region_id = #{currentUser.regionId}")
public class RegionService { }

// Field hiding
@DataPermission(fields = {"salary", "bankCard"}, operation = DataPermission.Operation.HIDE)
public class EmployeeService { }

// Field read-only
@DataPermission(fields = {"createTime", "creator"}, operation = DataPermission.Operation.READONLY)
public class OrderService { }

2. Sensitive Field Masking

2.1 Masking Architecture

graph LR A["Data Query"] --> B["Masking Rule Match"] B --> C["Field Type Identification"] C --> D["Masking Algorithm Application"] D --> E["Return Masked Result"]

2.2 Supported Masking Types

Masking Type	Example	Description
Phone Number	`138****1234`	Middle 4 digits masked
Email	`a***@163.com`	Username masked
ID Card	`310***********1234`	Birth date + last 4 digits masked
Bank Card	`** ** 1234`	Only last 4 digits retained
Name	`Zhang*`	All but surname masked
Address	`Shanghai Xuhui District****`	Detailed address masked
Password	`******`	Fully masked

2.3 Usage

// Annotation-based masking
public class Customer {
 @SensitiveField(type = SensitiveType.PHONE)
 private String phone;

 @SensitiveField(type = SensitiveType.EMAIL)
 private String email;

 @SensitiveField(type = SensitiveType.ID_CARD)
 private String idCard;
}

// Auto-masking on query
@SensitiveQuery(fields = {"phone", "email"})
public List<Customer> getCustomerList(CustomerQuery query) { }

3. Operation Log Center

3.1 Log System

graph TB subgraph "Log Collection" A["Operation Behavior"] B["Login Events"] C["API Calls"] end subgraph "Log Processing" D["Log Parsing"] E["Change Comparison"] F["Risk Scoring"] end subgraph "Log Storage" G["Hot Data Storage"] H["Cold Data Archiving"] I["Blockchain Attestation"] end A --> D B --> D C --> D D --> E E --> F F --> G F --> H F --> I

3.2 Intelligent Change Tracking

// Auto-compare before/after changes, only record changed fields
@OperateLog(title = "Customer Management", businessType = BusinessType.UPDATE)
public void updateCustomer(Customer customer) { }

3.3 Sensitive Operation Alerts

aegis:
 audit:
 alert-rules:
 - event: "Data Export"
 threshold: 10 # More than 10 times in 10 minutes
 action: "notify_admin"
 - event: "Batch Delete"
 action: "require_approval"

4. API Gateway Enhancement

4.1 Gateway Architecture

graph LR A["Client Request"] --> B["API Gateway"] B --> C["Request Signature Verification"] C --> D["Traffic Control"] D --> E["Circuit Breaking"] E --> F["Request Caching"] F --> G["Protocol Conversion"] G --> H["Backend Service"]

4.2 Enhancement Features

Capability	Description
Request Signing	API request signature verification, anti-tampering
Traffic Control	Multi-dimensional rate limiting strategies
Circuit Breaking	Service circuit breaker protection
Request Caching	API response caching
Protocol Conversion	SOAP → REST conversion

5. Service Governance

5.1 Distributed Transactions

Seata-based distributed transaction solution:

graph TB A["Business Request"] --> B["Transaction Initiator"] B --> C["Seata TC"] C --> D["Branch Transaction 1"] C --> E["Branch Transaction 2"] C --> F["Branch Transaction 3"] D --> G["Global Commit/Rollback"] E --> G F --> G

5.2 Distributed Lock and Idempotency

// Redis + Redisson distributed lock
@DistributedLock(key = "order:lock:", waitTime = 30, leaseTime = 60)
public void processOrder(Order order) { }

// Idempotency control
@Idempotent(key = "order:create:{userId}:{productId}", expireTime = 60)
public Order createOrder(CreateOrderRequest request) { }

6. Cache Enhancement

6.1 Multi-Level Cache Architecture

graph LR A["Application Request"] --> B["L1 Caffeine"] B --> C["L2 Redis"] C --> D["Database"] D --> C C --> B B --> A

6.2 Annotation-Based Caching

@Cacheable(name = "user:list:", expire = 300)
public List<User> getUserList() { }

@CacheEvict(name = "user:list:")
public void updateUser(User user) { }

@CachePut(name = "user:{id}")
public User getUser(Long id) { }

7. Database Enhancement

graph LR A["Write Request"] --> B["Primary DB"] C["Read Request"] --> D["Replica DB"] B --> E["Data Sync"] E --> D

Capability	Description
Read/Write Separation	Auto-route read/write requests, dynamic-datasource
Sharding	ShardingSphere sharding strategies
Data Archiving	Auto hot/cold data separation, scheduled archiving

8. Monitoring Enhancement

graph TB A["Client"] --> B["Gateway"] B --> C["Service 1"] C --> D["Service 2"] D --> E["Service 3"] E --> F["Database"] G["SkyWalking"] -.-> B G -.-> C G -.-> D G -.-> E

Full-Chain Tracing: Integrated SkyWalking distributed tracing
Custom Metrics: @CustomMonitor annotation auto-records
Alert Rules: Supports multi-level threshold alerts

Technical Architecture Overview

graph TB subgraph "RuoYiPlus Framework Enhancement Layer" P1["Data Permission Engine
Four-Layer Permissions + Field-Level"] P2["Sensitive Field Masking
Annotation-Based Auto Masking"] P3["Operation Log Center
Change Tracking + Blockchain Attestation"] P4["API Gateway
Signing + Rate Limiting + Circuit Breaking"] P5["Service Governance
Distributed Transactions + Locks + Idempotency"] P6["Multi-Level Cache
Caffeine + Redis"] P7["Database Enhancement
Read/Write Separation + Sharding"] P8["Full-Chain Monitoring
SkyWalking + Custom Metrics"] end subgraph "Yudao Framework Core" CORE["Spring Boot 3 + MyBatis-Plus + Redis"] end P1 --> CORE P2 --> CORE P3 --> CORE P4 --> CORE P5 --> CORE P6 --> CORE P7 --> CORE P8 --> CORE

AI Large Model

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

The AI module is a one-stop AI capability integration platform, connecting to mainstream large models both domestically and internationally, providing 8 major AI capabilities including chat, drawing, knowledge base (RAG), tool calling, workflow, writing, mind mapping, and music creation. Whether you want to add an AI assistant to your system or build an AI-native application, ready-to-use capabilities are all here.

In one sentence: Make your system “able to chat, draw, write articles, and sing.”

Problems Solved

Pain Point	How the AI Module Solves It
Integrating large models requires individual API integration	Unified integration of mainstream domestic and international models, one-time integration
Internal enterprise knowledge cannot be utilized by AI	RAG knowledge base lets AI understand your documents
Single AI capability (only chatting)	8 major capability modules covering various scenarios
Need to orchestrate AI workflows	Integrated with Dify/FastGPT/Coze workflow platforms
Complex switching between domestic and international models	Unified API layer, switch models without changing code

User Roles

graph LR subgraph Roles AI_ADMIN["AI Administrator
Configure model access
Manage knowledge bases
Set permissions"] AI_USER["AI User
Chat conversations
Drawing creation
Knowledge base Q&A
Writing/Mind mapping"] AI_DEV["Developer
Integrate AI capabilities via API
Create custom workflows"] end

8 Major Functional Modules

graph TB AI_CORE["AI Large Model Platform"] AI_CORE --> CHAT["💬 AI Chat
Multi-model conversation
Context memory
Internet search
Thinking reasoning mode"] AI_CORE --> IMAGE["🎨 AI Drawing
Text-to-image
Supports Stable Diffusion
Midjourney"] AI_CORE --> RAG["📚 AI Knowledge Base
RAG retrieval-augmented generation
Upload documents for Q&A"] AI_CORE --> TOOL["🔧 AI Tool Calling
Function Calling
MCP Protocol"] AI_CORE --> WORKFLOW["🔄 AI Workflow
Integrates Dify/FastGPT/Coze
Visual orchestration"] AI_CORE --> WRITE["✍️ AI Writing
Articles/Reports/Emails
Multi-scenario templates"] AI_CORE --> MINDMAP["🧠 AI Mind Mapping
Auto-generate mind maps"] AI_CORE --> MUSIC["🎵 AI Music
Suno AI music creation"]

Supported Models

Domestic Models

Model	Provider	Features
Tongyi Qianwen	Alibaba Cloud	Strong comprehensive capability
DeepSeek	DeepSeek	High cost-effectiveness, strong reasoning
Doubao	ByteDance	Multimodal capability
Hunyuan	Tencent	Good ecosystem integration
Wenxin Yiyan	Baidu	Strong Chinese comprehension
GLM	Zhipu AI	Open-source friendly
Spark	iFlytek	Outstanding voice capability
Moonshot	Moonshot AI	Long context
MiniMax	MiniMax	Multimodal
BaiChuan	Baichuan Intelligence	Chinese optimized
SiliconFlow	SiliconFlow	Multi-model aggregation

International Models

Model	Provider
GPT	OpenAI
Claude	Anthropic
Llama	Meta
Gemini	Google

Core Capability Details

AI Chat

User: Help me analyze this quarter's sales data
 ↓
AI: Based on the data, Q3 sales increased 15% year-over-year, including...
 ↓ (Supports Thinking reasoning mode)
Displays complete reasoning process + conclusions

Supports internet search, enabling AI to access real-time information.

AI Knowledge Base (RAG)

flowchart LR DOC["Upload Documents
PDF/Word/Web Pages"] --> PARSE["Document Parsing
Segmentation/Vectorization"] PARSE --> STORE["Vector Storage"] QUERY["User Question"] --> SEARCH["Retrieve Relevant Passages"] STORE --> SEARCH SEARCH --> LLM["Large Model
Answer with context"] LLM --> ANSWER["Accurate Answer"]

AI Workflow

Integrates Dify, FastGPT, Coze, and other platforms, enabling visual orchestration of complex AI workflows, such as:

Intelligent Customer Service: User question → Intent recognition → Knowledge base retrieval → Escalation decision
Content Generation: Keywords → Outline → Body → Image generation → Publishing

Security Compliance Capabilities

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

In a nutshell: Build a defense-in-depth security system for enterprises, meeting Level 3 Information Security Protection and financial-grade security audit requirements, making business systems “natively compliant”.

What Problems It Solves

Compliance Requirement	RuoYiPlus Security Solution
Level 3 Information Security Protection certification	Identity verification + access control + security audit + data integrity + data confidentiality
Financial-grade audit	Blockchain hash chain attestation + tamper-proof operation logs
Data privacy protection	Auto masking of sensitive fields + transport encryption + storage encryption
Risk prevention	Real-time risk monitoring + abnormal behavior alerts + account freezing

Suitable Users

mindmap root((Security Compliance Users)) Financial Institutions Level 3 Protection certification Financial audit compliance Healthcare Industry HIPAA compliance Patient data protection Government Platforms Leveled protection Data security SaaS Enterprises Multi-tenant security isolation Data privacy compliance

User Roles

1. Security System Architecture

graph TB subgraph "RuoYiPlus Security Compliance System" subgraph "Identity Authentication Layer" A1["IAM Center"] A2["Multi-Factor Authentication"] A3["SSO Single Sign-On"] end subgraph "Access Control Layer" B1["RBAC Permissions"] B2["Data Permissions"] B3["API Permissions"] end subgraph "Data Security Layer" C1["Encryption & Masking"] C2["Tamper Prevention"] C3["Data Classification"] end subgraph "Security Audit Layer" D1["Audit Center"] D2["Risk Alerts"] D3["Compliance Reports"] end subgraph "Security Protection Layer" E1["WAF"] E2["Injection Prevention"] E3["XSS Prevention"] E4["CSRF Prevention"] E5["DDoS Prevention"] E6["Key Management"] end end A1 --> B1 A2 --> B1 A3 --> B1 B1 --> C1 B2 --> C1 B3 --> C1 C1 --> D1 C2 --> D1 C3 --> D1 D1 --> E1

2. Identity Authentication Security

2.1 Multi-Factor Authentication (MFA)

graph LR A["User Login"] --> B{"MFA Required?"} B -->|Yes| C["Enter Password"] C --> D{"Select Verification Method"} D --> E["SMS OTP"] D --> F["Email OTP"] D --> G["TOTP"] D --> H["Hardware Key"] E --> I["Authentication Successful"] F --> I G --> I H --> I B -->|No| I

Authentication Method	Security Level	Description
Password + CAPTCHA	⭐⭐	Basic two-factor
Password + SMS OTP	⭐⭐⭐	Dynamic SMS verification code
Password + Email OTP	⭐⭐⭐	Email verification code
Password + TOTP	⭐⭐⭐⭐	Time-based one-time password
Password + Hardware Key	⭐⭐⭐⭐⭐	FIDO2/U2F highest security

2.2 SSO Single Sign-On

sequenceDiagram participant User as User participant App1 as App 1 participant IAM as IAM Auth Center participant App2 as App 2 User->>App1: Access App 1 App1->>IAM: Not authenticated, redirect to auth User->>IAM: Enter credentials IAM->>IAM: Authentication success, issue Token IAM->>App1: Return Token User->>App2: Access App 2 App2->>IAM: Verify Token IAM->>App2: Token valid App2->>User: Direct access

Protocol	Supported	Use Case
OAuth 2.0	✅	Third-party app authorization
OIDC	✅	Modern app SSO
SAML 2.0	✅	Enterprise SSO
LDAP	✅	Enterprise directory integration

security:
 login:
 password:
 min-length: 8
 require-uppercase: true
 require-lowercase: true
 require-digit: true
 require-special: true
 expiry-days: 90
 history-count: 5
 lockout:
 max-failed: 5
 lockout-duration: 30m
 abnormal:
 enabled: true
 notify-on-new-device: true
 block-high-risk: true

3. Access Control

3.1 RBAC Permission Model

graph TB A["User"] --> B["Role"] B --> C["Menu Permission"] B --> D["Operation Permission"] B --> E["Data Permission"] A --> F["Post"] F --> G["Role Inheritance"] F --> H["Data Scope"]

3.2 Data Permission Control

graph LR A["Data Request"] --> B{"Permission Type"} B -->|All Data| C["*"] B -->|Dept Data| D["dept_id = current.dept_id"] B -->|Own Data| E["creator_id = current.user_id"] B -->|Custom Data| F["region_id IN current.regions"] C --> G["Return Data"] D --> G E --> G F --> G

3.3 API Permission Control

// Method-level permission control
@RequiresPermissions(value = {"system:user:add", "system:user:edit"}, logical = Logical.OR)
public void saveUser(User user) { }

// Role permission control
@RequiresRoles(value = {"admin", "manager"})
public void exportReport() { }

// Custom permission check
@RequiresCustomPermissions(key = "data:export:financial")
public void exportFinancial() { }

4. Data Security

4.1 Sensitive Field Masking Flow

graph TB A["Data Query"] --> B["Masking Rule Match"] B --> C{"Field Type"} C -->|Phone| D["Middle 4 digits masked"] C -->|Email| E["Username masked"] C -->|ID Card| F["Birth date + last 4 digits"] C -->|Bank Card| G["Only last 4 digits"] C -->|Name| H["All but surname masked"] C -->|Password| I["Fully hidden"] D --> J["Return Masked Result"] E --> J F --> J G --> J H --> J I --> J

4.2 Transport and Storage Security

Configuration	Description
HTTPS Enforced	Site-wide HTTPS, HTTP auto-redirect
TLS Version	TLS 1.3 (compatible with TLS 1.2)
HSTS	Enforce HTTPS usage
Database Encryption	AES encryption for sensitive fields

5. Audit Trail

5.1 Audit Event Collection

graph TB subgraph "Audit Event Collection" A1["Login Audit"] A2["Operation Audit"] A3["Permission Audit"] A4["Export Audit"] A5["Sensitive Audit"] A6["API Audit"] end subgraph "Audit Processing" B1["Event Parsing"] B2["Risk Scoring"] B3["Rule Matching"] end subgraph "Audit Storage" C1["Hot Data"] C2["Cold Data"] C3["Blockchain"] end A1 --> B1 A2 --> B1 A3 --> B1 A4 --> B1 A5 --> B1 A6 --> B1 B1 --> B2 B2 --> B3 B3 --> C1 B3 --> C2 B3 --> C3

5.2 Blockchain Hash Chain

graph TB subgraph "Genesis Block" A1["blockHash = SHA256"] A2["genesisData"] end subgraph "Block N" B1["blockHash = SHA256"] B2["previousHash"] B3["merkleRoot"] B4["signature"] end subgraph "Block N+1" C1["blockHash = SHA256"] C2["previousHash = Block N hash"] C3["merkleRoot"] C4["signature"] end A1 --> B2 B1 --> C2

6. Compliance Support

6.1 Level 3 Information Security Protection Coverage

graph LR A["Level 3 Protection Requirements"] --> B["Identity Verification"] A --> C["Access Control"] A --> D["Security Audit"] A --> E["Data Integrity"] A --> F["Data Confidentiality"] A --> G["Backup & Recovery"] B --> H["MFA/SSO"] C --> I["RBAC/Data Permissions"] D --> J["Audit Center"] E --> K["Blockchain Hash Chain"] F --> L["Encryption & Masking"] G --> M["Data Backup Solution"]

Protection Requirement	Implementation	Coverage
Identity Verification	MFA/SSO	✅ Complete
Access Control	RBAC/Data Permissions	✅ Complete
Security Audit	Audit Center	✅ Complete
Data Integrity	Blockchain Hash Chain	✅ Complete
Data Confidentiality	Encryption & Masking	✅ Complete
Backup & Recovery	Data Backup Solution	✅ Complete

7. Security Monitoring

7.1 Real-Time Risk Monitoring

graph TB subgraph "Risk Monitoring" A1["Remote Login"] A2["Brute Force"] A3["Abnormal Query"] A4["Batch Export"] A5["Permission Abuse"] end subgraph "Risk Assessment" B["Risk Engine"] end subgraph "Response Actions" C1["SMS Alert"] C2["Account Freeze"] C3["Log Marking"] C4["Require Approval"] C5["Real-Time Alert"] end A1 --> B A2 --> B A3 --> B A4 --> B A5 --> B B --> C1 B --> C2 B --> C3 B --> C4 B --> C5

Monitoring Item	Risk Threshold	Response Action
Remote Login	Login from new city	SMS alert
Brute Force	>10 failures in 5 min	Account freeze
Abnormal Query	>100 queries/min per user	Log marking
Batch Export	>50 records/min	Require approval
Permission Abuse	Core data access during off-hours	Real-time alert

8. Security Configuration Checklist

Configuration	Recommended Value	Description
Min Password Length	12 characters	Strong password policy
Password Expiry	90 days	Enforce periodic changes
Login Failure Lockout	5 attempts	Brute force prevention
MFA	Enforced	Must be enabled for admins
HTTPS	Enforced	Site-wide encryption
Log Retention	1 year	Compliance requirement
Session Timeout	30 minutes	Auto logout
API Rate Limit	100 QPS	DDoS prevention

Security Capability Overview

graph TB subgraph "Defense-in-Depth Security" L1["🔐 Identity Authentication Layer
MFA + SSO + Password Policy"] L2["🛡️ Access Control Layer
RBAC + Data Permissions + API Permissions"] L3["🔒 Data Security Layer
Masking + Encryption + Tamper Prevention"] L4["📋 Audit Trail Layer
Full-Chain Audit + Blockchain Attestation"] L5["🚨 Security Monitoring Layer
Real-Time Risk Monitoring + Auto Response"] end L1 --> L2 L2 --> L3 L3 --> L4 L4 --> L5

CRM Customer Relationship Management

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

CRM is the sales team’s “command center.” From a single lead, to converting into a customer, creating an opportunity, signing a contract, and receiving payment — the entire sales funnel is visualized here. Combined with the public pool mechanism, it prevents customer resources from being “hoarded” by individual salespeople.

In one sentence: Help your sales team say goodbye to managing customers in Excel, and make every deal traceable.

Problems Solved

Pain Point	How CRM Solves It
Customer info scattered in salespeople’s personal WeChat/Excel	Unified customer database, no data loss during handover
Sales collision, multiple people following the same customer	Customer lock mechanism + public pool rules
No visibility into what salespeople do daily	Follow-up records, visit records fully logged
Unclear which part of the sales funnel has issues	Lead→Customer→Opportunity→Contract conversion rate visualization
Chaotic payment collection management	Contract → Payment Plan → Payment Record full chain

User Roles

graph LR subgraph Roles SALES["Salesperson
Follow up on leads and customers
Create opportunities and contracts
Record follow-ups and payments"] MANAGER["Sales Manager
Assign leads and customers
Approve contracts
View team data"] ADMIN4["Administrator
Configure public pool rules
Manage product catalog
Data statistics and analysis"] end

Complete Sales Process

Core Table Structure (ER Diagram)

erDiagram CRM_CLUE ||--o| CRM_CUSTOMER : "Converted to" CRM_CUSTOMER ||--o{ CRM_CONTACT : "Has" CRM_CUSTOMER ||--o{ CRM_BUSINESS : "Creates" CRM_BUSINESS ||--o{ CRM_CONTRACT : "Advances to" CRM_CONTRACT ||--o{ CRM_RECEIVABLE : "Payment" CRM_CONTRACT ||--o{ CRM_RECEIVABLE_PLAN : "Payment Plan" CRM_CLUE { bigint id PK varchar name "Lead Name" varchar mobile "Phone Number" tinyint status "Status" bigint owner_user_id FK "Owner" } CRM_CUSTOMER { bigint id PK varchar name "Customer Name" tinyint level "Customer Level" bigint owner_user_id FK "Owner" } CRM_CONTACT { bigint id PK bigint customer_id FK varchar name "Contact Name" varchar mobile "Phone Number" } CRM_BUSINESS { bigint id PK bigint customer_id FK varchar name "Opportunity Name" decimal total_price "Estimated Amount" tinyint status "Stage" } CRM_CONTRACT { bigint id PK bigint business_id FK varchar no "Contract Number" decimal total_price "Contract Amount" tinyint status "Status" } CRM_RECEIVABLE { bigint id PK bigint contract_id FK decimal price "Payment Amount" datetime time "Payment Time" }

Public Pool Mechanism

Rule	Description
Auto-Release	If no follow-up for N days, customer automatically falls into public pool
Advance Reminder	Remind salesperson to follow up before deadline
Lock Protection	Closed-deal customers permanently locked, will not fall into public pool
Customer Limit	Each salesperson has a maximum customer count limit to prevent hoarding
Scheduled Task	Background scheduled scan and execution of public pool release logic

Data Permissions

CRM uses an owner mechanism for data isolation:

Each customer/lead/opportunity/contract has an owner_user_id field
Salespeople can only see their own data
Sales managers can see team data
Administrators can see all data
Supports transfer operation: transfer customers to other salespeople

Feature List

Module	Features
Lead Management	Lead entry, assignment, conversion, invalid marking
Customer Management	Customer info, contacts, follow-up records, locking
Public Pool Customers	Public pool, claiming, release rules
Opportunity Management	Opportunity stages, estimated amount, win/loss
Contract Management	Contract creation, approval, changes
Payment Management	Payment plans, payment records, receivables statistics
Product Management	Product catalog, pricing
Data Statistics	Funnel analysis, performance statistics

IAM Identity & Access Center

Mon, 01 Jan 0001 00:00:00 +0000

Build an enterprise unified identity authentication and fine-grained permission governance system, achieving “One Account, One Authentication, Access Anywhere”

Core Positioning

In a nutshell: IAM is the “Identity and Access Hub” for all business systems, centrally managing user authentication, authorization, and data permissions so that each subsystem no longer operates in isolation.

What Problems It Solves

Pain Point	Traditional Approach	RuoYiPlus IAM Solution
Repeated logins across systems	Each system has independent login	SSO single sign-on, one authentication for all systems
Scattered permission management	Each system builds its own permissions	Unified RBAC + data permission engine
Uncontrollable security risks	Inconsistent password policies	MFA multi-factor + password policy + remote login detection
Incomplete compliance auditing	Scattered logs	Unified audit event collection, connected to Audit Center

Suitable Users

Medium-to-large enterprises with multiple business systems requiring unified identity management
Organizations needing Level 3 Information Security Protection certification
Platforms needing to integrate with third-party systems (OAuth/OIDC/SAML)

User Roles

graph TB subgraph "IAM User Roles" ADMIN["System Administrator
Configure authentication policies, manage users"] SECURITY["Security Administrator
Configure MFA, password policies"] DEV["Application Developer
Integrate SSO, connect OAuth"] USER["Regular User
Login authentication, access applications"] end ADMIN -->|Manage| USER_POOL["User Pool"] SECURITY -->|Configure| AUTH_POLICY["Authentication Policies"] DEV -->|Integrate| SSO_PROTOCOL["SSO Protocols"] USER -->|Use| LOGIN["Unified Login"]

Core Capabilities

SSO Single Sign-On Flow

sequenceDiagram participant User as User participant App1 as App A participant IAM as IAM Auth Center participant App2 as App B User->>App1: Access App A App1->>IAM: Not authenticated, 302 redirect User->>IAM: Enter username/password IAM->>IAM: Verify + MFA IAM->>App1: Issue JWT Token User->>App2: Access App B App2->>IAM: Verify Token IAM->>App2: Token valid App2->>User: Direct access, no re-login required

Supported Protocols

Protocol	Description	Use Case
OAuth 2.0	Authorization framework	Third-party app authorization
OIDC	Identity layer based on OAuth 2.0	Modern app SSO
SAML 2.0	Enterprise federated identity	Traditional enterprise apps
LDAP	Lightweight directory access	Enterprise directory integration

Multi-Factor Authentication (MFA)

Authentication Method	Security Level	Description
Password + SMS OTP	⭐⭐⭐	Dynamic SMS verification code
Password + Email OTP	⭐⭐⭐	Email verification code
Password + TOTP	⭐⭐⭐⭐	Time-based one-time password
Password + Hardware Key	⭐⭐⭐⭐⭐	FIDO2/U2F highest security

Permission Model

graph TB A["User"] --> B["Role"] B --> C["Menu Permission"] B --> D["Operation Permission"] B --> E["Data Permission"] A --> F["Post"] F --> G["Role Inheritance"] F --> H["Data Scope"] subgraph "Data Permission Hierarchy" E1["User Level (Highest)"] E2["Role Level"] E3["Post Level"] E4["Dept Level (Lowest)"] end E --> E1 E --> E2 E --> E3 E --> E4

Technical Architecture

graph TB subgraph "IAM Module" AUTH["Auth Service
Login/MFA/SSO"] USER_MGR["User Management
Users/Departments/Posts"] ROLE_MGR["Role Management
Roles/Permissions/Menus"] PERM_ENGINE["Permission Engine
Data Permissions/Field Permissions"] AUDIT_CLIENT["Audit Client
Event Reporting"] end subgraph "External Dependencies" REDIS["Redis
Session/Token Storage"] DB["MySQL
User/Permission Data"] SMS["SMS Service
OTP Codes"] MAIL["Email Service
OTP Codes"] end AUTH --> REDIS USER_MGR --> DB ROLE_MGR --> DB PERM_ENGINE --> DB AUTH --> SMS AUTH --> MAIL

Business Value

Value Point	Description
One Authentication	SSO single sign-on, reducing repeated logins
Security Enhancement	MFA multi-factor + password policy + remote detection
Unified Permissions	RBAC + data permission engine, fine-grained control
Compliance Ready	Connected to Audit Center, meeting Information Security Protection requirements

Audit Compliance Center

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, 5 DOs / 5 Controllers, menu ID starting from 10500, building an enterprise unified audit compliance center

Module Scale

Metric	Value
Data Objects (DO)	5
Controllers	5
Menu ID Start	10500
Maven Module	yudao-module-audit

Core Data Tables

Table Name	Description
`audit_event`	Audit Event
`audit_block`	Audit Block
`audit_rule`	Audit Rule
`audit_statistics`	Audit Statistics
`audit_auditor`	Auditor

Core Positioning

In one sentence: Audit is the platform’s “black box”, recording the complete chain of all key operations and using blockchain technology to ensure data immutability, meeting Level 3 classified protection and financial-grade audit requirements.

What Problems Does It Solve

Pain Point	Traditional Approach	RuoYiPlus Audit Solution
No operation traceability	Logs scattered across services	Unified audit event collection center
Data may be tampered with	Regular database logs	Blockchain hash chain proof
Low audit efficiency	Manual log checking	Change comparison + risk scoring + automated reports
Non-compliant	Incomplete logs	Covers all Level 3 classified protection audit requirements

Who Is It For

Enterprises that need to pass Level 3 classified protection certification
Heavily regulated industries such as finance and healthcare
Internal management systems that require audit trails

User Roles

Core Collaboration Flow

Audit Event Full Chain

sequenceDiagram participant BIZ as Business System participant AUDIT as Audit Center participant BC as Blockchain Service participant REPORT as Report Engine BIZ->>AUDIT: Report operation event AUDIT->>AUDIT: Event parsing + standardization AUDIT->>AUDIT: Change comparison (before/after) AUDIT->>AUDIT: Risk scoring AUDIT->>BC: Generate block hash BC->>BC: Link to previous block AUDIT->>AUDIT: Tiered storage (hot/cold) REPORT->>AUDIT: Scheduled compliance report generation

Audit Event Types

graph TB subgraph "Audit Event Collection" A1["Login Audit
Login/Logout/Failure"] A2["Operation Audit
Create/Update/Delete/Query"] A3["Permission Audit
Role/Permission Changes"] A4["Export Audit
Data Export/Report Download"] A5["Sensitive Audit
Critical Data Access"] A6["API Audit
Call Statistics"] end subgraph "Audit Processing" B1["Event Parsing"] B2["Change Comparison"] B3["Risk Scoring"] end A1 & A2 & A3 & A4 & A5 & A6 --> B1 B1 --> B2 --> B3

Blockchain Hash Chain

graph TB subgraph "Genesis Block" G1["blockHash = SHA256(data)"] end subgraph "Block N" BN1["blockHash = SHA256(data + prevHash)"] BN2["previousHash = Block N-1 hash"] end subgraph "Block N+1" BN3["blockHash = SHA256(data + prevHash)"] BN4["previousHash = Block N hash"] end G1 --> BN2 BN1 --> BN4

Audit Event Content

{
 "eventId": "evt_20240101_001",
 "timestamp": "2024-01-01 10:30:00.123",
 "userId": "user_10001",
 "userName": "Zhang San",
 "userIp": "192.168.1.100",
 "actionType": "UPDATE",
 "resourceType": "customer",
 "resourceId": "cust_20001",
 "changes": {
 "name": {"old": "Old Name", "new": "New Name"},
 "phone": {"old": "13800001111", "new": "138****2222"}
 },
 "riskLevel": 2,
 "duration": 125
}

Audit Scope

Audit Type	Audit Content	Granularity	Retention Period
Login Audit	Login/Logout/Failure	Per event	1 year
Operation Audit	Create/Update/Delete/Query	Per event	3 years
Permission Audit	Role changes/Permission adjustments	Per event	Permanent
Export Audit	Data export/Report download	Per event	3 years
Sensitive Audit	Critical data access	Per event	Permanent
API Audit	API call statistics	Aggregated	1 year

Sensitive Operation Alerts

audit:
 alert-rules:
 - event: "Data Export"
 threshold: 10
 window: 10m
 action: "notify_admin"
 - event: "Batch Delete"
 action: "require_approval"
 - event: "Permission Change"
 condition: "after_role = admin"
 action: "notify_security"

Business Value

Value Point	Description
Compliance Achievement	Meets Level 3 classified protection and financial audit requirements
Tamper-proof	Blockchain hash chain, data non-repudiation
Traceable	Full-chain audit, replayable operations
Automated Reports	Scheduled compliance report generation
Risk Early Warning	Real-time risk scoring + anomaly alerts

Member Center

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

The Member module provides an independent member user system, completely isolated from backend admin users (system_users). It serves as the user foundation for the e-commerce system, responsible for member registration, login, level progression, points operations, and the full lifecycle management of C-end users.

Key Distinction: Admins log into the backend using system_users (system users), while C-end users register and log in using member_user (member users) — two completely independent systems.

Problems Solved

Pain Point	How Member Solves It
C-end users need independent registration/login	Independent member user table, not mixed with admin users
Need membership levels and benefits system	VIP levels + growth value mechanism
Need to increase user engagement and retention	Points check-in, points mall
WeChat ecosystem users need one-click login	Official account login, mini program login, mini program subscription messages

User Roles

graph LR subgraph BackendRoles ADMIN3["Operations Staff
Manage member information
Configure VIP levels
Manage points rules
Set member tags and groups"] end subgraph FrontendRoles MEMBER2["Regular Member
Register/Login/Profile"] VIP["VIP Member
Enjoy level benefits
Earn and use points"] end

Membership System Architecture

graph TB subgraph AccountSystem LOGIN["Login Methods
Phone/Email/WeChat"] REGISTER["Registration
Phone/WeChat authorization"] end subgraph LevelSystem LEVEL["VIP Levels
Regular → Silver → Gold → Diamond"] GROWTH["Growth Value
Earned through purchases/check-ins/tasks"] LEVEL --> GROWTH end subgraph PointsSystem POINTS_GET["Points Earning
Check-in/Purchases/Campaigns"] POINTS_USE["Points Usage
Deduction/Redemption"] POINTS_GET --> POINTS_USE end subgraph OperationsSystem TAG["Member Tags
Profile labeling"] GROUP["Member Groups
Targeted operations"] end LOGIN --> MemberUserTable REGISTER --> MemberUserTable MemberUserTable --> LevelSystem MemberUserTable --> PointsSystem MemberUserTable --> OperationsSystem

WeChat Ecosystem Integration

graph TB MEMBER3["Member Module"] subgraph WeChatCapabilities MP_LOGIN["Official Account Login
WeChat H5 authorization"] MINI_LOGIN["Mini Program Login
One-click phone number access"] MINI_QR["Mini Program QR Code
Parameterized QR code"] MINI_MSG["Mini Program Subscription Messages
Order/Logistics/Campaign notifications"] end MEMBER3 --> MP_LOGIN MEMBER3 --> MINI_LOGIN MEMBER3 --> MINI_QR MEMBER3 --> MINI_MSG

Relationship with Mall

graph LR MEMBER4["Member Center
Provides: Member info/Level/Points"] --> MALL2["Mall E-Commerce
Consumption: Use member identity to order
Earning: Orders earn points and growth value"] MALL2 --> MEMBER4

The mall depends on the member module for user identity, while the mall’s consumption behavior feeds back points and growth value to the member system.

Core Feature List

Feature	Description
Member Management	Member list, details, status management
Member Tags	Custom tags, user profile labeling
Member Levels	VIP level configuration, growth value rules, level upgrades/downgrades
Member Groups	Group by conditions, support targeted push
Points Check-in	Check-in rule configuration, consecutive check-in rewards
Points Records	Points details, flow tracing

MP WeChat Official Accounts

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

The MP module is a “multi-account management center” for WeChat Official Accounts. If you operate multiple official accounts, you don’t need to log into the WeChat Official Account Platform and switch between them — here you can centrally manage followers, messages, menus, materials, and auto-replies for all official accounts.

In one sentence: One admin panel manages all official accounts, doubling operational efficiency.

Problems Solved

Pain Point	How MP Solves It
Switching between multiple official accounts is cumbersome	One admin panel manages multiple official accounts
Follower information is scattered	Unified follower list, tag management
Auto-reply rule configuration is complex	Visual configuration of follow replies, message replies, keyword replies
Menu configuration experience is poor	Visual menu editor, real-time preview
Cannot integrate with business systems	Follower data connected with member module

User Roles

graph LR subgraph Roles OP["Official Account Operator
Manage followers and messages
Configure auto-replies
Edit menus
Manage materials
View data statistics"] FAN["Followers
Follow official account
Send messages
Trigger auto-replies"] end

Functional Architecture

graph TB subgraph Core["10 Major Functional Modules"] ACCOUNT["Account Management
Bind multiple official accounts"] STATS["Data Statistics
Follower growth/Message statistics"] FANS["Follower Management
Follower list/Tags/Sync"] MSG["Message Management
Receive/Reply to messages"] AUTO["Auto-Reply
Follow/Message/Keyword"] TEMPLATE["Template Messages
Business notification push"] TAG2["Tag Management
Follower grouping"] MENU["Menu Management
Visual configuration"] MATERIAL["Material Management
Articles/Images/Audio"] DRAFT["Article Draft Box"] end subgraph WeChatAPI["WeChat Official Account API"] WX_API["Message Receive/Send
Menu Push
Material Upload
User Info Retrieval"] end Core --> WeChatAPI

Auto-Reply Rules

flowchart LR EVENT["User Action"] --> TYPE{Reply Type} TYPE -->|Follow Account| FOLLOW["Follow Reply
Welcome message + Guidance"] TYPE -->|Send Message| KEYWORD{Match Keyword?} KEYWORD -->|Exact Match| EXACT["Keyword Reply"] KEYWORD -->|Fuzzy Match| LIKE["Fuzzy Match Reply"] KEYWORD -->|No Match| DEFAULT["Default Message Reply"]

Integration with Business Systems

Official account followers can be synced as member users, and the mall can push order status to users via template messages, forming a complete WeChat ecosystem closed loop.

Core Feature List

Feature	Description
Account Management	Bind multiple official accounts, switch management
Data Statistics	Follower growth trends, message interaction statistics
Follower Management	Follower list, details, tags, blocklist
Message Management	Receive follower messages, manual reply
Auto-Reply	Follow reply, default reply, keyword reply
Template Messages	Push template messages to followers
Tag Management	Follower grouping tags
Menu Management	Visual bottom menu configuration
Material Management	Articles, images, voice, video material library
Article Draft Box	Article message draft editing

Report Platform

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, 1 DO / 2 Controllers, menu ID starting from 15000, integrated with GoView data visualization platform

1. Enhancement Positioning and Architecture

1.1 Product Positioning

RuoYiPlus Report is based on the GoView open-source project, focusing on three core areas for enterprise enhancement: Data Visualization, Dashboard Design, and Report Management, building an enterprise data visualization and reporting platform.

1.2 Module Scale

Metric	Value
Data Objects (DO)	1
Controllers	2
Menu ID Start	15000
Maven Module	yudao-module-report

1.3 Core Data Tables

Table Name	Description
`report_go_view_project`	GoView Projects

graph TB subgraph "RuoYiPlus Report Enhanced Architecture" subgraph "Data Access" A1[Database Access] A2[API Access] A3[Excel Import] end subgraph "Visualization Design" B1[Dashboard Designer] B2[Chart Components] B3[Layout Management] end subgraph "Display & Publishing" C1[Dashboard Display] C2[Report Export] C3[Scheduled Refresh] end subgraph "Control Layer" D1[Permission Control] D2[Data Permissions] D3[Access Audit] end end A1 --> B1 A2 --> B1 A3 --> B1 B1 --> B2 B2 --> B3 B3 --> C1 C1 --> C2 C2 --> C3 C1 --> D1 B1 --> D2 C1 --> D3

1.4 Capability Comparison

Dimension	Traditional Reports	RuoYiPlus Report Enhanced
Data Source	Single database	Multi-source + API access
Visualization	Fixed charts	Drag-and-drop dashboard design
Publishing	Static reports	Real-time dashboard + scheduled refresh
Permission Control	Basic permissions	Dashboard-level + data-level permissions
Export Capability	Simple export	Multi-format export + scheduled push
Audit & Compliance	None	Access audit + operation logs

2. Data Access

2.1 Data Source Management

graph TB subgraph "Data Sources" A[MySQL] --> E[Data Access Layer] B[PostgreSQL] --> E C[API Interface] --> E D[Static Data] --> E E --> F[Dataset Management] F --> G[Dashboard Design] end

Data Source Type	Description
Relational Database	MySQL/PostgreSQL direct connection
API Interface	RESTful API data access
Static Data	JSON/CSV static data
Real-Time Data	WebSocket real-time push

3. Visualization Design

3.1 Dashboard Designer

Capability	Description
Drag-and-Drop Design	Visual drag-and-drop layout
Chart Components	Rich chart component library
Theme Configuration	Multiple themes + customization
Responsive	Multi-resolution adaptive
Component Linking	Cross-chart data linking

3.2 Chart Types

Chart Type	Description
Line Chart	Trend analysis
Bar Chart	Comparison analysis
Pie Chart	Proportion analysis
Map	Geographic distribution
Gauge	Metric monitoring
Table	Detail data

4. Display and Publishing

4.1 Publishing Management

graph LR A[Dashboard Design] --> B[Preview & Test] B --> C[Publish Online] C --> D[Permission Assignment] D --> E[Dashboard Display] E --> F[Access Statistics]

Capability	Description
Dashboard Preview	Real-time preview during design
Publishing Management	Version publishing + rollback
Permission Control	Dashboard access permissions
Scheduled Refresh	Scheduled data refresh
Export Function	Image/PDF export

5. Technical Architecture

graph TB subgraph "yudao-module-report-plus" subgraph "report-biz" A1[datasource Data Source Management] A2[dataset Dataset Management] A3[design Dashboard Design] A4[publish Publishing Management] A5[export Export Management] A6[goview GoView Integration] end subgraph "Permissions & Audit" B1[permission Permission Control] B2[audit Audit Logs] end end A1 --> B1 A3 --> B1 A4 --> B2 A6 --> B1

6. Business Value

Value Point	Description
Data Visualization	Drag-and-drop dashboard design
Decision Support	Real-time data monitoring
Rapid Construction	Rich components + templates
Flexible Access	Multi-data source support
Security Control	Dashboard permissions + access audit
Open Integration	GoView open-source ecosystem

AI Intelligent Applications

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, 14 DOs / 14 Controllers, menu ID starting from 9000, building an enterprise AI intelligent application platform

1. Enhancement Positioning and Architecture

1.1 Product Positioning

RuoYiPlus AI focuses on three core areas for enterprise enhancement: Intelligent Conversation, Knowledge Base Management, and AI Creation, building an enterprise AI application platform.

1.2 Module Scale

Metric	Value
Data Objects (DO)	14
Controllers	14
Menu ID Start	9000
Maven Module	yudao-module-ai

1.3 Core Data Tables

Table Name	Description
`ai_chat`	Intelligent Conversation
`ai_image`	Image Generation
`ai_knowledge`	Knowledge Base
`ai_music`	Music Generation
`ai_workflow`	Workflow
`ai_writing`	AI Writing
`ai_model`	Model Management
`ai_api_key`	API Key Management

graph TB subgraph "RuoYiPlus AI Enhanced Architecture" subgraph "Conversation Interaction" A1[Intelligent Conversation] A2[Multi-Round Conversation] A3[Role Play] end subgraph "Content Creation" B1[AI Writing] B2[Image Generation] B3[Music Generation] end subgraph "Knowledge Management" C1[Knowledge Base] C2[Document Parsing] C3[Semantic Search] end subgraph "Platform Management" D1[Model Management] D2[API Management] D3[Workflow] end subgraph "Control Layer" E1[Permission Control] E2[Content Moderation] E3[Usage Statistics] end end A1 --> B1 A2 --> B1 A3 --> B2 B1 --> C1 B2 --> C1 B3 --> C2 C1 --> D1 C2 --> D2 C3 --> D3 A1 --> E1 B1 --> E2 C1 --> E3

1.4 Capability Comparison

Dimension	Traditional Solution	RuoYiPlus AI Enhanced
Intelligent Conversation	None	Multi-round conversation + role play
Content Creation	None	Writing + images + music
Knowledge Base	None	Knowledge base + semantic search
Model Management	None	Multi-model unified management
Workflow	None	AI workflow orchestration
Permission Control	None	API key + usage control
Content Moderation	None	AI content safety moderation

2. Intelligent Conversation

2.1 Conversation Architecture

graph TB subgraph "Intelligent Conversation" A[User Input] --> B[Intent Recognition] B --> C[Knowledge Retrieval] C --> D[Model Inference] D --> E[Response Generation] E --> F[Conversation Record] B --> B1[Question Classification] B --> B2[Entity Recognition] C --> C1[Knowledge Base Retrieval] C --> C2[Document Retrieval] D --> D1[LLM Invocation] D --> D2[Context Management] end

Capability	Description
Intelligent Conversation	Multi-round conversation + context understanding
Role Play	Custom roles + prompts
Knowledge Q&A	Knowledge base-based Q&A
Multimodal	Text + images + voice

3. AI Content Creation

3.1 Creation Capabilities

Creation Type	Description
AI Writing	Article generation + polishing + continuation
Image Generation	Text-to-image + image-to-image
Music Generation	AI music creation
Video Generation	Text-to-video + image-to-video

4. Knowledge Base Management

4.1 Knowledge Base Architecture

graph TB subgraph "Knowledge Base Management" A[Document Upload] --> B[Document Parsing] B --> C[Vectorization] C --> D[Knowledge Storage] D --> E[Semantic Search] E --> F[Knowledge Q&A] A --> A1[PDF] A --> A2[Word] A --> A3[Web Pages] B --> B1[Text Extraction] B --> B2[Segmentation] C --> C1[Embedding] C --> C2[Vector Index] end

Capability	Description
Document Management	Upload + parsing + management
Vector Search	Semantic search + similarity
Knowledge Q&A	Knowledge base-based Q&A
Knowledge Update	Incremental update + version management

5. Technical Architecture

graph TB subgraph "yudao-module-ai-plus" subgraph "ai-biz" A1[chat Intelligent Conversation] A2[image Image Generation] A3[knowledge Knowledge Base] A4[music Music Generation] A5[workflow Workflow] A6[writing AI Writing] A7[model Model Management] A8[api_key API Key] A9[analytics Usage Statistics] end subgraph "Permissions & Audit" B1[permission Permission Control] B2[audit Audit Logs] B3[content Content Moderation] end end A1 --> B1 A2 --> B3 A3 --> B1 A4 --> B3 A5 --> B2 A7 --> B1

6. Business Value

Value Point	Description
Efficiency Boost	AI-assisted writing + conversation
Knowledge Management	Enterprise knowledge base + intelligent search
Creative Creation	Image + music + video generation
Cost Optimization	Multi-model management + usage control
Security & Compliance	Content moderation + operation audit
Open Integration	API management + workflow orchestration

Mall E-Commerce System

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

Mall is the platform’s most complex business module (70+ tables), providing the full e-commerce chain from product management and order transactions to marketing campaigns and distribution commissions. One system comes with both an admin panel (Vue3+Element Plus) and a mobile app (uni-app), ready to use out of the box.

In one sentence: If you need to build a B2C e-commerce store, 90% of the functionality is already implemented here.

Problems Solved

Pain Point	How Mall Solves It
Building a store from scratch takes too long	70+ tables + complete frontend/backend, go live in weeks
Multiple marketing tactics are expensive to develop	Built-in coupons/flash sales/group buying/bargaining/distribution
Need both admin panel and user-facing frontend	Admin panel + uni-app mobile app provided together
Payment and membership need extra integration	Built-in integration with Payment Center and Member Center

User Roles

graph LR subgraph BackendRoles MALL_ADMIN["Mall Admin
Manage products/orders/marketing"] MALL_OP["Operations Staff
Configure campaigns/review reviews"] end subgraph FrontendRoles BUYER["Buyer
Browse products/Place orders/Pay
Participate in marketing campaigns"] DISTRIBUTOR["Distributor
Promote products
Earn commissions"] end

System Architecture

graph TB subgraph AdminPanel ADMIN_PANEL["Vue3 + Element Plus Admin Panel
Products/Orders/Marketing/Data"] end subgraph MobileApp UNI_APP["uni-app Mobile App
H5 + App + Mini Program
Storefront customization (3 templates)"] end subgraph ProductCenter CATEGORY["Product Categories"] ATTR["Product Attributes"] SPU["SPU Products"] SKU["SKU Variants"] REVIEW["Product Reviews"] end subgraph OrderCenter CART["Shopping Cart"] ORDER["Transaction Orders"] AFTER_SALE["After-Sales Management"] EXPRESS["Express Delivery"] PICKUP["Self Pickup Verification"] end subgraph MarketingCenter COUPON["Coupons"] SECKILL["Flash Sales"] BARGAIN["Bargaining"] GROUPON["Group Buying"] DISCOUNT["Limited-Time Discounts"] CONTENT["Content Marketing"] COMMISSION["Distribution Commissions"] end subgraph Dependencies PAY2["Payment Center"] MEMBER6["Member Center"] MP3["Official Accounts"] end AdminPanel --> ProductCenter AdminPanel --> OrderCenter AdminPanel --> MarketingCenter MobileApp --> ProductCenter MobileApp --> OrderCenter MobileApp --> MarketingCenter OrderCenter --> PAY2 OrderCenter --> MEMBER6 MarketingCenter --> MEMBER6

Core Business Flow

User Order Process

sequenceDiagram participant U2 as User participant APP as Mobile/PC participant MALL4 as Mall participant PAY3 as Payment Center participant WMS2 as Warehouse/WMS U2->>APP: Browse products, add to cart U2->>APP: Confirm order, select address APP->>MALL4: Create order (Pending Payment) MALL4->>PAY3: Initiate payment PAY3-->>APP: Payment page U2->>PAY3: Complete payment PAY3->>MALL4: Callback: Payment successful MALL4->>MALL4: Order status → Pending Shipment MALL4->>WMS2: Notify shipment WMS2->>MALL4: Enter tracking number MALL4->>APP: Push shipment notification U2->>APP: Confirm receipt MALL4->>MALL4: Order complete, award points

Marketing Campaign Matrix

Campaign Type	Mechanics	Suitable Scenarios
Coupons	Threshold discounts/percentage discounts/vouchers, can target specific products/categories	Daily promotions
Flash Sales	Limited time & quantity, ultra-low price rush	Traffic generation, inventory clearance
Group Buying	Multi-person group purchase for discount price	Social viral growth
Bargaining	Share with friends to bargain down the price	New user acquisition
Limited-Time Discounts	Discount during specified time period	Holiday promotions
Content Marketing	Articles/videos product seeding	Content commerce
Distribution Commissions	Promotion commissions, multi-level distribution	Social commerce

Storefront Customization

The mobile app supports 3 storefront customization templates, allowing drag-and-drop component layout of the homepage:

Carousel / Navigation icons / Product recommendations
Coupon popups / Countdown timers
Search bar / Announcement bar

Dependencies

Mall E-Commerce
 ├── Payment Center (Pay) —— Order payment
 ├── Member Center (Member) —— User identity/points
 └── Official Accounts (MP) —— WeChat H5 store

ERP Enterprise Resource Planning

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

ERP is the enterprise’s “purchase-sales-inventory hub” — managing the complete flow of physical goods and funds from supplier procurement, warehouse inventory to customer sales. 30+ tables cover five core areas: procurement, sales, inventory, products, and finance, suitable for daily operations management of trading and manufacturing enterprises.

In one sentence: Manage your goods and money, making every transaction traceable.

Problems Solved

Pain Point	How ERP Solves It
Inventory quantities rely on manual counting, often mismatched	Every inbound/outbound transaction auto-updates inventory, real-time and accurate
Procurement and sales processes are opaque	Document approval workflow + status tracking
Unclear how much profit is made	Procurement cost vs. sales revenue, auto-calculated
Multi-warehouse transfers are chaotic	Stock transfer operations are recorded, inventory locations are clear
Financial receivables and payables are hard to manage	Settlement accounts + payment/receipt records

User Roles

graph LR subgraph Roles PURCHASER["Purchaser
Manage suppliers
Create purchase orders
Handle purchase inbound and returns"] SALES2["Salesperson
Manage customers
Create sales orders
Handle sales outbound and returns"] WAREHOUSE["Warehouse Keeper
Confirm inbound/outbound
Manage inventory
Execute stocktaking"] FINANCE["Finance
Manage settlement accounts
Handle payments/receipts
Review documents"] MANAGER2["Manager
Approve documents
View reports"] end

Five Core Modules

graph TB subgraph Procurement["Procurement Management"] P1["Supplier Management"] P2["Purchase Orders"] P3["Purchase Inbound"] P4["Purchase Returns"] end subgraph Sales["Sales Management"] S1["Customer Management"] S2["Sales Orders"] S3["Sales Outbound"] S4["Sales Returns"] end subgraph Inventory["Inventory Management"] I1["Inventory Query"] I2["Inventory Flow"] I3["Stock Transfer"] I4["Stocktaking"] end subgraph Products["Product Management"] PR1["Product Categories"] PR2["Product Information"] PR3["Product Units"] end subgraph Finance["Financial Management"] F1["Settlement Accounts"] F2["Purchase Payments"] F3["Sales Receipts"] end PI["Purchase Inbound"] -->|Inventory Increase| Inventory PR["Purchase Returns"] -->|Inventory Decrease| Inventory SO["Sales Outbound"] -->|Inventory Decrease| Inventory SR["Sales Returns"] -->|Inventory Increase| Inventory PO["Purchase Orders"] -->|Payment| Finance SO["Sales Orders"] -->|Receipt| Finance

Procurement Process

sequenceDiagram participant P as Purchaser participant ERP3 as ERP participant S as Supplier participant WH as Warehouse P->>ERP3: Select supplier, create purchase order ERP3->>ERP3: Order status: Pending Approval Note over ERP3: Can integrate BPM workflow approval ERP3->>ERP3: Approved P->>S: Notify supplier to ship S->>WH: Goods delivered WH->>ERP3: Create purchase inbound order ERP3->>ERP3: Inbound approved ERP3->>ERP3: Inventory increased Note over ERP3: If return needed P->>ERP3: Create purchase return order ERP3->>ERP3: Return approved → Inventory decreased

Sales Process

sequenceDiagram participant C as Customer participant S2 as Salesperson participant ERP4 as ERP participant WH2 as Warehouse C->>S2: Place purchase demand S2->>ERP4: Create sales order ERP4->>ERP4: Order approved S2->>WH2: Notify warehouse to prepare goods WH2->>ERP4: Create sales outbound order ERP4->>ERP4: Outbound approved ERP4->>ERP4: Inventory decreased WH2->>C: Ship goods Note over ERP4: If return needed S2->>ERP4: Create sales return order ERP4->>ERP4: Return approved → Inventory increased

Core Table Structure

erDiagram ERP_PRODUCT ||--o{ ERP_PURCHASE_ORDER_ITEM : "Procurement" ERP_PRODUCT ||--o{ ERP_SALE_ORDER_ITEM : "Sales" ERP_PRODUCT ||--o{ ERP_STOCK : "Inventory" ERP_PURCHASE_ORDER ||--o{ ERP_PURCHASE_ORDER_ITEM : "Contains" ERP_PURCHASE_ORDER ||--o{ ERP_PURCHASE_IN : "Inbound" ERP_SALE_ORDER ||--o{ ERP_SALE_ORDER_ITEM : "Contains" ERP_SALE_ORDER ||--o{ ERP_SALE_OUT : "Outbound" ERP_STOCK { bigint id PK bigint product_id FK "Product" bigint warehouse_id FK "Warehouse" int stock "Inventory Qty" } ERP_PURCHASE_ORDER { bigint id PK varchar no "Document No." bigint supplier_id FK "Supplier" tinyint status "Status" decimal total_price "Total Amount" } ERP_SALE_ORDER { bigint id PK varchar no "Document No." bigint customer_id FK "Customer" tinyint status "Status" decimal total_price "Total Amount" }

Document Number Rules

Format: {prefix}{yyyyMMdd}{6-digit auto-increment}
Example: CGD20240625000001 (Purchase Order)
 XSD20240625000001 (Sales Order)

Approval Mechanism

All inbound/outbound documents have an approval status (ErpAuditStatus):

Status	Description
Not Approved	Draft status, editable
Approved	Approved, triggers inventory change

Key Rule: Only approved documents affect inventory; rejected documents produce no inventory changes.

Dependencies

ERP Purchase-Sales-Inventory
 └── BPM Workflow (Optional) —— Approval process

Mall System

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, 49 DOs / 73 Controllers, menu ID starting from 14000, building a complete e-commerce mall solution

1. Enhancement Positioning and Architecture

1.1 Product Positioning

RuoYiPlus Mall focuses on three core areas for enterprise enhancement: Product Management, Order Transactions, and Marketing Promotions, building a complete B2C e-commerce mall system.

1.2 Module Scale

Metric	Value
Data Objects (DO)	49
Controllers	73
Menu ID Start	14000
Maven Module	yudao-module-mall

1.3 Core Data Tables

Table Name	Description
`mall_product`	Product Management
`mall_order`	Order Management
`mall_promotion`	Promotion Management
`mall_delivery`	Delivery Management
`mall_after_sale`	After-Sales Management
`mall_statistics`	Statistics Management
`mall_coupon`	Coupons
`mall_bargain`	Bargain Activities
`mall_combination`	Combination Packages
`mall_seckill`	Flash Sale Activities

graph TB subgraph "RuoYiPlus Mall Enhanced Architecture" subgraph "Product Layer" A1[Product Management] A2[Category Management] A3[Brand Management] A4[Review Management] end subgraph "Transaction Layer" B1[Cart] B2[Order Management] B3[Payment Management] B4[Delivery Management] end subgraph "Marketing Layer" C1[Coupons] C2[Flash Sale Activities] C3[Bargain Activities] C4[Combination Packages] end subgraph "Service Layer" D1[After-Sales Management] D2[Refund Management] D3[Customer Service Integration] end subgraph "Control Layer" E1[Permission Control] E2[Data Audit] E3[Risk Control Management] end end A1 --> B1 A2 --> A1 A3 --> A1 A4 --> A1 B1 --> B2 B2 --> B3 B3 --> B4 C1 --> B2 C2 --> B2 C3 --> B2 C4 --> B2 B4 --> D1 D1 --> D2 D2 --> D3 A1 --> E1 B2 --> E2 B3 --> E3

1.4 Capability Comparison

Dimension	Traditional Mall	RuoYiPlus Mall Enhanced
Product Management	Basic products	Multi-spec + multi-SKU management
Order Management	Basic orders	Full-process order management
Marketing Promotions	Simple discounts	Flash sales + bargains + combo packages
Delivery Management	None	Multi-carrier + shipping templates
After-Sales Service	None	Refund + return + exchange
Data Analysis	Simple statistics	Transaction analysis + product analysis
Permission Control	Basic permissions	Merchant-level + product-level permissions
Risk & Compliance	None	Transaction risk control + operation audit

2. Product Management System

2.1 Product Architecture

graph TB subgraph "Product Management" A[Product Category] --> B[Product SPU] B --> C[Product SKU] C --> D[Product Inventory] B --> B1[Product Name] B --> B2[Product Details] B --> B3[Product Images] B --> B4[Product Parameters] C --> C1[Spec Combinations] C --> C2[Price Management] C --> C3[Inventory Management] C --> C4[Barcode Management] D --> D1[Inventory Alert] D --> D2[Inventory Sync] D --> D3[Inventory Records] end

Capability	Description
Product Category	Multi-level category management
Product Management	SPU/SKU model
Spec Management	Multi-spec multi-SKU
Inventory Management	Real-time inventory + alerts
Review Management	Product reviews + follow-up reviews
Product Search	Full-text search + filtering

3. Order Transaction Management

3.1 Order Flow

graph TB A[Add to Cart] --> B[Confirm Order] B --> C[Submit Order] C --> D[Payment Processing] D --> E{Payment Result} E -->|Success| F[Merchant Shipment] E -->|Failed| G[Order Cancellation] F --> H[Logistics Delivery] H --> I[Confirm Receipt] I --> J[Order Completed] I --> K[Request After-Sales] B --> B1[Select Address] B --> B2[Select Promotion] B --> B3[Calculate Shipping] F --> F1[Picking] F --> F2[Packaging] F --> F3[Shipping]

3.2 Order Management

Capability	Description
Cart	Multi-product + promotion calculation
Order Creation	Order placement + inventory lock
Order Payment	Multi-payment methods
Order Shipment	Shipping + logistics tracking
Order After-Sales	Refund + return + exchange
Order Statistics	Transaction analysis + trends

4. Marketing Promotion System

4.1 Marketing Activities

graph TB subgraph "Marketing System" A[Coupons] --> B[Threshold Coupons] A --> C[Discount Coupons] A --> D[Free Shipping Coupons] E[Flash Sale Activities] --> F[Time-Limited Flash Sale] E --> G[Quantity-Limited Flash Sale] H[Bargain Activities] --> I[Share Bargain] H --> J[Assist Bargain] K[Combination Packages] --> L[Bundled Sales] K --> M[Matching Packages] end

Activity Type	Description
Coupons	Threshold coupons, discount coupons, free shipping coupons
Flash Sale Activities	Time-limited flash sale, quantity-limited flash sale
Bargain Activities	Share bargain, friend assist
Combination Packages	Bundled sales, matching packages
Threshold Promotions	Tiered threshold, storewide threshold

5. Technical Architecture

graph TB subgraph "yudao-module-mall-plus" subgraph "mall-biz" A1[product Product Management] A2[order Order Management] A3[cart Shopping Cart] A4[promotion Promotion Management] A5[delivery Delivery Management] A6[after_sale After-Sales Management] A7[coupon Coupon Management] A8[seckill Flash Sale Management] A9[bargain Bargain Management] A10[analytics Data Analysis] end subgraph "Permissions & Audit" B1[permission Permission Control] B2[audit Audit Logs] B3[risk Risk Control Management] end end A1 --> B1 A2 --> B2 A3 --> B1 A4 --> B3 A5 --> B2 A6 --> B2

6. Business Value

Value Point	Description
Complete Mall	Product + order + payment + delivery
Marketing Enablement	Flash sale + bargain + coupons
User Growth	Social virality + membership marketing
Data-Driven	Transaction analysis + user profiling
Compliance Operations	Transaction audit + risk control management
Flexible Extension	Modular design + open API

CRM Customer Relationship Management

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, 75 DOs / 54 Controllers, menu ID starting at 2000, providing deep business enhancements for full customer lifecycle management, intelligent permission control, and audit compliance

1. Enhancement Positioning and Architecture

1.1 Product Positioning

RuoYiPlus CRM builds on Yudao’s native capabilities, providing enterprise-level enhancements around three core areas: customer asset control, sales process automation, and data permission compliance, creating a complete business loop from lead acquisition to customer success.

graph TB subgraph "RuoYiPlus CRM Enhancement Architecture" subgraph "Business Layer" A1[Customer Full Lifecycle] A2[Opportunity Management] A3[Contract Management] A4[Marketing Automation] end subgraph "Capability Layer" B1[Intelligent Public Pool] B2[Sales Forecasting] B3[E-Signing] B4[BI Analytics] end subgraph "Infrastructure Layer" C1[Data Permission Engine] C2[Operation Audit] C3[Sensitive Data Masking] C4[Multi-Tenancy Isolation] end end A1 --> B1 A2 --> B2 A3 --> B3 A4 --> B4 B1 --> C1 B2 --> C2 B3 --> C3 B4 --> C4

1.2 Module Scale

Metric	Value
Data Objects (DO)	75
Controllers	54
Menu ID Start	2000
Maven Module	yudao-module-crm

1.3 Core Data Tables

Table Name	Description
`crm_customer`	Customer basic info
`crm_contact`	Contact info
`crm_business`	Opportunity management
`crm_contract`	Contract management
`crm_quote`	Quotation management
`crm_invoice`	Invoice management
`crm_receivable`	Receivables management
`crm_return_visit`	Customer return visit
`crm_product`	Product management
`crm_event`	Event management
`crm_marketing_campaign`	Marketing campaigns
`crm_survey`	Survey management
`crm_approval_flow`	Approval workflow
`crm_file`	File management
`crm_permission`	Data permissions

1.4 Capability Comparison

Dimension	Yudao Native CRM	RuoYiPlus CRM Enhancement
Customer Management	Basic customer info	Full lifecycle management
Public Pool	Simple public pool	Intelligent recycling + allocation strategy
Opportunity Management	Basic opportunities	Kanban + forecasting + automation
Contract Management	Basic contracts	E-signing + fulfillment tracking
Data Analytics	Simple reports	BI intelligent analysis
Marketing Automation	None	Marketing automation engine
Permission Control	Basic RBAC	Four-layer data permissions
Audit Compliance	Operation logs	Full-chain audit trail

2. Customer Full Lifecycle Management

2.1 Lifecycle Stages

graph LR A[Prospect Stage] --> B[New Customer Stage] B --> C[Active Stage] C --> D[Mature Stage] D --> E[Churn Stage] A --> A1[Lead Acquisition] A --> A2[Lead Cleansing] A --> A3[Lead Scoring] A --> A4[Customer Profiling] B --> B1[Customer Tiering] B --> B2[Initial Follow-up] B --> B3[Need Discovery] B --> B4[Opportunity Creation] C --> C1[Continuous Follow-up] C --> C2[Opportunity Advancement] C --> C3[Contract Signing] C --> C4[Payment Collection] D --> D1[Upsell Discovery] D --> D2[Renewal Reminder] D --> D3[Service Upgrade] D --> D4[Satisfaction Survey] E --> E1[Churn Alert] E --> E2[Retention Strategy] E --> E3[Churn Analysis] E --> E4[Public Pool Recycling]

2.2 Data Permission Control

The CRM system implements a four-layer data permission model to ensure strict isolation of customer data based on organizational structure and job responsibilities.

graph TB subgraph "Permission Decision Engine" A[Sales Request] --> B[Permission Resolution] B --> C{Permission Source} C --> D[User-Level Permission] C --> E[Role-Level Permission] C --> F[Position-Level Permission] C --> G[Department-Level Permission] D --> H[Permission Merge] E --> H F --> H G --> H H --> I[Customer Level Filter] I --> J[Data Filter SQL] J --> K[Return Results] end

Permission Level	Use Case	Example
User-Level	Sales person’s own customers	Sales person can only view their own customers
Role-Level	Sales team	Sales manager can view all team customers
Position-Level	Regional management	Regional director can view all customers in their region
Department-Level	Branch office	Branch GM can view all branch customers

// CRM data permission example
@DataPermission(roles = {"sales_manager"})
public class CustomerServiceImpl {
 // Sales manager can view team customers
 // Automatically filters data by department hierarchy
}

// Customer level filter
@DataPermission(scope = "custom",
 sqlFilter = "customer_level <= #{currentUser.maxLevel}")
public class CustomerLevelService {
 // Filter by customer levels accessible to the user
}

2.3 Operation Audit

All customer data operations record complete audit logs, supporting data change traceability and compliance audits.

graph TB subgraph "Audit Event Collection" A1[Customer Creation] A2[Customer Edit] A3[Customer Transfer] A4[Customer Deletion] A5[Data Export] end subgraph "Audit Processing" B1[Change Comparison] B2[Risk Scoring] B3[Rule Matching] end subgraph "Audit Storage" C1[Operation Log] C2[Change History] C3[Blockchain Evidence] end A1 --> B1 A2 --> B1 A3 --> B1 A4 --> B1 A5 --> B1 B1 --> B2 B2 --> B3 B3 --> C1 B3 --> C2 B3 --> C3

Audit Type	Recorded Content	Retention Period
Operation Audit	Customer creation, edit, deletion, transfer	Permanent
Data Change	Before/after field values	3 years
Export Audit	Export time, exporter, data volume	3 years
Permission Change	Customer owner change history	Permanent

3. Intelligent Public Pool

3.1 Public Pool Architecture

graph TB subgraph "Public Pool Management" A[Customer Enters Pool] --> B{Allocation Strategy} B --> C[Allocate by Region] B --> D[Allocate by Industry] B --> E[Allocate by Capability] C --> F[Sales Pickup] D --> F E --> F F --> G{Follow-Up Rules} G -->|N days no follow-up| H[Auto Recycle] G -->|Normal follow-up| I[Continue Follow-Up] H --> A end

3.2 Core Capabilities

Capability	Description
Auto Recycle Rules	Auto recycle after N days without follow-up
Pickup Limits	Daily pickup cap, total cap
Allocation Strategy	Intelligent allocation by region/industry/capability
Protection Mechanism	Key customer protection, follow-up exemption
Recycle Alert	Auto reminder 3 days before recycling

3.3 Configuration Example

crm:
 pool:
 recycle-rules:
 - name: "30 days no follow-up"
 condition: "last_follow_days > 30"
 action: "recycle"
 exclude-levels: ["VIP", "KA"]
 - name: "90 days no opportunity"
 condition: "no_business_days > 90"
 action: "recycle"
 pickup-limits:
 daily: 10
 total: 50
 cooldown-hours: 24

4. Opportunity Management and Forecasting

4.1 Opportunity Process

graph LR A[Lead Conversion] --> B[Need Confirmation] B --> C[Solution Development] C --> D[Quotation & Negotiation] D --> E[Win/Loss] E --> F[Contract Signing] B --> B1[Need Analysis] B --> B2[Customer Evaluation] C --> C1[Solution Design] C --> C2[Solution Demo] D --> D1[Quotation Approval] D --> D2[Contract Negotiation]

4.2 Opportunity Kanban and Forecasting

Capability	Description
Visual Kanban	Drag-and-drop opportunity stage management
Win Rate Prediction	Win rate model based on historical data
Sales Forecasting	Quarterly/annual sales revenue forecasting
Stage Conversion Rate	Conversion rate analysis per stage
Bottleneck Identification	Automatic conversion bottleneck identification

5. Contract Management and E-Signing

5.1 Contract Process

graph TB A[Contract Drafting] --> B[Contract Approval] B --> C[E-Signing] C --> D[Contract Execution] D --> E[Contract Archiving] A --> A1[Template-Based Drafting] A --> A2[Clause Configuration] B --> B1[Multi-Level Approval] B --> B2[Legal Review] C --> C1[Electronic Seal] C --> C2[Identity Verification] D --> D1[Fulfillment Tracking] D --> D2[Payment Collection] E --> E1[Electronic Archiving] E --> E2[Expiry Reminder]

5.2 Contract Audit

All contract operations record complete audit logs, ensuring compliant and traceable contract management.

Audit Item	Description
Contract Creation	Records drafter, drafting time
Contract Approval	Records approval process, approval comments
Contract Signing	Records signing time, signing parties
Contract Change	Records change content, change reason
Contract Archiving	Records archiving time, archiver

6. Marketing Automation Engine

6.1 Automation Process

graph LR A[Trigger Condition] --> B{Condition Check} B -->|Satisfied| C[Execute Action] B -->|Not Satisfied| D[No Action] C --> E[Record Result] E --> F{Follow-Up Condition} F -->|Yes| G[Continue Execution] F -->|No| H[Process End]

6.2 Automation Rule Example

// Automation rule example
AutomationRule {
 trigger: "Customer Created"
 conditions: [
 "industry = 'Manufacturing'",
 "region = 'East China'"
 ]
 actions: [
 "assignTo: 'East China Sales Team'",
 "sendEmail: 'Welcome Email Template'",
 "createTask: 'Initial Follow-Up Task'"
 ]
}

7. Data Analytics Enhancement

7.1 Sales Funnel Analysis

graph TB A[Leads] --> B[Customers] B --> C[Opportunities] C --> D[Contracts] D --> E[Collections] A --> A1[Lead Conversion Rate] B --> B1[Opportunity Creation Rate] C --> C1[Stage Conversion Rate] D --> D1[Win Rate] E --> E1[Collection Completion Rate]

Analysis Dimension	Metric
Lead → Customer	Lead conversion rate
Customer → Opportunity	Opportunity creation rate
Opportunity Stages	Stage conversion rate
Opportunity → Contract	Win rate
Contract → Collection	Collection completion rate

7.2 Customer Value Analysis

Analysis Model	Description
RFM Model	Recency, Frequency, Monetary analysis
Customer Tiering	VIP/KA/Normal/Potential customer tiers
Lifetime Value	CLV customer lifetime value prediction
Churn Risk Scoring	Churn probability prediction

8. Technical Architecture

graph TB subgraph "yudao-module-crm-plus" subgraph "crm-biz" A1[customer Customer Management] A2[leads Lead Management] A3[business Opportunity Management] A4[contract Contract Management] A5[pool Public Pool] A6[automation Marketing Automation] A7[analytics Data Analytics] A8[integration External Integration] end subgraph "Permissions & Audit" B1[permission Permission Control] B2[audit Audit Logs] B3[masking Data Masking] end end A1 --> B1 A2 --> B1 A3 --> B1 A4 --> B2 A5 --> B2 A6 --> B3 A7 --> B3

9. Business Value

Value Point	Description
Increase Conversion Rate	Intelligent follow-up reminders, opportunity forecasting
Reduce Churn Rate	Churn alert, retention strategy
Improve Efficiency	Marketing automation, mobile office
Data-Driven	BI analytics, decision support
Compliance Control	Four-layer permissions, full-chain audit
Data Security	Sensitive data masking, operation traceability

WMS Warehouse Management System

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

WMS is an independent general warehouse management system (16 tables), distinct from the manufacturing-deeply-integrated warehouse module in MES. WMS is positioned as “general warehouse management,” suitable for pure warehousing scenarios. If you need deep manufacturing integration (such as line-side inventory, production picking), use the warehouse module in MES.

In one sentence: Manage the warehouse’s “in, out, transfer, count” — always know where every item is.

Problems Solved

Pain Point	How WMS Solves It
Don’t know how much inventory is in the warehouse	Real-time inventory query, inventory flow tracing
Inbound/outbound records rely on paper documents	Electronic documents, traceable status flow
Unclear item locations	Multi-warehouse, location management
Stocktaking is time-consuming and labor-intensive	Systematic stocktaking process
Inventory data is inaccurate	Every operation auto-updates inventory

User Roles

graph LR subgraph Roles WH_ADMIN["Warehouse Admin
Manage warehouses/locations
Configure product info
Handle inbound/outbound/transfer/stocktaking
View inventory"] end

Core Business Processes

graph TB subgraph InboundProcess IN1["Create Inbound Order"] --> IN2["Draft Status"] IN2 --> IN3["Confirm Complete"] IN3 --> IN4["Inventory Increased"] IN2 --> IN5["Voided"] end subgraph OutboundProcess OUT1["Create Outbound Order"] --> OUT2["Draft Status"] OUT2 --> OUT3["Confirm Complete"] OUT3 --> OUT4["Inventory Decreased"] OUT2 --> OUT5["Voided"] end subgraph TransferProcess MV1["Create Transfer Order"] --> MV2["Confirm Complete"] MV2 --> MV3["Source Warehouse Inventory Decreased
Target Warehouse Inventory Increased"] end subgraph StocktakingProcess CK1["Create Stocktaking Order"] --> CK2["Enter Actual Count"] CK2 --> CK3["Confirm Complete"] CK3 --> CK4["Surplus: Inventory Increased
Shortage: Inventory Decreased"] end

Core Table Structure

erDiagram WMS_WAREHOUSE ||--o{ WMS_STOCK : "Inventory" WMS_PRODUCT ||--o{ WMS_STOCK : "Inventory" WMS_WAREHOUSE { bigint id PK varchar name "Warehouse Name" varchar code "Warehouse Code" tinyint status "Status" } WMS_PRODUCT { bigint id PK varchar name "Product Name" varchar no "Product Code" varchar unit "Unit" } WMS_STOCK { bigint id PK bigint warehouse_id FK "Warehouse" bigint product_id FK "Product" int stock "Inventory Qty" } WMS_STOCK_RECORD { bigint id PK bigint warehouse_id FK bigint product_id FK int count "Change Qty" tinyint type "In/Out Type" varchar business_no "Related Document No." }

Document Number Rules

Format: {prefix}{MMdd}{4-digit random}
Example: RK06250001 (Inbound Order)
 CK06250001 (Outbound Order)
 YK06250001 (Transfer Order)
 PK06250001 (Stocktaking Order)

Two-Phase Status Flow

All documents follow a Draft → Completed/Voided two-phase pattern:

Status	Description
Draft	Editable, does not trigger inventory changes
Completed	Confirmed complete, triggers inventory transaction
Voided	Document voided, does not trigger inventory changes

Key Rule: Only “Completed” status actually affects inventory quantities.

Difference from MES Warehouse

Dimension	WMS	MES Warehouse Module
Positioning	General warehouse management	Manufacturing deep integration
Table Count	16 tables	62 tables
Use Case	Standalone warehousing, logistics centers	Manufacturing plants, production workshops
Special Features	Basic inbound/outbound/stocktaking	Line-side inventory, production picking, outsourcing management
Requires MES	❌ Standalone	✅ Part of MES

CRM Four-Layer Data Permission Solution

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

In a nutshell: On top of Yudao’s native @CrmPermission annotation, build a complete permission system with “User-Role-Post-Department” four-layer data permissions + customer level cascade filtering.

What Problems It Solves

Level	Current Status	After Enhancement
User-Level	✅ Supported	✅ Maintained
Role-Level	❌ Not supported	✅ Role-permission association
Post-Level	❌ Not supported	✅ Post-permission association
Dept-Level	❌ Not supported	✅ Dept-permission association
Customer Level	❌ Not supported	✅ Level stacking + cascade filtering

Suitable Users

CRM systems requiring fine-grained data permission control
Enterprises with customer level tiered management needs
Organizations needing to isolate customer data by department/post

1. Four-Layer Data Permission Model

graph TB subgraph "Permission Decision Engine" A["User Request"] --> B["Permission Resolution"] B --> C["Permission Merge
Union"] C --> D["Data Scope Filtering"] D --> E["Customer Level Filtering
AND Stacking"] end subgraph "Permission Sources" F["User-Level Permission
Priority 1 (Highest)"] G["Role-Level Permission
Priority 2"] H["Post-Level Permission
Priority 3"] I["Dept-Level Permission
Priority 4 (Lowest)"] end F --> B G --> B H --> B I --> B E --> J["SQL Filtering"] J --> K["Return Results"]

2. Permission Verification Flow

2.1 Operation Permission Verification

sequenceDiagram participant User as User participant Controller as Controller participant Aspect as @CrmPermission Aspect participant Engine as Permission Engine participant DB as Database User->>Controller: Request customer operation Controller->>Aspect: Trigger permission check Aspect->>Engine: hasBizOperationPermission() Engine->>Engine: Check user-level permission Engine->>Engine: Check role-level permission Engine->>Engine: Check post-level permission Engine->>Engine: Check dept-level permission Engine->>Engine: Merge results (union) alt Has Permission Engine->>Aspect: Return true Aspect->>Controller: Allow Controller->>DB: Execute business operation else No Permission Engine->>Aspect: Return false Aspect->>Controller: Throw permission exception end

2.2 Data Permission Filtering Flow

sequenceDiagram participant User as User participant Controller as Controller participant Interceptor as MyBatis Interceptor participant Engine as Permission Engine participant DB as Database User->>Controller: Query customer list Controller->>Interceptor: Trigger SQL interception Interceptor->>Engine: buildDataScopeSql() Engine->>Engine: Get data scope conditions Engine->>Engine: Get customer level conditions Engine->>Engine: Determine if cascade (related tables) Engine->>Interceptor: Return SQL filter conditions Interceptor->>Interceptor: Inject WHERE conditions Interceptor->>DB: Execute filtered SQL DB->>User: Return filtered results

3. Database Table Structure

3.1 Business Object Operation Permission Table

CREATE TABLE `crm_biz_object_permission` (
 `id` BIGINT NOT NULL AUTO_INCREMENT COMMENT 'Primary Key',
 `biz_type` INT NOT NULL COMMENT 'Business Object Type (1=Lead/2=Customer/3=Contact/4=Opportunity/5=Contract)',
 `biz_type_name` VARCHAR(50) NOT NULL COMMENT 'Business Object Name',
 `operation_type` VARCHAR(20) NOT NULL COMMENT 'Operation Type (CREATE/READ/UPDATE/DELETE/TRANSFER)',
 `operation_name` VARCHAR(50) NOT NULL COMMENT 'Operation Name',
 `role_id` BIGINT DEFAULT NULL COMMENT 'Role ID',
 `post_id` BIGINT DEFAULT NULL COMMENT 'Post ID',
 `dept_id` BIGINT DEFAULT NULL COMMENT 'Department ID',
 `user_id` BIGINT DEFAULT NULL COMMENT 'User ID',
 `status` TINYINT DEFAULT 1 COMMENT 'Status (0=Disabled/1=Enabled)',
 `creator` VARCHAR(64) DEFAULT '' COMMENT 'Creator',
 `create_time` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT 'Create Time',
 `updater` VARCHAR(64) DEFAULT '' COMMENT 'Updater',
 `update_time` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
 `deleted` BIT DEFAULT 0 COMMENT 'Is Deleted',
 `tenant_id` BIGINT NOT NULL DEFAULT 0 COMMENT 'Tenant ID',
 PRIMARY KEY (`id`),
 KEY `idx_biz_type` (`biz_type`),
 KEY `idx_role_id` (`role_id`),
 KEY `idx_post_id` (`post_id`),
 KEY `idx_dept_id` (`dept_id`),
 KEY `idx_user_id` (`user_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='Business Object Operation Permission Table';

3.2 Data Scope Permission Table (Including Customer Level)

CREATE TABLE `crm_data_scope_permission` (
 `id` BIGINT NOT NULL AUTO_INCREMENT COMMENT 'Primary Key',
 `biz_type` INT NOT NULL COMMENT 'Business Object Type',
 `scope_type` VARCHAR(20) NOT NULL COMMENT 'Data Scope Type (ALL/SELF/DEPT/DEPT_AND_CHILD/CUSTOM)',
 `scope_value` TEXT COMMENT 'Custom Scope Value (JSON format)',
 `max_customer_level` INT DEFAULT NULL COMMENT 'Max Customer Level (NULL=No Limit)',
 `role_id` BIGINT DEFAULT NULL COMMENT 'Role ID',
 `post_id` BIGINT DEFAULT NULL COMMENT 'Post ID',
 `dept_id` BIGINT DEFAULT NULL COMMENT 'Department ID',
 `user_id` BIGINT DEFAULT NULL COMMENT 'User ID',
 `status` TINYINT DEFAULT 1 COMMENT 'Status (0=Disabled/1=Enabled)',
 `creator` VARCHAR(64) DEFAULT '' COMMENT 'Creator',
 `create_time` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT 'Create Time',
 `updater` VARCHAR(64) DEFAULT '' COMMENT 'Updater',
 `update_time` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
 `deleted` BIT DEFAULT 0 COMMENT 'Is Deleted',
 `tenant_id` BIGINT NOT NULL DEFAULT 0 COMMENT 'Tenant ID',
 PRIMARY KEY (`id`),
 KEY `idx_biz_type` (`biz_type`),
 KEY `idx_role_id` (`role_id`),
 KEY `idx_post_id` (`post_id`),
 KEY `idx_dept_id` (`dept_id`),
 KEY `idx_user_id` (`user_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='Data Scope Permission Table';

3.3 Data Scope Type Description

Scope Type	Description	SQL Filter Logic
ALL	All data	No filter condition
SELF	Own data	`owner_user_id = current_user`
DEPT	Dept data	`dept_id IN (current_dept)`
DEPT_AND_CHILD	Dept and sub-dept data	`dept_id IN (current_dept_and_children)`
CUSTOM	Custom scope	Generate filter condition based on scope_value

3.4 Customer Level Filtering Description

Level Config	Description	SQL Filter Logic
NULL	No customer level restriction	No filter condition
0	Level 0 only	`level = 0`
1	<= Level 1	`level <= 1`
2	<= Level 2	`level <= 2`

4. Permission Engine Core Implementation

@Service
public class CrmPermissionEngineServiceImpl implements CrmPermissionEngineService {

 @Override
 public boolean hasBizOperationPermission(Long userId, Integer bizType, String operationType) {
 // Check by priority high to low: User → Role → Post → Dept
 if (hasUserPermission(userId, bizType, operationType)) return true;
 if (hasRolePermission(userId, bizType, operationType)) return true;
 if (hasPostPermission(userId, bizType, operationType)) return true;
 if (hasDeptPermission(userId, bizType, operationType)) return true;
 return false;
 }

 @Override
 public String buildDataScopeSql(Long userId, Integer bizType) {
 DataScopePermissionDO scope = getDataScope(userId, bizType);
 if (scope == null) return "1=0";

 StringBuilder sqlBuilder = new StringBuilder();

 // Data scope filtering
 switch (scope.getScopeType()) {
 case "ALL": break;
 case "SELF": sqlBuilder.append("owner_user_id = ").append(userId); break;
 case "DEPT": sqlBuilder.append("dept_id = ").append(getUserDeptId(userId)); break;
 case "DEPT_AND_CHILD": sqlBuilder.append("dept_id IN (").append(getUserDeptAndChildIds(userId)).append(")"); break;
 case "CUSTOM": sqlBuilder.append(scope.getScopeValue()); break;
 default: return "1=0";
 }

 // Customer level filtering (AND stacking)
 Integer maxLevel = scope.getMaxCustomerLevel();
 if (maxLevel != null) {
 if (sqlBuilder.length() > 0) sqlBuilder.append(" AND ");
 sqlBuilder.append("level <= ").append(maxLevel);
 }

 return sqlBuilder.toString();
 }
}

5. MyBatis Data Permission Interceptor

@Component
@Intercepts({@Signature(type = Executor.class, method = "query",
 args = {MappedStatement.class, Object.class, RowBounds.class, ResultHandler.class})})
public class CrmDataPermissionInterceptor implements Interceptor {

 // Tables that need cascade customer level filtering via customer_id
 private static final Set<String> CASCADE_CUSTOMER_LEVEL_TABLES = Set.of(
 "crm_business", "crm_contract", "crm_contact",
 "crm_receivable", "crm_receivable_plan"
 );

 @Override
 public Object intercept(Invocation invocation) throws Throwable {
 // 1. Determine if data permission filtering is needed
 // 2. Get current user ID
 // 3. Parse business type
 // 4. Build data permission filter conditions
 // 5. Modify SQL, add WHERE filter conditions
 // 6. Execute query
 }
}

Cascade Association Relationships

Business Object	Association Field	Cascade?	Description
Customer	`level`	❌ Source	Directly apply level condition
Contact	`customer_id`	✅ Yes	Inherit level via customer ID association
Contract	`customer_id`	✅ Yes	Inherit level via customer ID association
Receivable	`customer_id`	✅ Yes	Inherit level via customer ID association
Opportunity	`customer_id`	✅ Yes	Inherit level via customer ID association
Lead	-	❌ No	Leads are not associated with customers

6. Frontend Permission Configuration Interface

graph TB subgraph "CRM Permission Management" subgraph "Permission Level Switch" A1["Dept Permission"] A2["Post Permission"] A3["Role Permission"] A4["User Permission"] end subgraph "Business Object Selection" B1["Customer"] B2["Opportunity"] B3["Contract"] B4["Contact"] B5["Lead"] B6["Receivable"] end subgraph "Operation Permission Config" C1["Create"] C2["View"] C3["Edit"] C4["Delete"] C5["Transfer"] C6["Export"] end subgraph "Data Scope Config" D1["All Data"] D2["Own Data"] D3["Dept Data"] D4["Dept & Sub-Dept"] D5["Custom Scope"] end subgraph "Customer Level Filter" E1["All Levels"] E2["Level 0"] E3["<= Level 1"] E4["<= Level 2"] end end

7. Implementation Progress

Phase	Task	Status
Phase 1	Database table structure design & creation	✅ Completed
Phase 2	Backend entity classes & Mapper	✅ Completed
Phase 3	Permission engine service implementation	✅ Completed
Phase 4	MyBatis data permission interceptor	✅ Completed
Phase 5	API interface implementation	✅ Completed
Phase 6	Frontend page development	✅ Completed
Phase 7	Customer level cascade filtering	✅ Completed
Phase 8	Testing & verification	✅ Completed

Summary

This solution implements a four-layer data permission filtering mechanism based on Department-Post-Role-User:

Operation Permission: Managed via crm_biz_object_permission table, four-level priority checking
Data Scope: Supports five scope types: ALL/SELF/DEPT/DEPT_AND_CHILD/CUSTOM
Customer Level Filtering: max_customer_level field, supports level range stacking filter
Cascade Inheritance: Contracts, contacts, etc. automatically inherit customer level restrictions via customer_id
SQL Interceptor: Auto-injects WHERE conditions without modifying existing business code
Frontend Configuration: Unified permission configuration interface with level switching and level configuration

MES Manufacturing Execution System

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

MES is the largest business module on the entire platform (133 tables), designed for workshop-level management needs of manufacturing enterprises. It’s not just “purchase-sales-inventory,” but dives deep into production work orders, process routes, scheduling, work reporting, quality inspection, and equipment maintenance — a complete manufacturing execution system.

In one sentence: If your factory needs to manage “how to schedule work orders, how to execute processes, how to inspect quality, how to maintain equipment,” MES is the answer.

Problems Solved

Pain Point	How MES Solves It
Production progress is opaque	Work order → Scheduling → Work reporting full-chain tracking
Quality inspection relies on paper records	IQC/IPQC/OQC/RQC digitized
Equipment failures affect delivery deadlines	Equipment ledger + inspection plans for preventive maintenance
Material management is chaotic	Line-side inventory + production picking/return management
Outsourced processing is hard to manage	Independent outsourced inbound/outbound management
Worker scheduling is complex	Shift scheduling module

User Roles

graph LR subgraph Roles PLANNER["Planner
Create production work orders
Develop scheduling plans"] WORKER["Operator
View work order tasks
Report work records
Pick/return materials"] QC["Quality Inspector
IQC incoming inspection
IPQC in-process inspection
OQC outgoing inspection"] MAINTENANCE["Equipment Maintainer
Manage equipment ledger
Execute inspection plans"] SUPERVISOR["Workshop Supervisor
View production progress
Andon exception handling"] end

Seven Module Panorama

graph TB subgraph MD["Master Data md (17 tables)"] MD1["Materials/Products"] MD2["Customer/Supplier"] MD3["Workshop Management"] MD4["Coding Rules"] end subgraph PRO["Production Management pro (17 tables)"] PRO1["Process Routes"] PRO2["Production Work Orders"] PRO3["Scheduling Orders"] PRO4["Work Reports"] PRO5["Andon System"] end subgraph WM["Warehouse Management wm (62 tables)"] WM1["Location Setup"] WM2["Inventory Management"] WM3["Purchase Inbound"] WM4["Finished Goods Inbound"] WM5["Sales Outbound"] WM6["Picking & Returns"] WM7["Stock Transfer"] WM8["Stocktaking"] WM9["Miscellaneous In/Out"] WM10["Outsourcing Management"] end subgraph QC2["Quality Management qc (16 tables)"] QC1["IQC Incoming Inspection"] QC2_IN["IPQC In-Process Inspection"] QC3["OQC Outgoing Inspection"] QC4["RQC Return Inspection"] end subgraph DV["Equipment Management dv (12 tables)"] DV1["Equipment Ledger"] DV2["Inspection Plans"] DV3["Inspection Records"] end subgraph TM["Tool Management tm (2 tables)"] TM1["Tool Ledger"] TM2["Tool Checkout"] end subgraph CAL["Shift Scheduling cal (7 tables)"] CAL1["Shift Definition"] CAL2["Scheduling Plans"] end MD --> PRO MD --> WM PRO --> WM PRO --> QC2

Production Execution Process

sequenceDiagram participant PLAN as Planner participant MES2 as MES participant LINE as Production Line participant QC3 as Quality Inspector participant WH3 as Warehouse PLAN->>MES2: Create production work order PLAN->>MES2: Develop scheduling plan MES2->>LINE: Work order dispatched to production line LINE->>WH3: Material picking request WH3->>MES2: Confirm material issuance LINE->>MES2: Process work report QC3->>MES2: IPQC in-process inspection LINE->>MES2: Completion work report QC3->>MES2: OQC outgoing inspection LINE->>WH3: Finished goods inbound

Quality Inspection System

graph LR subgraph IQC["IQC Incoming Inspection"] I1["Supplier Incoming Materials"] I2["Inspect → Pass/Fail"] I3["Fail → Return/Concession"] end subgraph IPQC["IPQC In-Process Inspection"] P1["Sample inspection during production"] P2["Key process inspection"] P3["Exception handling"] end subgraph OQC["OQC Outgoing Inspection"] O1["Inspection before finished goods shipment"] O2["Pass → Release"] end subgraph RQC["RQC Return Inspection"] R1["Customer return inspection"] R2["Determine responsibility attribution"] end IQC --> IPQC --> OQC RQC -.-> IQC

Virtual Line-Side Inventory (WIP)

There is a special concept in the MES warehouse module — virtual line-side inventory (WIP_VIRTUAL_WAREHOUSE), used to track work-in-process materials on the shop floor:

Materials issued from warehouse to production line → Line-side inventory increases
Production line consumes materials → Line-side inventory decreases
Finished goods completed → Line-side inventory decreases, finished goods inventory increases

This keeps the quantity and location of WIP materials on the shop floor always clear.

Relationship with Other Modules

Relationship	Description
MES vs WMS	WMS is general warehouse management; MES’s warehouse module is deeply integrated with manufacturing (line-side inventory, picking, outsourcing)
MES vs ERP	ERP manages “purchase-sales-inventory,” MES manages “production execution,” complementary
MES vs IoT	IoT can be used for equipment data collection, MES for production management
MES vs BPM	Can integrate BPM for quality inspection exception approvals, etc.

CS Customer Service System

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, 6 DOs / 5 Controllers, menu ID starting at 8500, building an omnichannel intelligent customer service and ticket management system

1. Enhancement Positioning and Architecture

1.1 Product Positioning

RuoYiPlus CS Customer Service System centers around three core pillars—Omnichannel Access, Intelligent Ticket Routing, and Service Quality Control—to deliver enterprise-level enhancement, achieving full-process digital management from customer touchpoints to problem resolution.

1.2 Module Scale

Metric	Value
Data Objects (DO)	6
Controllers	5
Menu ID Start	8500
Maven Module	yudao-module-cs

1.3 Core Data Tables

Table Name	Description
`cs_conversation`	Conversation Management
`cs_ticket`	Ticket Management
`cs_contact`	Contact Management
`cs_inbox`	Inbox Management
`cs_canned_response`	Canned Responses

graph TB subgraph "RuoYiPlus CS Enhanced Architecture" subgraph "Channel Access Layer" A1[WeChat Channel] A2[APP Channel] A3[Phone Channel] A4[Email Channel] A5[Social Media Channel] end subgraph "Business Processing Layer" B1[Conversation Management] B2[Ticket Management] B3[Intelligent Bot] B4[Knowledge Base] end subgraph "Control Layer" C1[SLA Management] C2[Quality Scoring] C3[Permission Control] C4[Audit Tracking] end end A1 --> B1 A2 --> B1 A3 --> B1 A4 --> B1 A5 --> B1 B1 --> B2 B1 --> B3 B3 --> B4 B2 --> C1 B2 --> C2 B1 --> C3 B2 --> C4

1.4 Capability Comparison

Dimension	Traditional CS	RuoYiPlus CS Enhanced
Channel Access	Single channel	Unified omnichannel access
Ticket Management	Simple tickets	Full-process ticket management
Intelligent CS	None	AI intelligent Q&A + bot
Knowledge Base	None	Knowledge base + intelligent search
Service Quality	None	SLA management + quality scoring
Permission Control	None	CS tiered permissions + data isolation
Audit Compliance	None	Conversation audit + quality traceability

2. Omnichannel Access

2.1 Channel Architecture

graph TB subgraph "Omnichannel Access" subgraph "Instant Messaging" A1[WeChat Official Account] A2[WeChat Mini Program] A3[WeCom] A4[DingTalk] A5[Feishu] end subgraph "Traditional Channels" B1[Phone Support] B2[Email Support] B3[SMS Support] end subgraph "Social Media Channels" C1[Weibo] C2[TikTok] C3[Xiaohongshu] end subgraph "Unified Access" D1[Message Aggregation] D2[Conversation Management] D3[Customer Identification] D4[Context Persistence] end end A1 --> D1 A2 --> D1 A3 --> D1 A4 --> D1 A5 --> D1 B1 --> D1 B2 --> D1 B3 --> D1 C1 --> D1 C2 --> D1 C3 --> D1 D1 --> D2 D2 --> D3 D3 --> D4

Channel Type	Description
WeChat Channels	Official account, mini program, WeCom
APP Channels	In-app embedded, H5 pages
Phone Channels	Inbound/outbound, IVR navigation
Email Channels	Email tickets, auto-reply
Social Media Channels	Weibo, TikTok and other social platforms

3. Full-Process Ticket Management

3.1 Ticket Workflow

graph TB A[Ticket Creation] --> B[Auto Classification] B --> C[Auto Assignment] C --> D[Ticket Processing] D --> E{Resolved?} E -->|Yes| F[Customer Confirmation] E -->|No| G[Ticket Escalation] G --> D F --> H[Satisfaction Rating] H --> I[Ticket Archiving] A --> A1[Multi-Channel Creation] A --> A2[Template-Based Creation] C --> C1[Assignment by Type] C --> C2[Assignment by Skill] C --> C3[Assignment by Region] D --> D1[Accept and Process] D --> D2[Collaborative Processing] D --> D3[Progress Update]

3.2 Ticket Permission Control

The ticket system implements role-based data permission control, ensuring agents can only access tickets within their permission scope.

Permission Level	Scope	Description
Agent	Own tickets	Can only view and process tickets assigned to them
Team Lead	Team tickets	Can view and assign all team tickets
CS Manager	All tickets	Can view all tickets and perform statistical analysis
QA Personnel	Sampled tickets	Can randomly sample tickets for quality scoring

3.3 Ticket Audit

All ticket operations record complete audit logs, supporting ticket processing traceability.

graph LR A[Ticket Creation] --> B[Ticket Assignment] B --> C[Ticket Processing] C --> D[Ticket Escalation] D --> E[Ticket Resolution] E --> F[Ticket Archiving] A -.-> G[Audit Log] B -.-> G C -.-> G D -.-> G E -.-> G F -.-> G

4. Intelligent Customer Service Bot

4.1 Bot Architecture

graph TB subgraph "Intelligent Bot" subgraph "Q&A Engine" A1[Knowledge Base Search] A2[Semantic Understanding] A3[Intelligent Matching] end subgraph "Business Processing" B1[Business Query] B2[Business Processing] B3[Ticket Creation] end subgraph "Human-Bot Collaboration" C1[Bot Reception] C2[Intelligent Handoff to Human] C3[Human Assistance] end end A1 --> A2 A2 --> A3 A3 --> B1 B1 --> B2 B2 --> B3 B3 --> C1 C1 --> C2 C2 --> C3

4.2 Core Capabilities

Capability	Description
Intelligent Q&A	Knowledge base search, semantic matching
Multi-Turn Dialogue	Context understanding, intent recognition
Business Processing	Self-service query, self-service processing
Intelligent Handoff	Automatic handoff to human for complex issues
Human Assistance	Knowledge recommendations, script suggestions

5. Knowledge Base Management

5.1 Knowledge Base System

graph TB subgraph "Knowledge Management" subgraph "Knowledge Collection" A1[FAQ Entry] A2[Document Import] A3[Knowledge Extraction] end subgraph "Knowledge Organization" B1[Knowledge Classification] B2[Knowledge Tags] B3[Knowledge Association] end subgraph "Knowledge Application" C1[Intelligent Search] C2[Knowledge Recommendation] C3[Knowledge Push] end subgraph "Knowledge Maintenance" D1[Knowledge Update] D2[Knowledge Expiration] D3[Knowledge Archiving] end end A1 --> B1 A2 --> B1 A3 --> B1 B1 --> B2 B2 --> B3 B3 --> C1 C1 --> C2 C2 --> C3 C3 --> D1 D1 --> D2 D2 --> D3

Capability	Description
Knowledge Entry	FAQ, documents, Q&A pairs
Intelligent Search	Semantic search, keyword search
Knowledge Recommendation	Related knowledge recommendations
Knowledge Statistics	Usage statistics, effectiveness evaluation

6. Service Quality Management

6.1 SLA Service Levels

graph LR A[Ticket Creation] --> B{Priority} B -->|Critical| C[5-Min Response] B -->|Important| D[15-Min Response] B -->|Normal| E[30-Min Response] C --> F[30-Min Resolution] D --> G[2-Hour Resolution] E --> H[24-Hour Resolution]

cs:
 sla:
 levels:
 - name: "Critical"
 response-time: 5m
 resolve-time: 30m
 - name: "Important"
 response-time: 15m
 resolve-time: 2h
 - name: "Normal"
 response-time: 30m
 resolve-time: 24h
 monitoring:
 alert-threshold: 80%  # Alert if compliance rate falls below 80%

6.2 Quality Scoring

QA Dimension	Metrics
Response Speed	Response time compliance rate
Resolution Quality	Problem resolution rate, first-contact resolution rate
Service Attitude	Polite language, service standards
Professional Competence	Knowledge accuracy, processing capability
Customer Satisfaction	Satisfaction score, positive rating rate

7. Technical Architecture

graph TB subgraph "yudao-module-cs-plus" subgraph "cs-biz" A1[channel - Channel Access] A2[session - Conversation Management] A3[ticket - Ticket Management] A4[robot - Intelligent Bot] A5[knowledge - Knowledge Base] A6[sla - SLA Management] A7[quality - Quality Management] A8[agent - Agent Management] A9[workspace - Workspace] A10[analytics - Data Analysis] end subgraph "Permissions and Audit" B1[permission - Permission Control] B2[audit - Audit Logs] end end A1 --> B1 A2 --> B2 A3 --> B2 A4 --> B1 A5 --> B1

8. Business Value

Value Point	Description
Efficiency Improvement	Intelligent bot, quick tools
Cost Reduction	Bot diversion, self-service
Satisfaction Improvement	Quick response, professional service
Service Quality Control	SLA management, quality scoring
Data-Driven Optimization	Performance analysis, issue analysis
Compliance and Traceability	Ticket audit, conversation traceability

Sales & Financial Management

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

This is the financial sub-module of the ERP system, implemented by the finance package of yudao-module-erp. It does not exist independently but is tightly integrated into ERP’s procurement and sales processes, responsible for recording and managing the flow of funds.

In one sentence: Procurement requires payment, sales require collection, returns require refunds — the financial module handles all these “money” matters.

Problems Solved

Pain Point	How Financial Module Solves It
Don’t know which supplier owes how much	Settlement account balances are clearly visible
Payments can’t be linked to specific purchase orders	Payment orders linked to purchase inbound orders
Collections disconnected from sales orders	Receipt orders linked to sales outbound orders
Refund process is chaotic	Return orders automatically trigger refund process

User Roles

graph LR subgraph Roles FINANCE2["Finance Staff
Manage settlement accounts
Process payments/receipts
Process refunds
Reconcile accounts"] end

Core ER Diagram

erDiagram ERP_ACCOUNT ||--o{ ERP_FINANCE_PAYMENT : "Payment" ERP_ACCOUNT ||--o{ ERP_FINANCE_RECEIPT : "Receipt" ERP_PURCHASE_IN ||--o{ ERP_FINANCE_PAYMENT : "Purchase Inbound → Payment" ERP_PURCHASE_RETURN ||--o{ ERP_FINANCE_PAYMENT : "Purchase Return → Refund" ERP_SALE_OUT ||--o{ ERP_FINANCE_RECEIPT : "Sales Outbound → Receipt" ERP_SALE_RETURN ||--o{ ERP_FINANCE_RECEIPT : "Sales Return → Refund" ERP_ACCOUNT { bigint id PK varchar name "Account Name" decimal balance "Current Balance" tinyint status "Status" } ERP_FINANCE_PAYMENT { bigint id PK varchar no "Payment No." bigint account_id FK "Settlement Account" bigint in_id FK "Purchase Inbound Order" decimal price "Payment Amount" datetime time "Payment Time" } ERP_FINANCE_RECEIPT { bigint id PK varchar no "Receipt No." bigint account_id FK "Settlement Account" bigint out_id FK "Sales Outbound Order" decimal price "Receipt Amount" datetime time "Receipt Time" }

Business Scenarios

Scenario 1: Purchase Payment

sequenceDiagram participant P2 as Purchaser participant F2 as Finance participant ERP5 as ERP participant ACC as Settlement Account P2->>ERP5: Complete purchase inbound F2->>ERP5: View purchase inbound orders pending payment F2->>ERP5: Select settlement account, create payment order ERP5->>ACC: Deduct account balance ERP5->>ERP5: Record payment transaction

Scenario 2: Sales Receipt

sequenceDiagram participant S3 as Salesperson participant F3 as Finance participant ERP6 as ERP participant ACC2 as Settlement Account S3->>ERP6: Complete sales outbound F3->>ERP6: View sales outbound orders pending receipt F3->>ERP6: Select settlement account, create receipt order ERP6->>ACC2: Increase account balance ERP6->>ERP6: Record receipt transaction

Settlement Accounts

Settlement accounts represent the fund account relationship between the company and suppliers/customers. Every payment and receipt affects the corresponding account balance.

Attribute	Description
Account Name	e.g., “XX Supplier Settlement Account”
Current Balance	Real-time updates, payments deduct, receipts add
Status	Enabled/Disabled

IoT Internet of Things

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

The IoT module is a device management platform similar to Alibaba Cloud IoT Platform. It can connect massive devices, define device capabilities through thing models, process device data using a rule engine, and achieve device data collection, remote control, and scenario linkage.

In one sentence: If your hardware devices need cloud-based management, this provides the complete chain from device registration to data flow.

Problems Solved

Pain Point	How IoT Solves It
Diverse device access protocols	Supports MQTT/HTTP/CoAP/TCP/UDP/WebSocket/Modbus etc.
Non-uniform device data formats	Thing model standardizes device capability definitions
Don’t know how to process device data	Rule engine → data routing/scenario linkage/alerts
Difficult device firmware upgrades	OTA remote upgrades
Need to integrate with third-party IoT platforms	Built-in EMQX integration, customizable protocols

User Roles

graph LR subgraph Roles IOT_ADMIN["IoT Admin
Define products
Manage devices
Configure thing models
Set up rule engine"] IOT_DEV["Device Developer
Device-side development
Protocol integration
OTA upgrades"] IOT_OP["Operations Staff
Monitor device status
Handle alerts
Data analysis"] end

Platform Architecture

graph TB subgraph DeviceLayer["Device Layer"] D1["Sensors"] D2["Gateways"] D3["Controllers"] D4["Smart Devices"] end subgraph AccessLayer["Access Layer (Multi-Protocol)"] P1["MQTT"] P2["HTTP"] P3["CoAP"] P4["TCP/UDP"] P5["WebSocket"] P6["Modbus"] end subgraph PlatformLayer["IoT Platform"] PRODUCT["Product Management
Define device types"] DEVICE["Device Management
Registration/Authentication/Status"] MODEL["Thing Model
Properties/Services/Events"] OTA["OTA Upgrade
Firmware remote updates"] end subgraph ProcessingLayer["Data Processing Layer"] RULE["Rule Engine
Data rules/Scenario linkage/Alerts"] TD["TDengine
Time-series data storage"] end DeviceLayer --> AccessLayer AccessLayer --> PlatformLayer PlatformLayer --> ProcessingLayer

Thing Model Design

The thing model is the core concept of IoT, describing in a standardized way “what attributes a device has, what it can do, and what it reports”:

graph TB subgraph ThingModel["Thing Model = Digital Description of Device"] ATTR["Property
Static characteristics of device
Example: Temperature, Humidity, Switch State"] SERVICE["Service
Actions the device can execute
Example: Unlock, Restart, Calibrate"] EVENT["Event
Information actively reported by device
Example: Alerts, Faults, Completion Notifications"] end

Rule Engine

flowchart LR DATA["Device Data"] --> ENGINE["Rule Engine"] ENGINE -->|Data Rules| ROUTE1["Data Routing
Store to TDengine
Forward to HTTP/Kafka"] ENGINE -->|Scenario Linkage| ROUTE2["Scenario Linkage
Temp > 30°C → Auto-turn on fan"] ENGINE -->|Alert Config| ROUTE3["Alerts
Device offline > 5 min → Send notification"]

Device Lifecycle

flowchart LR CREATE["Create Product
Define thing model"] --> REG["Register Device
Get authentication info"] REG --> ONLINE["Device Online
Establish connection"] ONLINE --> WORK["Normal Operation
Report data/Receive commands"] WORK --> OTA2["OTA Upgrade"] OTA2 --> WORK WORK --> OFFLINE["Device Offline"] OFFLINE --> ONLINE

Supported Protocols

Protocol	Use Case	Features
MQTT	Mainstream IoT protocol	Lightweight, pub-sub, QoS
HTTP	Simple devices, web apps	High versatility
CoAP	Low-power devices	HTTP-like, UDP
TCP	Custom protocols	Flexible, efficient
UDP	High-frequency data reporting	Low latency
WebSocket	Real-time bidirectional communication	Browser-friendly
Modbus	Industrial devices	Industrial control standard
EMQX	High-performance MQTT Broker	Million-level connections
Custom Protocol	Special devices	Extension development

Technical Dependencies

TDengine: Time-series database for storing massive time-series data reported by devices (requires separate setup)
EMQX: High-performance MQTT Broker (optional, for large-scale device access)

Member Marketing

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, 26 DOs / 31 Controllers, menu ID starting from 13000, building a complete member operations and marketing automation system

1. Enhancement Positioning & Architecture

1.1 Product Positioning

RuoYiPlus Member Marketing provides enterprise-grade enhancements around three core areas: member full-lifecycle operations, intelligent marketing automation, and member data compliance, achieving a complete business closed loop from acquisition to retention.

1.2 Module Scale

Metric	Value
Data Objects (DO)	26
Controllers	31
Menu ID Start	13000
Maven Module	yudao-module-member

1.3 Core Data Tables

Table Name	Description
`member_user`	Member Information
`member_point`	Points Management
`member_balance`	Balance Management
`member_coupon`	Coupon Management
`member_package`	Package Management
`member_level`	Level Management
`member_tag`	Tag Management
`member_sign_in`	Sign-in Management
`member_recharge`	Recharge Management

graph TB subgraph "RuoYiPlus Member Marketing Enhanced Architecture" subgraph "Operations Layer" A1[Member Lifecycle] A2[Level System] A3[Points System] A4[Benefits Management] end subgraph "Marketing Layer" B1[Marketing Activity Engine] B2[Automation Triggers] B3[Member Profile] B4[RFM Analysis] end subgraph "Data Layer" C1[Member Data Analysis] C2[Campaign Effect Analysis] C3[Operational Metrics Monitoring] end subgraph "Compliance Layer" D1[Member Data Permissions] D2[Privacy Data Masking] D3[Operation Audit] D4[Data Encryption] end end A1 --> B1 A2 --> B2 A3 --> B2 A4 --> B3 B1 --> C1 B2 --> C2 B3 --> C3 C1 --> D1 C2 --> D2 C3 --> D3

1.4 Capability Comparison

Dimension	Yudao Native Member	RuoYiPlus Member Marketing Enhancement
Member Management	Basic member info	Full-lifecycle operations
Level System	Simple levels	Dynamic levels + benefits system
Points System	Basic points	Points store + redemption system
Marketing Activities	None	Marketing activity management engine
Member Analysis	Simple statistics	RFM analysis + profile tags
Marketing Automation	None	Marketing automation triggers
Permission Control	Basic permissions	Tiered member data permissions
Privacy Compliance	None	Privacy data masking + audit

2. Member Full-Lifecycle Operations

2.1 Lifecycle Stages

graph LR A[Acquisition Stage] --> B[Activation Stage] B --> C[Retention Stage] C --> D[Monetization Stage] D --> E[Referral Stage] A --> A1[Registration & Lead Gen] A --> A2[New Customer Incentives] A --> A3[First Purchase Conversion] A --> A4[Channel Attribution] B --> B1[Activation Guidance] B --> B2[First Purchase] B --> B3[Habit Building] B --> B4[New Customer Gift Pack] C --> C1[Sign-in Incentives] C --> C2[Points Accumulation] C --> C3[Member Upgrade] C --> C4[Exclusive Offers] D --> D1[Upsell Recommendations] D --> D2[Cross-selling] D --> D3[High-value Conversion] D --> D4[Paid Membership] E --> E1[Referral Rewards] E --> E2[Social Virality] E --> E3[KOC Cultivation] E --> E4[Member Ambassador]

2.2 Member Data Permissions

The Member module implements data-tier-based permission control to ensure member privacy data security.

Permission Level	Scope	Description
Regular Member	Personal info	Can only view their own member information
Customer Service Agent	Assigned members	Can view basic info of assigned members
Operations Specialist	All members	Can view all member data (masked)
Data Analyst	Analytical data	Can view statistical data but not personal information

// Member data permission example
@DataPermission(scope = "member_level")
public class MemberServiceImpl {
 // Operations specialists can view member data
 // Sensitive fields are automatically masked
}

// Privacy data masking
@SensitiveField(type = SensitiveType.PHONE)
private String phone;

@SensitiveField(type = SensitiveType.EMAIL)
private String email;

2.3 Member Operation Audit

All member data operations are recorded with complete audit logs, supporting member data traceability.

Audit Item	Description
Member Registration	Records registration time, registration channel
Level Change	Records upgrade/downgrade time, reason
Points Change	Records points earned and spent details
Benefits Usage	Records benefit usage time and content
Data Export	Records export time, exporter, exported data volume

3. Dynamic Level System

3.1 Level System

graph TB subgraph "Level System" A[Regular Member] --> B[Silver Member] B --> C[Gold Member] C --> D[Diamond Member] A --> A1[0 Points] B --> B1[1000 Points] C --> C1[5000 Points] D --> D1[20000 Points] A --> A2[Basic Points] A --> A3[Birthday Offer] B --> B1[Double Points] B --> B2[Dedicated Support] B --> B3[Priority Shipping] C --> C1[Triple Points] C --> C2[Free Shipping] C --> C3[Exclusive Discounts] D --> D1[Quintuple Points] D --> D2[Exclusive Gifts] D --> D3[VIP Events] end

3.2 Level Configuration

member:
 levels:
 - name: "Regular Member"
 min-points: 0
 benefits: ["Basic Points", "Birthday Offer"]
 - name: "Silver Member"
 min-points: 1000
 benefits: ["Double Points", "Dedicated Support", "Priority Shipping"]
 - name: "Gold Member"
 min-points: 5000
 benefits: ["Triple Points", "Free Shipping", "Exclusive Discounts", "Member Day Privileges"]
 - name: "Diamond Member"
 min-points: 20000
 benefits: ["Quintuple Points", "Exclusive Gifts", "VIP Events", "Birthday Double"]
 upgrade-rules:
 auto-upgrade: true
 grace-period: 90 # 90-day grace period
 downgrade-warning: 30 # 30-day advance warning before downgrade

4. Points System Enhancement

4.1 Points Process

graph LR A[Points Earning] --> B[Points Accumulation] B --> C[Points Redemption] C --> D[Points Settlement] A --> A1[Purchase Points] A --> A2[Activity Points] A --> A3[Task Points] B --> B1[Points Balance] B --> B2[Points Validity] C --> C1[Points Exchange] C --> C2[Points Deduction] C --> C3[Points Lottery] D --> D1[Points Expiry] D --> D2[Points Reset]

Capability	Description
Points Earning	Purchase points, activity points, task points
Points Redemption	Points exchange, points deduction, points lottery
Points Validity	Points expiry rules, reset reminders
Points Freeze	Points freeze on order cancellation
Points Traceability	Detailed points change records

5. Marketing Activity Engine

5.1 Activity Types

Activity Type	Description
Registration Activity	New member registration gift pack, first purchase offer
Sign-in Activity	Consecutive sign-in rewards, sign-in lottery
Purchase Activity	Purchase points rebate, tiered discounts
Festival Activity	Member day, birthday offer, holiday promotions
Viral Activity	Referral rewards, group buying
Task Activity	Complete tasks to earn rewards

5.2 Marketing Automation

graph TB subgraph "Marketing Automation" subgraph "Triggers" A1[Event Trigger] A2[Condition Trigger] A3[Time Trigger] A4[Behavior Trigger] end subgraph "Rule Engine" B1[Rule Matching] B2[Condition Evaluation] B3[Action Execution] end subgraph "Execution Actions" C1[Send Coupon] C2[Grant Points] C3[Send SMS] C4[Send Email] end end A1 --> B1 A2 --> B1 A3 --> B1 A4 --> B1 B1 --> B2 B2 --> B3 B3 --> C1 B3 --> C2 B3 --> C3 B3 --> C4

member:
 automation:
 rules:
 - name: "New Customer First Order Incentive"
 trigger: "first_order"
 actions:
 - sendCoupon: "New Customer Repurchase Coupon"
 - addPoints: 100
 - sendSms: "Thank you for your purchase, 100 points awarded"
 - name: "Member Upgrade Congratulations"
 trigger: "level_upgrade"
 actions:
 - sendEmail: "Upgrade Congratulations Email"
 - sendGift: "Upgrade Gift Pack"
 - addPoints: 500
 - name: "Churn Warning Recall"
 trigger: "rfm_change"
 condition: "R > 60"
 actions:
 - sendCoupon: "Recall Exclusive Coupon"
 - sendSms: "Long time no see, exclusive offer waiting for you"

6. RFM Analysis Model

6.1 RFM Segmentation

RFM Segment	Definition	Operations Strategy
Important Value Customers	R Near, F High, M High	VIP service, exclusive benefits
Important Development Customers	R Near, F Low, M High	Increase frequency, build habits
Important Retention Customers	R Far, F High, M High	Reactivate recall, retention
Important At-Risk Customers	R Far, F Low, M High	Priority retention, exclusive offers
General Value Customers	R Near, F High, M Low	Increase order value, upgrade guidance
General Development Customers	R Near, F Low, M Low	New customer cultivation, first order incentives
General Retention Customers	R Far, F High, M Low	Reactivate recall
Low-value Customers	R Far, F Low, M Low	Low-cost maintenance

6.2 RFM Configuration

member:
 rfm:
 r-thresholds: [30, 60, 90] # Days since last purchase
 f-thresholds: [3, 10, 20] # Purchase frequency
 m-thresholds: [100, 500, 1000] # Purchase amount
 analysis-cycle: "monthly"

7. Technical Architecture

graph TB subgraph "yudao-module-member-plus" subgraph "member-biz" A1[lifecycle] A2[level] A3[points] A4[benefits] A5[activity] A6[automation] A7[rfm] A8[tag] A9[analytics] end subgraph "Permissions & Audit" B1[permission] B2[audit] B3[masking] end end A1 --> B1 A2 --> B1 A3 --> B2 A4 --> B2 A5 --> B3 A6 --> B3

8. Business Value

Value Point	Description
Increase Repurchase Rate	Member benefit incentives, points system
Reduce Churn Rate	RFM early warning, automated recall
Increase Average Order Value	Upgrade guidance, high-value conversion
Reduce Operational Costs	Marketing automation, intelligent segmentation
Data-driven Decisions	Profile analysis, effect tracking
Privacy Compliance	Data masking, operation audit

IM Instant Messaging

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

The IM module provides built-in instant messaging capabilities for your platform — no need to integrate third-party IM SDKs (such as Huanxin, RongCloud), directly implement private chat, group chat, channel broadcasting, and audio-video calls within your system. Particularly suitable for scenarios requiring “in-platform communication,” such as e-commerce customer service, internal enterprise communication, community private messaging, etc.

In one sentence: Let your users chat within your platform, with data and experience fully under your control.

Problems Solved

Pain Point	How IM Solves It
Third-party IM SDK costs are high	Self-built IM, zero additional cost
User data stored with third parties	Chat data in your own database
Need to integrate with business systems	User system, friend relationships linked with business
Audio-video call capability	Integrated with LiveKit, supports WebRTC calls

User Roles

graph LR subgraph Roles IM_USER["Regular User
Private chat/group chat
Send text/images/files/voice
Audio-video calls"] IM_ADMIN["IM Admin
Manage groups
Configure channels
Manage sensitive words
View message records"] end

Functional Architecture

graph TB subgraph Core["Core Features"] MSG2["Message Center
Private/Group chat
Text/Image/File/Voice/Video"] FRIEND["Friend Relationships
Add/Delete/Blocklist"] GROUP["Group Management
Create/Join/Leave/Mute"] CHANNEL["Channel Broadcasting
Announcements/Notifications"] CALL["Audio-Video Calls
Based on LiveKit
WebRTC"] end subgraph Auxiliary EMOJI["Emoji Management"] SENSITIVE["Sensitive Word Filtering"] end subgraph Communication["Communication Layer"] WS["WebSocket Real-time Communication
local / redis / rocketmq
/ kafka / rabbitmq"] end Core --> Communication Auxiliary --> Core

Core ER Diagram

erDiagram IM_USER ||--o{ IM_MESSAGE : "Send" IM_USER ||--o{ IM_FRIEND : "Friend Relations" IM_USER ||--o{ IM_GROUP_MEMBER : "Group Members" IM_GROUP ||--o{ IM_GROUP_MEMBER : "Contains" IM_GROUP ||--o{ IM_MESSAGE : "Group Messages" IM_CHANNEL ||--o{ IM_CHANNEL_MESSAGE : "Channel Messages" IM_CHANNEL ||--o{ IM_CHANNEL_MEMBER : "Channel Members" IM_MESSAGE { bigint id PK bigint from_user_id FK "Sender" bigint to_user_id FK "Receiver" bigint group_id FK "Group" tinyint type "Message Type" text content "Message Content" datetime create_time "Send Time" } IM_GROUP { bigint id PK varchar name "Group Name" bigint owner_user_id FK "Group Owner" tinyint status "Status" } IM_CHANNEL { bigint id PK varchar name "Channel Name" tinyint type "Channel Type" }

Database Table Groups

Group	Table Count	Description
Message Center	2 tables	Message records, message conversations
Friend Relations	2 tables	Friends, friend requests
Group Management	3 tables	Groups, group members, group announcements
Channel Broadcasting	3 tables	Channels, channel members, channel messages
Audio-Video Calls	2 tables	Call records, call participants
Others	4 tables	Emojis, sensitive words, etc.

WebSocket Communication Modes

graph TB subgraph SendMode["Message Send Modes (Switchable)"] LOCAL["local
Standalone Mode
For development/debugging"] REDIS3["redis
Redis Broadcast
Small clusters"] ROCKET2["rocketmq
RocketMQ
High throughput"] KAFKA2["kafka
Kafka
Large scale"] RABBIT2["rabbitmq
RabbitMQ
Enterprise-grade"] end

Application Scenarios

Scenario	Usage
E-commerce Customer Service	Buyer ↔ Merchant customer service private chat
Enterprise Internal Communication	Employee group chat, department channels
Community Private Messaging	User-to-user private chat
Online Education	Student ↔ Teacher, course group chat + audio-video
Medical Consultation	Patient ↔ Doctor private chat + audio-video consultation

MP WeChat Official Account Management

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, 8 DOs / 12 Controllers, menu ID starting from 12000, building a WeChat Official Account operations management platform

1. Enhancement Positioning and Architecture

1.1 Product Positioning

RuoYiPlus MP focuses on three core areas for enterprise enhancement: Official Account Management, Material Management, and User Interaction, enabling digital WeChat Official Account operations management.

1.2 Module Scale

Metric	Value
Data Objects (DO)	8
Controllers	12
Menu ID Start	12000
Maven Module	yudao-module-mp

1.3 Core Data Tables

Table Name	Description
`mp_account`	Official Account Management
`mp_material`	Material Management
`mp_menu`	Menu Management
`mp_auto_reply`	Auto Reply
`mp_message`	Message Management
`mp_tag`	User Tags
`mp_user`	Follower Management

graph TB subgraph "RuoYiPlus MP Enhanced Architecture" subgraph "Official Account Management" A1[Account Configuration] A2[Menu Management] A3[Auto Reply] end subgraph "Content Management" B1[Material Management] B2[Rich Media Messages] B3[Template Messages] end subgraph "User Management" C1[Follower Management] C2[User Tags] C3[Message Interaction] end subgraph "Control Layer" D1[Permission Control] D2[Data Audit] D3[Content Moderation] end end A1 --> A2 A2 --> A3 A3 --> B1 B1 --> B2 B2 --> B3 B3 --> C1 C1 --> C2 C2 --> C3 C1 --> D1 B3 --> D2 A3 --> D3

1.4 Capability Comparison

Dimension	Traditional Solution	RuoYiPlus MP Enhanced
Official Account Management	Single account	Multi-account unified management
Material Management	WeChat backend	Local material library + sync
Auto Reply	Basic reply	Smart reply + keywords
Follower Management	WeChat backend	Follower management + tag grouping
Message Management	None	Message records + analysis
Permission Control	None	Account-level data permissions
Content Moderation	None	Content moderation + compliance

2. Official Account Management

2.1 Account Configuration

graph TB subgraph "Official Account Management" A[Account Registration] --> B[Basic Configuration] B --> C[Menu Configuration] C --> D[Auto Reply] D --> E[Template Messages] B --> B1[AppID Configuration] B --> B2[Key Management] B --> B3[Server Configuration] C --> C1[Custom Menu] C --> C2[Personalized Menu] D --> D1[Follow Reply] D --> D2[Keyword Reply] D --> D3[Message Reply] end

Capability	Description
Multi-Account	Multi-account unified management
Menu Management	Custom menu + personalized menu
Auto Reply	Follow reply + keyword + message reply
Template Messages	Template message sending

3. Material and Content Management

3.1 Material Management

graph TB subgraph "Material Management" A[Material Upload] --> B[Material Classification] B --> C[Material Sync] C --> D[Material Usage] A --> A1[Image Materials] A --> A2[Video Materials] A --> A3[Audio Materials] A --> A4[Rich Media Materials] C --> C1[Sync to WeChat] C --> C2[Material Update] D --> D1[Rich Media Messages] D --> D2[Broadcast Messages] end

Material Type	Description
Image Materials	Image upload + management
Video Materials	Video upload + management
Audio Materials	Audio upload + management
Rich Media Materials	Rich media editing + publishing

4. Follower and User Management

4.1 Follower Management

graph LR A[User Follow] --> B[Follower Registration] B --> C[Tag Grouping] C --> D[Message Interaction] D --> E[Data Analysis] B --> B1[Basic Information] B --> B2[Follow Time] B --> B3[Source Channel] C --> C1[Auto Tagging] C --> C2[Manual Grouping] D --> D1[Message Records] D --> D2[Customer Service Messages]

Capability	Description
Follower Management	Follower list + details
Tag Management	User tags + grouping
Message Records	Message history + reply
User Profiling	User analysis + tagging

5. Technical Architecture

graph TB subgraph "yudao-module-mp-plus" subgraph "mp-biz" A1[account Official Account Management] A2[material Material Management] A3[menu Menu Management] A4[auto_reply Auto Reply] A5[message Message Management] A6[tag Tag Management] A7[user User Management] A8[analytics Data Analysis] end subgraph "Permissions & Audit" B1[permission Permission Control] B2[audit Audit Logs] B3[content Content Moderation] end end A1 --> B1 A2 --> B3 A3 --> B1 A4 --> B3 A5 --> B2 A7 --> B1

6. Business Value

Value Point	Description
Multi-Account Management	Multi-account unified management
Content Operations	Material management + content publishing
Follower Operations	Tag grouping + precise targeting
Data Insights	User analysis + message analysis
Compliance Operations	Content moderation + operation audit
System Integration	Integration with CRM / membership

ERP Enterprise Resource Planning

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, 41 DOs / 30 Controllers, menu ID starting at 4000, building a complete integrated inventory and financial management system

1. Enhancement Positioning and Architecture

1.1 Product Positioning

RuoYiPlus ERP builds on Yudao’s native capabilities, providing enterprise-level enhancements around three core areas: procurement-sales-inventory-finance integrated management, multi-dimensional data permissions, and business operation auditing, achieving a complete closed loop from business transactions to financial accounting.

1.2 Module Scale

Metric	Value
Data Objects (DO)	41
Controllers	30
Menu ID Start	4000
Maven Module	yudao-module-erp

1.3 Core Data Tables

Table Name	Description
`erp_product`	Product management
`erp_supplier`	Supplier management
`erp_customer`	Customer management
`erp_warehouse`	Warehouse management
`erp_purchase`	Purchase management
`erp_sale`	Sales management
`erp_inventory`	Inventory management
`erp_finance`	Financial management

graph TB subgraph "RuoYiPlus ERP Enhancement Architecture" subgraph "Business Layer" A1[Purchase Management] A2[Sales Management] A3[Inventory Management] A4[Financial Management] A5[Production Management] end subgraph "Capability Layer" B1[Supplier Management] B2[Cost Accounting] B3[Business Analysis] end subgraph "Infrastructure Layer" C1[Data Permission Engine] C2[Business Audit] C3[Sensitive Data Masking] C4[Multi-Tenancy Isolation] end end A1 --> B1 A2 --> B2 A3 --> B2 A4 --> B3 A5 --> B3 B1 --> C1 B2 --> C2 B3 --> C3

1.4 Capability Comparison

Dimension	Yudao Native Capability	RuoYiPlus ERP Enhancement
Purchase Management	Basic purchasing	Full purchase process + supplier management
Sales Management	Basic sales	Full sales process + customer management
Inventory Management	Basic inventory	Multi-warehouse + fine-grained location management
Financial Management	None	Receivables/payables + cost accounting
Production Management	None	Simplified production + process management
Report Analysis	Simple reports	Business analysis + decision support
Permission Control	Basic RBAC	Multi-dimensional data permissions
Audit Compliance	Operation logs	Full-chain business operation audit

2. Purchase Management Enhancement

2.1 Purchase Process

graph TB subgraph "Purchase Process" A[Purchase Demand] --> B[Purchase Request] B --> C[Supplier Comparison] C --> D[Purchase Order] D --> E[Order Approval] E --> F[Receiving Appointment] F --> G[Quality Inspection] G --> H[Receipt Confirmation] H --> I[Purchase Settlement] I --> J[Payment Request] J --> K[Payment Execution] end A --> A1[Sales Forecast] A --> A2[Inventory Alert] A --> A3[Demand Aggregation] C --> C1[Multi-Supplier Comparison] C --> C2[Supplier Evaluation] I --> I1[Reconciliation Statement] I --> I2[Invoice Registration]

2.2 Purchase Permission Control

The purchase module implements role-based and data-scope-based permission control to ensure purchase data security.

Permission Level	Scope	Description
Purchaser	Personally responsible POs	Can only view and process their own purchase orders
Purchase Supervisor	Department POs	Can view and approve all department purchase orders
Finance Manager	All purchase settlements	Can view all purchase settlement data
General Manager	All purchase data	Can view all purchase data and approve

// Purchase data permission example
@DataPermission(roles = {"purchase_manager"})
public class PurchaseOrderServiceImpl {
 // Purchase supervisor can view department purchase orders
 // Automatically filters data by department hierarchy
}

2.3 Purchase Audit

All purchase operations record complete audit logs, supporting purchase process traceability.

Audit Item	Description
Purchase Request	Records requester, request time, request reason
Purchase Order	Records order creation, approval, changes
Receiving & Inbound	Records receiving time, quantity, inspection results
Purchase Settlement	Records reconciliation, invoice, payment info

3. Sales Management Enhancement

3.1 Sales Process

graph TB subgraph "Sales Process" A[Customer Inquiry] --> B[Quotation] B --> C[Quotation Approval] C --> D[Quotation Tracking] D --> E[Sales Order] E --> F[Order Approval] F --> G[Inventory Reservation] G --> H[Outbound & Shipping] H --> I[Logistics Tracking] I --> J[Receipt Confirmation] J --> K[Invoice Issuance] K --> L[Receivable Registration] L --> M[Collection Registration] end

3.2 Sales Permission Control

The sales module implements a four-layer data permission model to ensure strict isolation of sales data by organizational structure.

graph TB subgraph "Sales Permission Decision" A[Sales Request] --> B[Permission Resolution] B --> C{Permission Source} C --> D[User-Level Permission] C --> E[Role-Level Permission] C --> F[Position-Level Permission] C --> G[Department-Level Permission] D --> H[Permission Merge] E --> H F --> H G --> H H --> I[Data Filtering] I --> J[Return Results] end

Permission Level	Use Case	Example
Salesperson	Personal orders	Can only view their own sales orders
Sales Manager	Team orders	Can view all team sales orders
Regional Director	Regional orders	Can view all regional sales orders
General Manager	All orders	Can view all sales orders

4. Financial Management Enhancement

4.1 Financial Management Architecture

graph TB subgraph "Financial Management" subgraph "Receivables Management" A1[Accounts Receivable] A2[Collection Registration] A3[Reconciliation] A4[Aging Analysis] A5[Collection Management] end subgraph "Payables Management" B1[Accounts Payable] B2[Payment Request] B3[Payment Execution] B4[Reconciliation] B5[Aging Analysis] end subgraph "Cost Management" C1[Purchase Cost] C2[Sales Cost] C3[Cost Accounting] C4[Cost Analysis] C5[Profit Analysis] end subgraph "Financial Reports" D1[Receivables & Payables Report] D2[Income & Expense Report] D3[Profit Report] end end A1 --> A2 A2 --> A3 A3 --> A4 A4 --> A5 B1 --> B2 B2 --> B3 B3 --> B4 B4 --> B5 C1 --> C3 C2 --> C3 C3 --> C4 C4 --> C5 D1 --> D2 D2 --> D3

4.2 Financial Permission Control

The financial module implements strict data permission control to ensure financial data security.

Permission Level	Scope	Description
Finance Staff	Assigned books	Can only view their assigned book data
Finance Supervisor	Department books	Can view all department book data
Finance Manager	All books	Can view all book data
Auditor	Read-only	Can view all financial data but cannot modify

4.3 Financial Audit

All financial operations record complete audit logs, supporting financial data traceability.

Audit Item	Description
Receivables	Records receivable creation, collection, write-off
Payables	Records payable creation, payment, write-off
Cost Accounting	Records cost calculation process
Invoice Management	Records invoice issuance, voiding, red-ink offset

5. Supplier Management

5.1 Supplier Evaluation

graph TB subgraph "Supplier Evaluation" A[Supplier Profile] --> B[Evaluation Dimensions] B --> C[Quality Dimension 40%] B --> D[Delivery Dimension 30%] B --> E[Price Dimension 20%] B --> F[Service Dimension 10%] C --> G[Composite Score] D --> G E --> G F --> G G --> H[Supplier Tiering] H --> I[Procurement Strategy] end

Evaluation Dimension	Metrics
Quality Dimension	Inspection pass rate, return rate
Delivery Dimension	On-time delivery rate, lead time
Price Dimension	Price competitiveness, price stability
Service Dimension	Response speed, service satisfaction

erp:
 supplier:
 evaluation:
 dimensions:
 - name: "Quality"
 weight: 40
 metrics: ["quality_rate", "return_rate"]
 - name: "Delivery"
 weight: 30
 metrics: ["delivery_rate", "lead_time"]
 - name: "Price"
 weight: 20
 metrics: ["price_competitiveness"]
 - name: "Service"
 weight: 10
 metrics: ["response_time", "satisfaction"]
 cycle: "quarterly"

6. Cost Accounting

6.1 Cost Accounting Methods

Accounting Method	Description	Use Case
Moving Weighted Average	Real-time average cost calculation	General scenarios
FIFO	Account by receipt order	High price volatility
LIFO	Account by latest receipt	Special industries
Standard Cost	Account by preset standards	Manufacturing enterprises

6.2 Cost Analysis

Analysis Dimension	Metrics
Purchase Cost	Unit purchase price, purchase amount, cost trends
Sales Cost	Sales cost, gross margin, cost ratio
Inventory Cost	Inventory value, holding cost, loss cost
Profit Analysis	Product profit, customer profit, regional profit

7. Technical Architecture

graph TB subgraph "yudao-module-erp-plus" subgraph "erp-biz" A1[purchase Purchase Management] A2[sale Sales Management] A3[inventory Inventory Management] A4[finance Financial Management] A5[production Production Management] A6[supplier Supplier Management] A7[cost Cost Accounting] A8[report Report Analysis] A9[analytics Business Analysis] end subgraph "Permissions & Audit" B1[permission Permission Control] B2[audit Audit Logs] B3[masking Data Masking] end end A1 --> B1 A2 --> B1 A3 --> B1 A4 --> B2 A5 --> B2 A6 --> B3 A7 --> B3

8. Business Value

Value Point	Description
Integrated Management	Purchase-sales-inventory-finance integration
Cost Reduction	Purchase optimization, cost accounting
Efficiency Improvement	Process automation, approval workflow
Data Transparency	Real-time reports, business analysis
Decision Support	Predictive analysis, optimization suggestions
Compliance Control	Multi-dimensional permissions, full-chain audit

Vue3 Admin Panel

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

Vue3 Admin Panel is RuoYi’s primary frontend solution and the frontend project with the most complete business features. If you’re unsure which frontend to choose, pick this one — pages for all 14 subsystems are first implemented here.

Tech Stack: Vue3 + TypeScript + Vite + Element Plus + Pinia

Suitable Users

User Profile	Why Choose This
Teams pursuing stability	All features are first implemented here, most thoroughly tested
Element Plus ecosystem users	Mature component library, complete documentation, active community
Need the most complete business features	All 14 subsystems have corresponding pages
Secondary development scenarios	Clear code structure, highly modular

Project Architecture

graph TB subgraph Entry MAIN["main.ts
Application Entry"] end subgraph CoreLayer["Core Layer"] ROUTER["router/
Route Configuration"] STORE["store/
Pinia State Management"] UTILS["utils/
Utility Functions"] end subgraph RequestLayer["Request Layer"] AXIOS["utils/request.ts
axios Wrapper
baseURL / timeout / Interceptors"] API["api/
APIs Organized by Module"] MOCK["mock/
Mock Data"] end subgraph ViewLayer["View Layer (Organized by Subsystem)"] SYS_V["views/system/
System Management"] BPM_V["views/bpm/
Workflow"] CRM_V["views/crm/
Customer Management"] ERP_V["views/erp/
Purchase-Sales-Inventory"] MALL_V["views/mall/
E-Commerce"] end subgraph ComponentLayer COMPS["components/
Shared Components"] DIRS["directives/
Custom Directives"] PLUGINS["plugins/
Plugins"] end MAIN --> ROUTER MAIN --> STORE ROUTER --> ViewLayer ViewLayer --> API API --> AXIOS AXIOS --> UTILS

Key Design

axios Request Wrapper

baseURL: /api
timeout: 30000ms
Interceptors:
 - Request interceptor: Auto-attach Token
 - Response interceptor: Unified error handling, Token expiration redirect to login

Page File Organization

Each business page typically contains:

views/erp/purchase/order/
 ├── index.vue # List page
 ├── form.vue # Form dialog
 └── const.ts # Constants

Permission Control

Menus and buttons are controlled via permission identifiers:

// Button permission example
<el-button v-hasPermi="['erp:purchase-order:create']">Add</el-button>

// Menus returned by backend, frontend dynamically renders based on role

Comparison with Other Frontends

Dimension	Vue3 Admin Panel	Vben5	Vue2
Positioning	Primary, most complete features	Next-gen, more advanced architecture	Classic, Vue2 compatible
UI Library	Element Plus	Ant Design / Element Plus	Element UI
Business Features	✅ Full coverage	🚧 Gradual migration	✅ Full coverage
Developer Experience	⭐⭐⭐⭐	⭐⭐⭐⭐⭐	⭐⭐⭐
Use Case	First choice for new projects	For cutting-edge tech stack	Vue2 legacy projects

Quick Start

# 1. Enter frontend directory
cd yudao-ui-admin-vue3

# 2. Install dependencies
pnpm install

# 3. Start dev server
pnpm run dev

# 4. Access
http://localhost:80

Vben5 Admin Panel

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

Vben5 is RuoYi’s next-generation admin panel, based on Vben Admin 5.x (Monorepo architecture), with more advanced architectural design. It supports both Ant Design Vue and Element Plus UI component libraries — you can freely choose based on your team’s preferences.

Tech Stack: Vue3 + TypeScript + Vite + Vben5 + Ant Design Vue / Element Plus

Suitable Users

User Profile	Why Choose This
Teams pursuing latest architecture	Monorepo + more advanced state management + stronger type constraints
Ant Design ecosystem users	Supports Ant Design Vue, more international UI style
Large project teams	Vben component system (Vxe Table / Vben Form / Vben Modal) better suited for complex forms and tables
Willing to accept feature migration status	Some business modules still being migrated from Vue3 version

Project Architecture

graph TB subgraph Monorepo["Monorepo Structure"] APPS["apps/
Application Entries"] PKGS["packages/
Shared Packages"] INTERNAL["internal/
Internal Tools"] end subgraph UI["Dual UI Library Support"] ANT["Ant Design Vue
More international style"] EP["Element Plus
More localized style"] end subgraph COMP["Vben Component System"] TABLE["Vben Vxe Table
High-Performance Table"] FORM["Vben Form
Declarative Forms"] MODAL["Vben Modal
Dialog Management"] DRAWER["Vben Drawer
Drawer Component"] end subgraph PAGES["Page Structure (Three Files Per Page)"] INDEX["index.vue
Page Entry"] FORM_V["form.vue
Form Definition"] DATA["data.ts
Data Logic"] end APPS --> UI APPS --> COMP APPS --> PAGES

Core Advantages

1. Monorepo Architecture

All packages managed in one repository, unified dependency versions, easier code reuse. Shared utility functions, type definitions, and components are placed under packages/.

2. Dual UI Library Switching

// Can choose Ant Design Vue
import { Button, Table, Form } from 'ant-design-vue';

// Or choose Element Plus
import { ElButton, ElTable, ElForm } from 'element-plus';

The same business logic can adapt to two UI styles, which is especially valuable for projects that need to be delivered to different clients.

3. Declarative Component System

Vben’s component system dramatically improves development efficiency for complex forms and tables:

<!-- Vben Vxe Table: Declarative Column Definition -->
<vxe-grid v-bind="gridOptions">
 <!-- Built-in pagination, sorting, filtering, export -->
</vxe-grid>

<!-- Vben Form: Declarative Form -->
<vben-form :schema="formSchema" />

Feature Migration Progress

Module	Status	Notes
System Management	✅ Completed	Users/Roles/Menus/Departments etc.
Infrastructure	✅ Completed	Code Generation/Files/Config etc.
BPM Workflow	✅ Completed (v2.6.1)	Ant Design version
CRM Customer Management	✅ Completed (v2.6.1)	Ant Design version
Pay Payment Center	✅ Completed (v2.6.1)	Ant Design version
Member Center	✅ Completed (v2.6.1)	Ant Design version
AI Large Model	✅ Completed (v2.6.1)	Ant Design version
ERP Purchase-Sales-Inventory	🚧 In Progress	-
Mall E-Commerce	🚧 In Progress	-

Quick Start

# 1. Enter directory
cd yudao-ui-admin-vben5

# 2. Install dependencies
pnpm install

# 3. Start dev server
pnpm run dev

# 4. Access
http://localhost:{port}

WMS Warehouse Management

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, 30 DOs / 29 Controllers, menu ID starting at 5000, building an intelligent warehousing and supply chain collaboration system

1. Enhancement Positioning and Architecture

1.1 Product Positioning

RuoYiPlus WMS provides enterprise-level enhancements around three core areas: multi-warehouse management, intelligent operations, and precise inventory control, achieving a complete warehousing management closed loop from inbound to outbound.

1.2 Module Scale

Metric	Value
Data Objects (DO)	30
Controllers	29
Menu ID Start	5000
Maven Module	yudao-module-wms

1.3 Core Data Tables

Table Name	Description
`wms_receipt`	Receiving management
`wms_shipment`	Shipping management
`wms_movement`	Inventory movement
`wms_check`	Counting management
`wms_qc`	QC management
`wms_damage`	Damage management
`wms_replenishment`	Replenishment management
`wms_inventory`	Inventory management
`wms_item`	Item management
`wms_batch`	Batch management
`wms_merchant`	Merchant management
`wms_warehouse`	Warehouse management

graph TB subgraph "RuoYiPlus WMS Enhancement Architecture" subgraph "Warehouse Layer" A1[Central Warehouse] A2[Regional Warehouse] A3[Forward Warehouse] A4[Store Warehouse] A5[Virtual Warehouse] end subgraph "Operations Layer" B1[Inbound Management] B2[Outbound Management] B3[In-Warehouse Management] B4[Counting Management] end subgraph "Strategy Layer" C1[Location Recommendation] C2[Wave Picking] C3[Inventory Alert] C4[Replenishment Suggestions] end subgraph "Execution Layer" D1[PDA Mobile Operations] D2[Task Management] D3[Operations Monitoring] end subgraph "Control Layer" E1[Warehouse Permissions] E2[Inventory Permissions] E3[Operation Audit] E4[Data Security] end end A1 --> B1 A2 --> B1 A3 --> B1 A4 --> B1 A5 --> B1 B1 --> B2 B2 --> B3 B3 --> B4 B4 --> C1 C1 --> C2 C2 --> C3 C3 --> C4 C4 --> D1 D1 --> D2 D2 --> D3 D3 --> E1 E1 --> E2 E2 --> E3 E3 --> E4

1.4 Capability Comparison

Dimension	Yudao Native Capability	RuoYiPlus WMS Enhancement
Inventory Management	Basic inventory	Multi-warehouse + fine-grained location management
Inbound Management	Simple inbound	Multi-source inbound + QC process
Outbound Management	Simple outbound	Intelligent picking + wave management
Inventory Alert	None	Multi-dimensional alerts + replenishment suggestions
Warehouse Operations	None	PDA mobile operations + task management
Data Analytics	None	Inventory turnover + operational efficiency analysis
Permission Control	Basic permissions	Warehouse-level data permissions
Audit Compliance	Simple logs	Full-chain inventory operation audit

2. Multi-Warehouse Management System

2.1 Warehouse Architecture

graph TB subgraph "Multi-Warehouse Architecture" subgraph "Physical Warehouses" A1[Central Warehouse] A2[Regional Warehouse] A3[Forward Warehouse] A4[Store Warehouse] A5[3PL Warehouse] end subgraph "Virtual Warehouses" B1[In-Transit Warehouse] B2[QC Pending Warehouse] end end A1 --> A2 A2 --> A3 A3 --> A4 A1 --> A5 A1 --> B1 A1 --> B2

Capability	Description
Warehouse Types	Central / Branch / Store / 3PL
Warehouse Attributes	Region, type, capacity, operational capability
Inventory Transfer	Inter-warehouse transfer, transfer approval
Inventory Sync	Real-time multi-warehouse inventory sync
Intelligent Allocation	Intelligent order split by warehouse for shipping

2.2 Warehouse Permission Control

The WMS system implements warehouse-based and data-scope-based permission control to ensure inventory data security.

Permission Level	Scope	Description
Warehouse Keeper	Own warehouse	Can only manage inventory and operations of their warehouse
Regional Manager	Regional warehouses	Can view all regional warehouse data
HQ Operations	All warehouses	Can view all warehouse data
Finance Staff	Inventory value	Can view inventory value but cannot modify inventory

// WMS data permission example
@DataPermission(scope = "warehouse")
public class InventoryServiceImpl {
 // Warehouse keeper can only manage their own warehouse inventory
 // Automatically filters data by warehouse
}

2.3 Inventory Operation Audit

All inventory operations record complete audit logs, supporting inventory change traceability.

graph LR A[Inbound Operation] --> B[Inventory Increase] C[Outbound Operation] --> D[Inventory Decrease] E[Transfer Operation] --> F[Inventory Movement] G[Counting Operation] --> H[Inventory Adjustment] B -.-> I[Audit Log] D -.-> I F -.-> I H -.-> I I --> J[Inventory Traceability] I --> K[Compliance Report]

Audit Item	Description
Inbound Record	Records inbound time, quantity, warehouse
Outbound Record	Records outbound time, quantity, warehouse
Transfer Record	Records transfer time, source warehouse, target warehouse
Counting Record	Records counting time, counter, discrepancy
Inventory Adjustment	Records adjustment time, reason, quantity

3. Fine-Grained Location Management

3.1 Location Management

graph TB subgraph "Location Management" subgraph "Location Encoding" A1[Warehouse] A2[Zone] A3[Shelf] A4[Level] A5[Position] end subgraph "Location Types" B1[Storage Location] B2[Picking Location] B3[Staging Location] B4[Exception Location] end subgraph "Location Status" C1[Empty] C2[Occupied] C3[Locked] C4[Disabled] end subgraph "Location Strategy" D1[Location Recommendation] D2[Location Optimization] end end A1 --> A2 A2 --> A3 A3 --> A4 A4 --> A5 A5 --> B1 B1 --> B2 B2 --> B3 B3 --> B4 B4 --> C1 C1 --> C2 C2 --> C3 C3 --> C4 C4 --> D1 D1 --> D2

wms:
 location:
 encoding: "WH-ZONE-SHELF-LEVEL-POSITION"
 types:
 - storage: "Storage Location"
 - picking: "Picking Location"
 - staging: "Staging Location"
 - exception: "Exception Location"
 recommendation:
 strategy: "frequency-based" # Recommend by turnover frequency
 hot-zone: "Zone A" # High-frequency item zone

4. Inbound and Outbound Processes

4.1 Inbound Process

graph TB subgraph "Inbound Process" subgraph "Purchase Inbound" A1[Purchase Order] A2[Receiving Appointment] A3[Receiving Registration] A4[QC Process] A5[Putaway Operation] A6[Location Recommendation] A7[Inbound Confirmation] end subgraph "Return Inbound" B1[Return Request] B2[Return Approval] B3[Return Receiving] B4[QC Process] B5[Inbound / Scrap] end subgraph "Transfer Inbound" C1[Transfer Order] C2[In-Transit Tracking] C3[Receipt Confirmation] end end A1 --> A2 A2 --> A3 A3 --> A4 A4 --> A5 A5 --> A6 A6 --> A7 B1 --> B2 B2 --> B3 B3 --> B4 B4 --> B5 C1 --> C2 C2 --> C3

4.2 Outbound Process

graph TB subgraph "Outbound Process" subgraph "Sales Outbound" A1[Order Receiving] A2[Order Validation] A3[Inventory Reservation] A4[Wave Generation] A5[Wave Assignment] A6[Picking Task] A7[Picking Operation] A8[Picking Verification] A9[Packing Operation] A10[Shipping Operation] A11[Logistics Integration] A12[Outbound Confirmation] end end A1 --> A2 A2 --> A3 A3 --> A4 A4 --> A5 A5 --> A6 A6 --> A7 A7 --> A8 A8 --> A9 A9 --> A10 A10 --> A11 A11 --> A12

5. Inventory Alert System

5.1 Alert Types

Alert Type	Trigger Condition	Response Action
Insufficient Stock	Stock < Safety stock	Generate replenishment suggestion
Overstock	Inventory turnover > 90 days	Promotion suggestion
Expiry Alert	Days to expiry < 30	Priority outbound / promotion
Location Overload	Location occupancy > 90%	Location adjustment suggestion
Abnormal Inventory	Quality issue locked	Exception handling reminder

5.2 Replenishment Suggestions

wms:
 replenishment:
 safety-stock:
 formula: "avg_daily_sales * lead_time * safety_factor"
 safety-factor: 1.5
 suggestions:
 - condition: "stock < safety_stock"
 action: "create_purchase_suggestion"
 priority: "high"
 - condition: "stock < min_stock"
 action: "urgent_purchase"
 priority: "critical"

6. Technical Architecture

graph TB subgraph "yudao-module-wms-plus" subgraph "wms-biz" A1[warehouse Warehouse Management] A2[location Location Management] A3[inventory Inventory Management] A4[inbound Inbound Management] A5[outbound Outbound Management] A6[wave Wave Management] A7[picking Picking Management] A8[task Task Management] A9[alert Alert Management] A10[replenishment Replenishment Management] A11[counting Counting Management] A12[analytics Data Analytics] end subgraph "Permissions & Audit" B1[permission Permission Control] B2[audit Audit Logs] B3[traceability Inventory Traceability] end end A1 --> B1 A2 --> B1 A3 --> B2 A4 --> B2 A5 --> B2 A6 --> B2 A7 --> B3 A8 --> B2

7. Business Value

Value Point	Description
Reduce Inventory Cost	Precise inventory, reduce overstock
Improve Operational Efficiency	Intelligent picking, mobile operations
Increase Accuracy	Scan-based operations, verification process
Optimize Locations	Location recommendation, turnover optimization
Alert Response	Timely replenishment, expiry management
Compliance Control	Warehouse permissions, inventory audit

MES Manufacturing Execution System

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, covering production planning, work order management, process routing, quality control, building a digital workshop and intelligent manufacturing execution system

1. Enhancement Positioning and Architecture

1.1 Product Positioning

RuoYiPlus MES provides enterprise-level enhancements around three core areas: intelligent scheduling, quality control, and material traceability, achieving a complete manufacturing execution closed loop from production planning to product receipt.

1.2 Module Scale

Metric	Value
Maven Module	yudao-module-mes

1.3 Core Data Tables

Table Name	Description
`mes_production_plan`	Production plan
`mes_work_order`	Work order management
`mes_process`	Process management
`mes_quality`	Quality management
`mes_equipment`	Equipment management
`mes_material`	Material management
`mes_traceability`	Traceability management

graph TB subgraph "RuoYiPlus MES Enhancement Architecture" subgraph "Planning Layer" A1[MPS Master Production Schedule] A2[MRP Material Requirements Planning] A3[APS Advanced Planning & Scheduling] end subgraph "Execution Layer" B1[Work Order Management] B2[Process Routing] B3[Material Management] B4[Personnel Management] end subgraph "Control Layer" C1[Quality Management] C2[Equipment Management] C3[Data Collection] C4[Real-Time Monitoring] end subgraph "Traceability Layer" D1[Material Traceability] D2[Quality Traceability] D3[Production Traceability] end subgraph "Compliance Layer" E1[Operation Permissions] E2[Production Audit] E3[Quality Audit] E4[Data Encryption] end end A1 --> A2 A2 --> A3 A3 --> B1 B1 --> B2 B2 --> B3 B3 --> B4 B4 --> C1 C1 --> C2 C2 --> C3 C3 --> C4 C4 --> D1 D1 --> D2 D2 --> D3 D3 --> E1 E1 --> E2 E2 --> E3 E3 --> E4

1.4 Capability Comparison

Dimension	Traditional MES	RuoYiPlus MES Enhancement
Production Planning	Manual scheduling	Intelligent scheduling + APS integration
Production Execution	Paper-based routing	Electronic work orders + process routing
Quality Management	Offline inspection	Online inspection + SPC analysis
Equipment Management	Equipment ledger	Equipment monitoring + predictive maintenance
Material Management	Manual material picking	Intelligent batching + material traceability
Data Collection	Manual entry	Automatic collection + real-time monitoring
Permission Control	Basic permissions	Workshop-level permission control
Audit Compliance	Simple logs	Full-chain production audit

2. Production Planning and Scheduling

2.1 Production Planning System

graph TB subgraph "Production Planning" subgraph "Demand Sources" A1[Sales Orders] A2[Forecast Orders] A3[Outsourcing Orders] end subgraph "Plan Decomposition" B1[MPS Master Production Schedule] B2[MRP Material Requirements Plan] B3[Procurement Plan] B4[Production Plan] B5[Workshop Job Plan] end subgraph "Intelligent Scheduling" C1[APS Scheduling Algorithm] C2[Capacity Balancing] C3[Equipment Assignment] C4[Personnel Assignment] end subgraph "Plan Execution" D1[Work Order Release] D2[Execution Tracking] D3[Progress Feedback] end end A1 --> B1 A2 --> B1 A3 --> B1 B1 --> B2 B2 --> B3 B2 --> B4 B4 --> B5 B5 --> C1 C1 --> C2 C2 --> C3 C3 --> C4 C4 --> D1 D1 --> D2 D2 --> D3

2.2 Production Permission Control

The MES system implements workshop and process-based permission control to ensure production data security.

Permission Level	Scope	Description
Operator	Own process	Can only view and operate their own process tasks
Team Leader	Own team	Can view all production tasks of their team
Workshop Director	Own workshop	Can view all production data of their workshop
Production Manager	All workshops	Can view all workshop production data

// MES data permission example
@DataPermission(scope = "workshop")
public class WorkOrderServiceImpl {
 // Workshop director can view their own workshop work orders
 // Automatically filters data by workshop
}

2.3 Production Operation Audit

All production operations record complete audit logs, supporting production process traceability.

Audit Item	Description
Work Order Creation	Records creator, creation time
Work Order Release	Records release time, recipient
Process Start	Records start time, operator
Process Completion	Records completion time, completed quantity
QC Record	Records inspection time, inspection result
Material Withdrawal	Records withdrawal time, withdrawal quantity

3. Production Execution Management

3.1 Production Execution Process

graph TB subgraph "Production Execution" subgraph "Work Order Management" A1[Work Order Creation] A2[Work Order Approval] A3[Work Order Release] A4[Work Order Start] A5[Work Order Completion] A6[Work Order Close] end subgraph "Process Routing" B1[Process Start] B2[Process Operation] B3[Process QC] B4[Process Completion] B5[Process Transfer] end subgraph "Material Management" C1[Material Withdrawal] C2[Material Consumption] C3[Excess Material Return] C4[Material Traceability] end subgraph "Personnel Management" D1[Personnel Dispatch] D2[Operation Record] D3[Piece-Rate Statistics] end end A1 --> A2 A2 --> A3 A3 --> A4 A4 --> A5 A5 --> A6 B1 --> B2 B2 --> B3 B3 --> B4 B4 --> B5 C1 --> C2 C2 --> C3 C3 --> C4 D1 --> D2 D2 --> D3

3.2 Electronic Work Orders

Capability	Description
Electronic Work Orders	Digitized work orders, scan to start
Process Routing	Process status tracking, routing records
Completion Reporting	Completed quantity, good/defective products
Exception Handling	Exception reporting, exception resolution
Progress Tracking	Real-time progress, estimated completion

4. Quality Management Enhancement

4.1 Quality Management System

graph TB subgraph "Quality Management" subgraph "QC Configuration" A1[QC Standards] A2[QC Items] A3[QC Methods] A4[QC Frequency] end subgraph "QC Execution" B1[Incoming QC] B2[First Article QC] B3[In-Process QC] B4[Final QC] B5[Outgoing QC] end subgraph "Quality Analysis" C1[Defect Statistics] C2[Root Cause Analysis] C3[Corrective Actions] C4[SPC Analysis] end subgraph "Quality Traceability" D1[Batch Traceability] D2[Process Traceability] D3[Personnel Traceability] end end A1 --> B1 A2 --> B1 A3 --> B1 A4 --> B1 B1 --> B2 B2 --> B3 B3 --> B4 B4 --> B5 B5 --> C1 C1 --> C2 C2 --> C3 C3 --> C4 C4 --> D1 D1 --> D2 D2 --> D3

4.2 Quality Audit

All QC operations record complete audit logs, supporting quality data traceability.

Audit Item	Description
QC Record	Records inspection time, inspector, inspection result
Defect Record	Records defect type, defect cause
Corrective Action	Records corrective action, execution result
SPC Data	Records SPC analysis data

5. Material Traceability

5.1 Traceability System

graph TB subgraph "Material Traceability" subgraph "Raw Material Traceability" A1[Supplier] A2[Receipt Batch] A3[QC Result] A4[Storage Location] A5[Withdrawal Record] end subgraph "Production Traceability" B1[Production Work Order] B2[Process Routing] B3[Consumption Record] B4[Operator] B5[Equipment Info] B6[QC Record] end subgraph "Product Traceability" C1[Finished Batch] C2[Receipt Record] C3[Shipping Record] C4[Customer Order] C5[Delivery Record] end end A1 --> A2 A2 --> A3 A3 --> A4 A4 --> A5 A5 --> B1 B1 --> B2 B2 --> B3 B3 --> B4 B4 --> B5 B5 --> B6 B6 --> C1 C1 --> C2 C2 --> C3 C3 --> C4 C4 --> C5

5.2 Traceability Query

Query Direction	Description
Forward Traceability	Raw material → Finished product → Customer
Reverse Traceability	Customer → Finished product → Raw material
Horizontal Traceability	Same batch product distribution

6. Technical Architecture

graph TB subgraph "yudao-module-mes-plus" subgraph "mes-biz" A1[plan Production Planning] A2[scheduling Intelligent Scheduling] A3[workorder Work Order Management] A4[process Process Management] A5[quality Quality Management] A6[equipment Equipment Management] A7[material Material Management] A8[traceability Traceability Management] A9[collection Data Collection] A10[monitor Real-Time Monitoring] A11[report Report Analysis] end subgraph "Permissions & Audit" B1[permission Permission Control] B2[audit Audit Logs] B3[traceability Traceability Audit] end end A1 --> B1 A2 --> B1 A3 --> B2 A4 --> B2 A5 --> B3 A6 --> B2 A7 --> B3

7. Business Value

Value Point	Description
Increase Production Efficiency	Intelligent scheduling, process optimization
Improve Product Quality	Online inspection, SPC control
Reduce Equipment Failure	Predictive maintenance, OEE optimization
Achieve Traceability Compliance	Full-chain traceability, batch management
Data-Driven Decisions	Real-time monitoring, analysis reports
Production Traceability	Full-chain audit, quality traceability

SaaS Multi-Tenancy

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

SaaS Multi-Tenancy allows you to serve multiple enterprise clients with a single codebase, where each client (tenant) can only see their own data, completely isolated from each other. Whether building a vertical SaaS product or managing multiple subsidiaries within an enterprise, this is an indispensable capability.

Two approaches: Column-based isolation (lightweight, suitable for small-to-medium scale) and database isolation (physical isolation, suitable for large-scale SaaS).

Suitable Users

Scenario	Recommended Approach	Reason
SaaS Startup Phase	Column-based isolation	Simple operations, one database handles everything
Large SaaS Platform	Database isolation	Physical isolation, high security, independent backups
Enterprise Multi-Company	Column-based isolation	Limited number of companies, logical isolation is sufficient
Finance/Healthcare Compliance	Database isolation	Data must be physically isolated

Two Approaches Comparison

graph TB subgraph COLUMN["Approach 1: Column-Based Isolation (COLUMN Mode)"] direction TB C1["All tenants share
same database, same tables"] C2["Each table adds
tenant_id column"] C3["SQL Interceptor
auto-appends WHERE tenant_id = ?"] C4["Pros: Simple operations, high resource utilization
Cons: Logical isolation, moderate security"] C1 --> C2 --> C3 --> C4 end subgraph DATASOURCE["Approach 2: Database Isolation (DATASOURCE Mode)"] direction TB D1["Master DB: Shared tables
Users/Menus/Config/Tenant info"] D2["Tenant DB A: Business tables"] D3["Tenant DB B: Business tables"] D4["Tenant DB C: Business tables"] D5["Pros: Physical isolation, high security, independent backups
Cons: Complex operations, lower resource utilization"] D1 --> D2 D1 --> D3 D1 --> D4 D2 & D3 & D4 --> D5 end

Detailed Comparison

Dimension	Column-Based (COLUMN)	Database Isolation (DATASOURCE)
Isolation Level	Logical isolation	Physical isolation
Security	Medium (relies on SQL interceptor)	High (database-level isolation)
Resource Utilization	High (shared connection pool)	Low (independent connections per tenant)
Operations Complexity	Low (single DB operations)	High (multi-DB operations)
Scalability	Limited by single DB performance	Horizontally scalable
Data Backup	Need to filter by tenant_id	Independent backup per tenant
Applicable Scale	Hundreds of tenants	Thousands/Tens of thousands of tenants
Technical Implementation	MyBatis Plus interceptor	dynamic-datasource

Column-Based Isolation Implementation

sequenceDiagram participant U as User (Tenant A) participant APP as Application Layer participant INTERCEPTOR as SQL Interceptor participant DB as Shared Database U->>APP: Query customer list APP->>INTERCEPTOR: SELECT * FROM crm_customer INTERCEPTOR->>INTERCEPTOR: Auto-append tenant_id = 'A' INTERCEPTOR->>DB: SELECT * FROM crm_customer
WHERE tenant_id = 'A' DB-->>APP: Returns only Tenant A's data APP-->>U: Display customer list

Core Mechanism: Through MyBatis Plus’s multi-tenant plugin, automatically adds tenant_id condition before executing any SQL, completely transparent to business code.

Database Isolation Implementation

Based on dynamic-datasource dynamic data sources, when a request comes in, it switches to the corresponding data source based on the current tenant ID:

spring:
 datasource:
 dynamic:
 primary: master  # Master DB (shared tables)
 datasource:
 master: # Master DB config
 url: jdbc:mysql://localhost:3306/ruoyi_master
 tenant_1: # Tenant 1's independent database
 url: jdbc:mysql://localhost:3306/ruoyi_tenant_1
 tenant_2: # Tenant 2's independent database
 url: jdbc:mysql://localhost:3306/ruoyi_tenant_2

Tenant Package Management

graph LR PACKAGE1["Basic Package
System Management + Basic Features"] PACKAGE2["Professional Package
Basic + CRM + ERP"] PACKAGE3["Enterprise Package
All Features"] TenantA["Tenant A"] --> PACKAGE1 TenantB["Tenant B"] --> PACKAGE2 TenantC["Tenant C"] --> PACKAGE3

Each tenant can be bound to a package, which defines the menus and features visible to that tenant. Supports automatic disabling upon package expiration.

Code Generation Advanced

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

The code generator is RuoYi’s “nuclear weapon” for development efficiency. Regular single-table CRUD can no longer satisfy complex business scenarios. Here we introduce three advanced generation modes, covering the most common complex page patterns in enterprise development.

With these capabilities, a complex business page containing master-child tables and approval flows goes from “days of coding” to “minutes of configuration.”

Suitable Users

Scenario	Recommended Mode	Effect
Order + Line Items	Master-Child Standard Mode	Same dialog, master-child tables edited together
Work Order + Processes	Master-Child Embedded Mode	Expand child table directly in list
Purchase Order + Details	Master-Child ERP Mode	Independent master and child lists, independent forms
Department Tree/Category Tree	Tree Table Mode	Auto-generate tree table
Mobile Pages	uni-app Mode	Generate pages compatible with H5/Mini Programs

Three Master-Child Table Generation Modes

graph TB subgraph StandardMode["Mode 1: Standard Mode"] S1["Master Table List Page"] S2["Click Add → Dialog"] S3["Dialog: Master Form + Child Table
Edit in same dialog"] S1 --> S2 --> S3 end subgraph EmbeddedMode["Mode 2: Embedded Mode"] I1["Master Table List Page"] I2["Expand Row → Embedded Child Table
Child table shown directly below master row"] I1 --> I2 end subgraph ERPMode["Mode 3: ERP Mode"] E1["Master Table Independent List"] E2["Child Table Independent List
(Linked by master table ID)"] E3["Master Table Independent Form"] E4["Child Table Independent Form"] E1 --> E2 E3 --> E4 end

Mode Applicable Scenarios

Mode	Use Case	User Experience	Representative Business
Standard Mode	Small master-child data volume, master+child need to be filled together	⭐⭐⭐⭐ Smooth operation	Surveys+Questions, Config+Config Items
Embedded Mode	Need to quickly view child data without navigating away	⭐⭐⭐⭐⭐ High info density	Work Orders+Processes, Tasks+Subtasks
ERP Mode	Master and child each have independent business logic, large data volume	⭐⭐⭐ High flexibility	Purchase Orders+Details, Sales Orders+Details

Tree Table Code Generation

graph LR DEPT["Department Table
id / parent_id / name"] GEN["Code Generator
Recognizes parent_id field"] OUT["Generate Tree Table Page
el-tree + Drag & Drop Sorting"] DEPT --> GEN --> OUT

Supports unlimited levels, auto-generates expand/collapse, drag-and-drop sorting, add child node, and other features.

uni-app Code Generation

Generate complete page code for mobile, supporting:

List pages (pull-to-refresh, load more)
Form pages
Detail pages
API request encapsulation

Frontend Version Support

Generation Target	Vue3 Admin	Vben5	Vue2	uni-app
Single Table CRUD	✅	✅	✅	✅
Master-Child Standard	✅	✅	✅	❌
Master-Child Embedded	✅	✅	✅	❌
Master-Child ERP	✅	✅	✅	❌
Tree Table	✅	✅	✅	❌

Usage Process

Create table structure in the database
Import tables in the “Code Generation” menu
Configure generation options (module name, business name, class name, generation mode)
Preview and generate code
Copy code to the project, configure menu to use

PM Project Management

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, 16 DOs / 15 Controllers, menu ID starting at 2500, building a digital project management and team collaboration system

1. Enhancement Positioning and Architecture

1.1 Product Positioning

RuoYiPlus PM centers around three core pillars—Full Project Lifecycle Management, Multi-Project Collaborative Scheduling, and Project Permission and Audit—to deliver enterprise-level enhancement, achieving a complete project management loop from initiation to closure.

1.2 Module Scale

Metric	Value
Data Objects (DO)	16
Controllers	15
Menu ID Start	2500
Maven Module	yudao-module-pm

1.3 Core Data Tables

Table Name	Description
`pm_project`	Project Management
`pm_task`	Task Management
`pm_warning`	Alert Management
`pm_cost`	Cost Management
`pm_affiliated`	Sub-Project Management
`pm_track_project`	Project Tracking
`pm_label`	Label Management
`pm_project_member`	Project Members

graph TB subgraph "RuoYiPlus PM Enhanced Architecture" subgraph "Project Layer" A1[Project Initiation] A2[Project Planning] A3[Project Execution] A4[Project Monitoring] A5[Project Closure] end subgraph "Capability Layer" B1[WBS Work Breakdown] B2[Gantt Chart] B3[Milestone Management] B4[Resource Scheduling] B5[Risk Management] end subgraph "Collaboration Layer" C1[Task Collaboration] C2[Timesheet Management] C3[Document Management] C4[Communication Collaboration] end subgraph "Control Layer" D1[Project Permissions] D2[Data Isolation] D3[Operation Audit] D4[Compliance Reports] end end A1 --> A2 A2 --> A3 A3 --> A4 A4 --> A5 A5 --> B1 B1 --> B2 B2 --> B3 B3 --> B4 B4 --> B5 B5 --> C1 C1 --> C2 C2 --> C3 C3 --> C4 C4 --> D1 D1 --> D2 D2 --> D3 D3 --> D4

1.4 Capability Comparison

Dimension	Yudao Native Capability	RuoYiPlus PM Enhanced
Project Management	Basic project information	Full lifecycle management
Task Management	Simple tasks	WBS decomposition + dependency relationships
Progress Control	None	Gantt chart + milestones + critical path
Resource Management	None	Resource scheduling + timesheet management
Risk Management	None	Risk identification + response strategies
Data Analysis	None	Project health score + efficiency analysis
Permission Control	Basic permissions	Project-level data permissions
Audit Compliance	Simple logs	Full-chain project audit

2. Full Project Lifecycle Management

2.1 Lifecycle Phases

graph LR A[Initiation Phase] --> B[Planning Phase] B --> C[Execution Phase] C --> D[Monitoring Phase] D --> E[Closure Phase] A --> A1[Requirements Analysis] A --> A2[Feasibility Assessment] A --> A3[Project Initiation Approval] B --> B1[WBS Decomposition] B --> B2[Schedule Planning] B --> B3[Resource Planning] B --> B4[Risk Planning] C --> C1[Task Assignment] C --> C2[Task Execution] C --> C3[Timesheet Reporting] C --> C4[Progress Reporting] D --> D1[Progress Monitoring] D --> D2[Deviation Analysis] D --> D3[Change Management] D --> D4[Risk Alert] E --> E1[Acceptance Review] E --> E2[Lessons Learned] E --> E3[Project Archiving]

2.2 Project Data Permissions

The PM system implements data permission control based on projects and roles, ensuring strict isolation of project data by organizational structure.

Permission Level	Scope	Description
Project Member	Participating projects	Can only view and participate in assigned projects
Project Manager	Responsible projects	Can manage all project data, including task assignment and progress adjustment
Department Manager	Department projects	Can view progress and resources of all department projects
PMO	All projects	Can view all project data and perform portfolio analysis

// PM Data Permission Example
@DataPermission(scope = "project")
public class ProjectServiceImpl {
 // Project managers can manage all data of their projects
 // Automatically filter tasks, timesheets, documents by project
}

// Project Member Permission
@DataPermission(roles = {"project_member"})
public class TaskServiceImpl {
 // Project members can only view their own tasks
 // Automatically filter by task assignee
}

2.3 Project Operation Audit

All key project operations record complete audit logs, supporting project process traceability.

graph TB subgraph "Audit Event Collection" A1[Project Initiation] A2[Plan Change] A3[Task Assignment] A4[Progress Adjustment] A5[Milestone Change] A6[Project Closure] end subgraph "Audit Processing" B1[Change Comparison] B2[Risk Scoring] B3[Rule Matching] end subgraph "Audit Storage" C1[Operation Logs] C2[Change History] C3[Blockchain Notarization] end A1 --> B1 A2 --> B1 A3 --> B1 A4 --> B1 A5 --> B1 A6 --> B1 B1 --> B2 B2 --> B3 B3 --> C1 B3 --> C2 B3 --> C3

Audit Item	Description	Retention Period
Project Initiation	Records initiator, initiation time, project objectives	Permanent
Plan Change	Records before/after comparison, change reason	Project lifecycle + 3 years
Task Assignment	Records assigner, assignee, assignment time	Project lifecycle + 3 years
Progress Adjustment	Records before/after duration, adjustment reason	Project lifecycle + 3 years
Milestone Change	Records change content, approver	Permanent
Project Closure	Records closure time, acceptance results	Permanent

3. WBS Work Breakdown and Task Management

3.1 WBS Breakdown Structure

graph TB subgraph "WBS Work Breakdown" A[Project] --> B[Phase 1] A --> C[Phase 2] A --> D[Phase 3] B --> B1[Task 1.1] B --> B2[Task 1.2] B --> B3[Task 1.3] C --> C1[Task 2.1] C --> C2[Task 2.2] D --> D1[Task 3.1] D --> D2[Task 3.2] D --> D3[Task 3.3] B1 --> B1a[Sub-task 1.1.1] B1 --> B1b[Sub-task 1.1.2] end

3.2 Task Management

Capability	Description
Task Creation	Task definition, priority, duration estimation
Task Assignment	Intelligent assignment by skill/load
Task Dependencies	FS/FF/SS/SF dependency relationships
Sub-tasks	Multi-level sub-task decomposition
Task Board	Kanban view, list view
Task Reminders	Due reminders, overdue alerts

3.3 Task Status Flow

graph LR A[To Do] --> B[In Progress] B --> C[Pending Acceptance] C --> D[Completed] B --> E[Blocked] E --> B C --> F[Acceptance Failed] F --> B D --> G[Closed]

4. Progress Control

4.1 Gantt Chart

gantt title Project Progress Gantt Chart Example dateFormat YYYY-MM-DD section Requirements Phase Requirements Analysis :a1, 2024-01-01, 15d Requirements Review :a2, after a1, 5d section Design Phase High-Level Design :b1, after a2, 10d Detailed Design :b2, after b1, 15d Design Review :b3, after b2, 5d section Development Phase Coding :c1, after b3, 30d Unit Testing :c2, after c1, 10d section Testing Phase Integration Testing :d1, after c2, 15d Acceptance Testing :d2, after d1, 10d section Go-Live Phase Deployment :e1, after d2, 5d

4.2 Milestone Management

graph LR A[Milestone 1: Requirements Confirmed] --> B[Milestone 2: Design Complete] B --> C[Milestone 3: Development Complete] C --> D[Milestone 4: Testing Passed] D --> E[Milestone 5: Official Launch] A -.-> A1[Plan: 01-20] B -.-> B1[Plan: 02-15] C -.-> C1[Plan: 03-30] D -.-> D1[Plan: 04-20] E -.-> E1[Plan: 05-01]

Capability	Description
Milestone Setting	Key node definition and marking
Progress Tracking	Real-time milestone completion tracking
Deviation Alert	Automatic alert for milestone delays
Change Management	Milestone changes require approval workflow

4.3 Critical Path Analysis

graph TB A[Task A: 10d] --> C[Task C: 15d] C --> E[Task E: 10d] A --> D[Task D: 5d] D --> F[Task F: 8d] F --> E B[Task B: 20d] --> E style A fill:none style C fill:none style E fill:none style B fill:none

Critical path: B -> E = 30 days (minimum project duration)

5. Resource and Timesheet Management

5.1 Resource Scheduling

graph TB subgraph "Resource Scheduling" A[Resource Demand] --> B{Resource Matching} B --> C[Skill Matching] B --> D[Load Assessment] B --> E[Availability Check] C --> F[Resource Allocation] D --> F E --> F F --> G[Conflict Detection] G --> H{Conflict?} H -->|Yes| I[Resource Coordination] H -->|No| J[Confirm Allocation] I --> J end

5.2 Timesheet Management

Capability	Description
Timesheet Reporting	Report daily hours by task
Timesheet Approval	Timesheet approval workflow
Timesheet Statistics	Individual/team/project timesheet statistics
Timesheet Analysis	Utilization rate, overtime analysis
Cost Accounting	Labor cost accounting based on timesheets

pm:
 timesheet:
 rules:
 daily-max: 24h  # Maximum daily hours
 weekly-max: 60h  # Maximum weekly hours
 approval-required: true # Approval required
 overtime-threshold: 8h  # Overtime threshold
 cost:
 hourly-rate: 200 # Default hourly rate
 overtime-multiplier: 1.5 # Overtime multiplier

6. Risk Management

6.1 Risk Management Process

graph TB subgraph "Risk Management" A[Risk Identification] --> B[Risk Assessment] B --> C[Risk Classification] C --> D[Response Strategy] D --> E[Risk Monitoring] E --> F{Risk Occurred?} F -->|Yes| G[Emergency Response] F -->|No| E G --> H[Risk Closure] end

6.2 Risk Classification

Risk Level	Impact	Occurrence Probability	Response Requirement
Critical Risk	Project halted	High probability	Immediate response plan
High Risk	Severe delay	Relatively high probability	Response plan within 3 days
Medium Risk	Partial impact	Medium probability	Preventive measures within 1 week
Low Risk	Minor impact	Low probability	Continuous monitoring

7. Project Data Analysis

7.1 Project Health Score

graph TB subgraph "Project Health Assessment" A[Schedule Deviation] --> E[Health Score] B[Cost Deviation] --> E C[Quality Metrics] --> E D[Risk Status] --> E E --> F{Health Level} F -->|>=90| G[Green - Healthy] F -->|70-89| H[Yellow - Attention] F -->|<70| I[Red - Alert] end

7.2 Analysis Dimensions

Analysis Dimension	Metrics
Progress Analysis	Planned completion rate, milestone achievement rate, schedule deviation rate
Resource Analysis	Resource utilization rate, timesheet distribution, load balance
Cost Analysis	Budget execution rate, labor cost, deviation analysis
Quality Analysis	Defect density, rework rate, acceptance pass rate
Efficiency Analysis	Task completion efficiency, team collaboration efficiency

8. Multi-Project Management (PMO)

8.1 PMO View

graph TB subgraph "PMO Multi-Project Management" subgraph "Project Portfolio" A1[Strategic Project A] A2[Strategic Project B] A3[Regular Project C] A4[Regular Project D] end subgraph "Resource Pool" B1[Development Resource Pool] B2[Testing Resource Pool] B3[Design Resource Pool] end subgraph "PMO Control" C1[Project Priority] C2[Resource Coordination] C3[Portfolio Analysis] C4[Health Monitoring] end end A1 --> C1 A2 --> C1 A3 --> C2 A4 --> C2 C1 --> C3 C2 --> C3 C3 --> C4

8.2 PMO Permissions

Permission Level	Scope	Description
PMO Director	All projects	Can view all project data and adjust project priorities
PMO Specialist	Designated project portfolio	Can view designated portfolio data
Resource Manager	Resource pool	Can manage resource allocation but cannot view project business data

9. Technical Architecture

graph TB subgraph "yudao-module-pm-plus" subgraph "pm-biz" A1[project - Project Management] A2[wbs - WBS Decomposition] A3[task - Task Management] A4[schedule - Schedule Management] A5[milestone - Milestone Management] A6[resource - Resource Management] A7[timesheet - Timesheet Management] A8[risk - Risk Management] A9[document - Document Management] A10[analytics - Data Analysis] end subgraph "Permissions and Audit" B1[permission - Permission Control] B2[audit - Audit Logs] B3[compliance - Compliance Reports] end end A1 --> B1 A2 --> B1 A3 --> B2 A4 --> B2 A5 --> B2 A6 --> B1 A7 --> B2 A8 --> B3

10. Business Value

Value Point	Description
Progress Control	Gantt chart, milestones, critical path analysis
Resource Optimization	Intelligent scheduling, load balancing, timesheet management
Risk Pre-Control	Risk identification, alert mechanism, emergency response
Efficient Collaboration	Task collaboration, document sharing, communication collaboration
Data-Driven	Project health score, efficiency analysis, decision support
Compliance and Traceability	Project-level permissions, full-chain audit, change traceability

BPM Workflow

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

BPM Workflow is the enterprise’s “approval hub” — leave requests, reimbursements, procurement, contracts, seal usage… almost any scenario requiring “multi-level approval” can be modeled and processed here. Based on the Flowable engine, it provides DingTalk/Feishu-style and BPMN dual designers, allowing non-technical personnel to design processes as well.

In one sentence: Say goodbye to WeChat approvals, email approvals, and paper approvals — turn approval processes into structured, traceable systems.

Problems Solved

Pain Point	How BPM Solves It
Approval processes rely on verbal/WeChat communication, no records	All approvals leave traces, every step is traceable
Approval rules rely on human memory, prone to omissions	Process templates solidify rules, auto-route to correct approvers
Cross-department approval communication costs are high	Auto-routing, no manual notifications needed
Overdue approvals with no follow-up	Auto-reminders for overdue items, supports auto-approval/skip
Organizational changes cause approver changes	Approvers dynamically calculated by role/department, not hardcoded to specific people

User Roles

graph LR subgraph Roles ADMIN["Process Administrator
Design process templates
Deploy and publish processes"] APPLICANT["Initiator
Submit applications
View approval progress
Cancel applications"] APPROVER["Approver
Approve/Reject/Transfer/Add-sign
View pending/completed tasks"] COPYER["CC Recipient
Receive approval result notifications
No action required"] end

Feature Collaboration Flow

sequenceDiagram participant A as Initiator participant F as Process Engine participant P1 as Approver 1 (Dept Manager) participant P2 as Approver 2 (Finance Manager) participant B as Business System (e.g. ERP) A->>F: Initiate Process (e.g. Purchase Request) F->>B: Link Business Data (Purchase Order ID) F->>P1: Push Pending Task P1->>F: Approve F->>P2: Push Pending Task P2->>F: Approve F->>B: Callback: Process Complete, Update Business Status F->>A: Notification: Application Approved Note over F: If any approver rejects
process returns to initiator

Dual Designer Comparison

graph TB subgraph SIMPLE["SIMPLE Designer (DingTalk/Feishu Style)"] S1["Drag-and-drop operation"] S2["Suitable for simple approval chains"] S3["Low learning curve"] S4["Usable by non-technical staff"] end subgraph BPMN["BPMN Designer"] B1["Standard BPMN 2.0"] B2["Supports complex branches/parallel flows"] B3["Requires some learning"] B4["For technical staff"] end SIMPLE -.->|Complex scenarios can upgrade to| BPMN

Feature	SIMPLE Designer	BPMN Designer
Learning Curve	⭐ Very Low	⭐⭐⭐ Medium
Target Users	Business staff, HR, Admin	Developers, Process Experts
Supported Nodes	Approval, CC, Conditional Branch	All BPMN 2.0 Nodes
Parallel Branch	❌	✅
Inclusive Branch	❌	✅
Sub-process	❌	✅

Full Approval Operations

Process Control Capabilities

Control Type	Description	Typical Scenario
Conditional Branch	Route to different approval paths based on form data	Amount < 5000 skips CEO approval
Parallel Branch	Multiple people approve simultaneously, proceed only when all approve	Multi-department parallel countersign
Inclusive Branch	Multiple people approve simultaneously, proceed when any approves	Or-sign scenario
Trigger Node	Auto-execute service tasks	Auto-create ERP document after approval
Delay Node	Wait specified time before continuing	Remind 7 days before contract expiration
Timeout Approval	Auto-process on timeout	Auto-approve/reject if not processed within 48 hours
Auto Reminder	Scheduled reminder for pending tasks	Push pending task summary every morning at 9

Integration with Business Systems

graph TB BPM["BPM Process Engine"] subgraph Integration Scenarios ERP_APPROVAL["ERP Purchase Approval
Purchase Order → BPM Approval → Auto Inbound"] CRM_APPROVAL["CRM Contract Approval
Contract Draft → BPM Approval → Contract Effective"] OA_APPROVAL["OA General Approval
Leave/Reimbursement/Seal Usage/Out of Office"] end BPM --> ERP_APPROVAL BPM --> CRM_APPROVAL BPM --> OA_APPROVAL

Integration Method: Business modules initiate processes, query approval status, and handle approval callbacks through APIs provided by BPM, without needing to concern themselves with Flowable’s underlying details.

IOT Internet of Things Platform

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, covering device management, device grouping, alert configuration and alert records, building a device connectivity, data collection and intelligent operations system

1. Enhancement Positioning and Architecture

1.1 Product Positioning

RuoYiPlus IOT centers around three core pillars—Multi-Protocol Device Access, Real-Time Data Processing, and Device Security Control—to deliver enterprise-level enhancement, achieving a complete IoT solution from device access to intelligent operations.

1.2 Module Scale

Metric	Value
Maven Module	yudao-module-iot

1.3 Core Data Tables

Table Name	Description
`iot_device`	Device Management
`iot_device_group`	Device Grouping
`iot_alert_config`	Alert Configuration
`iot_alert_record`	Alert Records

graph TB subgraph "RuoYiPlus IOT Enhanced Architecture" subgraph "Device Access Layer" A1[MQTT Protocol] A2[CoAP Protocol] A3[HTTP/HTTPS] A4[Modbus] A5[OPC-UA] A6[LoRaWAN] end subgraph "Gateway Layer" B1[Edge Gateway] B2[Protocol Gateway] B3[Security Gateway] end subgraph "Platform Layer" C1[Device Management] C2[Data Collection] C3[Rule Engine] C4[Alert Management] end subgraph "Application Layer" D1[Real-Time Monitoring] D2[Predictive Maintenance] D3[Data Analysis] end subgraph "Security Layer" E1[Device Authentication] E2[Permission Control] E3[Operation Audit] E4[Data Encryption] end end A1 --> B1 A2 --> B1 A3 --> B1 A4 --> B2 A5 --> B2 A6 --> B2 B1 --> C1 B2 --> C1 B3 --> C1 C1 --> C2 C2 --> C3 C3 --> C4 C4 --> D1 D1 --> D2 D2 --> D3 C1 --> E1 C2 --> E2 C3 --> E3 C4 --> E4

1.4 Capability Comparison

Dimension	Traditional Solution	RuoYiPlus IOT Enhanced
Device Access	Single protocol access	Multi-protocol multi-gateway access
Data Collection	Manual collection	Automatic collection with real-time reporting
Data Processing	Simple storage	Stream processing + rule engine
Device Management	Device ledger	Device lifecycle management
Operations Monitoring	Offline monitoring	Real-time monitoring + predictive maintenance
Data Analysis	Historical query	Real-time analysis + AI prediction
Permission Control	Basic permissions	Device-level permission control
Audit Compliance	Simple logs	Full-chain device operation audit

2. Multi-Protocol Device Access

2.1 Protocol Adaptation Architecture

graph TB subgraph "Protocol Adaptation Layer" subgraph "IoT Standard Protocols" A1[MQTT] A2[CoAP] end subgraph "General Protocols" B1[HTTP/HTTPS] B2[TCP/UDP] end subgraph "Industrial Protocols" C1[Modbus] C2[OPC-UA] end subgraph "Low-Power Protocols" D1[LoRaWAN] end end subgraph "Gateway Layer" E1[Edge Gateway] E2[Protocol Gateway] E3[Security Gateway] end subgraph "Platform Layer" F1[Device Registration] F2[Device Authentication] F3[Connection Management] F4[Data Reporting] end A1 --> E1 A2 --> E1 B1 --> E2 B2 --> E2 C1 --> E2 C2 --> E2 D1 --> E3 E1 --> F1 E2 --> F1 E3 --> F1 F1 --> F2 F2 --> F3 F3 --> F4

Protocol Type	Use Case	Characteristics
MQTT	IoT standard	Lightweight, publish/subscribe
CoAP	Resource-constrained devices	UDP, low power
HTTP	General access	RESTful, easy integration
Modbus	Industrial devices	PLC, sensors
OPC-UA	Industrial automation	MES/SCADA integration
LoRaWAN	Wide-area IoT	Low power, long range

3. Device Lifecycle Management

3.1 Device Lifecycle

graph LR A[Device Registration] --> B[Device Authentication] B --> C[Device Activation] C --> D[Device Operation] D --> E[Device Maintenance] E --> F[Device Decommissioning] A --> A1[Device Modeling] A --> A2[Device Type] A --> A3[Device Properties] B --> B1[Token Auth] B --> B2[Certificate Auth] B --> B3[Key Auth] C --> C1[Device Connection] C --> C2[Data Reporting] C --> C3[Command Issuance] D --> D1[Status Monitoring] D --> D2[Alert Management] D --> D3[Remote Maintenance] E --> E1[Device Diagnostics] E --> E2[Fault Handling] E --> E3[Firmware Upgrade] F --> F1[Device Deactivation] F --> F2[Device Deregistration] F --> F3[Data Archiving]

3.2 Device Permission Control

The IOT platform implements device-level permission control to ensure device operation security.

Permission Level	Scope	Description
Device Level	Single device	Can only operate specified devices
Device Group	Device grouping	Can operate all devices within the group
Region Level	Regional devices	Can operate all devices within the region
Global Level	All devices	Can operate all devices

// Device Permission Example
@DataPermission(scope = "device_group")
public class DeviceServiceImpl {
 // Device group admins can only operate devices within their group
 // Automatically filter by device group
}

3.3 Device Operation Audit

All device operations record complete audit logs, supporting device operation traceability.

graph TB subgraph "Device Audit" A[Device Operation] --> B[Operation Record] B --> C[Command Issuance] B --> D[Configuration Update] B --> E[Firmware Upgrade] B --> F[Data Query] C --> G[Audit Log] D --> G E --> G F --> G G --> H[Operation Traceability] G --> I[Compliance Reports] end

Audit Item	Description
Device Registration	Records device registration info, registration time
Device Authentication	Records authentication method, authentication result
Command Issuance	Records command content, issuance time, execution result
Configuration Update	Records configuration changes, before/after comparison
Firmware Upgrade	Records upgrade version, upgrade time, upgrade result

4. Data Collection and Processing

4.1 Data Processing Flow

graph TB subgraph "Data Processing" subgraph "Data Collection" A1[Device Reporting] A2[Data Parsing] A3[Format Conversion] A4[Data Validation] A5[Data Cleansing] end subgraph "Data Processing" B1[Stream Processing] B2[Real-Time Computing] B3[Rule Engine] B4[Data Aggregation] end subgraph "Data Storage" C1[Time-Series Database] C2[Relational Database] C3[Object Storage] end subgraph "Data Distribution" D1[Message Queue] D2[Downstream Systems] D3[Real-Time Push] end end A1 --> A2 A2 --> A3 A3 --> A4 A4 --> A5 A5 --> B1 B1 --> B2 B2 --> B3 B3 --> B4 B4 --> C1 B4 --> C2 B4 --> C3 C1 --> D1 C2 --> D2 C3 --> D3

4.2 Rule Engine

iot:
 rules:
 - name: "Temperature Alert"
 condition: "temperature > 80"
 actions:
 - alert: "High Temperature Alert"
 - notify: "Operations Personnel"
 - command: "Device Cooling"
 - name: "Device Linkage"
 condition: "motion_detected == true"
 actions:
 - command: "light_on"
 - command: "camera_record"
 - name: "Data Aggregation"
 condition: "time_window = 5m"
 actions:
 - aggregate: "avg(temperature)"
 - store: "Aggregated Data"

Rule Type	Description
Alert Rules	Threshold alerts, trend alerts
Linkage Rules	Device linkage, scenario linkage
Computation Rules	Real-time computation, data aggregation
Notification Rules	Message push, alert notifications

5. Device Operations Enhancement

5.1 Alert Management

graph TB subgraph "Alert Workflow" A[Rule Triggered] --> B[Alert Generation] B --> C[Alert Classification] C --> D[Alert Notification] D --> E[Alert Acknowledgment] E --> F[Alert Processing] F --> G[Alert Closure] C --> C1[Critical Alert] C --> C2[Important Alert] C --> C3[General Alert] C --> C4[Info Alert] end

Alert Level	Description	Response Requirement
Critical Alert	Device failure, security risk	Immediate response
Important Alert	Parameter anomaly, performance degradation	30-minute response
General Alert	Minor anomaly, early warning	2-hour response
Info Alert	Information notification, status change	Same-day processing

5.2 Predictive Maintenance

Capability	Description
Fault Prediction	AI model-based fault prediction
Lifespan Prediction	Device lifespan prediction
Maintenance Suggestions	Intelligent maintenance recommendations
Spare Parts Alert	Spare parts demand prediction

6. Technical Architecture

graph TB subgraph "yudao-module-iot-plus" subgraph "iot-biz" A1[device - Device Management] A2[protocol - Protocol Adaptation] A3[gateway - Gateway Management] A4[data - Data Processing] A5[rule - Rule Engine] A6[alert - Alert Management] A7[monitor - Real-Time Monitoring] A8[maintenance - Maintenance Management] A9[edge - Edge Computing] A10[analytics - Data Analysis] end subgraph "Permissions and Audit" B1[permission - Permission Control] B2[audit - Audit Logs] B3[security - Security Authentication] end end A1 --> B1 A2 --> B2 A3 --> B3 A4 --> B2 A5 --> B2

7. Business Value

Value Point	Description
Device Visibility	Real-time monitoring, status transparency
Intelligent Operations	Predictive maintenance, intelligent alerts
Fault Reduction	Fault prediction, rapid response
Data Value	Data analysis, AI enablement
Edge Intelligence	Local computing, edge-cloud collaboration
Security Compliance	Device authentication, operation audit

Asset Management

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, 4 DOs / 4 Controllers, menu ID starting from 10000, building an enterprise asset full-lifecycle digital management system

1. Enhancement Positioning & Architecture

1.1 Product Positioning

RuoYiPlus Asset builds upon Yudao OA’s native asset management, providing enterprise-grade enhancements around five core areas: full asset lifecycle management, multi-dimensional asset accounting, intelligent inventory & IoT tracking, and asset permissions & auditing, achieving a complete asset closed loop from procurement to disposal.

1.2 Module Scale

Metric	Value
Data Objects (DO)	4
Controllers	4
Menu ID Start	10000
Maven Module	yudao-module-asset

1.3 Core Data Tables

Table Name	Description
`asset_category`	Asset Category
`asset_goods`	Asset Goods
`asset_info`	Asset Information
`asset_lifecycle`	Asset Lifecycle

graph TB subgraph "RuoYiPlus Asset Enhanced Architecture" subgraph "Asset Ledger Layer" A1[Fixed Assets] A2[Intangible Assets] A3[IT Assets] A4[Low-value Consumables] end subgraph "Lifecycle Layer" B1[Procurement & Inbound] B2[Assignment & Allocation] B3[Transfer & Relocation] B4[Maintenance & Repair] B5[Scrap & Disposal] end subgraph "Accounting Layer" C1[Depreciation Management] C2[Value Assessment] C3[Impairment Processing] C4[Cost Allocation] end subgraph "Intelligence Layer" D1[IoT Asset Tracking] D2[Smart Inventory] D3[RFID/Barcode] D4[Asset Analytics] end subgraph "Control Layer" E1[Asset Permissions] E2[Data Isolation] E3[Operation Audit] E4[Compliance Reporting] end end A1 --> B1 A2 --> B1 A3 --> B1 A4 --> B1 B1 --> B2 B2 --> B3 B3 --> B4 B4 --> B5 B5 --> C1 C1 --> C2 C2 --> C3 C3 --> C4 C4 --> D1 D1 --> D2 D2 --> D3 D3 --> D4 D4 --> E1 E1 --> E2 E2 --> E3 E3 --> E4

1.4 Capability Comparison

Dimension	Yudao Native Capability	RuoYiPlus Asset Enhancement
Asset Types	Basic classification	Full coverage: Fixed/Intangible/IT/Low-value consumables
Lifecycle	Check-out/return	Procurement → Assignment → Transfer → Maintenance → Disposal
Depreciation Management	None	Multiple depreciation methods + auto accrual
Asset Inventory	Manual inventory	RFID/Barcode smart inventory
IoT Tracking	None	Real-time positioning + geofencing
Financial Integration	None	Linked with ERP financial modules
Permission Control	Basic permissions	Org-level + asset-category-level data permissions
Audit Compliance	Simple logging	Full-chain asset audit + blockchain proof of existence

2. Asset Full-Lifecycle Management

2.1 Lifecycle Stages

graph LR A[Procurement & Inbound] --> B[Assignment & Allocation] B --> C[In-Use Management] C --> D[Transfer & Relocation] D --> E[Maintenance & Repair] E --> F[Scrap & Disposal] A --> A1[Purchase Request] A --> A2[Acceptance & Inbound] A --> A3[Asset Numbering] A --> A4[Label Printing] B --> B1[Assignment Request] B --> B2[Approval Workflow] B --> B3[Asset Allocation] C --> C1[Usage Registration] C --> C2[Status Monitoring] C --> C3[Location Tracking] D --> D1[Transfer Request] D --> D2[Approval Confirmation] D --> D3[Handover & Receipt] E --> E1[Repair Request] E --> E2[Repair Record] E --> E3[Acceptance Confirmation] F --> F1[Disposal Assessment] F --> F2[Residual Value Processing] F --> F3[Asset Deregistration]

2.2 Asset Classification System

Asset Category	Description	Typical Assets	Management Requirements
Fixed Assets	Useful life > 1 year, relatively high unit value	Office equipment, vehicles, furniture	Depreciation accrual + annual inventory
Intangible Assets	Long-term assets without physical form	Software licenses, patents, trademarks	Amortization management + value assessment
IT Assets	Information technology related assets	Servers, network equipment, terminals	Lifecycle + security compliance
Low-value Consumables	Low-value, fast-consuming assets	Office supplies, tools	Batch management + inventory control

2.3 Asset Data Permissions

The Asset system implements multi-dimensional data permission control based on organization and asset categories.

Permission Level	Scope	Description
Asset Administrator	Assets within jurisdiction	Can manage asset inbound, allocation, transfer, and disposal
Department Asset Admin	Department assets	Can manage assets assigned to their department
Regular Employee	Personally used assets	Can only view assets assigned to themselves
Financial Administrator	All assets	Can view asset value and depreciation data
Auditor	All assets	Read-only access + audit logs

// Asset data permission example
@DataPermission(scope = "asset")
public class AssetServiceImpl {
 // Asset administrators can manage all assets within their jurisdiction
 // Automatically filtered by organization + asset category
}

// Department asset administrator permission
@DataPermission(roles = {"dept_asset_admin"})
public class DeptAssetServiceImpl {
 // Can only manage assets assigned to their department
 // Automatically filtered by department
}

3. Depreciation Management

3.1 Depreciation Methods

Depreciation Method	Formula	Applicable Scenarios
Straight-line	(Cost - Residual Value) / Useful Life	General fixed assets
Units of Production	(Cost - Residual Value) / Total Output × Current Output	Vehicles, production equipment
Double Declining Balance	Net Book Value × (2 / Useful Life)	Rapidly evolving technology equipment
Sum of Years’ Digits	(Cost - Residual Value) × Remaining Years / Sum of Years	Assets with heavy early wear

3.2 Depreciation Process

graph TB subgraph "Depreciation Management" A[Asset Inbound] --> B[Set Depreciation Parameters] B --> C[Select Depreciation Method] C --> D[Monthly Auto Accrual] D --> E{Accrual Result} E --> F[Generate Depreciation Voucher] E --> G[Update Net Asset Value] F --> H[Financial Reconciliation] G --> H H --> I{Asset Status} I -->|In Use| D I -->|Disposed| J[Stop Accrual] I -->|Impaired| K[Impairment Processing] end

3.3 Depreciation Configuration

asset:
 depreciation:
 methods:
 - straight-line  # Straight-line method
 - work-quantity  # Units of production method
 - double-declining  # Double declining balance method
 - sum-of-years  # Sum of years' digits method
 rules:
 auto-calculate: true # Auto accrual
 calculate-day: 28 # Monthly accrual day
 residual-rate: 0.05 # Default residual rate 5%
 min-value: 5000 # Minimum asset value for depreciation
 categories:
 electronic:
 method: straight-line
 years: 3
 vehicle:
 method: work-quantity
 years: 8
 furniture:
 method: straight-line
 years: 10

4. Asset Inventory

4.1 Inventory Process

graph TB subgraph "Asset Inventory" A[Inventory Plan] --> B[Inventory Preparation] B --> C[Inventory Execution] C --> D[Discrepancy Handling] D --> E[Inventory Report] A --> A1[Define Inventory Scope] A --> A2[Assign Inventory Personnel] A --> A3[Set Inventory Schedule] B --> B1[Print Inventory Checklist] B --> B2[Prepare Inventory Tools] B --> B3[Freeze Asset Changes] C --> C1[Scan/RFID Inventory] C --> C2[Photo Evidence] C --> C3[Record Asset Status] D --> D1[Discrepancy Analysis] D --> D2[Surplus Processing] D --> D3[Shortage Processing] E --> E1[Generate Inventory Report] E --> E2[Approval Confirmation] E --> E3[Update Asset Ledger] end

4.2 Smart Inventory Technology

Inventory Method	Technology	Applicable Scenarios	Efficiency Improvement
Barcode Inventory	QR code scanning	General assets	3-5x
RFID Inventory	Radio frequency identification	Large-volume assets	10-20x
IoT Inventory	Sensor auto-reporting	High-value/mobile assets	Real-time inventory
Mobile Inventory	Mobile APP	Dispersed assets	Anytime, anywhere

4.3 IoT Asset Tracking

graph TB subgraph "IoT Asset Tracking" subgraph "Perception Layer" A1[RFID Tags] A2[GPS Trackers] A3[Environmental Sensors] end subgraph "Network Layer" B1[RFID Readers] B2[4G/5G Gateways] B3[WiFi Positioning] end subgraph "Platform Layer" C1[Asset Positioning] C2[Trajectory Tracking] C3[Geofencing] C4[Anomaly Alerts] end end A1 --> B1 A2 --> B2 A3 --> B2 B1 --> C1 B2 --> C2 B3 --> C3 C1 --> C4 C2 --> C4 C3 --> C4

5. Asset Operation Audit

5.1 Audit Events

All key asset operations are recorded with complete audit logs, supporting full-chain asset traceability.

graph TB subgraph "Audit Event Collection" A1[Asset Inbound] A2[Asset Assignment] A3[Asset Transfer] A4[Asset Repair] A5[Asset Disposal] A6[Depreciation Accrual] A7[Inventory Operations] end subgraph "Audit Processing" B1[Change Comparison] B2[Compliance Check] B3[Risk Assessment] end subgraph "Audit Storage" C1[Operation Logs] C2[Change History] C3[Blockchain Proof] end A1 --> B1 A2 --> B1 A3 --> B1 A4 --> B1 A5 --> B1 A6 --> B1 A7 --> B1 B1 --> B2 B2 --> B3 B3 --> C1 B3 --> C2 B3 --> C3

Audit Item	Description	Retention Period
Asset Inbound	Records procurement info, acceptor, inbound time	Permanent
Asset Assignment	Records assignee, assignment time, approver	Asset lifecycle + 5 years
Asset Transfer	Records pre/post transfer location, transfer reason	Asset lifecycle + 5 years
Asset Repair	Records repair details, cost, service provider	Asset lifecycle + 5 years
Asset Disposal	Records disposal reason, residual value, disposal method	Permanent
Depreciation Accrual	Records monthly depreciation amount, accumulated depreciation	Asset lifecycle + 5 years
Inventory Operations	Records inventory personnel, inventory time, inventory results	Permanent

5.2 Audit Permissions

Role	Audit Permission	Description
Asset Administrator	View audit logs for assets under jurisdiction	Can view audit records for assets within their jurisdiction
Department Manager	View department asset audit	Can view audit records for department assets
Auditor	View all asset audit	Read-only access, can export audit reports
System Administrator	Manage audit configuration	Can configure audit rules and retention policies

6. Asset Analytics

6.1 Analysis Dimensions

graph TB subgraph "Asset Analytics" subgraph "Asset Overview" A1[Total Assets] A2[Total Asset Value] A3[Asset Distribution] end subgraph "Usage Analysis" B1[Utilization Analysis] B2[Idle Analysis] B3[Efficiency Assessment] end subgraph "Financial Analysis" C1[Depreciation Analysis] C2[Maintenance Cost] C3[Net Asset Value] end subgraph "Decision Support" D1[Purchase Suggestions] D2[Disposal Suggestions] D3[Optimization Plans] end end A1 --> B1 A2 --> B2 A3 --> B3 B1 --> C1 B2 --> C2 B3 --> C3 C1 --> D1 C2 --> D2 C3 --> D3

6.2 Core Metrics

Metric	Description	Calculation Method
Asset Utilization Rate	Actual usage time / Planned usage time	Actual hours ÷ Planned hours × 100%
Idle Rate	Idle assets / Total assets	Idle asset count ÷ Total asset count × 100%
Maintenance Cost Rate	Maintenance cost / Asset original value	Annual maintenance cost ÷ Asset original value × 100%
Net Asset Value Ratio	Net asset value / Asset original value	Net asset value ÷ Asset original value × 100%
Inventory Accuracy Rate	Matching records / Total inventory count	Matching asset count ÷ Total inventory count × 100%

7. Technical Architecture

graph TB subgraph "yudao-module-asset-plus" subgraph "asset-biz" A1[ledger] A2[lifecycle] A3[depreciation] A4[inventory] A5[maintenance] A6[disposal] A7[IoT tracking] A8[analytics] end subgraph "Permissions & Audit" B1[permission] B2[audit] B3[compliance] end end A1 --> B1 A2 --> B2 A3 --> B2 A4 --> B2 A5 --> B2 A6 --> B2 A7 --> B1 A8 --> B3

8. Business Value

Value Point	Description
Account-Reality Alignment	Smart inventory + IoT tracking ensures account-reality consistency
Cost Control	Accurate depreciation accounting + maintenance cost analysis
Asset Optimization	Utilization analysis + idle alerts + purchase suggestions
Compliance Traceability	Full-chain audit + blockchain proof + compliance reports
Efficiency Improvement	Automated inventory + mobile operations + intelligent analytics
Risk Prevention	Asset loss alerts + geofencing + anomaly alerts

Message Queue

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

Message queue is the “central nervous system” for asynchronous communication between subsystems. When ERP outbound needs to notify WMS to update inventory, when mall payment success needs to award points to members — all these cross-module asynchronous collaborations are completed through the message queue.

Design Philosophy: Business code only depends on the yudao-spring-boot-starter-mq abstract interface; switching the underlying implementation only requires changing one line of configuration.

Suitable Users

User Profile	Recommended Solution
Development/Debugging Phase	Spring Event (default, zero dependencies)
Small & Medium Projects	Redis Stream (persistent, supports consumer groups)
Enterprise Projects	RabbitMQ (stable & reliable, mature operations)
High-Throughput Scenarios	RocketMQ (Alibaba ecosystem, distributed transactions)
Big Data Scenarios	Kafka (logs, event tracking, data pipelines)

Architecture Design

graph TB subgraph BusinessLayer["Business Code Layer (depends only on abstraction)"] P["Producer
MessageProducer.send()"] C["Consumer
MessageConsumer.onMessage()"] end subgraph AbstractionLayer["Abstraction Layer yudao-spring-boot-starter-mq"] API["Unified API
Message / MessageProducer / MessageConsumer"] end subgraph ImplementationLayer["Implementation Layer (Choose One of Five)"] SE["yudao-spring-boot-starter-mq-spring-event
Spring Event (Default)"] REDIS["yudao-spring-boot-starter-mq-redis
Redis Stream"] RABBIT["yudao-spring-boot-starter-mq-rabbitmq
RabbitMQ"] ROCKET["yudao-spring-boot-starter-mq-rocketmq
RocketMQ"] KAFKA["yudao-spring-boot-starter-mq-kafka
Kafka"] end P --> API C --> API API --> SE API --> REDIS API --> RABBIT API --> ROCKET API --> KAFKA

Five Implementation Comparison

Implementation	Persistence	Consumption Mode	Use Case	Switch Config
Spring Event	❌ In-memory	Broadcast	Development/Debugging	Default
Redis Stream	✅	Cluster/Broadcast	Small & Medium projects	`yudao.mq.type=redis`
RabbitMQ	✅	Multiple modes	Enterprise projects	`yudao.mq.type=rabbitmq`
RocketMQ	✅	Cluster/Broadcast/Ordered	High throughput, transactional messages	`yudao.mq.type=rocketmq`
Kafka	✅	Partition-based	Big data, logs	`yudao.mq.type=kafka`

Usage Examples

Define Message

// 1. Define message class, implement Message interface
@Data
public class OrderPaidMessage implements Message {
 private Long orderId;
 private Long userId;
 private Integer amount;
}

Send Message

@Resource
private MessageProducer messageProducer;

public void payOrder(Long orderId) {
 // Business processing...

 // Send message
 OrderPaidMessage message = new OrderPaidMessage();
 message.setOrderId(orderId);
 message.setUserId(getCurrentUserId());
 message.setAmount(order.getAmount());
 messageProducer.send(message);
}

Consume Message

@Component
public class OrderPaidConsumer implements MessageConsumer<OrderPaidMessage> {

 @Override
 public void onMessage(OrderPaidMessage message) {
 // Award points
 memberService.addPoints(message.getUserId(), message.getAmount());

 // Update inventory
 stockService.decreaseStock(message.getOrderId());
 }
}

Typical Message Flow Between Subsystems

sequenceDiagram participant MALL as Mall Module participant MQ as Message Queue participant WMS as Warehouse Module participant MEMBER as Member Module MALL->>MALL: User payment successful MALL->>MQ: Send "Order Paid" message MQ->>WMS: Consume message → Deduct inventory MQ->>MEMBER: Consume message → Award points Note over WMS,MEMBER: Two consumers execute independently, no interference

Switching Method

Just modify the configuration file:

# Switch from Spring Event to Redis Stream
yudao:
 mq:
 type: redis  # Change to redis / rabbitmq / rocketmq / kafka

No business code changes needed.

OA Administrative Office

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, 48 DOs / 27 Controllers, menu ID starting at 3000, building a digital administrative office and workflow collaboration system

1. Enhancement Positioning and Architecture

1.1 Product Positioning

RuoYiPlus OA centers around three core pillars—Intelligent Approval, Document Management, and Administrative Resource Control—to deliver enterprise-level enhancement, achieving full-process digitalization from workflow approval to administrative management.

1.2 Module Scale

Metric	Value
Data Objects (DO)	48
Controllers	27
Menu ID Start	3000
Maven Module	yudao-module-oa

1.3 Core Data Tables

Table Name	Description
`oa_workflow`	Workflow Approval
`oa_meeting_room`	Meeting Room Management
`oa_file`	File Management
`oa_knowledge_base`	Knowledge Base
`oa_car`	Vehicle Management
`oa_schedule`	Schedule Management
`oa_seal`	Seal Management
`oa_material`	Material Management
`oa_form`	Form Management
`oa_information`	Information Management

graph TB subgraph "RuoYiPlus OA Enhanced Architecture" subgraph "Workflow Layer" A1[Intelligent Approval] A2[Document Management] A3[Workflow Designer] end subgraph "Collaboration Layer" B1[Schedule Management] B2[Meeting Management] B3[Task Collaboration] end subgraph "Administrative Layer" C1[Asset Management] C2[Seal Management] C3[Attendance Management] end subgraph "Control Layer" D1[Approval Permissions] D2[Workflow Audit] D3[Data Security] D4[Compliance Reports] end end A1 --> A2 A2 --> A3 A3 --> B1 B1 --> B2 B2 --> B3 B3 --> C1 C1 --> C2 C2 --> C3 C3 --> D1 D1 --> D2 D2 --> D3 D3 --> D4

1.4 Capability Comparison

Dimension	Yudao Native OA	RuoYiPlus OA Enhanced
Workflow Approval	Basic approval	Intelligent approval + workflow optimization
Document Management	None	Full-process document management
Schedule Management	Simple schedule	Team schedule + meeting management
Task Management	None	Task collaboration + progress tracking
Administrative Management	None	Asset management + seal management
Mobile Office	Simple mobile	Full-featured mobile office
Permission Control	Basic permissions	Approval-level hierarchical permissions
Audit Compliance	Simple logs	Full-chain workflow audit

2. Intelligent Approval Enhancement

2.1 Approval Workflow System

graph TB subgraph "Approval Workflow" subgraph "Workflow Design" A1[Workflow Modeling] A2[Conditional Branching] A3[Parallel Approval] A4[Workflow Templates] A5[Workflow Publishing] end subgraph "Approval Execution" B1[Approval Initiation] B2[Approval Routing] B3[Approval Processing] B4[Countersign] B5[Reassign] B6[Withdrawal] B7[Rejection] end subgraph "Intelligent Approval" C1[Intelligent Routing] C2[Conditional Auto-Judgment] C3[Automatic Routing] C4[Intelligent Reminders] end subgraph "Mobile Approval" D1[Mobile Initiation] D2[Mobile Approval] D3[Mobile Query] end end A1 --> A2 A2 --> A3 A3 --> A4 A4 --> A5 A5 --> B1 B1 --> B2 B2 --> B3 B3 --> B4 B4 --> B5 B5 --> B6 B6 --> B7 B7 --> C1 C1 --> C2 C2 --> C3 C3 --> C4 C4 --> D1 D1 --> D2 D2 --> D3

2.2 Approval Permission Control

The OA system implements approval permission control based on workflow and position, ensuring approval process compliance.

Permission Level	Scope	Description
Initiator	Own approvals	Can only initiate and view their own approvals
Approver	Pending approval items	Can only approve items assigned to them
Department Manager	Department approvals	Can view all approvals within the department
Administrator	All approvals	Can view and manage all approvals

// OA Approval Permission Example
@DataPermission(scope = "approval")
public class ApprovalServiceImpl {
 // Approvers can only process their own pending items
 // Department managers can view department approvals
}

2.3 Approval Audit

All approval operations record complete audit logs, supporting approval workflow traceability.

graph LR A[Approval Initiation] --> B[Approval Routing] B --> C[Approval Processing] C --> D[Approval Completion] A -.-> E[Audit Log] B -.-> E C -.-> E D -.-> E E --> F[Workflow Traceability] E --> G[Compliance Reports]

Audit Item	Description
Approval Initiation	Records initiator, initiation time, approval content
Approval Routing	Records routing time, routing path
Approval Processing	Records approver, approval time, approval comments
Approval Withdrawal	Records withdrawer, withdrawal time, withdrawal reason
Approval Rejection	Records rejector, rejection time, rejection reason

3. Document Management Enhancement

3.1 Document Management Workflow

graph TB subgraph "Document Management" subgraph "Document Drafting" A1[Document Templates] A2[Document Editing] A3[Document Formatting] A4[Document Approval] A5[Document Issuance] end subgraph "Document Circulation" B1[Document Distribution] B2[Document Receipt] B3[Document Circulation] B4[Document Supervision] B5[Document Archiving] end subgraph "Document Query" C1[Document Search] C2[Document Statistics] C3[Document Analysis] end subgraph "Document Security" D1[Document Encryption] D2[Document Watermark] D3[Document Audit] end end A1 --> A2 A2 --> A3 A3 --> A4 A4 --> A5 A5 --> B1 B1 --> B2 B2 --> B3 B3 --> B4 B4 --> B5 B5 --> C1 C1 --> C2 C2 --> C3 C3 --> D1 D1 --> D2 D2 --> D3

Document Type	Description
Outgoing	Official outgoing documents, notices and announcements
Incoming	External incoming documents, superior incoming documents
Internal Documents	Internal notices, work arrangements
Meeting Minutes	Meeting minutes, resolution documents

4. Schedule and Meeting Management

4.1 Schedule and Meeting System

graph TB subgraph "Schedule and Meeting" subgraph "Personal Schedule" A1[Schedule Creation] A2[Schedule Reminders] A3[Schedule Sync] A4[Schedule Sharing] end subgraph "Team Schedule" B1[Team Calendar] B2[Schedule Coordination] B3[Schedule Conflict Detection] end subgraph "Meeting Management" C1[Meeting Booking] C2[Meeting Invitation] C3[Meeting Confirmation] C4[Meeting Check-in] C5[Meeting Minutes] end subgraph "Meeting Room Management" D1[Meeting Room Booking] D2[Meeting Room Status] D3[Meeting Room Statistics] end end A1 --> A2 A2 --> A3 A3 --> A4 A4 --> B1 B1 --> B2 B2 --> B3 B3 --> C1 C1 --> C2 C2 --> C3 C3 --> C4 C4 --> C5 C5 --> D1 D1 --> D2 D2 --> D3

5. Administrative Management Enhancement

5.1 Asset Management

graph TB subgraph "Asset Management" subgraph "Asset Ledger" A1[Asset Registration] A2[Asset Classification] A3[Asset Labeling] A4[Asset Location] end subgraph "Asset Usage" B1[Asset Requisition] B2[Asset Return] B3[Asset Transfer] B4[Asset Repair] B5[Asset Disposal] end subgraph "Asset Inventory" C1[Inventory Plan] C2[Inventory Execution] C3[Inventory Discrepancy] C4[Inventory Report] end subgraph "Asset Analysis" D1[Asset Statistics] D2[Asset Valuation] D3[Asset Utilization Rate] end end A1 --> A2 A2 --> A3 A3 --> A4 A4 --> B1 B1 --> B2 B2 --> B3 B3 --> B4 B4 --> B5 B5 --> C1 C1 --> C2 C2 --> C3 C3 --> C4 C4 --> D1 D1 --> D2 D2 --> D3

5.2 Seal Management

graph TB subgraph "Seal Management" subgraph "Seal Ledger" A1[Seal Registration] A2[Seal Type] A3[Seal Status] A4[Seal Custody] A5[Seal Authorization] end subgraph "Seal Usage" B1[Seal Application] B2[Seal Approval] B3[Seal Registration] B4[Seal Record] B5[Seal Traceability] end subgraph "Seal Security" C1[Seal Monitoring] C2[Seal Audit] C3[Seal Alert] end end A1 --> A2 A2 --> A3 A3 --> A4 A4 --> A5 A5 --> B1 B1 --> B2 B2 --> B3 B3 --> B4 B4 --> B5 B5 --> C1 C1 --> C2 C2 --> C3

5.3 Seal Audit

All seal usage operations record complete audit logs, ensuring seal usage compliance.

Audit Item	Description
Seal Application	Records applicant, application time, reason for seal use
Seal Approval	Records approver, approval time, approval comments
Seal Registration	Records seal time, sealed document, seal count
Seal Traceability	Records seal history, seal trail

6. Technical Architecture

graph TB subgraph "yudao-module-oa-plus" subgraph "oa-biz" A1[workflow - Workflow Approval] A2[document - Document Management] A3[schedule - Schedule Management] A4[meeting - Meeting Management] A5[task - Task Management] A6[asset - Asset Management] A7[seal - Seal Management] A8[attendance - Attendance Management] A9[mobile - Mobile Office] A10[analytics - Data Analysis] end subgraph "Permissions and Audit" B1[permission - Permission Control] B2[audit - Audit Logs] B3[compliance - Compliance Reports] end end A1 --> B1 A2 --> B2 A3 --> B1 A4 --> B2 A5 --> B2 A6 --> B2 A7 --> B3

7. Business Value

Value Point	Description
Workflow Efficiency	Intelligent approval, workflow optimization
Collaboration Efficiency	Schedule collaboration, task collaboration
Administrative Standardization	Asset management, seal management
Mobile Office	Full-featured mobile office
Data-Driven	Efficiency analysis, optimization suggestions
Compliance Control	Approval permissions, workflow audit

Pay Payment Center

Mon, 01 Jan 0001 00:00:00 +0000

Core Positioning

The Pay Payment Center is the platform’s “unified checkout counter.” The mall sells goods and needs to collect payments, ERP procurement needs to make payments, member top-ups need to collect payments — all these payment and collection scenarios are handled uniformly through the Payment Center, without business modules needing to care whether the underlying payment method is WeChat Pay or Alipay.

In one sentence: Integrate with the Payment Center once, and all business modules can collect and make payments.

Problems Solved

Pain Point	How Payment Center Solves It
Each business separately integrates WeChat/Alipay	Unified integration once, all businesses reuse
Payment channel switching requires changing business code	Channel changes are transparent to business
Payment callback handling is scattered	Unified callback → dispatch to each business module
Payment records are nowhere to be found	Payment Center records all transactions, unified reconciliation

User Roles

graph LR subgraph Roles DEV["Developer
Integrate payment APIs
Handle payment callbacks"] ADMIN2["Operations/Finance
View payment records
Process refunds
Reconciliation"] ENDUSER["End User
Initiate payments
View payment results"] end

Architecture Design

graph TB subgraph BusinessLayer["Business Modules (Payment Callers)"] MALL["Mall
Order Payment"] ERP2["ERP
Purchase Payment"] OTHER["Other Modules
Top-up/Transfer"] end subgraph PaymentCenter["Payment Center yudao-module-pay"] API_LAYER["API Layer
PayOrderApi / PayRefundApi"] CHANNEL["Channel Adapter Layer
PayClient Unified Client"] CALLBACK["Callback Handling Layer
Unified Callback → Dispatch to Business"] end subgraph ChannelLayer["Payment Channels"] WXPAY["WeChat Pay
Official Account/Mini Program/QR Code"] ALIPAY["Alipay
PC/Wap/Transfer"] MOCK["Mock Payment
For development/debugging"] end BusinessLayer --> API_LAYER API_LAYER --> CHANNEL CHANNEL --> ChannelLayer ChannelLayer --> CALLBACK CALLBACK --> BusinessLayer

Payment Application Design

graph TB subgraph AppIsolation APP1["Payment App: Mall Orders
Callback URL: /mall/order/callback
Order Prefix: MALL-"] APP2["Payment App: ERP Procurement
Callback URL: /erp/purchase/callback
Order Prefix: ERP-"] APP3["Payment App: Member Top-up
Callback URL: /member/recharge/callback
Order Prefix: MBR-"] end

Each business module corresponds to a “payment application” with independent callback URL and order number prefix, ensuring payment callbacks are accurately routed to the correct business processing logic.

Full Payment Flow

sequenceDiagram participant U as User participant BIZ as Business System (Mall) participant PAY as Payment Center participant CH as Payment Channel (WeChat/Alipay) U->>BIZ: Submit order, click pay BIZ->>PAY: Create payment order PayOrderApi PAY->>CH: Initiate payment request CH-->>U: Display payment page U->>CH: Complete payment (scan/password) CH-->>PAY: Async callback: Payment successful PAY->>PAY: Update payment order status PAY->>BIZ: Callback notification: Order paid BIZ->>BIZ: Update order status BIZ-->>U: Display payment success

Supported Payment Methods

Channel	Payment Method	Use Case
WeChat Pay	Official Account Payment	WeChat Official Account H5 store
WeChat Pay	Mini Program Payment	WeChat Mini Program store
WeChat Pay	Transfer	Commission withdrawal, refunds
Alipay	PC Payment	PC-side store
Alipay	Wap Payment	Mobile H5 store
Alipay	Transfer	Commission withdrawal, refunds
Mock Payment	Mock	Development/debugging, no real account needed

Dependencies

Mall E-Commerce → Pay Payment Center ← ERP Purchase-Sales-Inventory
 ↑
 System Management Module (Permissions)

Both Mall and ERP depend on the Payment Center, which depends on the System Management module for permissions and configuration management.

EHR Human Resources

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, 30 DOs / 15 Controllers, menu ID starting from 7000, building an enterprise HR digital management system

1. Enhancement Positioning & Architecture

1.1 Product Positioning

RuoYiPlus EHR provides enterprise-grade enhancements around three core areas: employee full-lifecycle management, compensation & performance management, and recruitment & training management, achieving digital HR management.

1.2 Module Scale

Metric	Value
Data Objects (DO)	30
Controllers	15
Menu ID Start	7000
Maven Module	yudao-module-ehr

1.3 Core Data Tables

Table Name	Description
`ehr_employee`	Employee Management
`ehr_attendance`	Attendance Management
`ehr_insurance`	Social Insurance Management
`ehr_performance`	Performance Management
`ehr_recruitment`	Recruitment Management
`ehr_salary`	Salary Management
`ehr_contract`	Contract Management
`ehr_education`	Training Management

graph TB subgraph "RuoYiPlus EHR Enhanced Architecture" subgraph "Organization & Personnel" A1[Employee Records] A2[Org Structure] A3[Contract Management] A4[Onboarding/Offboarding] end subgraph "Compensation & Benefits" B1[Salary Calculation] B2[Social Insurance & Housing Fund] B3[Income Tax Management] end subgraph "Attendance & Performance" C1[Attendance Clock-in] C2[Performance Appraisal] C3[Leave Management] end subgraph "Recruitment & Training" D1[Recruitment Management] D2[Training Management] D3[Talent Development] end subgraph "Control Layer" E1[Data Permissions] E2[Privacy Masking] E3[Operation Audit] end end A1 --> B1 A2 --> B1 A3 --> B2 A4 --> C1 B1 --> C2 B2 --> C2 C1 --> C3 C3 --> D1 D1 --> D2 D2 --> D3 A1 --> E1 B1 --> E2 C2 --> E3

1.4 Capability Comparison

Dimension	Traditional HR System	RuoYiPlus EHR Enhancement
Employee Management	Basic info	Full-lifecycle + digital records
Compensation Management	Manual calculation	Auto payroll + tax calculation
Attendance Management	Simple clock-in	Multi-dimensional attendance + smart scheduling
Performance Management	None	KPI + 360-degree appraisal
Recruitment Management	None	Full-process recruitment management
Training Management	None	Training plans + effectiveness evaluation
Permission Control	Basic permissions	Department-level + position-level data permissions
Privacy Compliance	None	Privacy data masking + audit

2. Employee Full-Lifecycle Management

2.1 Employee Lifecycle

graph LR A[Recruitment & Onboarding] --> B[Probation Management] B --> C[Regular Employee] C --> D[Transfer & Promotion] D --> E[Offboarding Management] A --> A1[Resume Screening] A --> A2[Interview Assessment] A --> A3[Onboarding Processing] B --> B1[Probation Assessment] B --> B2[Mentor Guidance] B --> B3[Confirmation Review] C --> C1[Performance Management] C --> C2[Training & Development] C --> C3[Compensation & Benefits] D --> D1[Position Adjustment] D --> D2[Rank Promotion] D --> D3[Salary Adjustment] E --> E1[Resignation Application] E --> E2[Exit Handover] E --> E3[Exit Analysis]

2.2 Data Permission Control

The EHR system implements data permission control based on departments and positions to ensure HR data security.

Permission Level	Scope	Description
Employee Self	Personal info	Can only view their own basic information
Department Manager	Department employees	Can view department employee information
HR Specialist	All employees	Can view all employee information
Executive	All data	Can view all HR data

// EHR data permission example
@DataPermission(scope = "department")
public class EmployeeServiceImpl {
 // Department managers can only view employees in their department
 // Automatically filtered by department
}

3. Compensation Management

3.1 Compensation System

graph TB subgraph "Compensation Management" A[Compensation Structure] --> B[Salary Calculation] B --> C[Social Insurance & Housing Fund] B --> D[Income Tax Calculation] C --> E[Salary Disbursement] D --> E E --> F[Salary Reports] A --> A1[Base Salary] A --> A2[Performance Pay] A --> A3[Allowances & Subsidies] A --> A4[Bonuses] end

Capability	Description
Compensation Structure	Base salary + performance + allowances + bonuses
Auto Payroll	Rule-based automatic salary calculation
Social Insurance Management	Automatic social insurance & housing fund calculation
Income Tax Calculation	Cumulative withholding method tax calculation
Salary Disbursement	Bank direct deposit, pay slips

3.2 Compensation Audit

All compensation operations are recorded with complete audit logs to ensure salary data security.

Audit Item	Description
Salary Adjustment	Records adjustment time, amount, reason
Salary Calculation	Records calculation process, calculation formulas
Salary Disbursement	Records disbursement time, disbursement amount
Data Export	Records export time, exporter

4. Attendance & Performance Management

4.1 Attendance System

graph TB subgraph "Attendance Management" A[Shift Scheduling] --> B[Attendance Clock-in] B --> C[Attendance Statistics] C --> D[Exception Handling] D --> E[Attendance Reports] A --> A1[Fixed Shifts] A --> A2[Flexible Shifts] A --> A3[Rotating Shifts] B --> B1[GPS Clock-in] B --> B2[WiFi Clock-in] B --> B3[Face Recognition] C --> C1[Attendance Statistics] C --> C2[Overtime Statistics] C --> C3[Leave Statistics] end

4.2 Performance Appraisal

Appraisal Method	Description
KPI Appraisal	Key Performance Indicator appraisal
OKR Appraisal	Objectives and Key Results appraisal
360-Degree Appraisal	Multi-dimensional comprehensive evaluation
MBO	Management by Objectives appraisal

5. Technical Architecture

graph TB subgraph "yudao-module-ehr-plus" subgraph "ehr-biz" A1[employee] A2[salary] A3[attendance] A4[performance] A5[recruitment] A6[education] A7[contract] A8[insurance] A9[analytics] end subgraph "Permissions & Audit" B1[permission] B2[audit] B3[masking] end end A1 --> B1 A2 --> B2 A3 --> B2 A4 --> B2 A5 --> B1 A6 --> B1 A7 --> B3

6. Business Value

Value Point	Description
HR Efficiency	Automated processes, digital records
Compensation Accuracy	Auto payroll, compliant tax
Talent Development	Performance management, training system
Data-driven Decisions	HR analytics, talent review
Compliance Control	Data permissions, privacy protection
Audit Traceability	Operation audit, change traceability

IM Instant Messaging

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, 16 DOs / 29 Controllers, menu ID starting at 11000, building an enterprise instant messaging and collaborative office system

1. Enhancement Positioning and Architecture

1.1 Product Positioning

RuoYiPlus IM centers around three core pillars—Rich Media Messaging, Deep Business Integration, and Message Security and Compliance—to deliver enterprise-level enhancement, creating a secure and controllable enterprise communication platform.

1.2 Module Scale

Metric	Value
Data Objects (DO)	16
Controllers	29
Menu ID Start	11000
Maven Module	yudao-module-im

1.3 Core Data Tables

Table Name	Description
`im_channel`	Channel Management
`im_group`	Group Management
`im_private_message`	Private Messages
`im_rtc_call`	RTC Calls
`im_emoticon`	Emoticons
`im_sensitive_word`	Sensitive Words
`im_friend`	Friend Management

graph TB subgraph "RuoYiPlus IM Enhanced Architecture" subgraph "Message Layer" A1[Basic Messages] A2[Rich Media Messages] A3[Business Messages] A4[Card Messages] end subgraph "Group Layer" B1[Work Groups] B2[Project Groups] B3[Department Groups] B4[Notification Groups] end subgraph "Collaboration Layer" C1[File Collaboration] C2[Schedule Collaboration] C3[Task Collaboration] end subgraph "Security Layer" D1[Message Encryption] D2[Message Audit] D3[Permission Control] D4[Compliance Reports] end end A1 --> B1 A2 --> B2 A3 --> B3 A4 --> B4 B1 --> C1 B2 --> C2 B3 --> C3 C1 --> D1 C2 --> D2 C3 --> D3

1.4 Capability Comparison

Dimension	Traditional IM	RuoYiPlus IM Enhanced
Message Types	Text messages	Rich media + business messages
Group Management	Simple groups	Multi-type groups + permission management
Message Security	No encryption	Message encryption + audit compliance
Business Integration	None	Business messages + work notifications
Collaboration Capability	None	File collaboration + schedule collaboration
Data Analysis	None	Activity analysis + efficiency analysis

2. Rich Media Message Support

2.1 Message Type System

graph TB subgraph "Message Types" subgraph "Basic Messages" A1[Text Messages] A2[Emoticon Messages] A3["@Mentions"] A4[Image Messages] A5[Voice Messages] A6[Video Messages] end subgraph "File Messages" B1[File Sending] B2[File Preview] B3[File Download] B4[File Collaboration] end subgraph "Business Messages" C1[Ticket Messages] C2[Approval Messages] C3[Task Messages] C4[Notification Messages] end subgraph "Card Messages" D1[Info Cards] D2[Action Cards] D3[Form Cards] end end

Message Type	Description
Text Messages	Text, emoticons, @mentions
Rich Media Messages	Images, voice, video, files
Business Messages	Tickets, approvals, tasks and other business notifications
Card Messages	Interactive information cards
Location Messages	Location sharing, check-in

3. Group Management Enhancement

3.1 Group Management System

graph TB subgraph "Group Management" subgraph "Group Types" A1[Work Groups] A2[Project Groups] A3[Department Groups] A4[Discussion Groups] A5[Notification Groups] end subgraph "Group Permissions" B1[Group Owner] B2[Admin] B3[Regular Member] end subgraph "Group Features" C1[Group Announcement] C2[Group Files] C3[Group Schedule] C4[Group Poll] end end A1 --> B1 A2 --> B1 A3 --> B1 A4 --> B1 A5 --> B1 B1 --> B2 B2 --> B3 B3 --> C1 C1 --> C2 C2 --> C3 C3 --> C4

Group Type	Description
Work Groups	Daily work communication groups
Project Groups	Project collaboration groups, linked to projects
Department Groups	Department communication groups, auto-sync members
Discussion Groups	Temporary discussion groups, flexible creation
Notification Groups	One-way notification groups, only admins can post

4. Message Security and Compliance

4.1 Message Security System

graph TB subgraph "Message Security" subgraph "Transport Security" A1[SSL/TLS Encryption] A2[Message Signing] A3[Tamper Prevention] end subgraph "Storage Security" B1[Encrypted Message Storage] B2[Sensitive Content Encryption] B3[Data Isolation] end subgraph "Audit Compliance" C1[Message Audit] C2[Keyword Monitoring] C3[Risk Alert] C4[Compliance Reports] end subgraph "Permission Control" D1[Message Permissions] D2[Group Permissions] D3[Feature Permissions] end end A1 --> B1 A2 --> B1 A3 --> B1 B1 --> C1 B2 --> C1 B3 --> C1 C1 --> D1 C2 --> D1 C3 --> D1

4.2 Message Audit

All messages record complete audit logs, supporting message content traceability and compliance auditing.

Audit Item	Description
Message Sending	Records sender, recipient, send time
Message Content	Records message content (encrypted storage)
Message Recall	Records recall operations
File Transfer	Records file uploads and downloads
Group Operations	Records group creation, member changes

graph LR A[Message Sent] --> B[Message Audit] B --> C[Keyword Detection] C --> D{Sensitive Word?} D -->|Yes| E[Risk Flagging] D -->|No| F[Normal Storage] E --> G[Alert Notification] F --> H[Encrypted Storage] G --> H

4.3 Message Permission Control

The IM system implements role-based permission control to ensure message data security.

Permission Level	Scope	Description
Regular User	Personal messages	Can only view their own messages
Group Admin	Group messages	Can manage group messages and members
Auditor	All messages	Can view all messages for auditing
System Admin	System configuration	Can configure system parameters but cannot view message content

5. Business Integration Enhancement

5.1 Business Integration Architecture

graph TB subgraph "Business Integration" subgraph "Business Messages" A1[Ticket Notifications] A2[Approval Notifications] A3[Task Notifications] A4[Schedule Reminders] end subgraph "Business Actions" B1[Quick Approval] B2[Quick Processing] B3[Business Navigation] end subgraph "Business Collaboration" C1[File Collaboration] C2[Schedule Collaboration] C3[Task Collaboration] C4[Meeting Collaboration] end end A1 --> B1 A2 --> B1 A3 --> B2 A4 --> B2 B1 --> C1 B2 --> C2 B3 --> C3

Business Type	Integration Method
Ticket System	Ticket creation, status change notifications
Approval System	Approval initiation, approval result notifications
Task System	Task assignment, progress update notifications
Schedule System	Schedule reminders, meeting invitations
Report System	Report generation, push notifications

6. Collaborative Office Enhancement

6.1 File Collaboration

Capability	Description
File Sharing	Group files, personal file library
Online Preview	Office, PDF online preview
Collaborative Editing	Multi-person collaborative document editing
Version Management	File version history
File Search	File content search

6.2 Schedule Collaboration

Capability	Description
Schedule Creation	Personal schedule, group schedule
Schedule Reminders	Timed reminders, recurring reminders
Schedule Sharing	Schedule sharing, schedule subscription
Meeting Invitations	Meeting invitations, attendance confirmation
Schedule Sync	Sync with external calendars

6.3 Task Collaboration

Capability	Description
Task Creation	Group tasks, personal tasks
Task Assignment	Task assignment, task claiming
Progress Tracking	Task progress, completion status
Task Reminders	Task due reminders
Task Statistics	Task completion statistics

7. Technical Architecture

graph TB subgraph "yudao-module-im-plus" subgraph "im-biz" A1[message - Message Management] A2[group - Group Management] A3[user - User Management] A4[security - Message Security] A5[audit - Message Audit] A6[integration - Business Integration] A7[collaboration - Collaborative Office] A8[file - File Collaboration] A9[schedule - Schedule Collaboration] A10[task - Task Collaboration] A11[search - Message Search] A12[archive - Message Archiving] A13[analytics - Data Analysis] end subgraph "Permissions and Audit" B1[permission - Permission Control] B2[audit - Audit Logs] B3[monitoring - Monitoring and Alerting] end end A1 --> B1 A2 --> B1 A3 --> B1 A4 --> B2 A5 --> B2 A6 --> B3

8. Business Value

Value Point	Description
Communication Efficiency	Rich media messages, business integration
Collaborative Office	File collaboration, schedule collaboration
Security Compliance	Message encryption, audit compliance
Business Enablement	Business messages, quick actions
Data Insights	Activity analysis, efficiency analysis
Permission Control	Hierarchical permissions, data isolation

Mail Middleware

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, 5 DOs / 5 Controllers, menu ID starting from 11500, building an enterprise-grade email sending/receiving and marketing automation system

1. Enhancement Positioning & Architecture

1.1 Product Positioning

RuoYiPlus Mail provides enterprise-grade enhancements around three core areas: multi-channel sending, email receiving management, and marketing automation, building a highly reliable, auditable enterprise email infrastructure.

1.2 Module Scale

Metric	Value
Data Objects (DO)	5
Controllers	5
Menu ID Start	11500
Maven Module	yudao-module-mail

1.3 Core Data Tables

Table Name	Description
`mail_attachment`	Attachment Management
`mail_blacklist`	Blacklist Management
`mail_send_log`	Send Log
`mail_receive_log`	Receive Log
`mail_template`	Email Template

graph TB subgraph "RuoYiPlus Mail Enhanced Architecture" subgraph "Sending Layer" A1[Alibaba Cloud DirectMail] A2[AWS SES] A3[Local SMTP] A4[Corporate Email] end subgraph "Engine Layer" B1[Async Sending] B2[Smart Retry] B3[Rate Limiting] B4[Batch Optimization] end subgraph "Business Layer" C1[Template Engine] C2[Email Receiving] C3[Marketing Email] C4[Attachment Management] end subgraph "Monitoring Layer" D1[Full-Chain Tracking] D2[Statistical Analysis] D3[Send Audit] D4[Compliance Reports] end end A1 --> B1 A2 --> B1 A3 --> B1 A4 --> B1 B1 --> B2 B2 --> B3 B3 --> B4 B4 --> C1 C1 --> C2 C2 --> C3 C3 --> C4 C4 --> D1 D1 --> D2 D2 --> D3 D3 --> D4

1.4 Capability Comparison

Dimension	Yudao Native Capability	RuoYiPlus Mail Enhancement
Sending Capability	Simple sending	Multi-channel + async sending
Receiving Capability	None	IMAP/POP3 receiving
Template Management	None	Template engine + variable substitution
Attachment Management	Simple attachments	Multi-storage + version management
Send Monitoring	None	Full-chain tracking + statistical analysis
Marketing Email	None	Marketing email + batch sending
Audit Compliance	Simple logging	Full-chain email send audit

2. Multi-Channel Sending Architecture

2.1 Sending Channel Architecture

graph TB subgraph "Sending Channels" subgraph "Domestic Channels" A1[Alibaba Cloud DirectMail] A2[Tencent Corporate Email] end subgraph "International Channels" B1[AWS SES] end subgraph "Self-built Channels" C1[Local SMTP] end subgraph "Send Engine" D1[Async Sending] D2[Smart Retry] D3[Rate Limiting] D4[Failover] end end A1 --> D1 A2 --> D1 B1 --> D1 C1 --> D1 D1 --> D2 D2 --> D3 D3 --> D4

Channel Type	Applicable Scenarios	Features
Alibaba Cloud DirectMail	Domestic business	High deliverability, domestic optimization
AWS SES	International business	Global coverage, low cost
Local SMTP	Self-built systems	Full control, privacy protection
Corporate Email	Internal enterprise	Enterprise authentication, brand image

2.2 Async Send Engine

mail:
 async:
 enabled: true
 pool-size: 10
 queue-capacity: 1000
 batch-size: 50
 retry:
 max-attempts: 3
 backoff:
 initial-interval: 1000
 multiplier: 2.0
 max-interval: 30000
 rate-limit:
 enabled: true
 qps: 100
 burst: 200

Capability	Description
Async Sending	Thread pool async processing
Smart Retry	Exponential backoff retry strategy
Rate Limiting	Token bucket algorithm rate limiting
Batch Optimization	Batch send optimization
Failover	Automatic channel failover

3. Email Receiving Management

3.1 Receiving Architecture

graph TB subgraph "Email Receiving" subgraph "Receiving Protocols" A1[IMAP] A2[POP3] end subgraph "Receive Processing" B1[Email Parsing] B2[Content Extraction] B3[Attachment Processing] B4[Auto Classification] end subgraph "Receive Storage" C1[Email Archiving] C2[Search & Retrieval] C3[Data Analysis] end end A1 --> B1 A2 --> B1 B1 --> B2 B2 --> B3 B3 --> B4 B4 --> C1 C1 --> C2 C2 --> C3

Capability	Description
IMAP Receiving	Real-time inbox sync
POP3 Receiving	Scheduled email pull
Email Parsing	Content and attachment parsing
Auto Classification	Rule-based auto classification
Auto Reply	Auto reply templates

4. Template Engine Enhancement

4.1 Template Management System

graph TB subgraph "Template Management" subgraph "Template Creation" A1[Template Design] A2[Variable Definition] A3[Style Configuration] A4[Template Review] A5[Template Publishing] end subgraph "Template Types" B1[Business Templates] B2[Marketing Templates] B3[System Templates] end subgraph "Template Application" C1[Variable Substitution] C2[Conditional Rendering] C3[Loop Rendering] C4[Template Preview] end end A1 --> A2 A2 --> A3 A3 --> A4 A4 --> A5 A5 --> B1 A5 --> B2 A5 --> B3 B1 --> C1 B2 --> C1 B3 --> C1 C1 --> C2 C2 --> C3 C3 --> C4

Capability	Description
Thymeleaf Templates	HTML template rendering
Variable Substitution	Dynamic variable injection
Conditional Rendering	Conditional branch display
Template Versioning	Version management, history tracking
Template Testing	Test send, effect preview

5. Marketing Email Enhancement

5.1 Marketing Automation

graph LR A[Trigger Event] --> B{Condition Check} B -->|Satisfied| C[Execute Action] B -->|Not Satisfied| D[Skip] C --> E[Send Email] E --> F[Record Result] F --> G{Follow-up Condition} G -->|Yes| H[Continue Execution] G -->|No| I[End Flow]

mail:
 marketing:
 automation:
 - trigger: "Member Registration"
 template: "Welcome Email"
 delay: 0
 - trigger: "Member Upgrade"
 template: "Upgrade Congratulations"
 delay: 0
 - trigger: "7 Days After Purchase"
 template: "Repurchase Reminder"
 delay: 7d
 - trigger: "Birthday"
 template: "Birthday Greeting"
 condition: "member.birthday == today"

5.2 Blacklist Management

Capability	Description
Auto Blacklist	Bounced emails automatically added to blacklist
Manual Blacklist	Manually add to blacklist
Blacklist Filtering	Auto filter when sending
Blacklist Appeal	Blacklist appeal for removal

6. Send Monitoring & Analytics

6.1 Full-Chain Tracking

graph LR A[Send Request] --> B[Queue Waiting] B --> C[Send Execution] C --> D[Delivery Status] D --> E[Open Tracking] E --> F[Click Tracking] A -.-> G[Audit Log] B -.-> G C -.-> G D -.-> G E -.-> G F -.-> G

Tracking Node	Description
Send Request	Send request record
Queue Status	Queue waiting status
Send Execution	Send execution status
Delivery Status	Delivery success/failure
Open Tracking	Email open tracking
Click Tracking	Link click tracking

6.2 Email Send Audit

All email send operations are recorded with complete audit logs, supporting email send traceability.

Audit Item	Description
Send Request	Records sender, recipient, send time
Email Content	Records email subject, content (encrypted storage)
Send Result	Records send success/failure, failure reason
Open Record	Records email open time, open count
Click Record	Records link click time, click count

6.3 Statistical Analysis

Analysis Dimension	Metrics
Send Statistics	Send volume, success rate, failure rate
Delivery Analysis	Delivery rate, bounce rate, bounce reasons
Effect Analysis	Open rate, click rate, conversion rate
Channel Analysis	Channel performance comparison
Template Analysis	Template effect comparison

7. Technical Architecture

graph TB subgraph "yudao-module-mail-plus" subgraph "mail-biz" A1[adapter] A2[storage] A3[engine] A4[template] A5[receive] A6[marketing] A7[blacklist] A8[tracking] A9[analytics] end subgraph "Permissions & Audit" B1[permission] B2[audit] B3[masking] end end A1 --> B1 A2 --> B2 A3 --> B2 A4 --> B3 A5 --> B2 A6 --> B2

8. Business Value

Value Point	Description
High Deliverability	Multi-channel, intelligent routing
Reliable Sending	Async sending, smart retry
Marketing Empowerment	Marketing email, automated triggers
Effect Tracking	Open rate, click rate analysis
Cost Optimization	Channel selection, batch optimization
Compliance Audit	Full-chain tracking, send audit

Pay Payment System

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, 14 DOs / 19 Controllers, menu ID starting from 12500, building a unified payment and fund management platform

1. Enhancement Positioning and Architecture

1.1 Product Positioning

RuoYiPlus Pay focuses on three core areas for enterprise enhancement: Multi-Channel Payment, Fund Management, and Transaction Security, building a unified payment infrastructure.

1.2 Module Scale

Metric	Value
Data Objects (DO)	14
Controllers	19
Menu ID Start	12500
Maven Module	yudao-module-pay

1.3 Core Data Tables

Table Name	Description
`pay_order`	Payment Orders
`pay_refund`	Refund Management
`pay_transfer`	Transfer Management
`pay_wallet`	Wallet Management
`pay_recharge`	Recharge Management
`pay_channel`	Payment Channels
`pay_app`	Payment Applications

graph TB subgraph "RuoYiPlus Pay Enhanced Architecture" subgraph "Payment Channels" A1[WeChat Pay] A2[Alipay] A3[UnionPay] A4[Balance Payment] end subgraph "Payment Capabilities" B1[Payment Ordering] B2[Payment Refund] B3[Transfer Payment] B4[Wallet Management] end subgraph "Fund Management" C1[Recharge Management] C2[Reconciliation Management] C3[Bill Management] end subgraph "Control Layer" D1[Payment Security] D2[Risk Control Management] D3[Operation Audit] end end A1 --> B1 A2 --> B1 A3 --> B1 A4 --> B1 B1 --> B2 B2 --> B3 B3 --> B4 B4 --> C1 C1 --> C2 C2 --> C3 B1 --> D1 B2 --> D2 C3 --> D3

1.4 Capability Comparison

Dimension	Traditional Solution	RuoYiPlus Pay Enhanced
Payment Channels	Single channel	WeChat + Alipay + UnionPay
Refund Management	Manual processing	Automatic refund + original route return
Wallet Management	None	Balance + recharge + withdrawal
Reconciliation	Manual reconciliation	Automatic reconciliation + discrepancy handling
Transfer Payment	None	Enterprise payment to user balance
Security & Risk	None	Payment security + risk control
Audit & Compliance	Simple logging	Full-chain payment audit

2. Payment Channel Management

2.1 Multi-Channel Access

graph TB subgraph "Payment Channels" subgraph "WeChat Pay" A1[JSAPI Payment] A2[Mini Program Payment] A3[H5 Payment] A4[Native Payment] end subgraph "Alipay" B1[Mobile Website Payment] B2[Desktop Website Payment] B3[QR Code Payment] end subgraph "UnionPay" C1[Gateway Payment] C2[No-Redirect Payment] end subgraph "Balance Payment" D1[Wallet Balance] D2[Points Deduction] end end

Payment Channel	Supported Methods
WeChat Pay	JSAPI / Mini Program / H5 / Native / APP
Alipay	Mobile Website / Desktop Website / QR Code / APP
UnionPay	Gateway Payment / No-Redirect Payment
Balance Payment	Wallet Balance / Points Deduction

3. Payment Transaction Management

3.1 Payment Flow

graph TB A[Business Ordering] --> B[Create Payment Order] B --> C[Select Payment Channel] C --> D[Initiate Payment] D --> E{Payment Result} E -->|Success| F[Payment Callback] E -->|Failed| G[Payment Closure] F --> H[Business Notification] H --> I[Transaction Complete] D --> D1[Get Payment Parameters] D --> D2[Invoke Payment] D --> D3[Wait for Payment] F --> F1[Signature Verification] F --> F2[Update Status] F --> F3[Notify Business]

3.2 Core Capabilities

Capability	Description
Payment Ordering	Unified payment order interface
Payment Refund	Original route refund + partial refund
Payment Query	Real-time payment status query
Payment Callback	Async notification + signature verification
Payment Closure	Timeout closure + manual closure

4. Wallet and Fund Management

4.1 Wallet System

graph LR A[Recharge] --> B[Wallet Balance] B --> C[Consumption Payment] B --> D[Withdrawal] C --> E[Transaction Records] D --> E A --> E

Capability	Description
Wallet Recharge	Multi-channel recharge
Balance Payment	Wallet balance payment
Withdrawal Management	Withdrawal request + approval
Bill Management	Transaction records + billing
Reconciliation	Automatic reconciliation + discrepancy handling

5. Technical Architecture

graph TB subgraph "yudao-module-pay-plus" subgraph "pay-biz" A1[order Payment Orders] A2[refund Refund Management] A3[transfer Transfer Management] A4[wallet Wallet Management] A5[recharge Recharge Management] A6[channel Channel Management] A7[app Application Management] A8[notify Callback Notification] A9[reconciliation Reconciliation Management] end subgraph "Permissions & Audit" B1[security Payment Security] B2[audit Audit Logs] B3[risk Risk Control Management] end end A1 --> B1 A2 --> B2 A3 --> B2 A4 --> B3 A5 --> B2

6. Business Value

Value Point	Description
Payment Convenience	Unified multi-channel access
Fund Security	Payment security + risk control management
Efficient Reconciliation	Automatic reconciliation + discrepancy handling
Fund Management	Wallet + recharge + withdrawal
Compliance Audit	Full-chain payment audit
Flexible Extension	Pluggable payment channels

FITS Issue Feedback System

Mon, 01 Jan 0001 00:00:00 +0000

Based on the latest RuoyiPlus backend architecture, 7 DOs / 2 Controllers, menu IDs starting from 8000, building an enterprise-level issue feedback and tracking system

1. Enhancement Positioning and Architecture

1.1 Product Positioning

RuoYiPlus FITS provides enterprise-level enhancements around three core areas: Issue Tracking, Exception Reporting, and Project Management, building an efficient issue feedback and resolution closed loop.

1.2 Module Scale

Metric	Value
Data Objects (DO)	7
Controllers	2
Menu ID Start	8000
Maven Module	yudao-module-fits

1.3 Core Data Tables

Table Name	Description
`fits_issue`	Issue Management
`fits_project`	Project Management
`fits_exception_report`	Exception Report

graph TB subgraph "RuoYiPlus FITS Enhancement Architecture" subgraph "Issue Management" A1[Issue Creation] A2[Issue Assignment] A3[Issue Processing] A4[Issue Closure] end subgraph "Exception Report" B1[Exception Capture] B2[Exception Classification] B3[Exception Statistics] end subgraph "Project Management" C1[Project Configuration] C2[Member Management] end subgraph "Governance Layer" D1[Permission Control] D2[Operation Audit] end end A1 --> A2 A2 --> A3 A3 --> A4 B1 --> B2 B2 --> B3 C1 --> C2 A1 --> D1 B1 --> D2

1.4 Capability Comparison

Dimension	Traditional Approach	RuoYiPlus FITS Enhancement
Issue Management	Simple recording	Full-process tracking + assignment
Exception Reporting	Scattered logs	Unified exception capture + classification
Project Management	None	Multi-project independent management
Statistical Analysis	None	Issue trends + exception statistics
Permission Control	None	Project-level permission isolation
Audit Compliance	None	Operation audit + change traceability

2. Issue Management

2.1 Issue Workflow

graph TB A[Issue Creation] --> B[Issue Assignment] B --> C[Issue Processing] C --> D{Resolved?} D -->|Yes| E[Verification & Closure] D -->|No| F[Re-process] F --> C E --> G[Issue Archiving] A --> A1[Issue Description] A --> A2[Priority] A --> A3[Attachment Upload] C --> C1[Processing Records] C --> C2[Status Update] C --> C3[Notify Stakeholders]

Capability	Description
Issue Creation	Description + priority + attachments
Issue Assignment	Manual assignment + auto assignment
Issue Processing	Processing records + status transitions
Issue Closure	Verification + archiving
Notification	Email + in-app notifications

3. Exception Report Management

3.1 Exception Handling

graph LR A[Exception Capture] --> B[Exception Classification] B --> C[Exception Aggregation] C --> D[Trend Analysis] D --> E[Alert Notification] B --> B1[System Exception] B --> B2[Business Exception] B --> B3[Performance Exception] C --> C1[Similar Aggregation] C --> C2[Frequency Statistics]

Capability	Description
Exception Capture	Auto capture + manual reporting
Exception Classification	System/business/performance classification
Exception Aggregation	Similar exception aggregation analysis
Trend Analysis	Exception trends + frequency statistics
Alert Notification	Threshold alerts + notifications

4. Technical Architecture

graph TB subgraph "yudao-module-fits-plus" subgraph "fits-biz" A1[issue Issue Management] A2[project Project Management] A3[exception Exception Report] A4[notification Notification Management] A5[analytics Statistical Analysis] end subgraph "Permission & Audit" B1[permission Permission Control] B2[audit Audit Log] end end A1 --> B1 A2 --> B1 A3 --> B2 A4 --> B2

5. Business Value

Value Point	Description
Issue Closed Loop	Create → Assign → Process → Close
Exception Monitoring	Real-time capture + trend analysis
Efficiency Improvement	Auto assignment + notification reminders
Data Insights	Issue trends + exception statistics
Multi-Project Support	Multi-project independent management
Audit Compliance	Operation audit + change traceability

Changelog

Mon, 01 Jan 0001 00:00:00 +0000

Version Evolution

RuoYi-Vue-Pro started from v2.0.0 and has been continuously iterating to date, with a total codebase of approximately 260,000 lines (160,000 lines of source code, 60,000 lines of comments, 1,121+ unit tests).

v2.6.1 (2025-07-19) Key Updates

Large-Scale Vben5 + Ant Design Migration:

Migration Module	Status
BPM Workflow	✅ Completed
CRM Customer Management	✅ Completed
Pay Payment Center	✅ Completed
Member Center	✅ Completed
AI Large Model	✅ Completed
Vben5 + Element Plus Code Generation Examples	✅ Added

Monthly Update Records

Time	Major Updates
2026-05	System optimization and bug fixes
2026-04	Feature iteration
2026-03	Feature iteration
2026-02	Feature iteration
2026-01	Feature iteration
2025-12	Feature iteration
2025-11	Feature iteration
2025-10	Feature iteration
2025-09	Feature iteration
2025-08	Feature iteration
2025-07	v2.6.1: Large-Scale Vben5 + Ant Design Migration

Technical Metrics

Metric	Value
Total Lines of Code	259,995
Source Code Lines	161,332
Comment Lines	59,755
Unit Tests	1,121+
Business Subsystems	14
Total Database Tables	300+
Supported Frontend Versions	4 (Vue3 / Vben5 / Vue2 / uni-app)

⚡️ Turn Jupyter Notebooks into Blog Posts

Mon, 15 Jul 2024 00:00:00 +0000

As a researcher or data scientist, your work often lives in Jupyter Notebooks. But sharing those insights effectively usually means taking screenshots, messy copy-pasting, or exporting to PDF.

Hugo Blox changes that. With the {{< notebook >}} shortcode, you can render your actual .ipynb files directly as beautiful, interactive blog posts or project pages. Keep your code, outputs, and narrative in one place.

Table of Contents

Why publish notebooks?

Tip

Reproducible Research: By publishing the actual notebook, you allow others to download and run your code, verifying your results and building upon your work.

No more screenshots – Render crisp code and vector plots directly from your source.
Theme consistent – Notebooks automatically adapt to your site’s theme (including dark mode).
Flexible sourcing – Display notebooks from your assets/ folder, page bundles, or even directly from a remote GitHub URL.
Interactive – Users can copy code blocks or download the full notebook to run locally.

Example: Data Science Workflow

Below is a live example of a notebook rendered right here in this post. Notice how the markdown, code, and outputs (text, HTML, and JSON) are all preserved and styled.

Launch Readiness Analysis

Python · Kernel: Python 3 · nbformat 4.5 · 6 cells

Download notebook

Language: Python
Version: 3.11
Kernel: Python 3 python3
nbformat: 4.5
Authors: Ownable CMS

Markdown

Ship Notebook Stories in Minutes

Hugo Blox Notebook renderer turns your .ipynb experiments into beautiful long-form posts. Use this sample to see how markdown, code, and outputs flow together.

Markdown

Drop notebooks inside assets/notebooks/ (or import them as page resources).
Reference them with {{</* notebook src="your.ipynb" */>}}.
Control code, outputs, metadata badges, and download links via shortcode params.

In [1]

demo quickstart

1
2
3
4
5
6


import math
accuracy = 0.982
print("Collecting data...")
print("Training notebook-ready block...")
print("Done!")
accuracy

Collecting data...
Training notebook-ready block...
Done!

0.982

In [2]

1
2


from IPython.display import HTML
HTML("<div style='font-family:Inter,ui-sans-serif;'><strong>Launch Readiness:</strong> <span style='color:#22c55e;'>98.2% confidence</span><br><em>Notebook blocks are theme-aware and dark-mode friendly.</em></div>")

Launch Readiness: 98.2% confidence
Notebook blocks are theme-aware and dark-mode friendly.

In [3]

metrics

1
2
3
4
5
6
7
8


metrics = {
 'metrics': {
 'engagement_rate': 0.73,
 'read_time_minutes': 4.6,
 'subscribers': 1280
 }
}
metrics

{
"metrics": {
"engagement_rate": 0.73,
"read_time_minutes": 4.6,
"subscribers": 1280
}
}

Markdown

Tip: Pair this block with Call-to-Action cards or the Embed shortcode to link to GitHub repos, datasets, or ARXIV preprints.

How to add a notebook

Save your notebook. Place your .ipynb file in assets/notebooks/ (for global access) or inside a page bundle (like content/blog/my-post/analysis.ipynb).
Add the shortcode. In any Markdown page, simply use: {{< notebook src="analysis.ipynb" >}}
Customize. You can hide code cells for non-technical audiences (show_code=false) or just show the output (show_outputs=true).

Important

Hugo Blox respects your privacy. Notebook rendering happens statically at build time—no third-party services required.

Next steps

Try it out: Drop one of your existing notebooks into this site and see how it looks.
Link your papers: Use the Embed shortcode to link your notebook to your latest arXiv preprint or GitHub repository.
Get help: Join the community on or check the .

Happy researching! 🚀

RuoYiPlus Enterprise Enhancement

Fri, 28 Jun 2024 00:00:00 +0000

Out-of-the-box enhancement solutions for enterprise-scale operations, built on RuoYi-Vue-Pro and Yudao.

14 Major Modules: Security & compliance, identity governance (IAM/SSO/OAuth2), commercialization (license/version matrix), enterprise collaboration (IM/PM/CS), email infrastructure, and more. Covering four core domains, filling the “last mile” gap between open-source frameworks and enterprise deployment.

Exchange Matching Engine

Sat, 01 Jun 2024 00:00:00 +0000

Exchange matching engine based on Rust + Raft consensus protocol.

Key Capabilities:

Order book & matching: Strict price-time priority algorithm, full lifecycle management for limit/market orders
Raft State Machine Replication (SMR): Order commands replicated via Raft Log, with Snapshot + WAL mechanisms
Multi-symbol dynamic management: Raft Group sharding by symbol for horizontal scaling
Account & risk control: Rate limiting, position checks, contract/leverage/liquidation, options Greeks calculation
Clearing, settlement & market data: Settlement flow design, on-chain deposit/withdrawal, Level 2/3 push optimization

PyRebuilderSharp

Mon, 20 May 2024 00:00:00 +0000

Cross-platform Python bytecode decompiler based on .NET 10 + Avalonia UI.

Key Innovation — Block-Level Fault Tolerance:

Four-stage modular pipeline: PycReader → BlockScanner → ControlFlowScanner → AstBuilder → PythonCodeGenerator
Each basic block independently performs stack simulation and AST construction — one block failure doesn’t affect 99% of remaining code
182 real .pyc baseline test suite (Python 3.6–3.13), 100% pass rate
AI-assisted deep application: idea validation, boundary completion, pattern-matching code generation

QuantByQlib

Fri, 15 Mar 2024 00:00:00 +0000

AI-driven quantitative stock selection system based on Qlib + LightGBM with dual LLM fallback architecture.

Key Capabilities:

Dual LLM fallback (Claude primary + DeepSeek fallback) for high-quality stock analysis reports
RD-Agent factor discovery auto-injected into LightGBM strategies via standardized IC validation pipelines
“Discovery → Validation → Production” closed loop
Combining local ML precision with cloud LLM versatility

Example Talk: Recent Work

Mon, 01 Jan 2024 00:00:00 +0000

Example Talk

Dr. Alex Johnson · Meta AI

Research Overview

Multimodal LLMs
Efficient training
Responsible AI

Code & Math

def score(x: int) -> int:
 return x * x

$$ E = mc^2 $$

Dual Column Layout

Left Column

Point A
Point B
Point C

Right Column

Detail 1
Detail 2
Detail 3

Main Content (2/3 width)

This column takes up twice the space of the right column.

def example():
 return "code works too"

Note
Key points in smaller column

Image + Text Layout

Results

95% accuracy
10x faster inference
Lower memory usage

Breakthrough!

Speaker Notes

Press S to open presenter view with notes!

This slide has hidden speaker notes below.

Note:

This is a speaker note (only visible in presenter view)
Press S key to open presenter console
Perfect for remembering key talking points
Can include reminders, timing, references
Supports Markdown formatting too!

Progressive Reveals

Content appears step-by-step:

First point appears Then the second point Finally the conclusion This one can be highlighted!

Note: Use fragments to control pacing and maintain audience attention. Each fragment appears on click.

Diagrams with Mermaid

graph LR A[Research Question] --> B{Hypothesis} B -->|Valid| C[Experiment] B -->|Invalid| D[Revise] C --> E[Analyze Data] E --> F{Significant?} F -->|Yes| G[Publish] F -->|No| D

Perfect for: Workflows, architectures, processes

Note: Mermaid diagrams are created from simple text. They’re version-controllable and edit anywhere!

Research Results

Model	Accuracy	Speed	Memory
Baseline	87.3%	1.0x	2GB
Ours (v1)	92.1%	1.5x	1.8GB
Ours (v2)	95.8%	2.3x	1.2GB

Key Finding: 8.5% improvement over baseline with 40% memory reduction

Note: Tables are perfect for comparative results. Markdown tables are simple and version-control friendly.

Custom Backgrounds

This slide has a blue background!

You can customize:

Background colors
Background images
Gradients
Videos (yes, really!)

Use {{< slide background-color="#hex" >}}

There’s more content below! ⬇️

Press the Down Arrow to see substeps.

Note: This demonstrates Reveal.js’s vertical slide feature. Great for optional details or deep dives.

Substep 1: Details

This is additional content in a vertical stack.

Navigate down for more, or right to skip to next topic →

Substep 2: More Details

Even more detailed information.

Press Up Arrow to go back, or Right Arrow to continue.

Citations & Quotes

“The best way to predict the future is to invent it.”

— Alan Kay

Or reference research:

Recent work by Smith et al. (2024) demonstrates that Markdown-based slides improve reproducibility by 78% compared to proprietary formats¹.

Media: YouTube Videos

Note: Embed YouTube videos with just the video ID. Perfect for demos, tutorials, or interviews.

Media: All Options

Embed various media types with simple shortcodes:

YouTube: {{< youtube VIDEO_ID >}}
Bilibili: {{< bilibili id="BV1..." >}}
Local videos: {{< video src="file.mp4" controls="yes" >}}
Audio: {{< audio src="file.mp3" >}}

Perfect for demos, interviews, tutorials, or podcasts!

Note: All media types work seamlessly in slides. Just use the appropriate shortcode.

Interactive Elements

Try these keyboard shortcuts:

→ ← : Navigate slides
↓ ↑ : Vertical navigation
S : Speaker notes
F : Fullscreen
O : Overview mode
/ : Search
ESC : Exit modes

Hidden Slide Demo (Inline Comment)

This slide is hidden using the  comment method.

Perfect for:

Speaker-only content
Backup slides
Work-in-progress content

Note: This slide won’t appear in the presentation but remains in source for reference.

Thanks

Questions?

🌐 Website:
🐦 X/Twitter:
💬 Discord:
⭐ GitHub:

All slides created with Markdown • No vendor lock-in • Edit anywhere

Note: Thank you for your attention! Feel free to reach out with questions or contributions.

🎨 Branding Your Slides

Add your identity to every slide with simple configuration!

What you can add:

Element	Position Options
Logo	top-left, top-right, bottom-left, bottom-right
Title	Same as above
Author	Same as above
Footer Text	Same + bottom-center

Edit the branding: section in your slide’s front matter (top of file).

📁 Adding Your Logo

Place your logo in assets/media/ folder
Use SVG format for best results (auto-adapts to any theme!)
Add to front matter:

branding:
 logo:
 filename: "your-logo.svg" # Must be in assets/media/
 position: "top-right"
 width: "60px"

Tip: SVGs with fill="currentColor" automatically match theme colors!

📝 Title & Author Overlays

Show presentation title and/or author on every slide:

branding:
 title:
 show: true
 position: "bottom-left"
 text: "Short Title" # Optional: override long page title

 author:
 show: true
 position: "bottom-right"

Author is auto-detected from page front matter (author: or authors:).

📄 Footer Text

Add copyright, conference name, or any persistent text:

branding:
 footer:
 text: "© 2026 RuoyiPlus · Ruoyi Plus 2026"
 position: "bottom-center"

Tip: Supports Markdown! Use [Link](url) for clickable links.

🔇 Hiding Branding Per-Slide

Sometimes you want a clean slide (title slides, full-screen images).

Add this comment at the start of your slide content:

<!-- no-branding -->
## My Clean Slide

Content here...

☝️ This slide uses  — notice no logo or overlays!

🔇 Selective Hiding

Hide just the header (logo + title):

<!-- no-header -->

Or just the footer (author + footer text):

<!-- no-footer -->

☝️ This slide uses  — footer still visible below!

✅ Quick Reference

Comment	Hides
`<!-- no-branding -->`	Everything (logo, title, author, footer)
`<!-- no-header -->`	Logo + Title overlay
`<!-- no-footer -->`	Author + Footer text

☝️ This slide uses  — logo still visible above!

🚀 Get Started

Copy this example’s front matter as a starting point
Replace logo with yours in assets/media/
Customize positions and text
Use  for special slides

Pro tip: Set site-wide defaults in config/_default/params.yaml under slides.branding!

Smith, J. et al. (2024). Open Science Presentations. Nature Methods. ↩︎

🎉 Easily create your own simple yet highly customizable blog

Fri, 27 Oct 2023 00:00:00 +0000

Welcome 👋

Table of Contents

Overview

The Hugo Blox website builder for Hugo, along with its starter templates, is designed for professional creators, educators, and teams/organizations - although it can be used to create any kind of site
The template can be modified and customised to suit your needs. It’s a good platform for anyone looking to take control of their data and online identity whilst having the convenience to start off with a no-code solution (write in Markdown and customize with YAML parameters) and having flexibility to later add even deeper personalization with HTML and CSS
You can work with all your favourite tools and apps with hundreds of plugins and integrations to speed up your workflows, interact with your readers, and much more

Get Started

Quick Start Guide

New to Hugo Blox? Follow these steps to get your site up and running in minutes!

👉
📚
💬 or
🐦 Twitter: #MadeWithHugoBlox
💡
⬆️ Updating Hugo Blox? View the and

Important

Remember to backup your site before making major updates!

Crowd-funded open-source software

To help us develop this template and software sustainably under the MIT license, we ask all individuals and businesses that use it to help support its ongoing maintenance and development via sponsorship.

As a token of appreciation for sponsoring, you can unlock awesome rewards and extra features 🦄✨

Ecosystem

: Automatically import publications from BibTeX

Inspiration

are building with this template.

Features

Enhanced Markdown Support

Hugo Blox now supports GitHub and Obsidian-style callouts! Use standard Markdown alert syntax like > [!NOTE] for better portability.

Page builder - Create anything with no-code and
Edit any type of content - Blog posts, publications, talks, slides, projects, and more!
Create content in , , or
Plugin System - Fully customizable
Display Code and Math - Code syntax highlighting and LaTeX math supported
Integrations - , , Maps, Contact Forms, and more!
Beautiful Site - Simple and refreshing one-page design
Industry-Leading SEO - Help get your website found on search engines and social media
Media Galleries - Display your images and videos with captions in a customizable gallery
Mobile Friendly - Look amazing on every screen with a mobile friendly version of your site
Multi-language - 35+ language packs including English, Chinese, and Português
Multi-user - Each author gets their own profile page
Privacy Pack - Assists with GDPR
Stand Out - Bring your site to life with animation, parallax backgrounds, and scroll effects
One-Click Deployment - No servers. No databases. Only files.

Version Requirements

The new Markdown alert syntax requires Hugo v0.132.0 or later. Make sure you’re using a compatible version!

Themes

Hugo Blox and its templates come with automatic day (light) and night (dark) mode built-in. Visitors can choose their preferred mode by clicking the sun/moon icon in the header.

for your site. Themes are fully customizable.

License

Released under the license.

PyTorch

Thu, 26 Oct 2023 00:00:00 +0000

PyTorch is a Python package that provides tensor computation (like NumPy) with strong GPU acceleration.

scikit-learn

Thu, 26 Oct 2023 00:00:00 +0000

scikit-learn is a Python module for machine learning built on top of SciPy and is distributed under the 3-Clause BSD license.

🧠 Sharpen your thinking with a second brain

Thu, 26 Oct 2023 00:00:00 +0000

Create a personal knowledge base and share your knowledge with your peers.

Hugo Blox web framework empowers you with one of the most flexible note-taking capabilities out there.

Create a powerful knowledge base that works on top of a local folder of plain text Markdown files.

Use it as your second brain, either publicly sharing your knowledge with your peers via your website, or via a private GitHub repository and password-protected site just for yourself.

Mindmaps

Hugo Blox supports a Markdown extension for mindmaps.

With this open format, can even edit your mindmaps in other popular tools such as Obsidian.

Simply insert a Markdown code block labelled as markmap and optionally set the height of the mindmap as shown in the example below.

Mindmaps can be created by simply writing the items as a Markdown list within the markmap code block, indenting each item to create as many sub-levels as you need:


```markmap {height="200px"}
- Hugo Modules
- Hugo Blox
- netlify
- netlify-cms
- slides
```

renders as

- Hugo Modules
- Hugo Blox
- netlify
- netlify-cms
- slides

Anh here’s a more advanced mindmap with formatting, code blocks, and math:


```markmap
- Mindmaps
- Links
- [Hugo Blox Docs](https://docs.hugoblox.com/)
- [Discord Community](https://discord.gg/z8wNYzb)
- [GitHub](https://github.com/HugoBlox/kit)
- Features
- Markdown formatting
- **inline** ~~text~~ *styles*
- multiline
text
- `inline code`
- Math: $x = {-b \pm \sqrt{b^2-4ac} \over 2a}$
```

renders as

- Mindmaps
- Links
- [Hugo Blox Docs](https://docs.hugoblox.com/)
- [Discord Community](https://discord.gg/z8wNYzb)
- [GitHub](https://github.com/HugoBlox/kit)
- Features
- Markdown formatting
- **inline** ~~text~~ *styles*
- multiline
text
- `inline code`
- Math: $x = {-b \pm \sqrt{b^2-4ac} \over 2a}$

Highlighting

Highlight important text with mark:

<mark>Highlighted text</mark>

Callouts

Use (aka asides, hints, or alerts) to draw attention to notes, tips, and warnings.

Use the > [!NOTE] syntax to create a callout.

> [!NOTE]
> A Markdown aside is useful for displaying notices, hints, or definitions to your readers.

renders as

Note

A Markdown aside is useful for displaying notices, hints, or definitions to your readers.

Or use the warning callout type so your readers don’t miss critical details:

Warning

A Markdown aside is useful for displaying notices, hints, or definitions to your readers.

📈 Communicate your results effectively with the best data visualizations

Wed, 25 Oct 2023 00:00:00 +0000

Hugo Blox is designed to give technical content creators a seamless experience. You can focus on the content and Hugo Blox handles the rest.

Use popular tools such as Plotly, Mermaid, and data frames.

Embed Rich Content

HuggingFace Model

google/embeddinggemma-300m

sentence-similarity

1.56514M

1.74k

HuggingFace Dataset

fka/prompts.chat

dataset

a.k.a. Awesome ChatGPT Prompts This is a Dataset Repository mirror of prompts.chat — a social platform for AI prompts. 📢 Notice This Hugging Face dataset is a mirror. For the …

30.917k

9.745k

GitHub Repository

kit

by HugoBlox • HTML

🧱 Describe your site, AI builds it, you own it as Markdown. Snap together Tailwind blocks like Lego — landing pages, blogs, portfolios, docs & more. No AI slop. Free to deploy anywhere 👇

2.948k

9.531k

academic blog documentation-tool +17

Custom embed with manual data

My Custom Resource

example.com

A great resource for learning

Custom Images

Embed beautiful images from any source with Hugo image processing (Unsplash, custom URLs, etc.):

Data Visualization Guide

example.com

Beautiful data visualization workspace

You can also add images to any platform embed:

plotly.py

by plotly • Python

The interactive graphing library for Python ✨

2.814k

769

18.623k

d3 dashboard declarative +11

Charts

Hugo Blox supports the popular format for interactive data visualizations. With Plotly, you can design almost any kind of visualization you can imagine!

Save your Plotly JSON in your page folder, for example line-chart.json, and then add the {{< chart data="line-chart" >}} shortcode where you would like the chart to appear.

Demo:

You might also find the useful.

Diagrams

Hugo Blox supports the Mermaid Markdown extension for diagrams.

An example flowchart:

```mermaid
graph TD
A[Hard] -->|Text| B(Round)
B --> C{Decision}
C -->|One| D[Result 1]
C -->|Two| E[Result 2]
```

renders as

graph TD A[Hard] -->|Text| B(Round) B --> C{Decision} C -->|One| D[Result 1] C -->|Two| E[Result 2]

An example sequence diagram:

```mermaid
sequenceDiagram
Alice->>John: Hello John, how are you?
loop Healthcheck
John->>John: Fight against hypochondria
end
Note right of John: Rational thoughts!
John-->>Alice: Great!
John->>Bob: How about you?
Bob-->>John: Jolly good!
```

renders as

sequenceDiagram Alice->>John: Hello John, how are you? loop Healthcheck John->>John: Fight against hypochondria end Note right of John: Rational thoughts! John-->>Alice: Great! John->>Bob: How about you? Bob-->>John: Jolly good!

An example class diagram:

```mermaid
classDiagram
Class01 <|-- AveryLongClass : Cool
Class03 *-- Class04
Class05 o-- Class06
Class07 .. Class08
Class09 --> C2 : Where am i?
Class09 --* C3
Class09 --|> Class07
Class07 : equals()
Class07 : Object[] elementData
Class01 : size()
Class01 : int chimp
Class01 : int gorilla
Class08 <--> C2: Cool label
```

renders as

classDiagram Class01 <|-- AveryLongClass : Cool Class03 *-- Class04 Class05 o-- Class06 Class07 .. Class08 Class09 --> C2 : Where am i? Class09 --* C3 Class09 --|> Class07 Class07 : equals() Class07 : Object[] elementData Class01 : size() Class01 : int chimp Class01 : int gorilla Class08 <--> C2: Cool label

An example state diagram:

```mermaid
stateDiagram
[*] --> Still
Still --> [*]
Still --> Moving
Moving --> Still
Moving --> Crash
Crash --> [*]
```

renders as

stateDiagram [*] --> Still Still --> [*] Still --> Moving Moving --> Still Moving --> Crash Crash --> [*]

Data Frames

Save your spreadsheet as a CSV file in your page’s folder and then render it by adding the Table shortcode to your page:

{{< table path="results.csv" header="true" caption="Table 1: My results" >}}

renders as

Table 1: My results
customer_id	score
1	0
2	0.5
3	1

Interactive Buttons

Add engaging call-to-action buttons to your data visualization posts:

Basic Buttons

Learn Plotly

{{< button url="/" >}}Contact Us{{< /button >}}

{{< button url="https://plotly.com/python/" new_tab="true" style="secondary" >}}Learn Plotly{{< /button >}}

Styled Buttons for Data Actions

View Dashboard

Download Data

View Source Code

{{< button url="#" style="primary" size="lg" align="center" icon="chart-bar" >}}View Dashboard{{< /button >}}

{{< button url="/data/results.csv" style="outline" icon="document-arrow-down" >}}Download Data{{< /button >}}

{{< button url="https://github.com/HugoBlox" new_tab="true" style="ghost" icon="arrow-top-right-on-square" icon_position="right" >}}View Source Code{{< /button >}}

Multiple Aligned Buttons

Try Jupyter

Open in Colab

{{< button url="https://jupyter.org/" new_tab="true" style="secondary" rounded="full" align="center" >}}Try Jupyter{{< /button >}}

{{< button url="https://colab.research.google.com/" new_tab="true" style="primary" rounded="full" align="center" icon="rocket-launch" >}}Open in Colab{{< /button >}}

👩🏼‍🏫 Teach academic courses

Tue, 24 Oct 2023 00:00:00 +0000

is designed to give technical content creators a seamless experience. You can focus on the content and the HugoBlox Kit which this template is built upon handles the rest.

Embed videos, podcasts, code, LaTeX math, and even test students!

On this page, you’ll find some examples of the types of technical content that can be rendered with Hugo Blox.

Citation

Here’s an example of citing a publication using the cite shortcode:

Delon XIE (2019). An example preprint / working paper.

Preprint Code Slides Dataset Poster Source Document Video Custom Link Preprint

You can also use the default view by omitting the view parameter:

Delon XIE

Equal contribution

, Robert Ford

Equal contribution

(2013). An example conference paper. ICW. Best Paper Award

PDF Code Dataset Slides Source Document Video PDF DOI

Video

Teach your course by sharing videos with your students. Choose from one of the following approaches:

Youtube:

{{< youtube D2vj0WcvH5c >}}

Bilibili:

{{< bilibili BV1WV4y1r7DF >}}

Video file

Videos may be added to a page by either placing them in your assets/media/ media library or in your , and then embedding them with the video shortcode:

{{< video src="my_video.mp4" controls="yes" >}}

Podcast

You can add a podcast or music to a page by placing the MP3 file in the page’s folder or the media library folder and then embedding the audio on your page with the audio shortcode:

{{< audio src="ambient-piano.mp3" >}}

Try it out:

Test students

Provide a simple yet fun self-assessment by revealing the solutions to challenges with the spoiler shortcode:

{{< spoiler text="👉 Click to view the solution" >}}
You found me!
{{< /spoiler >}}

renders as

👉 Click to view the solution

You found me 🎉

Math

HugoBlox Kit supports a Markdown extension for $\LaTeX$ math. Enable math by setting the math: true option in your page’s front matter, or enable math for your entire site by toggling math in your config/_default/params.yaml file:

features:
 math:
 enable: true

To render inline or block math, wrap your LaTeX math with $...$ or $$...$$, respectively.

Example math block:

$$
\gamma_{n} = \frac{ \left | \left (\mathbf x_{n} - \mathbf x_{n-1} \right )^T \left [\nabla F (\mathbf x_{n}) - \nabla F (\mathbf x_{n-1}) \right ] \right |}{\left \|\nabla F(\mathbf{x}_{n}) - \nabla F(\mathbf{x}_{n-1}) \right \|^2}
$$

renders as

$$\gamma_{n} = \frac{ \left | \left (\mathbf x_{n} - \mathbf x_{n-1} \right )^T \left [\nabla F (\mathbf x_{n}) - \nabla F (\mathbf x_{n-1}) \right ] \right |}{\left \|\nabla F(\mathbf{x}_{n}) - \nabla F(\mathbf{x}_{n-1}) \right \|^2}$$

Example inline math $\nabla F(\mathbf{x}_{n})$ renders as $\nabla F(\mathbf{x}_{n})$.

Example multi-line math using the math linebreak (\\):

$$f(k;p_{0}^{*}) = \begin{cases}p_{0}^{*} & \text{if }k=1, \\
1-p_{0}^{*} & \text{if }k=0.\end{cases}$$

renders as

$$ f(k;p_{0}^{*}) = \begin{cases}p_{0}^{*} & \text{if }k=1, \\ 1-p_{0}^{*} & \text{if }k=0.\end{cases} $$

Code

HugoBlox Kit utilises Hugo’s Markdown extension for highlighting code syntax. The code theme can be selected in the config/_default/params.yaml file.

```python
import pandas as pd
data = pd.read_csv("data.csv")
data.head()
```

renders as

import pandas as pd
data = pd.read_csv("data.csv")
data.head()

Inline Images

{{< icon name="python" >}} Python

renders as

Python

Embed Media

Tue, 24 Oct 2023 00:00:00 +0000

is designed to give technical content creators a seamless experience. You can focus on the content and the HugoBlox Kit which this template is built upon handles the rest.

Embed videos, podcasts, code, LaTeX math, and even test students!

On this page, you’ll find some examples of the types of technical content that can be rendered with Hugo Blox.

Video

Teach your course by sharing videos with your students. Choose from one of the following approaches:

Youtube:

{{< youtube w7Ft2ymGmfc >}}

Bilibili:

{{< bilibili id="BV1WV4y1r7DF" >}}

Video file

Videos may be added to a page by either placing them in your assets/media/ media library or in your , and then embedding them with the video shortcode:

{{< video src="my_video.mp4" controls="yes" >}}

Podcast

You can add a podcast or music to a page by placing the MP3 file in the page’s folder or the media library folder and then embedding the audio on your page with the audio shortcode:

{{< audio src="ambient-piano.mp3" >}}

Try it out:

Test students

Provide a simple yet fun self-assessment by revealing the solutions to challenges with the spoiler shortcode:

{{< spoiler text="👉 Click to view the solution" >}}
You found me!
{{< /spoiler >}}

renders as

👉 Click to view the solution

You found me 🎉

Math

HugoBlox Kit supports a Markdown extension for $\LaTeX$ math. You can enable this feature by toggling the math option in your config/_default/params.yaml file.

To render inline or block math, wrap your LaTeX math with {{< math >}}$...${{< /math >}} or {{< math >}}$$...$${{< /math >}}, respectively.

Note

We wrap the LaTeX math in the Hugo Blox math shortcode to prevent Hugo rendering our math as Markdown. This callout now uses the standard Markdown alert syntax!

Example math block:

{{< math >}}
$$
\gamma_{n} = \frac{ \left | \left (\mathbf x_{n} - \mathbf x_{n-1} \right )^T \left [\nabla F (\mathbf x_{n}) - \nabla F (\mathbf x_{n-1}) \right ] \right |}{\left \|\nabla F(\mathbf{x}_{n}) - \nabla F(\mathbf{x}_{n-1}) \right \|^2}
$$
{{< /math >}}

renders as

Example inline math {{< math >}}$\nabla F(\mathbf{x}_{n})${{< /math >}} renders as $\nabla F(\mathbf{x}_{n})$ .

Example multi-line math using the math linebreak (\\):

{{< math >}}
$$f(k;p_{0}^{*}) = \begin{cases}p_{0}^{*} & \text{if }k=1, \\
1-p_{0}^{*} & \text{if }k=0.\end{cases}$$
{{< /math >}}

renders as

$$ f(k;p_{0}^{*}) = \begin{cases}p_{0}^{*} & \text{if }k=1, \\ 1-p_{0}^{*} & \text{if }k=0.\end{cases} $$

Code

HugoBlox Kit utilises Hugo’s Markdown extension for highlighting code syntax. The code theme can be selected in the config/_default/params.yaml file.

```python
import pandas as pd
data = pd.read_csv("data.csv")
data.head()
```

renders as

import pandas as pd
data = pd.read_csv("data.csv")
data.head()

Inline Images

{{< icon name="python" >}} Python

renders as

Python

Experience

Tue, 24 Oct 2023 00:00:00 +0000

✅ Manage your projects

Mon, 23 Oct 2023 00:00:00 +0000

Easily manage your projects - create ideation mind maps, Gantt charts, todo lists, and more!

Ideation

Hugo Blox supports a Markdown extension for mindmaps.

Simply insert a Markdown code block labelled as markmap and optionally set the height of the mindmap as shown in the example below.

Mindmaps can be created by simply writing the items as a Markdown list within the markmap code block, indenting each item to create as many sub-levels as you need:


```markmap {height="200px"}
- Hugo Modules
- Hugo Blox
- netlify
- netlify-cms
- slides
```

renders as

- Hugo Modules
- Hugo Blox
- netlify
- netlify-cms
- slides

Diagrams

Hugo Blox supports the Mermaid Markdown extension for diagrams.

An example Gantt diagram:

```mermaid
gantt
section Section
Completed :done, des1, 2014-01-06,2014-01-08
Active :active, des2, 2014-01-07, 3d
Parallel 1 : des3, after des1, 1d
Parallel 2 : des4, after des1, 1d
Parallel 3 : des5, after des3, 1d
Parallel 4 : des6, after des4, 1d
```

renders as

gantt section Section Completed :done, des1, 2014-01-06,2014-01-08 Active :active, des2, 2014-01-07, 3d Parallel 1 : des3, after des1, 1d Parallel 2 : des4, after des1, 1d Parallel 3 : des5, after des3, 1d Parallel 4 : des6, after des4, 1d

Todo lists

You can even write your todo lists in Markdown too:

- [x] Write math example
 - [x] Write diagram example
- [ ] Do something else

renders as

Write math example
- Write diagram example
Do something else

Flink Real-Time Stream Computing & ETL

Tue, 01 Aug 2023 00:00:00 +0000

Financial data pipeline based on Flink + scheduled tasks.

Key Capabilities:

Flink CDC real-time data sync (MySQL binlog / HBase change logs)
Flink SQL streaming ETL: real-time cleaning, aggregation, windowed computation
Minute-level K-line synthesis, buy/sell pressure ratio, anomaly trade detection
Checkpoint mechanism ensuring Exactly-Once semantics
Offline ETL: Airflow + Crontab scheduling, automated daily/monthly reports

Kuaiding IoT Parking System

Tue, 01 Jun 2021 00:00:00 +0000

Hainan’s second-largest parking lot system, covering 280 parking lots across 3 major cities.

Key Capabilities:

MQTT protocol cloud-station-terminal tripartite solution
30-second periodic device health checks, gate opening latency < 1.5s
Local video storage + async upload
Real-time anomaly video capture, issue localization, and maintenance dispatching
Tech stack: Java Spring + C# + MySQL + Raspberry Pi + PLC

An example preprint / working paper

Sun, 07 Apr 2019 00:00:00 +0000

This work is driven by the results in my on LLMs.

Note

Create your slides in Markdown - click the Slides button to check out the example.

Add the publication’s full text or supplementary notes here. You can use rich formatting such as including .

Create Beautiful Presentations with Markdown

Sun, 01 Jan 2017 00:00:00 +0000

🎯 Why Markdown Slides?

True Presentation Freedom

Unlike PowerPoint or Keynote, your presentations are future-proof, portable, and completely under your control. No proprietary formats, no vendor lock-in, no subscription fees.

The Problem with Traditional Slides

PowerPoint & Keynote:

💸 Expensive licenses or subscriptions
🔒 Proprietary file formats (.pptx, .key)
💻 Platform-specific (Windows/Mac only)
📦 Large binary files
🚫 Difficult to version control
😰 Lost formatting when sharing

Google Slides:

☁️ Requires internet connection
🔐 Data stored on Google’s servers
📱 Limited offline editing
🎨 Formatting breaks when exporting
🔗 Dependency on Google’s platform

The Hugo Blox Solution

Markdown Changes Everything

Write your presentations in simple, human-readable Markdown. Edit anywhere, present anywhere, own forever.

✨ What You Get

🎨 Professional Design, Zero Effort

15+ Built-in Themes — Black, white, sky, league, and more
Syntax Highlighting — Beautiful code blocks with 50+ languages
Math Support — LaTeX equations render perfectly: $E = mc^2$
Responsive — Looks great on any screen size

📝 Write in Plain Text

## My Slide Title

- Point one
- Point two
- Point three

```python
def hello():
 return "World!"
```

---

That’s it! No complex UI, no formatting headaches.

🔄 Edit Anywhere, Anytime

Zero Lock-In

Your slides are just Markdown files. Edit them in:

Ownable CMS — Visual editing with live preview
VS Code — With Markdown extensions
Obsidian — Note-taking app that speaks Markdown
Typora — Minimal distraction writing
Any text editor — Even Notepad works!

Try Ownable CMS

🎯 Advanced Features

Dual Column Layouts:

<div style="display: flex; gap: 2rem;">
 <div style="flex: 1;">Column 1</div>
 <div style="flex: 1;">Column 2</div>
</div>

Fragment Animations:

{{< fragment >}}Appear on click!{{< /fragment >}}

Speaker Notes:

Note: Your private notes here
(visible in presenter view only)

Vertical Slide Stacks: Navigate down for sub-topics!

🚀 Getting Started is Easy

Create Your First Slide Deck in 3 Steps

Step 1: Create Your Slides

Create content/slides/my-talk/index.md:

---
title: "My Amazing Talk"
type: slides
slides:
 theme: black
---

# My Amazing Talk
### Ruoyi Plus

---

## Main Points

- Point 1
- Point 2
- Point 3

---

## Thank You!

Step 2: Link to Your Event

In your event page (content/events/my-event/index.md):

---
title: "My Conference Presentation"
slides: "my-talk" # References the slides folder name
---

Step 3: Present!

Your slides are automatically:

✅ Embedded on the event page
✅ Available in fullscreen mode (click arrows-expand button)
✅ Accessible at a direct URL
✅ Keyboard-navigatable (→ ← keys)

Read Full Documentation

💎 Why Academics & Researchers Love It

Quote

“I can finally version control my presentations with Git, collaborate using GitHub, and never worry about formatting breaking again. Game changer for reproducible research!” — Dr. Xin Liu, MIT

Perfect for Research

Version Control — Track every change with Git
Collaboration — Use GitHub pull requests for slide reviews
Reproducibility — Slides are plain text, commit them with your code
Open Science — Share presentations on GitHub, no barriers
Citations — Include BibTeX references easily
Jupyter Integration — Embed notebooks and visualizations

Perfect for Teaching

Reusable Content — Mix and match slides across courses
Student Contributions — Students can submit slide PRs
Live Coding — Syntax highlighting for all languages
Interactive Examples — Embed interactive visualizations
Accessible — Keyboard navigation, screen reader friendly

🎬 See It In Action

Note

Try it now! The slides embedded above demonstrate all these features:

Code highlighting with Python
Mathematical equations with LaTeX
Dual column layouts (slides 4-6)
Fragment animations
Multiple themes

Click the arrows-expand fullscreen button (top right) to experience presentation mode!

Live Features to Try

Navigate: Use arrow keys (→ ←) or click controls
Fullscreen: Click the expand button to go fullscreen
Speaker Notes: Press S to open presenter view (try it!)
Overview: Press ESC to see all slides at once
Search: Press / to search slide content
Zoom: Alt+Click to zoom into details

external-link Open Slides in New Tab

🆚 Comparison

Feature	PowerPoint	Google Slides	Hugo Blox
Cost	$159.99/year	Free*	Free Forever
Format	Binary (`.pptx`)	Proprietary	Plain Markdown
Version Control	❌ Difficult	❌ Limited	✅ Git Native
Offline Editing	✅ Yes	⚠️ Limited	✅ Fully Offline
Platform Lock-in	⚠️ Microsoft	⚠️ Google	✅ None
Code Highlighting	⚠️ Basic	⚠️ Limited	✅ 50+ Languages
Math Equations	⚠️ Clunky	⚠️ Basic	✅ Full LaTeX
Portability	❌ Poor	❌ Requires Google	✅ Works Anywhere
Future-Proof	❌ Format changes	⚠️ API changes	✅ Plain Text Forever
Open Source	❌ No	❌ No	✅ Yes

Success

Hugo Blox wins on freedom, portability, and long-term sustainability.

🛠️ Advanced Capabilities

Code Blocks with Syntax Highlighting

import torch
import torch.nn as nn

class Transformer(nn.Module):
 def __init__(self, d_model=512, nhead=8):
 super().__init__()
 self.attention = nn.MultiheadAttention(d_model, nhead)

 def forward(self, x):
 return self.attention(x, x, x)[0]

Mathematical Equations

Display equations with LaTeX:

$$
\nabla \times \vec{E} = -\frac{\partial \vec{B}}{\partial t}
$$

$$
\int_{-\infty}^{\infty} e^{-x^2} dx = \sqrt{\pi}
$$

Dual Column Layouts

Perfect for before/after comparisons, code + explanation, or image + text:

<div style="display: flex; gap: 2rem;">
 <div style="flex: 1;">Left content</div>
 <div style="flex: 1;">Right content</div>
</div>

See slides 4-6 in the embedded presentation above for live examples!

🎓 For Educators: Teach the Future

Empower Your Students

Teaching with Hugo Blox means teaching modern, transferable skills:

Markdown (used everywhere: GitHub, Notion, Obsidian)
Version control (essential for careers)
Web technologies (HTML, CSS)
Reproducible science practices

Course Integration

courses/
├── ml-101/
│ ├── lecture-1/
│ │ ├── index.md (slides)
│ │ └── notes.md
│ ├── lecture-2/
│ │ └── index.md
│ └── _index.md

Each lecture gets its own slide deck, all version controlled, all editable by students as PRs.

🌍 Join the Community

Built by Academics, for Academics

Hugo Blox is used by researchers at:

🎓 Stanford, MIT, Harvard, Oxford, Cambridge
🏢 Google Research, Meta AI, OpenAI
🔬 CERN, NASA, NIH
🌐 Thousands of universities worldwide

Star on GitHub

Get Help & Connect

📚
💬
🐛
🐦

🚀 Ready to Create?

Start Building Beautiful Presentations Today

No installation required. No account needed. Just Markdown and your creativity.

Get Started Now

Try Ownable CMS

📖 Additional Resources

Templates & Examples

Tips & Tricks

Pro Tips for Better Presentations

Keep slides simple — one idea per slide
Use dual columns for comparisons
Add speaker notes with Note: prefix
Test presenter view before your talk
Use fragments to control pacing
Version control your slides with Git
Share source files for reproducibility

Have questions? Check out the or !

Want to contribute? Hugo Blox is open source! .

Haoshouyi P2P Fintech Platform

Fri, 01 Jan 2016 00:00:00 +0000

Internet finance matching platform centered on auto mortgage and supply chain financing.

Key Metrics:

50K+ active users, ¥2B+ cumulative transaction volume, ¥250M outstanding loans
Huishang Bank fund custody, Level 3 information security compliance
Three funding rounds completed
Top 10 vertical P2P platform of its era

An example journal article

Tue, 01 Sep 2015 00:00:00 +0000

Note

Click the Cite button above to demo the feature to enable visitors to import publication metadata into their reference management software.

Note

Create your slides in Markdown - click the Slides button to check out the example.

Add the publication’s full text or supplementary notes here. You can use rich formatting such as including .

An example conference paper

Mon, 01 Jul 2013 00:00:00 +0000

Note

Click the Cite button above to demo the feature to enable visitors to import publication metadata into their reference management software.

Note

Create your slides in Markdown - click the Slides button to check out the example.

Add the publication’s full text or supplementary notes here. You can use rich formatting such as including .

Shangnuo Financial Asset Management

Tue, 01 May 2012 00:00:00 +0000

Financial asset management system based on financing guarantee licenses.

Key Features:

Due diligence & risk assessment modules
Scorecard mechanisms with full loan lifecycle management (origination, tracking, post-loan)
Risk resolution closed loop (collection assignment, legal intervention, asset auction)
360° customer view (multi-dimensional data integration, precision marketing)
Tech stack: Java Spring + MySQL

POS Inventory & Restaurant System

Tue, 01 Jun 2010 00:00:00 +0000

Inventory management and restaurant POS solutions for small and medium businesses.

Key Features:

Inventory POS: Goods receiving, inventory management, sales invoicing, membership management, multi-store chain support
Yishi Fine Dining Software: Table management, iPad ordering, kitchen printing, bill splitting
Wireless printer integration
Tech stack: Delphi / C# / SQL Server / Embedded POS hardware drivers

Buttons

Mon, 01 Jan 0001 00:00:00 +0000

A modern, customizable button shortcode with gradient styling, icons, and smart link handling.

Basic Usage

Visit External Site

The above buttons are created with:

{{< button url="/contact" >}}Contact Us{{< /button >}}

{{< button url="https://example.com" new_tab="true" style="secondary" >}}Visit External Site{{< /button >}}

Style Variants

Primary (Default)

Primary Button

{{< button url="#" style="primary" >}}Primary Button{{< /button >}}

Secondary

Secondary Button

{{< button url="#" style="secondary" >}}Secondary Button{{< /button >}}

Outline

Outline Button

{{< button url="#" style="outline" >}}Outline Button{{< /button >}}

Ghost

Ghost Button

{{< button url="#" style="ghost" >}}Ghost Button{{< /button >}}

Sizes

Extra Large

{{< button url="#" size="sm" >}}Small Button{{< /button >}}
{{< button url="#" size="md" >}}Medium Button{{< /button >}}
{{< button url="#" size="lg" >}}Large Button{{< /button >}}
{{< button url="#" size="xl" >}}Extra Large{{< /button >}}

Alignment

Left (Default)

Left Aligned

Center

Center Aligned

Right

Right Aligned

{{< button url="#" align="left" >}}Left Aligned{{< /button >}}
{{< button url="#" align="center" >}}Center Aligned{{< /button >}}
{{< button url="#" align="right" >}}Right Aligned{{< /button >}}

With Icons

Icon Before Text

Download

Icon After Text

Continue

{{< button url="#" icon="arrow-down-tray" >}}Download{{< /button >}}
{{< button url="#" icon="arrow-right" icon_position="right" >}}Continue{{< /button >}}

Rounded Corners

Small Radius

Medium Radius (Default)

Medium Radius

Large Radius

Pill Shape

Pill Button

{{< button url="#" rounded="sm" >}}Small Radius{{< /button >}}
{{< button url="#" rounded="md" >}}Medium Radius{{< /button >}}
{{< button url="#" rounded="lg" >}}Large Radius{{< /button >}}
{{< button url="#" rounded="full" >}}Pill Button{{< /button >}}

Advanced Examples

Call-to-Action Button

Get Started Today

{{< button url="/signup" style="primary" size="lg" align="center" icon="rocket-launch" >}}Get Started Today{{< /button >}}

External Link with New Tab

View on GitHub

{{< button url="https://github.com/hugo-blox/kit" new_tab="true" style="outline" icon="arrow-top-right-on-square" icon_position="right" >}}View on GitHub{{< /button >}}

Download Button

Download PDF

{{< button url="/files/document.pdf" style="secondary" icon="document-arrow-down" rounded="full" >}}Download PDF{{< /button >}}

Parameters

Parameter	Type	Default	Description
`url`	string	`#`	Required. Button destination URL (internal or external)
`text`	string	Inner content	Button text (overrides shortcode content)
`new_tab`	boolean	`false`	Whether to open link in new tab
`style`	string	`primary`	Button style: `primary`, `secondary`, `outline`, `ghost`
`size`	string	`md`	Button size: `sm`, `md`, `lg`, `xl`
`align`	string	`left`	Button alignment: `left`, `center`, `right`
`icon`	string	-	Icon name from
`icon_position`	string	`left`	Icon position: `left`, `right`
`rounded`	string	`md`	Border radius: `sm`, `md`, `lg`, `xl`, `full`
`disabled`	boolean	`false`	Whether button should be disabled

Security Features

The button shortcode automatically handles security for external links:

External links get rel="noreferrer" attribute
External links opening in new tab get rel="noopener noreferrer"
Internal links opening in new tab get rel="noopener"

This ensures safe navigation while maintaining functionality.

Accessibility

The button shortcode includes built-in accessibility features:

Proper role="button" attribute
aria-label support
Keyboard focus indicators
High contrast focus rings
Disabled state handling

Callouts

Mon, 01 Jan 0001 00:00:00 +0000

Hugo Blox supports GitHub and Obsidian-style Markdown callouts for maximum compatibility and content portability.

Callouts are a useful feature to draw attention to important or related content such as notes, hints, or warnings in your articles.

Usage

Basic Callout Types

Hugo Blox supports all 15+ callout types from :

Information & Notes:

> [!NOTE]
> This is a note callout with important information that users should know.

Note

This is a note callout with important information that users should know.

> [!INFO]
> Alternative info callout - same styling as NOTE.

Info

Alternative info callout - same styling as NOTE.

> [!ABSTRACT]
> Use for abstracts, summaries, or TL;DR sections.

Abstract

Use for abstracts, summaries, or TL;DR sections.

Actions & Tasks:

> [!TODO]
> This is something that needs to be done.

Todo

This is something that needs to be done.

> [!TIP]
> Here's a helpful tip to make your workflow more efficient!

Tip

Here’s a helpful tip to make your workflow more efficient!

> [!SUCCESS]
> Great job! This operation completed successfully.

Success

Great job! This operation completed successfully.

Questions & Interactive:

> [!QUESTION]
> What do you think about this approach? Let us know!

Question

What do you think about this approach? Let us know!

> [!EXAMPLE]
> Here's a practical example of how to implement this feature.

Example

Here’s a practical example of how to implement this feature.

> [!QUOTE]
> "The best way to predict the future is to invent it." - Alan Kay

Quote

“The best way to predict the future is to invent it.” - Alan Kay

Warnings & Errors:

> [!WARNING]
> Be careful! This action might have unexpected consequences.

Warning

Be careful! This action might have unexpected consequences.

> [!CAUTION]
> Danger! This operation is irreversible and could cause data loss.

Caution

Danger! This operation is irreversible and could cause data loss.

> [!IMPORTANT]
> This is critical information that users must understand to proceed.

Important

This is critical information that users must understand to proceed.

> [!DANGER]
> This is extremely dangerous - proceed with extreme caution!

Danger

This is extremely dangerous - proceed with extreme caution!

> [!FAILURE]
> This operation failed. Check your configuration and try again.

Failure

This operation failed. Check your configuration and try again.

> [!BUG]
> Known issue: This feature doesn't work properly in Safari < 14.

Bug

Known issue: This feature doesn’t work properly in Safari < 14.

Custom Titles

You can customize the title of any callout:

> [!WARNING]+ Custom Warning Title
> This warning has a custom title instead of just "Warning".

Custom Warning Title

This warning has a custom title instead of just “Warning”.

Legacy Syntax (Deprecated)

The old shortcode syntax still works but shows a deprecation warning:

{{< callout note >}}
This still works but is deprecated. Use the Markdown syntax above!
{{< /callout >}}

CSS Customization

Hugo Blox generates callouts with semantic CSS classes and data attributes, making customization easy. Each callout has:

Base class: .callout
Type-specific data attribute: data-callout="note"
Component classes: .callout-icon, .callout-title, .callout-content, .callout-body

Custom CSS Example (add to your assets/css/custom.css):

/* Customize NOTE callouts */
.callout[data-callout="note"] {
 border-left-width: 8px;
 box-shadow: 0 4px 6px -1px rgb(0 0 0 / 0.1);
}

/* Make SUCCESS callouts pulse */
.callout[data-callout="success"] {
 animation: pulse 2s infinite;
}

/* Custom icon styling */
.callout-icon svg {
 transition: transform 0.2s;
}

.callout:hover .callout-icon svg {
 transform: scale(1.1);
}

/* Dark mode overrides */
@media (prefers-color-scheme: dark) {
 .callout[data-callout="warning"] {
 background-color: rgb(92 25 2);
 border-color: rgb(245 158 11);
 }
}

This approach matches , ensuring your styles work across platforms.

Benefits of the New Syntax

Portable: Works with GitHub, Obsidian, and other Markdown editors
Standard: Uses widely-adopted Markdown callout syntax
Clean: No Hugo-specific shortcodes needed
Future-proof: Supported by the latest Hugo versions (0.132.0+)
Customizable: Semantic CSS classes and data attributes for easy styling
Complete: All 15+ Obsidian callout types supported
Multilingual: Callout titles are automatically translated based on your site’s language (and can be customized in the language packs)

Cards

Mon, 01 Jan 0001 00:00:00 +0000

A Hugo extension to create cards. Cards can be shown as links or as plain text.

Usage

Learn Shortcodes A card without an icon or link

is rendered by:

{{< cards >}}
 {{< card url="../callout" title="Callout" icon="academic-cap" >}}
 {{< card url="" title="A card without an icon" >}}
{{< /cards >}}

Options

Parameter	Description
`icon`	Name of the icon. Defaults to
`title`	Title heading for the card.
`subtitle`	Subtitle heading (supports Markdown).
`url`	URL

Internationalization (i18n)

Mon, 01 Jan 0001 00:00:00 +0000

Hugo Blox enables you to easily edit the interface text as well as translating your site into multiple languages using Hugo’s feature.

View the full docs at

Spoilers

Mon, 01 Jan 0001 00:00:00 +0000

A Hugo shortcode to toggle collapsible content.

Example

Click to view the spoiler

You found me!

Markdown is supported.

Usage

{{< spoiler text="Click to view the spoiler" >}}

This is the content of the details.

Markdown is **supported**.

{{< /spoiler >}}

Steps

Mon, 01 Jan 0001 00:00:00 +0000

Display a series of steps, such as for a tutorial.

Example

Step 1

The first step here…

Step 2

The second step here…

Step 3

The third step here…

Usage

Use the Markdown level-3 headings to represent step titles within the steps shortcode:

{{% steps %}}

### Step 1

The first step here...

### Step 2

The second step here...

### Step 3

The third step here...

{{% /steps %}}

RuoYiPlus

Environment Setup

Step One

Getting Started

Quick Start from Template

Create a site

Configure your new site

Add your content

Publish your site

Next

Business Vision

Core Positioning

What Problems It Solves

Target Customer Profile

1. Product Matrix

1.1 Version System

1.2 Feature Comparison

2. Business Model

2.1 Licensing Model

2.2 Module-Based Licensing

2.3 Service Model

3. Ecosystem Partnerships

3.1 Partner Ecosystem

3.2 ISV Partnership Model

4. Development Roadmap

4.1 Short-Term Plan

4.2 Medium-to-Long-Term Vision

5. Success Stories

Case 1: Provincial Government Cloud Platform

Case 2: Financial Institution CRM

Case 3: Manufacturing Group ERP

Contact Us

Customizing Hugo

Feature List

Core Positioning

Feature Panorama

System Features (19 Items)

Infrastructure (17 Items)

Business Subsystem Overview

Suitable Users

Project Structure

Folder Structure

Hugo File Naming Convention

Docs Navigation

Configuration

Full Documentation

Navigation

Menu

Left Sidebar

Extra Links

Right Sidebar

Report Dashboards & Data Visualization

Core Positioning

Problems Solved

User Roles

Three Reporting Engines

Dashboard Design Process

Built-in Chart Components (Partial)

Typical Application Scenarios

Yudao Framework Enhancement Capabilities

Core Positioning

What Problems It Solves

Suitable Users

1. Data Permission Engine

1.1 Four-Layer Permission Model

1.2 Capability Comparison

1.3 Usage

2. Sensitive Field Masking

2.1 Masking Architecture

2.2 Supported Masking Types

2.3 Usage

3. Operation Log Center

3.1 Log System

3.2 Intelligent Change Tracking

3.3 Sensitive Operation Alerts

4. API Gateway Enhancement

4.1 Gateway Architecture

4.2 Enhancement Features

5. Service Governance

5.1 Distributed Transactions