A data management function automatic generation system and apparatus

Abstract

This application discloses an automatic data management function generation system and device, applied in the database field. The device is equipped with the system. The system includes: a data source design module for generating table metadata in response to user input commands in a graphical design interface; an automatic form generation module for generating front-end code for forms by recognizing the table metadata; a business layer data encapsulation module for encapsulating the front-end form data, enabling the encapsulated form data to interface with back-end business logic; and a historical data management module for storing historical versions of form data. This reduces workload while avoiding code oversights and errors caused by human error.

Description

Technical Field

[0001] This application relates to the field of databases, and more particularly to a data management function automatic generation system and device. Background Technology

[0002] Traditional project information management systems require software developers to spend a significant amount of time writing HTML code for their functional modules. The development process includes collecting user data display requirements, creating data structures and storing the data, extracting and encapsulating data in the business layer code, developing forms for the front-end pages, and requesting and displaying data on the front-end pages. The entire development process is time-consuming, labor-intensive, and prone to errors. Summary of the Invention

[0003] To address the problem that the development process of existing technologies is labor-intensive and prone to errors, this application provides an automatic data management function generation system and device.

[0004] In a first aspect, embodiments of this application provide an automatic data management function generation system, comprising: a data source design module for generating table metadata in response to user input instructions in a graphical design interface; an automatic form generation module for generating front-end code for a form by recognizing the table metadata; a business layer data encapsulation module for encapsulating the front-end form data so that the encapsulated form data can be connected to the back-end business logic; and a historical data management module for storing historical versions of form data.

[0005] In some embodiments, the table metadata includes field types for one or more fields. The automatic form generation module is further configured to: for each field, determine the field type of the field based on the table metadata, and determine the target form control corresponding to the field type according to a first mapping relationship; wherein, the first mapping relationship includes multiple form controls corresponding to multiple field types respectively; and generate the front-end code of the form based on the target form control corresponding to each field.

[0006] In some embodiments, the table metadata further includes constraints and remarks for one or more fields. The form automatic generation module is further configured to: for each field requiring validation, determine the field type, constraint, or remarks of the field based on the table metadata, and determine the target validation rule corresponding to the field according to a second mapping relationship; wherein, the second mapping relationship includes multiple validation rules corresponding to multiple field attributes, the field attributes being field type, constraint, or remarks; and generate the front-end code of the form based on the target validation rules corresponding to each field.

[0007] In some embodiments, the business layer data encapsulation module includes: an entity layer for representing form data using entity classes or data transfer objects; a service layer for providing interfaces for validating, storing, updating, and querying form data; and a cache layer for caching predetermined target form data.

[0008] In some embodiments, the caching layer is further configured to: cache the target form data in memory or front-end local storage.

[0009] In some embodiments, the historical data management module is further configured to: extract form data from historical versions; generate an initial data document based on the form data from historical versions; convert the initial data document to obtain an uneditable target data document; and save the target data document.

[0010] In some embodiments, when converting the initial data document, the historical data management module is configured to archive the target data document according to form version.

[0011] In some embodiments, the target data document is a PDF document. When converting the initial data document, the historical data management module is configured to: convert the initial data document into an OpenXML document based on form rules and Java Architecture for XMLBinding; fix the form structure and form data in the OpenXML document to obtain a Word document; and convert the Word document into a PDF document.

[0012] In some embodiments, when converting the Word document to a PDF document, the historical data management module is configured to: convert the Word document to a PDF document using Docx4J and add a watermark to the PDF document.

[0013] Secondly, embodiments of this application provide a data management function automatic generation device, which is equipped with the data management function automatic generation system as described in the first aspect.

[0014] The technical solution provided in this application has the following advantages compared with the prior art: (1) Provide a data management function automatic generation system that can reduce the function development cost and development technical difficulty. Through no code or a small amount of code writing, non-professional developers can realize the development and application of the functional modules of the project information management system.

[0015] (2) Traditional functional module development usually requires developers to write code manually, which is a huge workload and prone to errors. By using the data management function to automatically generate the code for data sources, form modules, etc., the workload can be reduced while avoiding code omissions and errors caused by human factors.

[0016] (3) Business personnel can also quickly implement application requirements and realize the online and shared construction of business. Through the on-demand organizational model and various business forms, applications can be expanded as needed to achieve full-process management of data and business.

[0017] (4) Historical data archiving is used to encapsulate and preserve the original data format and content, ensuring the original appearance of form content and data. Through conversion, watermarking and other technical means, the security management of multiple versions of historical data and the technical support for historical data traceability are ensured. Attached Figure Description

[0018] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0019] Figure 1 An exemplary block diagram of the data management function automatically generated system provided in the embodiments of this application is shown.

[0020] Figure 2 A schematic diagram of an automatic data management function generation system provided in a preferred embodiment of this application.

[0021] Figure 3 An exemplary block diagram of the device automatically generated for the data management function provided in the embodiments of this application is shown. Detailed Implementation

[0022] To better understand the above-mentioned objectives, features, and advantages of this application, embodiments of this application will be further described below. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.

[0023] Numerous specific details are set forth in the following description to provide a thorough understanding of this application, but this application may also be implemented in other ways than those described herein. Clearly, the embodiments described in the specification are only a portion of, and not all, of the embodiments of this application.

[0024] Figure 1 An exemplary block diagram of the system for automatically generating data management functions provided in the embodiments of this application is shown. Figure 1 As shown, the automatic data management function generation system 100 (hereinafter referred to as system 100) includes a data source design module 110, an automatic form generation module 120, a business layer data encapsulation module 130, and a historical data management module 140.

[0025] The data source design module 110 generates table metadata in response to user input in the graphical design interface. Table metadata defines the database structure (or table structure). (For example only, see reference only.) Figure 2 A database structure includes elements such as fields, indexes, foreign keys, and constraints.

[0026] In some embodiments, the data source design module 110 is also configured to generate entity class definitions or database configuration files in response to instructions entered by the user in the graphical design interface.

[0027] The main function of the data source design module 110 is to facilitate business and system administrators (non-professional developers) in designing table structures according to business needs. This module can generate corresponding table metadata. The data source design module 110 can be integrated with vendor database connection modules to achieve compatibility with commercially available and open-source databases.

[0028] The data source design module 110 enables visual structured modeling through a graphical design interface. In practical applications, the configuration of database parameters such as Chinese and English names, and field types is first implemented through the developed page. Then, the data source design module 110 creates table metadata described using Database Definition Language (DDL), which is then distributed to the database from the system presentation layer through the system business layer. This allows for visual management and maintenance of the data source.

[0029] The form auto-generation module 120 is used to generate the front-end code for forms by recognizing table metadata. The front-end code displays the form interface and collects user input through it, allowing users to enter, modify, and view form data.

[0030] In some embodiments, the form automatic generation module 120 can match form controls according to field types to generate the front-end code of the form. Specifically, the table data includes field types of one or more fields, and the form automatic generation module 120 is further configured to: for each field, determine the field type of the field based on the table data, and determine the target form control corresponding to the field type of the field according to a first mapping relationship, wherein the first mapping relationship includes multiple form controls corresponding to multiple field types respectively; and generate the front-end code of the form based on the target form controls corresponding to each field. As an example only, when the field type is a string, the target form control is a text box; when the field type is a date, the target form control is a date picker; when the field type is a boolean value, the target form control is a radio button or a checkbox.

[0031] In some embodiments, the data source design module 110 is further configured to: call a large language model (LLM) capable of writing code, using table metadata as input to the large model, to obtain the front-end code of the form output by the large model. The large model can be obtained by fine-tuning a pre-trained model based on the Transformer architecture using a training set, wherein the training samples include table metadata and the front-end code of the corresponding form.

[0032] In some embodiments, the form automatic generation module 120 can also match validation rules based on field type, constraints, or remarks. Specifically, the table data also includes constraints and remarks for one or more fields. The form automatic generation module 120 is further configured to: for each field requiring validation, determine the field type, constraints, or remarks of the field based on the table data, and determine the target validation rule corresponding to the field according to a second mapping relationship, wherein the second mapping relationship includes multiple validation rules corresponding to multiple field attributes, the field attributes being field type, constraints, or remarks; and generate the front-end code of the form based on the target validation rules corresponding to each field. As an example only, when the field type is email, the target validation rule is used to check whether the file format is correct, for example, whether it is a .eml file or a .msg file; when the field constraint is NOT NULL (i.e., the corresponding field is required), the target validation rule is used to verify whether the field value is empty; when the field constraint is UNIQUE, the target validation rule is used to verify whether the field value (such as username) is unique; when the remarks contain keywords such as telephone, mobile phone, ID card, etc., the target validation rule is used to verify whether the number of digits and specific parts of the number are valid.

[0033] In some embodiments, the data source design module 110 is also configured to update table metadata in response to instructions entered by a user (such as a system administrator) in a graphical design interface, for example, adding or deleting fields. Accordingly, the form auto-generation module 120 is also configured to update the front-end code of the form based on the updated table metadata.

[0034] The business layer data encapsulation module 130 is used to encapsulate the form data of the front end, so that the encapsulated form data can be connected to the business logic of the back end.

[0035] The business layer data encapsulation module 130 primarily implements data list and form data extraction. By separating the user interface from the underlying data logic, it provides an efficient, flexible, and stable middleware layer. Through the encapsulation of this middleware layer, forms automatically generated by the front end can directly interface with the backend business logic, reducing repetitive work during development while ensuring the consistency and security of data flow.

[0036] In some embodiments, reference Figure 2The business layer data encapsulation module 130 includes an entity layer, a service layer, and a cache layer. The functions of these layers are described in detail below.

[0037] The entity layer uses entity classes or data transfer objects (DTOs) to represent form data. An entity class, in object-oriented programming, is a class used to represent core data objects in a business domain. It typically maps directly to tables in a database and contains attributes and methods related to business logic. Entity classes usually correspond one-to-one with tables in the database, with each instance representing a record in the table. A DTO is a design pattern primarily used for transferring data between different layers or systems. The main purpose of a DTO is to encapsulate data, reduce network calls, improve system performance, and simplify data interaction.

[0038] The service layer provides interfaces for validating, storing, updating, and querying form data. Taking the form data query interface as an example, this interface can retrieve form data by data ID and user data by user and role information.

[0039] The caching layer is used to cache pre-defined target form data. This target form data consists of frequently used form data, such as system phrases, dropdown menu options, and commonly used field values. In some embodiments, the caching layer further caches the target form data in memory (such as Redis) or on-premises local storage. This reduces redundant backend requests and ensures high-performance support for the system and modules.

[0040] The historical data management module 140 is used to store historical versions of form data. Due to user business needs, data content updates, and other reasons, existing forms need to be dynamically adjusted, but historical data may not be compatible with the adjusted forms. Therefore, historical data archiving is used to encapsulate and preserve the original data format and content, ensuring the original form content and data appearance, and providing historical traceability for project management.

[0041] In some embodiments, the historical data management module 140 is further configured to: extract historical versions of form data; generate an initial data document based on the historical versions of form data; convert the initial data document to obtain an uneditable target data document; and save the target data document. By generating an initial data document containing historical form data and converting it into an uneditable document, the secure management of historical form data is ensured.

[0042] In some embodiments, when saving the target data document, the historical data management module 140 is configured to archive the target data document according to form versions. By saving form data from different periods as different versions of documents, multi-version management of historical form data is achieved.

[0043] In some embodiments, when converting the initial data document, the historical data management module 140 is configured to: convert the initial data document into an OpenXML document based on Java Architecture for XML Binding (JAXB) according to form rules; fix the form structure and form data in the OpenXML document to obtain a Word document; and convert the Word document into a PDF document. Form rules refer to the mapping rules between form data and document structure; for example, a field in the form corresponds to a placeholder in the document. JAXB is a framework in the Java standard used for converting between and between Java and document structures. Specifically, the JAXB document processing includes: first converting the OpenXML document into a Java object; dynamically populating form data by modifying the Java object, for example, replacing placeholders and inserting table rows; and then converting the modified Java object back into an OpenXML document. Fixing here refers to saving the form structure and form data together in the Word document, so that the generated Word document not only contains form data but also retains the form structure (such as table styles).

[0044] In some embodiments, when converting the Word document to a PDF document, the historical data management module 140 is configured to convert the Word document to a PDF document using Docx4J and add a watermark to the PDF document. This strengthens the secure management of historical form data.

[0045] Figure 2 This is a schematic diagram of an automatic data management function generation system provided in a preferred embodiment of this application. For example... Figure 2 As shown, system 100 includes a data source design module 110, an automatic form generation module 120, a business layer data encapsulation module 130, a historical data management module 140, and a database 150.

[0046] Users (e.g., system administrators or regular users) access system 100 through a user interface. For example, a system administrator designs table structures such as fields, indexes, foreign keys, constraints, and comments through a graphical design interface, and the data source design module 110 generates the corresponding table metadata. Similarly, regular users (also known as application users) input, update, or query user data through a user interface.

[0047] The data source design module 110 is used to generate table metadata in response to user input commands in the graphical design interface. Table metadata is used to define table structure such as fields, indexes, foreign keys, constraints, and comments.

[0048] The form auto-generation module 120 identifies field information (such as field type) in the table metadata according to customized rules, and matches form controls for each field based on the identification results. The form auto-generation module 120 also supports matching validation rules for fields that require validation. Furthermore, the form auto-generation module 120 automatically generates the form and front-end code based on the matched form controls and validation rules.

[0049] The business layer data encapsulation module 130 includes an entity layer, a service layer, and a caching layer. The entity layer uses entity classes (Entities) or data transfer objects (DTOs) to represent form data. The service layer provides interfaces for validating, storing, updating, and querying form data. The caching layer caches the target form data in memory (such as Redis) or in the front-end local storage.

[0050] The historical data management module 140 is used to archive target data documents (hereinafter referred to as attachments) containing historical form data according to form version.

[0051] The data source design module 110, the automatic form generation module 120, and the business layer data encapsulation module 130 can be merged into an automatic form configuration module 105. The automatic form configuration module 105 and the historical data management module 140 are involved in data extraction and persistence operations.

[0052] Database 150 is used to store table metadata, rule data (such as custom rules and validation rules), file data (such as emails), form data, business data (such as orders), and multi-version attachments.

[0053] Figure 3 An exemplary block diagram of the device is automatically generated for the data management functions provided in the embodiments of this application. For example... Figure 3 As shown, the data management function automatic generation device 10 is equipped with the aforementioned data management function automatic generation system 100. The data management function automatic generation device 10 includes, but is not limited to, a server. More details about system 100 and its modules can be found on [website / platform name - implied]. Figure 1 , Figure 2 The relevant information can be found here, so I will not repeat it here.

[0054] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to the process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0055] The above descriptions are merely embodiments of this application, which enable those skilled in the art to understand and implement this application. Various modifications to the embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments described herein, but is to be accorded the widest scope consistent with the principles and features disclosed herein.

Claims

1. A data management function automatic generation system, characterized in that, include: The data source design module is used to generate table metadata in response to user input commands in the graphical design interface; The form auto-generation module is used to generate the front-end code of the form by recognizing the table metadata; The business layer data encapsulation module is used to encapsulate the form data from the front end, so that the encapsulated form data can be connected to the business logic of the back end. The historical data management module is used to save form data from previous versions.

2. The system according to claim 1, characterized in that, The table metadata includes the field types of one or more fields; The automatic form generation module is further used for: For each field, the field type is determined based on the table metadata, and the target form control corresponding to the field type is determined according to the first mapping relationship; wherein, the first mapping relationship includes multiple form controls corresponding to multiple field types respectively; Generate the front-end code of the form based on the target form controls corresponding to each field.

3. The system according to claim 2, characterized in that, The table metadata also includes constraints and remarks for one or more fields; The automatic form generation module is further used for: For each field that needs to be validated, the field type, constraint, or remark of the field is determined based on the table metadata, and the target validation rule corresponding to the field is determined according to the second mapping relationship; wherein, the second mapping relationship includes multiple validation rules corresponding to multiple field attributes respectively, and the field attributes are field type, constraint, or remark; The front-end code for the form is generated based on the target validation rules corresponding to each field.

4. The system according to claim 1, characterized in that, The business layer data encapsulation module includes: The entity layer is used to represent form data using entity classes or data transfer objects; The service layer provides interfaces for validating, storing, updating, and querying form data. A caching layer is used to cache pre-defined target form data.

5. The system according to claim 4, characterized in that, The caching layer is further used for: The target form data is cached in memory or on the front end's local storage.

6. The system according to claim 1, characterized in that, The historical data management module is further used for: Extract form data from historical versions; Generate an initial data document based on the form data from the historical versions; The initial data document is converted to obtain a non-editable target data document; Save the target data document.

7. The system according to claim 6, characterized in that, When saving the target data document, the historical data management module is configured as follows: The target data document is archived according to form version.

8. The system according to claim 6 or 7, characterized in that, The target data document is a PDF document. When converting the initial data document, the historical data management module is configured as follows: According to the form rules, the initial data document is converted into an OpenXML document based on Java Architecture for XML Binding; The form structure and form data in the OpenXML document are fixed to obtain a Word document; Convert the Word document into a PDF document.

9. The system according to claim 8, characterized in that, When converting the Word document to a PDF document, the historical data management module is configured as follows: Convert the Word document to a PDF document using Docx4J and add a watermark to the PDF document.

10. A data management function automatic generation device, characterized in that, The device is equipped with an automatic data management function generation system as described in any one of claims 1 to 9.

Images