A low-code development platform based on a rules engine

Abstract

The application relates to the technical field of low-code development platforms, in particular to a low-code development platform based on a rule engine, which comprises a system architecture, a low-code development module and a process engine module, the system architecture adopts a Vue framework as a front-end framework, the system architecture adopts a Spring Boot framework as a back-end core framework, and the low-code development module comprises a front-end form generation tool and a back-end design and generation tool.The application improves development efficiency, reduces technical threshold, realizes efficient cooperation between business and technology, deeply couples the low-code function and the process engine function through a preset standardized interface, guarantees technical advancement and maintainability, meanwhile, a front-end component library supports custom extension, a back-end service is modularized, can flexibly cope with the addition and change of future business functions, ensures that all applications developed based on the platform comply with uniform standards in safety, auditability, data consistency and code style, and is beneficial to long-term operation and maintenance of enterprise-level applications.

Description

Technical Field

[0001] This invention relates to the field of low-code development platform technology, specifically a low-code development platform based on a rules engine. Background Technology

[0002] In recent years, with the deepening of enterprise digital transformation, various business systems have been widely used in enterprises and institutions. These systems typically involve a large number of business scenarios with similar functions or routine processes, such as various administrative approvals, expense reimbursement applications, work order processing, and project management. Traditional software development models require developers to perform a complete set of manual coding work for each such business process, from database design and backend business logic coding to frontend interface development. This leads to problems such as high repetitive development tasks, large workload, long development cycles, and high labor costs.

[0003] To improve development efficiency, the low-code development concept emerged. Low-code development platforms allow developers to create applications through graphical user interfaces and configurable methods, using visual modeling and drag-and-drop components, thereby significantly reducing the workload of traditional manual coding. Meanwhile, for business scenarios involving multi-person collaboration, multi-step approvals, or status transitions, process engine technology is a core tool for automating and standardizing business process management. It enables visual definition, automated execution, and real-time monitoring of business processes.

[0004] However, existing technical solutions often suffer from the following shortcomings: On the one hand, many low-code platforms focus on quickly generating static forms and pages, lacking deep integration and automated driving capabilities for dynamic and complex business processes, making it difficult to meet the needs of process-intensive applications; on the other hand, while independent process engines are powerful, they typically require developers to write a large amount of code to interface with specific business forms and data models, resulting in high integration complexity and failing to achieve deep integration with front-end application generation. In other words, low-code capabilities and process engine capabilities are often fragmented, failing to form an integrated solution. When building a process-driven application, developers still need to design forms in the low-code platform, design processes in the process engine, and then manually link the two through additional development work, failing to truly achieve the efficient goal of "configuration as development," and the software construction process remains not simplified enough. No solutions have yet been proposed to address these technical issues. Summary of the Invention

[0005] To address the problems in related technologies, this invention proposes a low-code development platform based on a rules engine to overcome the aforementioned technical issues in existing technologies. The purpose of this invention is to improve development efficiency, enable rapid delivery, lower the technical threshold, and achieve efficient collaboration between business and technology. It adopts a modular and layered system architecture, deeply coupling low-code functionality with process engine functionality through pre-defined standardized interfaces to ensure technological advancement and maintainability. At the same time, the front-end component library supports custom extensions, and the back-end service is modularized, enabling flexible responses to future additions and changes in business functions. It ensures that all applications developed based on the platform adhere to unified standards in terms of security, auditability, data consistency, and coding style, which is beneficial for the long-term operation and maintenance of enterprise-level applications.

[0006] To achieve the above objectives, the present invention provides the following technical solution: a low-code development platform based on a rules engine, comprising: The system architecture adopts a B / S architecture and separates the front-end and back-end. A low-code development module is used to generate application forms and business logic through visual configuration. The low-code development module is integrated into the system architecture. The process engine module is used to model, deploy, execute, and monitor business processes, and is integrated within the system architecture. The low-code development module process engine module connects through a preset interface, which supports the automatic association of the custom forms generated by the low-code development module with the business processes defined by the process engine module, and realizes the automatic initiation of processes based on form data.

[0007] Preferably, the system architecture uses the Vue framework as the front-end framework and the Spring Boot framework as the back-end core framework, and is divided into a three-tier architecture: The data layer includes relational databases for storing structured data, file servers for storing unstructured data, cache databases, and external interfaces for data interaction. The service layer includes basic services, process services integrated with the process engine module, form services integrated with the low-code development module, and statistical report services. The application layer includes a personal center, permission management, role management, notification management, log management, and various business function modules extended and generated through the low-code development module.

[0008] Preferably, in the front-end and back-end separation architecture, communication between the front-end and back-end is implemented through the HTTP protocol and the WebSocket protocol; wherein, the HTTP protocol is used to handle one-time request-response interactions such as form submission and file upload; the WebSocket protocol is used to realize full-duplex real-time communication between the client and the server and supports message push.

[0009] Preferably, the backend framework integrates a MyBatis-Plus component, a Shiro framework, and a logging framework. The MyBatis-Plus component is used for data persistence operations on relational databases; the Shiro framework is used for role-based access control and permission management; and the logging framework is used for monitoring and recording system operation status and user operations.

[0010] Preferably, in the data layer, structured data is stored in a MySQL relational database and divided into four types of data tables according to the nature of the data: process engine table, online form engine table, system basic function table, and business data table. The system basic function table includes personnel information, permissions, and logs, and the business data table is defined and generated online through the low-code development module.

[0011] Preferably, the process engine module adopts the Activity process engine, which provides the following service components: Repository services are used for storing, deploying, deleting, and versioning process definition models; Run services to start, query, suspend, and activate process instances; Task service is used to manage process tasks, including creating, querying, completing, assigning, and updating tasks; Historical services are used to query historical data such as process instances, historical tasks, and approval information. Management services are used to perform background management and maintenance operations.

[0012] Preferably, the working process of the process engine module includes: In the flowchart definition phase, the steps, connections, events, and conditions of the business process are defined graphically using a process designer. During the process deployment phase, the defined flowchart model is imported into the process engine module for parsing, verification, and storage. During the process execution phase, process instances are created based on the process definition, activity nodes are triggered sequentially or conditionally, tasks are assigned to participants according to predefined rules, and the process is driven to the next node or ends after the task is completed.

[0013] Preferably, the low-code development module includes: (1) A front-end form generation tool, wherein the front-end form generation tool includes: ① The component library provides input, selection, and layout-based visual components and supports custom component extensions; ② Page designer, which supports visual page design by dragging and dropping components, and allows configuration of component properties and validation rules; ③ Front-end code generator, used to automatically generate page code or pop-up code for Vue components based on the designed page model; (2) Backend design and generation tools, wherein the backend design and generation tools include: ① Online data table structure designer, which supports visual creation and modification of database table structure, and supports defining one-to-one, one-to-many and many-to-many table relationships; ② Backend code generator, used to generate and output the corresponding backend service layer, control layer and data persistence layer code online based on the designed table structure model.

[0014] Preferably, the permission management adopts a role-based access control model, which realizes access control of system resources by assigning permissions to roles and then assigning roles to users, and provides configuration functions for user management, department management, position management, menu management and role management.

[0015] Preferably, the front-end framework manages HTTP API requests through the Axios library and is configured with request interceptors and response interceptors for uniformly adding authentication tokens and handling request / response data formats and errors; the front-end framework manages front-end routing and menus through Vue-Router, supporting static routes and dynamic routes that are dynamically loaded based on user permissions.

[0016] Compared with the prior art, the beneficial effects of the present invention are: (1) This invention is a low-code development platform based on a rule engine. By deeply integrating the low-code development module and the process engine module, it creatively integrates the visual design of the front-end interface with the visual modeling of the back-end business process. Developers only need to complete the entire process from defining the business data model and designing the user interface to arranging complex business processes through the visual configuration within the platform. The platform automatically generates front-end and back-end code according to the configuration, which greatly reduces the amount of manual coding work. This shortens the time required to build a process-driven complex business application from the traditional weekly or monthly time to daily or hourly time, significantly accelerating the development speed of the application. It is a powerful tool to empower rapid innovation and agile development. (2) This invention is a low-code development platform based on a rule engine. The platform encapsulates complex process orchestration logic, database operations, access control and other backend technical details in a graphical configuration interface. Non-professional developers can directly participate in the construction of applications and process design, which lowers the technical threshold. At the same time, professional developers can focus on the expansion, customization and encapsulation of core business logic of the platform, realizing efficient collaboration between business and technology and improving the overall agile response capability. (3) This invention is a low-code development platform based on a rule engine. It adopts a modular and layered system architecture design, integrates a mature and stable technology stack, and deeply couples the low-code function with the process engine function through a preset standardized interface. This not only ensures the technical advancement and maintainability of the platform itself, but also enables the business applications generated by the platform to have business process execution capabilities, refined permission control and a sound log monitoring mechanism, thus ensuring the continuity and stable operation of the business applications. (4) This invention is a low-code development platform based on a rule engine. By integrating the Activity process engine, it provides powerful business process lifecycle management capabilities. Business processes can be defined graphically and modified online in an intuitive way, and version management is supported. This makes it easy to deal with frequent changes in business rules. The execution status, task allocation, and approval history of process instances are fully visible and traceable, realizing automated driving and intelligent management of business processes, and improving the standardization and transparency of internal operations of enterprises. (5) This invention is a low-code development platform based on a rule engine. It adopts a B / S architecture with front-end and back-end separation and a three-layer (data layer, service layer, application layer) design. It has good scalability. The front-end component library supports custom extensions, and the back-end service is modularized. It can flexibly cope with the addition and changes of future business functions. At the same time, the platform supports unified management of structured and unstructured data and has the ability to handle high-concurrency requests and real-time message push. It can meet the needs of various enterprise-level application scenarios, from simple information reporting to complex multi-level approval and multi-system integration. (6) This invention is a low-code development platform based on a rule engine. By setting a role-based permission model, a unified log framework, a standardized data storage scheme and a code generation template, it ensures that all applications developed on the platform follow a unified standard in terms of security, auditability, data consistency and code style, which is conducive to the long-term operation and maintenance and knowledge accumulation of enterprise-level applications. Attached Figure Description

[0017] Figure 1 This is a schematic diagram of the system architecture in an embodiment of the present invention; Figure 2 This is a schematic diagram of the data layer, service layer, and application layer in an embodiment of the present invention. Detailed Implementation

[0018] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Example

[0019] Please see Figure 1-2 This invention proposes a technical solution for a low-code development platform based on a rules engine: a low-code development platform based on a rules engine, comprising: The system architecture adopts a B / S architecture and separates the front-end and back-end. The low-code development module is used to generate application forms and business logic through visual configuration. The low-code development module is integrated into the system architecture. The process engine module is used to model, deploy, execute, and monitor business processes. The process engine module is integrated into the system architecture. Among them, the low-code development module and the process engine module connect through preset interfaces, which supports the automatic association of custom forms generated by the low-code development module with the business processes defined by the process engine module, and realizes the automatic initiation of processes based on form data.

[0020] In this embodiment, the low-code development module and the process engine module achieve deep data and logic binding at the service layer through a set of predefined and standardized "form-process association interfaces".

[0021] When a user submits a form bound to a process through a low-code generated application frontend, the HTTP POST request sent by the frontend Axios not only contains the form data but also carries the form ID. Upon receiving this, the backend controller calls the form service to handle business data persistence. Subsequently, the form service calls the process service's `startProcessInstanceByForm(String formId, Map...)` method.<String,Object> The `variables` method. The process service retrieves the bound process definition based on the `formId` and starts a new process instance using the variables populated with form data, thus achieving automatic process initiation based on form data. The entire process requires no additional process initiation code from the developer.

[0022] Furthermore, the system architecture uses Vue as the front-end framework and Spring Boot as the core back-end framework, and is divided into a three-tier architecture: The data layer includes relational databases for storing structured data, file servers for storing unstructured data, cache databases, and external interfaces for data interaction. The service layer includes basic services, process services integrated with the process engine module, form services integrated with the low-code development module, and statistical reporting services. The application layer includes the user center, permission management, role management, notification management, log management, and various business function modules generated through low-code development modules.

[0023] Furthermore, in the front-end and back-end separation architecture, communication between the front-end and back-end is achieved through the HTTP protocol and the WebSocket protocol. The HTTP protocol is used to handle one-time request-response interactions such as form submission and file upload; the WebSocket protocol is used to realize full-duplex real-time communication between the client and the server and supports message push.

[0024] Furthermore, the backend framework integrates MyBatis-Plus components, Shiro framework, and logging framework. The MyBatis-Plus component is used for data persistence operations on relational databases; the Shiro framework is used to implement role-based access control and permission management; and the logging framework is used to monitor and record system operation status and user operations.

[0025] Furthermore, in the data layer, structured data is stored in a MySQL relational database and divided into four types of data tables according to the nature of the data: process engine table, online form engine table, system basic function table, and business data table. The system basic function table includes personnel information, permissions, and logs, while the business data table is defined and generated online through a low-code development module.

[0026] Furthermore, the workflow engine module adopts the Activity workflow engine, which provides the following service components: Repository services are used for storing, deploying, deleting, and versioning process definition models; Run services to start, query, suspend, and activate process instances; Task service is used to manage process tasks, including creating, querying, completing, assigning, and updating tasks; Historical services are used to query historical data such as process instances, historical tasks, and approval information. Management services are used to perform background management and maintenance operations.

[0027] Furthermore, the workflow of the process engine module includes: In the flowchart definition phase, the steps, connections, events, and conditions of the business process are defined graphically using a process designer. During the process deployment phase, the defined flowchart model is imported into the process engine module for parsing, verification, and storage. During the process execution phase, process instances are created based on the process definition, activity nodes are triggered sequentially or conditionally, tasks are assigned to participants according to predefined rules, and the process is driven to the next node or ends after the task is completed.

[0028] Furthermore, low-code development modules include: (1) Front-end form generation tools, which include: ① The component library provides input, selection, and layout-based visual components and supports custom component extensions; ② Page designer, which supports visual page design by dragging and dropping components, and allows configuration of component properties and validation rules; ③ Front-end code generator, used to automatically generate page code or pop-up code for Vue components based on the designed page model; (2) Backend design and generation tools, which include: ① Online data table structure designer, which supports visual creation and modification of database table structure, and supports defining one-to-one, one-to-many and many-to-many table relationships; ② Backend code generator, used to generate and output the corresponding backend service layer, control layer and data persistence layer code online based on the designed table structure model.

[0029] In this embodiment, the Vue single-file components (.vue files) generated by the front-end code generator are not directly embedded into the main platform application, but rather exist as independent, dynamically loadable modules. The platform front-end (main framework) injects these newly generated page route configurations into the routing system through Vue-Router's dynamic routing API (router.addRoute()). Form submission requests in the generated pages are uniformly directed to a common form data receiving endpoint on the platform backend (e.g., / api / form / data / submit). This endpoint routes the request to the corresponding form service processing logic based on the formId in the request header or body.

[0030] The Java classes (Controller, Service, Mapper, etc.) generated by the backend code generator are processed by a code compilation and loading manager on the platform. This manager uses Java dynamic compilation technologies (such as the JavaCompiler API) or Spring Boot's DevTools hot deployment mechanism to dynamically load these newly generated classes into the Spring application context. The generated Mapper XML files are placed in a path that MyBatis-Plus can scan. To ensure security isolation, the generated business service classes are typically placed in a separate, platform-managed subpackage.

[0031] After the user completes the design, the online table structure designer not only generates the SQL code for `CREATE TABLE`, but also automatically or semi-automatically (with administrator confirmation) executes these DDL statements in the specified business database (MySQL instance) through a database schema management service of the platform (integrated with Flyway or Liquibase), truly realizing "online table creation". The generated business data tables are logically isolated from the platform's own system tables (process engine tables, form engine metadata tables, system function tables) through `tenant_id` (tenant ID) or `app_id` (application ID).

[0032] Furthermore, the access control system adopts a role-based access control model, which implements access control of system resources by assigning permissions to roles and then assigning roles to users, and provides configuration functions for user management, department management, position management, menu management and role management.

[0033] Furthermore, the front-end framework manages HTTP API requests through the Axios library and is configured with request and response interceptors for uniformly adding authentication tokens and handling request / response data formats and errors; the front-end framework manages front-end routing and menus through Vue-Router, supporting static routes and dynamic routes that are dynamically loaded based on user permissions.

[0034] In this embodiment, during the process execution phase, when the process engine (Activity) creates a user task (UserTask) and assigns it to a participant, the task service (TaskService) not only stores the task information but also associates it with a specific form ID generated by the low-code development module based on the preset "task form Key" in the process model definition. When a user accesses the task through the platform's task center, the front end sends a request to the form service (e.g., GET / api / form / render / {taskId}). The form service finds the corresponding form ID and the data of the current process instance based on the taskId, and dynamically renders a form interface containing filled-in data and fields to be filled in. After the user processes the task (approval, filling in comments) and submits it on this interface, the data updates the business table and also drives the process to the next node as a task variable.

[0035] The graphical interface of the workflow designer allows you to directly configure the "Exclusive Gateway" condition expression for the workflow path as a reference to a field in the form. For example, the condition can be configured as ${formData.amount>10000}. During workflow execution, the workflow engine's expression parser can obtain the value of formData.amount from the workflow variable (whose value comes from the form data at startup and subsequent task data) and make a judgment, thereby automatically selecting the correct workflow branch and achieving intelligent routing.

[0036] While the front-end page is being generated, the code generator creates a corresponding menu record in the system backend (stored in the system's basic function table) and generates a permission identifier (e.g., business:order:view) associated with that menu operation (such as view, add, delete). These newly generated permission points are automatically registered in Shiro's permission management system.

[0037] System administrators can view these newly generated menus and permission points in a unified role management interface and assign them to the corresponding roles just like configuring native platform functions. When a user logs in, their permission list (including permissions for new business functions) is loaded, and Vue-Router uses this list to filter and generate dynamic routes that the user can access, thereby achieving seamless and secure access control for newly generated application functions.

[0038] This invention achieves rapid application building and automated process execution driven by form data and primarily through visual configuration by deeply integrating a low-code development module and a process engine module, combined with a standardized system architecture. Its working process can be summarized into the following core steps: I. Architecture and Communication Fundamentals The system employs a B / S architecture with a front-end and back-end separation. The front-end, based on the Vue framework, is responsible for user interaction and UI rendering; the back-end, based on the Spring Boot framework, provides RESTful APIs and business logic processing. The front-end and back-end communicate via HTTP (for regular requests, such as form submissions managed by the Axios library) and WebSocket (for real-time message push), ensuring flexible and real-time interaction.

[0039] II. Application Creation Phase: Low-code Visual Development 1. Front-end page design: Users can drag and drop visual components such as input boxes and drop-down boxes from the component library through the page designer to design forms or page interfaces in a "what you see is what you get" manner, and configure component properties and validation rules.

[0040] 2. Backend Data Modeling: Users can visually define the structure (fields, types, relationships) of business data tables using an online data table structure designer. The platform automatically executes DDL statements to create the actual business data tables in the MySQL database.

[0041] 3. Full-stack code generation and dynamic integration: (1) Front-end: The front-end code generator converts the page design into independent Vue single-file components. The platform's main framework injects the newly generated page into the front-end routing system through Vue-Router's dynamic routing mechanism, making it an accessible menu item.

[0042] (2) Backend: The backend code generator generates corresponding Java code such as Controller, Service, and Mapper based on the data table model. The platform uses dynamic compilation technology to hot-load this code into the Spring application context and automatically configures the MyBatis-Plus data mapping.

[0043] III. Process Definition Phase: Graphical Process Modeling 1. Process Design: Users can draw business processes graphically in the process designer, and define task nodes, approvers, gateways (such as exclusive gateways) and flow paths.

[0044] 2. Intelligent routing configuration: Form fields can be directly referenced as judgment expressions in process conditions (such as exclusive gateways) (e.g., ${formData.amount>10000}) to achieve automated branch selection based on form data.

[0045] 3. Process Deployment: The completed flowchart model is deployed to the Activity process engine. The engine's repository service parses, validates, and stores it to generate an executable process definition.

[0046] IV. Core Driving Phase: Automatic Association of Forms and Processes The low-code development module and the process engine module are deeply bound together through a set of predefined "form-process association interfaces".

[0047] Association Configuration: In the platform, specific forms generated by low-code are associated and bound with specific processes defined by Activity.

[0048] Data-driven startup: When a user submits a form that is already bound to a process on the front end, the request will carry the form ID and form data to the backend general endpoint.

[0049] After persisting the business data, the backend form service automatically calls the process service's interface (such as startProcessInstanceByForm), passing in the form ID and data.

[0050] The process service locates the bound process definition based on the form ID and automatically starts a new process instance using the form data as process variables. Developers do not need to write any code to start the process.

[0051] V. Process Execution and Task Handling Phase Task creation and assignment: The process engine (running service) advances the process according to the definition. When the user task node is reached, the task service will create a task and assign it to the specified participant.

[0052] Dynamic form task interface: Tasks and forms are linked via a "task form key". When a user accesses a task from the task center, the front end requests the form service.

[0053] The form service finds the corresponding form ID and current process instance data based on the task ID, and dynamically renders the task form interface with pre-filled data and fields to be filled.

[0054] Task processing and workflow advancement: After the user approves or submits the form on this interface, the data is simultaneously updated in the business database and returned to the workflow engine as a task variable. The engine drives the workflow to the next node until completion. The entire process is fully recorded in the historical service.

[0055] VI. Unified Access Control and Security Measures Automatic permission generation: When generating the front-end page of business functions, the platform will automatically create the corresponding menu and permission identifier (such as business:order:view) and register them in the Shiro permission management system.

[0056] Role-Based Access Control (RBAC) Dynamic Authorization: Administrators can assign newly generated business permissions to roles in the role management interface, just like configuring native functions. After a user logs in, their permission list determines the dynamic routes generated by Vue-Router, achieving secure access control for new features.

[0057] System support: MyBatis-Plus is responsible for data persistence, Shiro is responsible for authentication and authorization, and the logging framework monitors system operation and user actions.

[0058] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A low-code development platform based on a rules engine, characterized in that, include: The system architecture adopts a B / S architecture and separates the front-end and back-end. A low-code development module is used to generate application forms and business logic through visual configuration. The low-code development module is integrated into the system architecture. The process engine module is used to model, deploy, execute, and monitor business processes, and is integrated within the system architecture. The low-code development module process engine module connects through a preset interface, which supports the automatic association of the custom forms generated by the low-code development module with the business processes defined by the process engine module, and realizes the automatic initiation of processes based on form data.

2. The low-code development platform based on a rules engine according to claim 1, characterized in that, The system architecture uses Vue as the front-end framework and Spring Boot as the back-end core framework, and is divided into a three-tier architecture: The data layer includes relational databases for storing structured data, file servers for storing unstructured data, cache databases, and external interfaces for data interaction. The service layer includes basic services, process services integrated with the process engine module, form services integrated with the low-code development module, and statistical report services. The application layer includes a personal center, permission management, role management, notification management, log management, and various business function modules extended and generated through the low-code development module.

3. The low-code development platform based on a rules engine according to claim 2, characterized in that, In the aforementioned front-end and back-end separation architecture, communication between the front-end and back-end is achieved through the HTTP protocol and the WebSocket protocol. The HTTP protocol is used to handle one-time request-response interactions such as form submission and file upload; the WebSocket protocol is used to achieve full-duplex real-time communication between the client and the server and supports message push.

4. The low-code development platform based on a rules engine according to claim 1, characterized in that, The backend framework integrates MyBatis-Plus components, Shiro framework, and logging framework. The MyBatis-Plus component is used for data persistence operations on relational databases; the Shiro framework is used for role-based access control and permission management; and the logging framework is used for monitoring and recording system operation status and user operations.

5. A low-code development platform based on a rules engine according to claim 2, characterized in that, In the data layer, structured data is stored in a MySQL relational database and is divided into four types of data tables according to the nature of the data: process engine table, online form engine table, system basic function table, and business data table. The system basic function table includes personnel information, permissions, and logs. The business data table is defined and generated online through the low-code development module.

6. The low-code development platform based on a rules engine according to claim 1, characterized in that, The process engine module adopts the Activity process engine, which provides the following service components: Repository services are used for storing, deploying, deleting, and versioning process definition models; Run services to start, query, suspend, and activate process instances; Task service is used to manage process tasks, including creating, querying, completing, assigning, and updating tasks; Historical services are used to query historical data such as process instances, historical tasks, and approval information. Management services are used to perform background management and maintenance operations.

7. A low-code development platform based on a rules engine according to claim 6, characterized in that, The workflow of the process engine module includes: In the flowchart definition phase, the steps, connections, events, and conditions of the business process are defined graphically using a process designer. During the process deployment phase, the defined flowchart model is imported into the process engine module for parsing, verification, and storage. During the process execution phase, process instances are created based on the process definition, activity nodes are triggered sequentially or conditionally, tasks are assigned to participants according to predefined rules, and the process is driven to the next node or ends after the task is completed.

8. A low-code development platform based on a rules engine according to claim 1, characterized in that, The low-code development module includes: (1) A front-end form generation tool, wherein the front-end form generation tool includes: ① The component library provides input, selection, and layout-based visual components and supports custom component extensions; ② Page designer, which supports visual page design by dragging and dropping components, and allows configuration of component properties and validation rules; ③ Front-end code generator, used to automatically generate page code or pop-up code for Vue components based on the designed page model; (2) Backend design and generation tools, wherein the backend design and generation tools include: ① Online data table structure designer, which supports visual creation and modification of database table structure, and supports defining one-to-one, one-to-many and many-to-many table relationships; ② Backend code generator, used to generate and output the corresponding backend service layer, control layer and data persistence layer code online based on the designed table structure model.

9. A low-code development platform based on a rules engine according to claim 2, characterized in that, The permission management adopts a role-based access control model, which realizes access control of system resources by assigning permissions to roles and then assigning roles to users, and provides configuration functions for user management, department management, position management, menu management and role management.

10. A low-code development platform based on a rules engine according to claim 1, characterized in that, The front-end framework manages HTTP API requests through the Axios library and is configured with request interceptors and response interceptors for uniformly adding authentication tokens and handling request / response data formats and errors. The front-end framework uses Vue-Router for front-end routing and menu management, supporting static routes and dynamic routes that are dynamically loaded based on user permissions.

Images