Method, device, equipment and medium for establishing association architecture based on metadata drive

By defining ordinary and dynamic association fields in low-code platforms and establishing relational metadata and storage space for them, the problem of not being able to associate different types of tables in the existing technology is solved, and dynamic association and data integrity of multiple types of objects are achieved. meets the needs of complex scenarios.

CN117971184BActive Publication Date: 2024-12-06和创(北京)科技股份有限公司
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410153945.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-02-02
Publication Date
2024-12-06
Estimated Expiration
2044-02-02

AI Technical Summary

Technical Problem

The existing low-code platform has limitations in the relationship management, and it is impossible to effectively allow the association fields to be associated with different types of business tables, and cannot meet the needs of complex scenarios.

Method used

By defining ordinary association fields and dynamic association fields, establishing relationship metadata for them, allocating storage space, realizing the association relationship between business objects and multiple types of business objects, and using integrity and conditional constraints to ensure legal association mapping.

Benefits of technology

In the low-code platform, dynamic association of multiple types of objects in the associated field is realized, which meets the needs of complex associated relationship scenarios, ensures data integrity and consistency, and improves the flexibility of associated relationships.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117971184B_ABST
    Figure CN117971184B_ABST
Patent Text Reader

Abstract

The present invention provides a method, device, equipment and medium for establishing an association architecture based on metadata drive, wherein the method includes: defining logical fields corresponding to each business, wherein the logical fields include common association fields and dynamic association fields; establishing a relationship metadata for the common association fields, establishing one or more relationship metadata for the dynamic association fields, and defining constraint rules for verifying the actual form corresponding to each relationship metadata, wherein the dynamic association fields can establish an association relationship between a business object and multiple types of business objects; allocating storage space to the logical fields according to the field type, allocating a storage column for storing the actual form association object to the common association fields, and allocating a storage column for storing the association business identifier and a storage column for storing the actual form association object to the dynamic association fields. The present invention establishes an association relationship between the current business and other multiple types of businesses through metadata.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method, device, equipment and medium for establishing an association architecture based on metadata drive. Background Art

[0002] A low-code platform is a program development tool that simplifies the development process through a graphical interface, enabling non-technical users to create, customize, and manage applications, thereby improving development efficiency and supporting business process automation.

[0003] In related technologies, low-code platforms have limitations in relationship management. The logical fields of business objects are usually mapped to the columns of physical tables. When logical fields need to express relationships, traditional foreign key mechanisms usually only allow fields to be associated with one type of table, which cannot meet complex scenarios that require simultaneous association of multiple types of tables. Taking the payment scenario as an example, the payment object needs to establish relationships with the project and the payment object respectively. The payment object only needs to establish a general relationship with the project object, while the payment object may be Party A's customer or supplier. It is necessary to choose to establish a relationship with Party A's customer object or supplier object based on actual conditions.

[0004] Based on the above analysis of the development status of the technical field, the existing technical solutions lack solutions that allow association fields to associate with different types of business tables. Summary of the invention

[0005] The purpose of the present invention is to provide a method, device, equipment and medium for establishing an association architecture based on metadata drive, aiming to solve the above-mentioned problems in the prior art.

[0006] According to a first aspect of an embodiment of the present invention, a method for establishing a metadata-driven association architecture is provided, comprising:

[0007] Define the logical fields corresponding to each business, where the logical fields include common association fields and dynamic association fields;

[0008] Establish a relationship metadata for common association fields, establish one or more relationship metadata for dynamic association fields, and define constraint rules for each relationship metadata for verifying the actual form. Dynamic association fields can establish associations between business objects and multiple types of business objects.

[0009] Storage space is allocated to logical fields according to field types, a storage column for storing actual form-related objects is allocated to common association fields, a storage column for storing association business identifiers and a storage column for storing actual form-related objects are allocated to dynamic association fields, and an established association architecture is obtained.

[0010] According to a second aspect of an embodiment of the present invention, there is provided a metadata-driven association architecture establishment device, comprising:

[0011] The logical field definition module is used to define the logical fields corresponding to each business, wherein the logical fields include common association fields and dynamic association fields;

[0012] A relationship metadata establishment module is used to establish a relationship metadata for a common relationship field, establish one or more relationship metadata for a dynamic relationship field, and define constraint rules corresponding to each relationship metadata for verifying the actual form, wherein the dynamic relationship field can establish a relationship between a business object and multiple types of business objects;

[0013] The storage space allocation module is used to allocate storage space to logical fields according to field types, allocate a storage column for storing actual form-related objects to common association fields, allocate a storage column for storing association business identifiers and a storage column for storing actual form-related objects to dynamic association fields, and obtain an established association architecture.

[0014] According to a third aspect of an embodiment of the present invention, there is provided an electronic device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the computer program is executed by the processor, the steps of the method for establishing an association architecture based on metadata-driven operation are implemented as provided in the first aspect of the present disclosure.

[0015] According to a fourth aspect of an embodiment of the present invention, a computer-readable storage medium is provided, on which a program for implementing information transmission is stored. When the program is executed by a processor, the steps of the method for establishing an association architecture based on metadata-driven provided in the first aspect of the present disclosure are implemented.

[0016] The technical solution provided by the embodiment of the present invention includes the following beneficial effects: the concept of metadata is introduced in the low-code platform implementation, and the associated fields can not only associate single-type objects in the traditional way, but also support dynamic association of multiple different types of objects. It can establish complex association relationship scenarios according to user needs, and ensure that users can only use legal actual association mappings through integrity constraints and conditional constraints.

[0017] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate one or more embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0019] Figure 1 is a flowchart of a method for establishing an association architecture based on metadata drive according to an embodiment of the present invention;

[0020] Figure 2 is a schematic diagram of a field metadata table of an embodiment of the present invention;

[0021] Figure 3 is a schematic diagram of a relational metadata table of an embodiment of the present invention;

[0022] Figure 4 is a schematic diagram of establishing actual association mapping according to an embodiment of the present invention;

[0023] Figure 5 is a schematic diagram of an association relationship index table according to an embodiment of the present invention;

[0024] Figure 6 is a schematic diagram of a metadata-driven association architecture establishment device according to an embodiment of the present invention;

[0025] Figure 7 is a schematic diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0026] In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the following will be combined with the drawings in one or more embodiments of this specification to clearly and completely describe the technical solutions in one or more embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this document.

[0027] Method Embodiment

[0028] According to an embodiment of the present invention, a method for establishing an association architecture based on metadata drive is provided. Figure 1 is a flowchart of a method for establishing a metadata-driven association architecture according to an embodiment of the present invention. Figure 1 As shown, the metadata-driven association architecture establishment method according to an embodiment of the present invention specifically includes:

[0029] In step S110, the logical fields corresponding to each business are defined, wherein the logical fields include common association fields and dynamic association fields, specifically including:

[0030] Define each logical field by defining the business identifier, field identifier, field name and field type. The business identifier represents the business name, the field identifier is the unique identifier for different fields in each business, and the field name is used to distinguish the fields within the business. Corresponding to the field identifier, the field type includes common association fields, dynamic association fields and other common types of fields. Other common types of fields include numeric type, text type, date and Boolean value, etc. Figure 2 Schematic diagram of a field metadata table of an embodiment of the present invention. Figure 2 As shown, Figure 2 The meta_field table in the table represents the metadata table corresponding to the logical field. At this time, the corresponding storage column name has not been assigned.

[0031] In step S120, a relationship metadata is established for a common association field, one or more relationship metadata is established for a dynamic association field, and constraint rules corresponding to each relationship metadata for verifying the actual form are defined, wherein the dynamic association field can establish an association relationship between a business object and multiple types of business objects, specifically including:

[0032] A corresponding piece of relational metadata is created for each common relational field. With the common relational field as the medium, the relational metadata between the current business to which the common relational field belongs and the referenced business is created. The logical field with the field ID 1004 represents the project. The payment business can only correspond to one project in the same scenario, so only one piece of relational metadata can be created.

[0033] Multiple corresponding relationship metadata are established for each dynamic association field. With the dynamic association field as the medium, relationship metadata is established between the current business to which the dynamic association field belongs and multiple referenced businesses. The logical field with field identifier 1005 identifies the payment object. The payment business may correspond to multiple payment objects in the same scenario, such as Party A's customer project_owner or supplier supplier.

[0034] According to the actual business situation, set corresponding reference constraint types and conditional constraints for all established relationship metadata. The reference constraint type indicates the constraints on the upstream and downstream relationships between the current business and the referenced business, and the conditional constraint indicates the constraints on the specific values ​​of the logical fields between the current business and the referenced business when the actual form is entered.

[0035] The reference constraint types specifically include strict mode, cascade mode and empty mode. The strict mode means that when deleting the upstream business data of the actual form, if the upstream business data has associated downstream business data, deletion is not allowed. The cascade mode means that when deleting the upstream business data of the actual form, the associated downstream business data must be deleted together. The empty mode means that when deleting the upstream business data of the actual form, the associated downstream business data will be set to null value.

[0036] Figure 3 Schematic diagram of a relational metadata table according to an embodiment of the present invention. Figure 3 As shown in the figure, each row of data in meta_ref represents a piece of relationship metadata.

[0037] In step S130, storage space is allocated to the logical field according to the field type, a storage column for storing the actual form associated object is allocated to the common associated field, and a storage column for storing the associated business identifier and a storage column for storing the actual form associated object are allocated to the dynamic associated field, and the established association architecture is obtained, which specifically includes:

[0038] In the storage table used to store actual form fields, a storage column for storing the primary key corresponding to the associated business is allocated to the common associated field, a storage column for saving the associated business identifier and a storage column for storing the primary key corresponding to the associated business are allocated to the dynamic associated field, wherein the associated business identifier is the business identifier of the referenced business, and storage columns for storing corresponding numerical values ​​are allocated to other common type fields, wherein the storage columns are empty before the actual form is entered.

[0039] After the corresponding storage column is allocated, the allocated storage column information is recorded in Figure 2 In the meta_field table and meta_obj table, meta_obj represents the management metadata table, data_table_1 and data_table_2 represent the storage tables of two physical spaces, and the management metadata table mainly records the table names of the storage tables corresponding to different businesses to facilitate unified management. In this embodiment, the space allocated for the project is listed as col4, and the space allocated for the payment object is listed as col5 and col6.

[0040] The method further comprises:

[0041] In step S140, the actual form is entered based on the existing relationship metadata, and the constraint rules are used to determine whether the actual form meets the entry requirements. All actual forms that meet the conditions are screened out through the constraint rules. Preferably, the user selects the form to be entered from the actual forms that meet the constraint conditions according to the situation, and the information of the objects in the actual forms that meet the requirements is stored in the storage columns corresponding to the logical fields to obtain the established association relationship instance;

[0042] During the actual input process, the actual form is entered based on the existing dynamic association field relationship metadata, and the business identifier to be associated is selected from the business identifiers associated with one or more relationship metadata. Preferably, the actual associated business data can be selected from the actual associated business objects to obtain an instance.

[0043] Figure 4 is a schematic diagram of establishing the actual association mapping in an embodiment of the present invention, such as Figure 4 As shown, the situation of the storage table after actual entry is shown. When the current business is the payment business payment, it is necessary to establish a general association relationship with the engineering project project. Therefore, in the storage table data_table_1 that stores the physical information of the payment business, col4 stores the primary key value of the specific business of the engineering project. In this embodiment, the primary key value is the id of the engineering project, and the col4 column corresponding to the payment business in data_table_1 can only store the primary key of the engineering project project; the payment object of the payment business is sometimes the upstream Party A customer, and sometimes it is the downstream supplier. When the payment object is the Party A customer, the value of the col5 column is the Party A customer project_owner, and the col6 column stores the specific primary key value id of the Party A customer. When the payment object is the supplier, the col5 column stores the supplier supplier, and the col6 column stores the specific primary key value id of the supplier, thereby realizing dynamic association.

[0044] Based on the existing relationship metadata, add or delete relationship metadata or modify the information in the existing relationship metadata according to actual needs.

[0045] Figure 5 Schematic diagram of an association relationship index table of an embodiment of the present invention. Figure 5 As shown, the specific information included in the association relationship index table is displayed. The association relationship index table is used to locate the specific mapping space position of the association field in the physical storage table, which is convenient for data search of specific associated businesses. The table name of the association relationship index table can be stored in a column in meta_ref.

[0046] To sum up, in response to the current problems, the above technical solution of the embodiment of the present invention proposes a method for establishing an association architecture based on metadata-driven, and introduces the concept of metadata in the low-code platform implementation. The association field can not only associate a single type of object in the traditional way, but also realize the dynamic association of multiple different types of objects by allocating two columns of physical storage space in the storage table for the logical fields of the dynamic association relationship. Through dynamic association, association relationships can be established with data of different business types; integrity constraints and conditional constraints are used to ensure that users can only use legal actual association mappings. The defined integrity constraints include strict mode, cascade mode and empty mode, which ensures data integrity and consistency between tables; users can add, delete or modify the established association relationships according to actual needs, making the association relationships between business objects more flexible and able to meet the complex scenarios of actual application of association relationships.

[0047] Device Embodiment

[0048] According to an embodiment of the present invention, a metadata-driven association architecture establishment device is provided. Figure 6 is a schematic diagram of a metadata-driven association architecture establishment device according to an embodiment of the present invention. Figure 6 As shown, the metadata-driven association architecture establishment device according to an embodiment of the present invention specifically includes:

[0049] The logical field definition module 60 is used to define the logical fields corresponding to each business, wherein the logical fields include common association fields and dynamic association fields, and are specifically used to:

[0050] Each logical field is defined by defining the business identifier, field identifier, field name and field type. The business identifier represents the business name, the field identifier is the unique identifier for different fields in each business, and the field type includes common association fields, dynamic association fields and other common types of fields.

[0051] The relationship metadata establishment module 62 is used to establish a relationship metadata for a common association field, establish one or more relationship metadata for a dynamic association field, and define constraint rules corresponding to each relationship metadata for verifying the actual form, wherein the dynamic association field can establish an association relationship between a business object and multiple types of business objects, specifically used for:

[0052] A corresponding piece of relational metadata is established for each common relational field, and the relational metadata between the current business to which the common relational field belongs and the referenced business is established using the common relational field as a medium;

[0053] Multiple corresponding relationship metadata are established for each dynamic association field, and the relationship metadata between the current business to which the dynamic association field belongs and multiple referenced businesses are established using the dynamic association field as a medium.

[0054] According to the actual business situation, set corresponding reference constraint types and conditional constraints for all established relationship metadata. The reference constraint type represents the constraints on the upstream and downstream relationships between the current business and the referenced business, and the conditional constraint represents the constraints on the specific values ​​of the logical fields between the current business and the referenced business when the actual form is entered.

[0055] The reference constraint types specifically include strict mode, cascade mode and empty mode. The strict mode means that when deleting the upstream business data of the actual form, if the upstream business data has associated downstream business data, deletion is not allowed. The cascade mode means that when deleting the upstream business data of the actual form, the associated downstream business data must be deleted together. The empty mode means that when deleting the upstream business data of the actual form, the associated downstream business data will be set to null value.

[0056] The storage space allocation module 64 is used to allocate storage space for the logical field according to the field type, allocate a storage column for storing the actual form associated object to the common associated field, allocate a storage column for storing the associated business identifier and a storage column for storing the actual form associated object to the dynamic associated field, and obtain the established association architecture, which is specifically used to:

[0057] In the storage table used to store actual form fields, a storage column for storing the primary key corresponding to the associated business is allocated to the common associated field, a storage column for saving the associated business identifier and a storage column for storing the primary key corresponding to the associated business are allocated to the dynamic associated field, wherein the associated business identifier is the business identifier of the referenced business, and storage columns for storing corresponding numerical values ​​are allocated to other common type fields, wherein the storage columns are empty before the actual form is entered.

[0058] The device further comprises:

[0059] The actual entry module 66 is used to enter the actual form based on the existing relationship metadata, determine whether the actual form meets the entry requirements through constraint rules, store the information of the objects in the actual form that meet the requirements into the storage columns corresponding to each logical field, and obtain the established association relationship; based on the existing relationship metadata, add, delete, or modify the information in the existing relationship metadata according to actual needs.

[0060] To sum up, in response to the current problems, the above technical solution of the embodiment of the present invention proposes a metadata-driven association architecture establishment device, introduces the concept of metadata in the low-code platform implementation, alleviates the uncertainty of using only physical storage, and the association field can not only associate a single object in the traditional way, but also supports dynamic association of multiple objects, and can flexibly select one or more associated selected business objects according to actual conditions; in the process of the current business metadata table, a space for storing the corresponding field value of the referenced business and a space for storing the referenced business identifier are allocated to the association field whose field type is a dynamic association relationship, so as to distinguish different referenced businesses; the association relationship between the current business and all referenced businesses is recorded through the association relationship metadata table, which can meet the complex scenarios that need to associate multiple tables at the same time; and conditional constraints are defined in the association relationship metadata table, and the constraint types specifically include strict mode, cascade mode and empty mode, which ensure the applicability and rationality of the association relationship. Users can only select legal associated business data, and finally realize the association of information of multiple tables through association fields.

[0061] Electronic device embodiment

[0062] Figure 7 7 is a schematic diagram of an electronic device according to an embodiment of the present invention. The electronic device 700 may include at least one processor 710 and a memory 720. The processor 710 may execute instructions stored in the memory 720. The processor 710 is connected to the memory 720 through a data bus. In addition to the memory 720, the processor 710 may also be connected to an input device 730, an output device 740, and a communication device 750 through a data bus.

[0063] The processor 710 may be any conventional processor, such as a commercially available CPU. The processor may also include a graphics processor (Graphic Process Unit, GPU), a field programmable gate array (Field Programmable Gate Array, FPGA), a system on chip (System on Chip, SOC), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC) or a combination thereof.

[0064] The memory 720 may be implemented by any type of volatile or nonvolatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0065] In the embodiment of the present disclosure, executable instructions are stored in the memory 720, and the processor 710 can read the executable instructions from the memory 720 and execute the instructions to implement all or part of the steps of any metadata-driven association architecture establishment method in the above exemplary embodiments.

[0066] Computer Readable Storage Medium Embodiments

[0067] In addition to the above-mentioned methods and apparatus, an exemplary embodiment of the present disclosure may also be a computer program product or a computer-readable storage medium storing the computer program product, wherein the computer product includes computer program instructions that can be executed by a processor to implement all or part of the steps described in any of the metadata-driven association architecture establishment methods in the above-mentioned exemplary embodiments.

[0068] The computer program product may be written in any combination of one or more programming languages ​​to write program codes for performing the operations of the embodiments of the present application, including object-oriented programming languages ​​such as Java, C++, etc., and also conventional procedural programming languages ​​such as "C" language or similar programming languages ​​and scripting languages ​​(e.g., Python). The program code may be executed entirely on the user computing device, partially on the user computing device, as an independent software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0069] Computer readable storage media can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can include, for example, but is not limited to, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples of readable storage media include: a static random access memory (SRAM) with one or more wires electrically connected, an electrically erasable programmable read-only memory (EEPROM), an erasable programmable read-only memory (EPROM), a programmable read-only memory (PROM), a read-only memory (ROM), a magnetic memory, a flash memory, a magnetic disk or an optical disk, or any suitable combination of the above.

[0070] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for establishing a metadata-driven association architecture, characterized in that: include: Define the logical fields corresponding to each business, wherein the logical fields include common association fields and dynamic association fields; Establishing a relational metadata for the common relational field, establishing one or more relational metadata for the dynamic relational field, and defining constraint rules for verifying the actual form corresponding to each relational metadata, wherein the dynamic relational field can establish an association relationship between a business object and multiple types of business objects; Allocate storage space to the logical field according to the field type, allocate a storage column for storing the actual form associated object to the common associated field, allocate a storage column for storing the associated business identifier and a storage column for storing the actual form associated object to the dynamic associated field, and obtain an established association architecture, which specifically includes: In the storage table for storing the actual form fields, a storage column for storing the primary key corresponding to the associated business is allocated to the common associated field, a storage column for storing the associated business identifier and a storage column for storing the primary key corresponding to the associated business are allocated to the dynamic associated field, wherein the associated business identifier is the business identifier of the referenced business, and a storage column for storing the corresponding numerical value is allocated to other common type fields, wherein the storage column is a null value before the actual form is entered, wherein the other common type fields include numeric type, text type, date and Boolean value; The method further comprises: An actual form is entered based on the existing relationship metadata. During the actual entry process, the actual form is entered based on the relationship metadata to which the existing dynamic association field belongs. A business identifier to be associated is selected from business identifiers associated with one or more relationship metadata. Whether the actual form meets the entry requirements is determined by the constraint rules. Information on objects in the actual form that meet the requirements is stored in the corresponding storage column to obtain an established association relationship instance. Based on the existing relationship metadata, the relationship metadata is added or deleted, or information in the existing relationship metadata is modified according to actual needs.

2. The method according to claim 1, characterized in that The logic fields corresponding to the definition of each business specifically include: Each logical field is defined by defining a business identifier, a field identifier, a field name and a field type, wherein the business identifier represents the business name, the field identifier serves as a unique identifier for different fields within each business, and the field type includes a common associated field, a dynamic associated field and other common types of fields.

3. The method according to claim 1, characterized in that The step of establishing a piece of relation metadata for the common relation field and establishing one or more pieces of relation metadata for the dynamic relation field specifically includes: A corresponding piece of relationship metadata is established for each common association field, and the relationship metadata between the current business to which the common association field belongs and the referenced business is established using the common association field as a medium; A plurality of corresponding relationship metadata are established for each dynamic association field, and relationship metadata between the current business to which the dynamic association field belongs and a plurality of referenced businesses are established using the dynamic association field as a medium.

4. The method according to claim 3, characterized in that The constraint rules for verifying the actual form corresponding to the metadata of each relationship specifically include: According to the actual business situation, corresponding reference constraint types and conditional constraints are set for all established relationship metadata, wherein the reference constraint type represents the constraints on the upstream and downstream relationships between the current business and the referenced business, and the conditional constraints represent the constraints on the specific values ​​of the logical fields between the current business and the referenced business when the actual form is entered.

5. The method according to claim 4, characterized in that The reference constraint types specifically include strict mode, cascade mode and empty mode, wherein the strict mode means that when deleting the upstream business data of the actual form, if the upstream business data has associated downstream business data, deletion is not allowed; the cascade mode means that when deleting the upstream business data of the actual form, the associated downstream business data must be deleted together; the empty mode means that when deleting the upstream business data of the actual form, the associated downstream business data is set to a null value.

6. A metadata-driven association architecture establishment device, characterized in that: include: A logic field definition module, used to define the logic fields corresponding to each business, wherein the logic fields include common association fields and dynamic association fields; A relationship metadata establishment module, used to establish a relationship metadata for the common association field, establish one or more relationship metadata for the dynamic association field, and define constraint rules corresponding to each relationship metadata for verifying the actual form, wherein the dynamic association field can establish an association relationship between a business object and multiple types of business objects; The storage space allocation module is used to allocate storage space to the logical field according to the field type, allocate a storage column for storing the actual form associated object to the common associated field, allocate a storage column for storing the associated business identifier and a storage column for storing the actual form associated object to the dynamic associated field, and obtain the established association architecture, which is specifically used to: In the storage table for storing the actual form fields, a storage column for storing the primary key corresponding to the associated business is allocated to the common associated field, a storage column for storing the associated business identifier and a storage column for storing the primary key corresponding to the associated business are allocated to the dynamic associated field, wherein the associated business identifier is the business identifier of the referenced business, and a storage column for storing the corresponding numerical value is allocated to other common type fields, wherein the storage column is a null value before the actual form is entered, wherein the other common type fields include numeric type, text type, date and Boolean value; The device further comprises: The actual entry module is used to enter the actual form based on the existing relationship metadata. During the actual entry process, the actual form is entered based on the relationship metadata to which the existing dynamic association field belongs, and the business identifier to be associated is selected from the business identifiers associated with one or more relationship metadata. It is judged whether the actual form meets the entry requirements through the constraint rules, and the information of the objects in the actual form that meet the requirements is stored in the corresponding storage column to obtain an established association relationship instance; based on the existing relationship metadata, the relationship metadata is added, deleted, or the information in the existing relationship metadata is modified according to actual needs.

7. An electronic device, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the computer program is executed by the processor, the steps of the method for establishing a metadata-driven association architecture as described in any one of claims 1 to 5 are implemented.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores an implementation program for information transmission, and when the program is executed by a processor, the steps of the method for establishing an association architecture based on metadata drive as described in any one of claims 1 to 5 are implemented.