Business process system combining dynamic form and process engine

Abstract

The invention provides a business process system combining a dynamic form and a process engine, and relates to the technical field of business processes, the business process system comprises a code generation module, a flexible form module and a dynamic process module, the code generation module is used for automatically generating code files related to adding, deleting, checking and changing functions according to a database table structure, and the flexible form module is used for generating a flexible form; uniformly compressing and packaging into a code package; the flexible form module is used for designing and configuring a form according to the code package of the code generation module; according to the method, the form can be dynamically generated and closely integrated with the process engine, automatic management of the business process is realized, and seamless connection between the form designer and the process design engine and between the form engine and the process execution engine is realized, so that each link of the business process can dynamically generate and process the form according to actual requirements; the flexibility and the automation degree of the system are greatly improved, the automation requirement of an enterprise in a complex business process is met, the working efficiency is improved, and manual operation errors are reduced.

Description

Technical Field

[0001] The present invention relates to the field of business process technology, and in particular to a business process system combining a dynamic form and a process engine. Background Art

[0002] With the advancement of informatization, the business processes of enterprises and organizations have become increasingly complex. Traditional manual operations and static forms often lead to problems such as poor information flow, low approval efficiency, and difficult business process management.

[0003] Specifically: existing workflow engines and form management systems are mostly independent modules, the linkage between the two is weak, and there is a lack of effective integration and collaboration, which makes the definition and management process of business processes complex and difficult to maintain. How to effectively combine dynamic forms and process engines to provide an efficient system that can automatically manage business processes, dynamically generate forms and bind them to process tasks is a problem to be solved. Therefore, the present invention proposes a business process system that combines dynamic forms and process engines to solve the problems existing in the prior art. Summary of the invention

[0004] In response to the above problems, the present invention proposes a business process system that combines dynamic forms and process engines. The business process system that combines dynamic forms and process engines greatly improves the flexibility and automation level of the system, meets the automation needs of enterprises in complex business processes, improves work efficiency, and reduces manual operation errors.

[0005] To achieve the purpose of the present invention, the present invention is implemented by the following technical solutions: a business process system combining dynamic forms and process engines, including a code generation module, a flexible form module and a dynamic process module, wherein the code generation module is used to automatically generate code files related to the add, delete, check and modify functions according to the database table structure, and uniformly compress and package them into a code package;

[0006] The flexible form module is used to design and configure forms according to the code package of the above code generation module, and supports binding of form fields with data tables in the database. It also provides a visual form designer and a dynamic form engine. The visual form designer allows users to design forms and customize component extensions. The dynamic form engine is used to dynamically inject extended form functions and is responsible for data submission, verification and storage.

[0007] The dynamic process module provides process visualization functions and workflow creation, management and execution functions for users to design business processes and configure task parameters, and supports dynamic adjustment and execution of processes. At the same time, it provides the function of adding form configuration items in process design, binding dynamic forms with tasks, generating corresponding forms according to different process node configurations, and interacting with the execution status and process variables of the process.

[0008] A further improvement lies in that: the code generation module includes a database connection and table analysis module, a code generation construction module, and an extraction and introduction module. The database connection and table analysis module connects to the database based on the database development framework MyBatis-Plus, obtains the table structure, including the fields and data types of the table, and converts them into Java objects. The code generation construction module is used to analyze the Java object structure and then fill in the template based on the Velocity template engine to generate corresponding Java class codes, including entity class, DAO layer, and Service layer code files, and package them into a Zip file code package. The extraction and introduction module provides a channel for developers to extract the code package and introduce the generated code files into the project for adjustment and testing.

[0009] A further improvement lies in that: the flexible form module includes a form designer module, a field and database table binding module, a form verification module, a form rendering and dynamic display module, a form submission and data storage module, a form template and reuse module, and a form version management module. The form designer module includes a user interface unit, a field property configuration unit, a form layout unit, and a component extension unit. The user interface unit allows users to create forms by dragging and selecting components and configure the properties of the components. The field property configuration unit provides detailed configuration for each field, including field name, prompt information, data type, verification rules, and display / hide control logic. The form layout unit is used to provide different layout methods to allow users to flexibly adjust the positions and arrangement methods of form fields. The component extension unit allows users to upload custom controls or components according to their needs and use them in the form.

[0010] A further improvement lies in that: the field and database table binding module includes a field automatic binding database table unit, a field data binding unit, and a field type verification and conversion unit. The field automatic binding database table unit is used to automatically generate a field mapping relationship associated with the business database table according to the field properties configured by the user during form design, automatically generate data mapping codes based on the table structure and field types in the database, and associate the form fields with the corresponding fields in the data table. The field data binding unit is used to automatically transmit the data input by the user to the backend database through an interface when the form is submitted, and at the same time verify the field data according to its type and verification rules and store it in the database. The field type verification and conversion unit is used to automatically perform type verification according to different field data types to ensure that the data meets the requirements of the database table.

[0011] A further improvement lies in that: the form verification module includes a front-end verification unit, a back-end verification unit, and a dynamic extension unit for verification rules. The front-end verification unit is used to perform immediate verification through front-end JavaScript code before the form is submitted to check whether the data entered by the user conforms to the preset rules; the back-end verification unit is used to perform verification again when the form is submitted to the back-end server to ensure the integrity and accuracy of the data; the dynamic extension unit for verification rules is used for users to customize verification rules.

[0012] A further improvement lies in that: the form rendering and dynamic display module includes a form rendering engine unit, a dynamic field control unit, and a real-time data binding and update unit. The form rendering engine unit is responsible for dynamically rendering the form interface according to the configuration generated by the designer; the dynamic field control unit is used to provide a dependency configuration module during form rendering for users to configure the display rules of specified fields; the real-time data binding and update unit is used to obtain real-time data through the API interface to ensure that the form content is always up-to-date.

[0013] A further improvement lies in that: the form submission and data storage module includes a form submission mechanism unit, a data storage and update unit, and a process data binding unit. The form submission mechanism unit is used to provide multiple form submission methods after the user fills out the form; the data storage and update unit is used to store the submitted data into the relevant tables in the database according to the preset field mapping, and automatically generate SQL statements to perform insert or update operations; the process data binding unit is used to bind the form data to the relevant data of the current process task after the form data is stored in the database, so that the form data becomes a process variable in the process engine for subsequent nodes to use, and supports mapping the form data to the process variable.

[0014] A further improvement lies in that: the form template and reuse module includes a form template library, and a template modification and update unit. The form template library provides management and reuse of form templates and supports quick import, export, and sharing operations; the template modification and update unit is used to dynamically adjust the template content according to the requirements of the current process and automatically update the forms related to the template when the user uses the template;

[0015] The form version management module includes a version control unit and a version release and rollback unit. The version control unit is used to manage the versions of form designs and provide historical versions; the version release and rollback unit is used for form release and rollback.

[0016] A further improvement lies in that: the dynamic process module includes a process designer and a process engine, a combined module for process design and form design, a collaborative module for dynamic form and process engine, and an interactive module for process execution and form rendering; the process designer and process engine include a process designer unit, a process engine unit, a process execution unit, and a process task management unit. The process designer unit enables users to create business processes, place task nodes, conditional judgments, and event configurations in the flow chart, and publish the process to the backend process engine to generate corresponding process definition models; the process engine unit is developed based on the Flowable framework, supports process definition, task management, and process instance control, extends the support for dynamic forms, is used to configure dynamic forms at process nodes, and simultaneously execute and manage the designed business processes, schedule and execute process tasks; the process execution unit is used to select process definitions, start processes through the unified interface of the process engine unit to generate process instances, and simultaneously control the flow of processes; the process task management unit is used for users to view process instances, query workflow progress, task nodes, and submit forms.

[0017] The combined module for process design and form design includes a form design stage and a process design stage. In the form design stage, users create forms according to business requirements. Each form contains multiple fields, and users set attributes for each field. The generated form configuration file is passed to the process designer unit to bind the form to the corresponding process node. In the process design stage, users define the execution order, conditions, and actions of nodes according to the business process, configure forms for each node, dynamically load the required forms through the form configuration file, and synchronously package and publish these process configuration information and form information as process definitions for transfer to the process engine for execution.

[0018] A further improvement lies in that: the collaborative module for dynamic form and process engine includes a mapping unit for form and process, a data flow and storage unit, and a two-way binding unit for process data and form fields. The mapping unit for form and process is used to load the forms to be displayed according to the process configuration provided by the process designer unit when the business process is started, and at each node of the process, call the dynamic form engine to render the corresponding form page according to the node requirements; the data flow and storage unit is used to submit the data to the process execution unit after the user fills in the data on the form page, verify the data, save it to the database, and simultaneously store the data in the process variables; the two-way binding unit for process data and form fields is used to automatically render the form corresponding to the node when the process enters a certain node, adjust the form content according to the process variables, and after the form is submitted, pass the form data back to the workflow to update the status and variables of the process.

[0019] The process execution and form rendering interaction module includes a process execution stage, a form data submission stage, and a process node transition stage. In the process execution stage, at each node of the process, the process engine unit starts the corresponding form rendering task according to the process path and configuration, calls the dynamic form engine to render the form of the corresponding node, and renders the specific form interface according to the form configuration. In the form data submission stage, after the user fills in the form and submits the form data, the process engine unit receives the data and saves it as a process variable. The process execution unit makes conditional judgments based on the form data to decide whether to continue executing the process or jump to other nodes according to the form data. In the process node transition stage, after the form data is submitted, the process engine unit makes conditional judgments based on the data filled in by the user to determine the next step of the process, and then the process engine unit determines whether to continue the transition through the variable value.

[0020] The beneficial effects of the present invention are as follows:

[0021] 1. The present invention can dynamically generate forms and be closely integrated with the process engine to realize the automated management of business processes, achieving seamless docking between the form designer and the process design engine, and between the form engine and the process execution engine, enabling each link of the business process to dynamically generate and process forms according to actual needs, greatly improving the flexibility and automation of the system, meeting the automated needs of enterprises in complex business processes, improving work efficiency, and reducing manual operation errors.

[0022] 2. The present invention deeply integrates the dynamic form with the process engine, enabling the form to be dynamically generated at each process node and automatically interact with the process execution status and process variables, thereby realizing the automated and flexible management of business processes.

[0023] 3. The present invention solves the problems of poor flexibility and difficult integration of traditional systems through innovative modular design and efficient system interaction mechanisms. Through the deep integration of the dynamic form engine and the workflow engine, it can achieve automatic adaptation of forms and processes, automatic data collection, and automated process control, greatly improving the management efficiency and flexibility of business processes. Brief Description of the Drawings

[0024] Figure 1 It is the front view of the present invention. Detailed Embodiments

[0025] To deepen the understanding of the present invention, the following will further elaborate on the present invention in combination with embodiments. These embodiments are only used to explain the present invention and do not constitute a limitation to the protection scope of the present invention.

[0026] Embodiment 1

[0027] According to Figure 1As shown in the figure, this embodiment proposes a business process system that combines a dynamic form and a process engine, including a code generation module, a flexible form module, and a dynamic process module. The code generation module is used to automatically generate code files related to the functions of adding, deleting, querying, and modifying according to the database table structure, and uniformly compress and package them into a code package;

[0028] The flexible form module is used to design and configure forms based on the code package of the above code generation module, support the binding of form fields to data tables in the database, and at the same time provide a visual form designer and a dynamic form engine. The visual form designer is used for users to design forms and customize component extensions. The dynamic form engine is used to dynamically inject extended form functions and is responsible for data submission, verification, and storage;

[0029] The dynamic process module provides process visualization functions and the functions of creating, managing, and executing workflows, allowing users to design business processes and configure task parameters, and supporting the dynamic adjustment and execution of processes. At the same time, it provides the function of adding form configuration items in the process design, binds the dynamic form to the task, generates corresponding forms according to different process node configurations, and interacts with the execution status and process variables of the process.

[0030] The code generation module includes a database connection and table analysis module, a code generation and construction module, and a decompression and introduction module; the flexible form module includes a form designer module, a field and database table binding module, a form verification module, a form rendering and dynamic display module, a form submission and data storage module, a form template and reuse module, and a form version management module; the dynamic process module includes a process designer and a process engine, a process design and form design combination module, a dynamic form and process engine collaboration module, and a process execution and form rendering interaction module.

[0031] Deep integration of dynamic forms with the workflow engine solves the problem of automatic adaptation between form data and process status, enhancing the automation and intelligence of process management; synchronizing automated code generation with form configuration enables automatic code generation based on form design and database structure, not only improving development efficiency but also ensuring system consistency and standardization; through tools such as visual form designers and process graphical editors, users can complete process design and form management without writing complex code, improving system usability and flexibility; through the efficient collaboration of each module, when users fill out forms, the system automatically matches and transfers processes, improving the flexibility and efficiency of business processing; the deep integration of form design and process design, introducing the integration of form designers and process design engines, allows users to intuitively perform dynamic binding of forms and processes, greatly simplifying form management and configuration in traditional process design and avoiding isolated operations between multiple systems; linking dynamic forms with the process engine enables each process node to dynamically display and process form data according to business requirements, enhancing system flexibility and customizability; through automated mapping of form fields and process variables, users do not need to manually configure process variables, and the transfer process of form data is automatically processed, improving system intelligence and automation; through clear hierarchical management of the overall and sub-modules for various functions of forms and processes, the scalability and maintainability of the system are greatly improved, making collaboration between different modules more efficient. In summary, it significantly enhances the management efficiency and flexibility of business processes, solves problems such as high system integration difficulty and separation of workflow and form configuration in the existing technology, and has important technical value and market application prospects.

[0032] Embodiment 2

[0033] According to Figure 1 As shown, this embodiment proposes a business process system combining dynamic forms and a process engine, including a code generation module, a flexible form module, and a dynamic process module;

[0034] Code generation module: used to automatically generate code files related to create, read, update, and delete (CRUD) functions according to the database table structure. The code includes entity classes, data access layer (DAO), service layer (Service), control layer (Controller), etc. All files are uniformly compressed and packaged into a code package. By automatically generating code, the workload of developers is reduced, and the consistency and standardization of the code are ensured.

[0035] The core function of the code generation module is to generate business-related code based on the database table. Its purpose is to reduce the repetitive work of developers in implementing basic CRUD functions and ensure the consistency and reliability of the code.

[0036] Specifically, it includes:

[0037] Database connection and table analysis: Connect to the database based on the database development framework MyBatis-Plus, obtain the table structure, including information such as table fields and data types, and convert them into Java objects;

[0038] Code generation and construction: After analyzing the above Java object structure, fill in the template based on the Velocity template engine to generate the corresponding Java class code, including code files for entity classes, DAO layers, Service layers, etc., and package them into a Zip file code package;

[0039] Unzip and import: Developers unzip the code package and import the generated code files into the project for fine-tuning and testing.

[0040] Flexible form module: Used to design and configure forms based on the code package generated by the above code generation module, and support binding form fields to data tables in the database, defining field types, field validation rules, etc. This module provides a visual form designer. Users can design forms by dragging components, support common form components (such as text boxes, drop-down boxes, radio boxes, etc.), and support custom component extensions. Coupled with directly binding data tables and fields, it simplifies the form design process and reduces errors. Additionally, this module also includes a dynamic form engine, which is developed based on the open-source form-create form rendering engine. It dynamically injects to expand form functions, providing greater flexibility, allowing the system to adjust form content or form at runtime as needed. And it is responsible for data submission, validation, and storage.

[0041] The flexible form module designs forms through a visual interface and associates them with the backend data structure. Users can create forms by dragging on the front-end interface. And output the dynamically generated form configuration (in JSON format), and finally generate a dynamic form page through the dynamic form engine.

[0042] Form Designer

[0043] User interface design: The form designer provides a visual user interface. Users create forms by dragging and selecting components. The designer supports common form elements (such as text boxes, radio boxes, drop-down boxes, check boxes, date pickers, etc.). Users can configure the properties of these components, including name, data type, default value, required field, etc.

[0044] Field Attribute Configuration: The designer supports detailed configuration for each field, including: field name and prompt information (Label); data type (such as text, number, date, etc.), which matches the data type in the database; validation rules (such as required field, maximum length, regular expression validation, etc.); display / hide control logic, which supports dynamically showing or hiding certain fields based on the values of other fields.

[0045] Form Layout: The form designer supports different layout methods (such as single-column, double-column, grid layout, etc.), and users can flexibly adjust the positions and arrangements of form fields.

[0046] Component Expandability: The form designer supports the expansion of custom components. Users can upload custom controls or components according to their needs and use them in the form.

[0047] Field Binding to Database Table

[0048] Automatic Field Binding to Database Table: According to the field attributes configured by the user during form design, the system automatically generates a field mapping relationship associated with the business database table. This module will automatically generate data mapping code based on the table structure and field types in the database to associate the form fields with the corresponding fields in the data table.

[0049] Field Data Binding: When the form is submitted, the data entered by the user will be automatically transmitted to the backend database through an interface. After being formatted and verified according to its type and validation rules, the field data is stored in the database.

[0050] Field Type Validation and Conversion: According to different field data types (such as text, number, date, etc.), the system will automatically perform type validation to ensure that the data meets the requirements of the database table; for date type fields, the system will convert the date into a format that can be stored in the database.

[0051] Form Validation

[0052] Front-end Validation: Before the form is submitted, the system performs immediate validation through front-end JavaScript code to check whether the data entered by the user meets the preset rules (such as required, minimum / maximum length, format validation, etc.). If the validation fails, the system will give corresponding error prompts to avoid submitting invalid data.

[0053] Back-end Validation: When the form is submitted to the back-end server, the back-end will perform validation again to ensure the integrity and accuracy of the data. Back-end validation includes not only the legality of the field values themselves but also the logical validation with other fields (such as whether the start and end times of two date fields are reasonable, or the dependency relationship between the values of a select box and other field values, etc.).

[0054] Dynamic Extension of Validation Rules: The system supports users to customize validation rules. Users can add complex validation logic through a simple configuration interface (for example, a certain field depends on the value of another field, and certain options are only displayed under specific conditions).

[0055] Form Rendering and Dynamic Display

[0056] Form Rendering Engine: This engine is responsible for dynamically rendering the form interface according to the configuration generated by the designer. The rendering process includes generating HTML code, CSS styles, and front-end control logic. During the rendering process, the attributes of form fields (such as type, label, default value, option list, etc.) will generate corresponding front-end elements according to the system configuration.

[0057] Dynamic Field Control: When the form is rendered, some fields may be dynamically displayed or hidden according to the values of other fields. The system provides a "dependency configuration" module where users can configure the display rules of certain fields (for example, when a certain option is selected, other fields will be automatically displayed or hidden).

[0058] Real-time Data Binding and Update: During the form rendering process, some fields may need to be dynamically updated. For example, when selecting a dropdown box, it may trigger data updates in other fields (such as dynamically loading a list of cities). This module supports obtaining real-time data through API interfaces to ensure that the form content is always up-to-date.

[0059] Form Submission and Data Storage

[0060] Form Submission Mechanism: After the user fills out the form and clicks the submit button, the form data will be packaged and sent to the backend server. This module supports multiple form submission methods (such as synchronous, asynchronous, JSON format, etc.).

[0061] Data Storage and Update: The submitted data will be stored in the relevant tables in the database according to the preset field mapping. When the form is submitted, the system will automatically generate SQL statements to perform insert or update operations.

[0062] Process Data Binding: After the form data is stored in the database, it will be bound to the relevant data of the current process task. The form data will become an important process variable in the process engine for use by subsequent nodes. The system supports mapping form data to process variables to ensure data transfer between different task nodes.

[0063] Form Templates and Reusability

[0064] Form Template Library: To improve development efficiency, the flexible form module supports the management and reuse of form templates. Users can save a certain type of form as a template, which can be reused in other business processes. Form templates support operations such as quick import, export, and sharing, facilitating collaboration among different departments within the organization.

[0065] Template Modification and Update: When users use a template, the system dynamically adjusts the template content according to the requirements of the current process. After modifying the template, the system automatically updates the forms related to the template to ensure the unity and consistency of the forms.

[0066] Form Version Management

[0067] Version Control: This function supports the management of form design versions. Each time a form is modified, a new version is generated. Users can view the historical versions of the form and roll back to a previous version as needed.

[0068] Version Release and Rollback: The form version management module supports the release and rollback functions of forms. The released form will be deployed to the production environment for users to use. If there are problems, the system supports rolling back to the previous stable version.

[0069] Dynamic Process Module: This module includes a process designer and a process engine. The process designer is developed based on Vue and BPMN.js and supports the visual design of processes. Users can design business processes through a graphical interface, configure task nodes, conditional judgments, events, etc., and support the dynamic adjustment and execution of processes. The process engine is based on the open-source process engine Flowable to implement the creation, management, and execution of workflows. In addition, this module realizes the integration of dynamic forms and the process engine, supports adding form configuration items in process design, and binds dynamic forms to tasks. This means that when designing business processes, developers can directly assign dynamic forms to each task, making the interaction between business processes and forms seamless. It can generate corresponding forms according to different process node configurations and interact with the execution status and process variables of the process. During the process execution, users fill in form data and submit it. The system stores the form data in the database and automatically transfers to the next process node according to the conditional judgment in the process.

[0070] The dynamic process module realizes the definition of business processes, the control of approval processes, and the rendering of dynamic forms by integrating the process engine and dynamic forms. Users can design flowcharts, select different task nodes, bind dynamic forms, and configure approver strategies for process nodes. The process engine automatically manages the execution of processes according to the designed process definition, including task assignment, process node transfer, etc. Users can also dynamically adjust the process definition and modify the node configuration in the process.

[0071] Process Designer and Process Engine

[0072] Process Designer: Through the front - end process designer, users can create business processes and configure task nodes, conditional judgments, events, etc. in the flow chart. The flow chart supports basic BPMN elements such as various tasks, events, gateways, and connection lines. After the design is completed, users can publish the process to the back - end process engine to generate the corresponding process definition model.

[0073] Process Engine: Developed based on the Flowable framework, it supports functions such as process definition, task management, and process instance control. The core lies in the extended support for dynamic forms, where dynamic forms can be configured at process nodes. The engine is responsible for executing and managing the designed business processes, scheduling and executing process tasks to ensure that the processes are executed in the set order and rules;

[0074] Process Execution: Select a process definition and start the process through the unified interface of the process engine to generate a process instance. After the process is started, the process engine will automatically enter different nodes and display different forms according to the defined conditions and approver strategies, collect data at process nodes and interact with the database through form submissions, and at the same time control the flow of the process.

[0075] Process Task Management: Users can view process instances, query workflow progress, task nodes, submit forms, etc.

[0076] Combination of Process Design and Form Design

[0077] Form Design Stage: In the form designer, users create forms according to business requirements. Each form contains multiple fields, and users can set attributes for each field, such as field type, validation rules, etc. The generated form configuration file is passed to the process designer to bind the form to the corresponding process node.

[0078] Process Design Stage: In the process designer, users define the execution order, conditions, and actions of nodes according to the business process and configure forms for each node. Through the form configuration file, the process design engine can dynamically load the required forms. The process designer packages these process configuration information and form information together and publishes them as a process definition to be transferred to the process engine for execution.

[0079] Collaboration between Dynamic Forms and Process Engine

[0080] Mapping between Forms and Processes: When a business process is started, the process engine loads the forms to be displayed according to the process configuration provided by the process designer. At each node of the process, the process engine calls the dynamic form engine to render the corresponding form page. This rendering process includes the display of form fields, the filling of default values, the determination of field types, etc., ensuring that the data required to be collected at the current node can be input through the dynamic form and submitted to the background for storage.

[0081] Data Flow and Storage: After the user fills in the data on the form page, the form engine submits the data to the process execution engine. The process execution engine validates the data, saves it to the database, and stores the data in process variables for subsequent process judgment and conditional flow.

[0082] Two-way Binding between Process Data and Form Fields: There is a two-way binding relationship between the variables of the workflow node and the form fields. When the process enters a certain node, the system automatically renders the form corresponding to that node and adjusts the form content according to the process variables. Similarly, after the form is submitted, the form data is passed back to the workflow engine to update the process status and variables.

[0083] Interaction between Process Execution and Form Rendering

[0084] Process Execution Phase: At each node of the process, the process engine starts the corresponding form rendering task according to the process path and configuration. It calls the dynamic form engine to render the form for the corresponding node, and the form engine renders the specific form interface according to the form configuration generated by the designer.

[0085] Form Data Submission: After the user fills in the form, the form engine submits the form data, and the process engine receives the data and saves it as a process variable. The process execution engine makes conditional judgments based on the form data to decide whether to continue executing the process or jump to other nodes according to the form data.

[0086] Process Node Transition: After the form data is submitted, the process engine can make conditional judgments based on the data filled in by the user to determine the next step of the process. For example, some process nodes may map a certain word in the form to process variables (such as "approval status", "comments", etc.), and then the process engine determines whether to continue the transition based on the variable value.

[0087] The present invention can dynamically generate forms and be closely integrated with a process engine to achieve automated management of business processes, enabling seamless docking between a form designer and a process design engine, and between a form engine and a process execution engine. This allows each link in the business process to dynamically generate and process forms according to actual needs, greatly enhancing the flexibility and automation level of the system, meeting the automated requirements of enterprises in complex business processes, improving work efficiency, and reducing manual operation errors. Moreover, the present invention deeply integrates dynamic forms with the process engine, enabling forms to be dynamically generated at each process node and automatically interact with the process execution status and process variables, thereby achieving automated and flexible management of business processes. At the same time, through innovative modular design and an efficient system interaction mechanism, the present invention solves problems such as poor flexibility and difficult integration in traditional systems. Through the deep integration of a dynamic form engine and a workflow engine, it can achieve automatic adaptation of forms and processes, automatic data collection, and automated process control, significantly enhancing the management efficiency and flexibility of business processes.

[0088] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited by the above embodiments. The above embodiments and the descriptions in the specification are only used to illustrate the principles of the present invention. Without departing from the spirit and scope of the present invention, the present invention will have various changes and improvements, and all these changes and improvements fall within the scope of the present invention claimed. The scope of protection claimed by the present invention is defined by the appended claims and their equivalents.

Claims

1. A business process system combining a dynamic form and a process engine, comprising a code generation module, a flexible form module and a dynamic process module, characterized in that: The code generation module is used to automatically generate code files related to the add, delete, check and modify functions according to the database table structure, and uniformly compress and package them into a code package; The flexible form module is used to design and configure forms according to the code package of the above code generation module, and supports binding of form fields with data tables in the database. It also provides a visual form designer and a dynamic form engine. The visual form designer allows users to design forms and customize component extensions. The dynamic form engine is used to dynamically inject extended form functions and is responsible for data submission, verification and storage. The dynamic process module provides process visualization functions and workflow creation, management and execution functions for users to design business processes and configure task parameters, and supports dynamic adjustment and execution of processes. At the same time, it provides the function of adding form configuration items in process design, binding dynamic forms with tasks, generating corresponding forms according to different process node configurations, and interacting with the execution status and process variables of the process.

2. A business process system combining dynamic forms and process engines according to claim 1, characterized in that: The code generation module includes a database connection and table analysis module, a code generation construction module and a decompression and introduction module. The database connection and table analysis module is connected to the database based on the database development framework MyBatis-Plus, obtains the table structure, including the fields and data types of the table, and converts it into a Java object; the code generation construction module is used to analyze the Java object structure, fill in the template based on the Velocity template engine, generate the corresponding Java class code, including the entity class, DAO layer, Service layer code files, and package them into a Zip file code package; the decompression and introduction module is used to provide developers with a channel to decompress the code package, and introduce the generated code file into the project for adjustment and testing.

3. A business process system combining dynamic forms and process engines according to claim 1, characterized in that: The flexible form module includes a form designer module, a field and database table binding module, a form verification module, a form rendering and dynamic display module, a form submission and data storage module, a form template and reuse module, and a form version management module; the form designer module includes a user interface unit, a field attribute configuration unit, a form layout unit, and a component extension unit. The user interface unit allows users to create forms by dragging and selecting components, and configure the attributes of components; the field attribute configuration unit provides detailed configuration of each field, including field name and prompt information, data type, verification rules, and display / hide control logic; the form layout unit is used to provide different layout methods, allowing users to flexibly adjust the position and arrangement of form fields; the component extension unit is used for users to upload custom controls or components according to needs and use them in forms.

4. A business process system combining dynamic forms and process engines according to claim 3, characterized in that: The field and database table binding module includes a field automatic binding database table unit, a field data binding unit, and a field type checking and conversion unit. The field automatic binding database table unit is used to automatically generate a field mapping relationship associated with a business database table according to the field attributes configured by the user during form design, and automatically generate a data mapping code according to the table structure and field type in the database to associate the form field with the corresponding field in the data table; The field data binding unit is used to automatically transmit the data entered by the user to the back-end database through the interface when the form is submitted, and at the same time, the field data is verified according to its type and verification rules and then stored in the database; the field type verification and conversion unit is used to automatically perform type verification according to the different field data types to ensure that the data meets the requirements of the database table.

5. A business process system combining a dynamic form and a process engine according to claim 4, characterized in that: The form verification module includes a front-end verification unit, a back-end verification unit and a dynamic expansion unit of verification rules. The front-end verification unit is used to perform real-time verification through front-end JavaScript code before the form is submitted to check whether the data entered by the user complies with the preset rules; the back-end verification unit is used to perform verification again when the form is submitted to the back-end server to ensure the integrity and accuracy of the data; the dynamic expansion unit of verification rules is used for users to customize verification rules.

6. A business process system combining a dynamic form and a process engine according to claim 5, characterized in that: The form rendering and dynamic display module includes a form rendering engine unit, a dynamic field control unit, and a real-time data binding and updating unit. The form rendering engine unit is responsible for dynamically rendering the form interface according to the configuration generated by the designer; The dynamic field control unit is used to provide a dependency configuration module when rendering a form, so that users can configure the display rules of specified fields; the real-time data binding and updating unit is used to obtain real-time data through an API interface to ensure that the form content is always up to date.

7. A business process system combining a dynamic form and a process engine according to claim 6, characterized in that: The form submission and data storage module includes a form submission mechanism unit, a data storage and update unit, and a process data binding unit. The form submission mechanism unit is used to provide multiple form submission methods after the user fills in the form; the data storage and update unit is used to store the submitted data in the relevant table of the database according to the preset field mapping, and automatically generate SQL statements to perform insert or update operations; The process data binding unit is used to bind the form data with the relevant data of the current process task after it is stored in the database, so that the form data becomes the process variable in the process engine for use by subsequent nodes, and supports mapping the form data with the process variables.

8. A business process system combining a dynamic form and a process engine according to claim 7, characterized in that: The form template and reuse module includes a form template library and a template modification and update unit. The form template library provides management and reuse of form templates and supports fast import, export and sharing operations. The template modification and update unit is used to dynamically adjust the template content according to the needs of the current process when the user uses the template, and automatically update the form related to the template. The form version management module includes a version control unit and a version publishing and rollback unit. The version control unit is used to manage the version of the form design and provide historical versions; the version publishing and rollback unit is used to publish and rollback the form.

9. A business process system combining dynamic forms and process engines according to claim 1, characterized in that: The dynamic process module includes a process designer and a process engine, a process design and form design combination module, a dynamic form and process engine collaboration module, and a process execution and form rendering interaction module; The process designer and process engine include a process designer unit, a process engine unit, a process execution unit, and a process task management unit. The process designer unit allows users to create business processes and configure task nodes, conditional judgments, and events in a flow chart, and publishes the process to the back-end process engine to generate a corresponding process definition model; the process engine unit is developed based on the Flowable framework, supports process definition, task management, process instance control, and extends support for dynamic forms, which is used to configure dynamic forms at process nodes, and at the same time execute and manage designed business processes, and schedule and execute process tasks; The process execution unit is used to select a process definition, start the process through a unified interface of the process engine unit, generate a process instance, and control the flow of the process; The process task management unit is used by users to view process instances, query workflow progress, task nodes, and submit forms; The process design and form design combination module includes a form design phase and a process design phase. In the form design phase, the user creates a form according to business needs. Each form contains multiple fields. The user sets properties for each field. The generated form configuration file is passed to the process designer unit to bind the form to the corresponding process node. During the process design phase, the user defines the execution order, conditions and actions of the nodes according to the business process, and configures a form for each node. Through the form configuration file, the required form is dynamically loaded, and the process configuration information and form information are packaged and published as a process definition, which is then transferred to the process engine for execution.

10. A business process system combining a dynamic form and a process engine according to claim 9, characterized in that: The dynamic form and process engine collaboration module includes a form and process mapping unit, a data flow and storage unit, and a process data and form field two-way binding unit. The form and process mapping unit is used to load the form to be displayed according to the process configuration provided by the process designer unit when the business process is started, and at each node of the process, the dynamic form engine is called according to the node requirements to render the corresponding form page; the data flow and storage unit is used to submit the data to the process execution unit after the user fills in the data on the form page, verify the data, save it to the database, and store the data in the process variables; the process data and form field two-way binding unit is used to automatically render the form corresponding to a node when the process enters a node, and adjust the form content according to the process variables. After the form is submitted, the form data is passed back to the workflow to update the state and variables of the process; The process execution and form rendering interaction module includes a process execution phase, a form data submission phase and a process node transfer phase. In the process execution phase, the process engine unit starts the corresponding form rendering task at each node of the process according to the process path and configuration, calls the dynamic form engine to render the form of the corresponding node, and renders a specific form interface according to the form configuration; In the form data submission phase, after the user fills in the form, the form data is submitted, the process engine unit receives the data and saves it as a process variable, and the process execution unit makes a conditional judgment based on the form data to decide whether to continue executing the process or jump to other nodes based on the form data; In the process node transfer stage, after the form data is submitted, the process engine unit performs conditional judgment based on the data filled in by the user to determine the next step of the process, and then the process engine unit determines whether to continue the flow based on the variable value.

Images