Form construction method and device based on entity association model, equipment and medium

Abstract

The invention relates to a form construction method and device based on an entity association model, equipment and a medium, the method comprises the steps that attribute information of to-be-processed entities is acquired, the to-be-processed entities comprise a first entity, a second entity and a third entity which have the same attribute information, and the second entity and the third entity are applied to the first entity; according to the attribute information of the to-be-processed entity, an entity association model is constructed, and a first logic relation between the first entity and other entities and a second logic relation between all the entities and the attribute information of all the entities are described in the entity association model; and generating a form according to the entity association model and the business demand. According to the method provided by the invention, the form is generated according to the entity association model and the business demand, so that the automation and intelligence of form construction are realized, the efficiency of form construction is greatly improved, and the time and error rate of manual operation are reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, and in particular, the present application relates to a form construction method and device based on an entity association model, equipment and medium. BACKGROUND

[0002] With the global entry into the digital economy era, enterprises are experiencing a deep transformation from "informatization" to "digital intelligence". Under this background, the external environment faced by enterprises has undergone fundamental changes: Customer demand individualization: The Internet has given rise to "thousand faces" service needs, and traditional standardized business models are difficult to meet differentiated needs. For example, the Internet of Vehicles platform needs to dynamically generate personalized data queries and forms according to user portraits, and real-time association of multi-dimensional data such as vehicle inventory, spare parts, and vehicle conditions.

[0003] Market competition is white-hot: Enterprise competition shifts from cost advantage to efficiency and innovation speed. Gartner data shows that enterprises with efficient data processing capabilities have a business process response speed that is 30% faster than traditional enterprises, and dynamic forms as the core carrier of data collection and process driving have become a key tool for improving agility.

[0004] Policy compliance is complicated: Industry regulations (such as GDPR data privacy protection and financial industry compliance audit) require enterprises to establish a traceable and configurable digital form system, and traditional hard-coded forms are difficult to meet dynamic compliance needs.

[0005] Traditional enterprises generally face three core problems in business system construction, which become the internal driving force for digital transformation: 1. Data silos and process fragmentation: Each business system (ERP, CRM, OA) is built independently, with repeated definition of form fields and lack of association logic. For example, product tree forms and vehicle forms need to be manually synchronized, resulting in information lag and increased error rates.

[0006] 2. Development efficiency and demand change imbalance: Rapid iteration of business needs (20%-30% of form field adjustment needs per month) and traditional code development cycle (1-2 weeks for a single form modification) form a strong contradiction, and low-code tools are needed to achieve "just-in-time" changes.

[0007] 3. High barriers for non-technical personnel participation: There is a professional gap between business departments and IT departments, and 80% of enterprise form design still relies on IT teams, and business personnel cannot independently construct dynamic forms that meet actual scenarios (such as financial personnel needing to dynamically adjust fields according to monthly, quarterly time dimensions, and tractor, harvester product line dimensions).

[0008] With the maturity of technologies such as cloud computing, big data, and artificial intelligence, an infrastructure can be built for the digital transformation of enterprises: Low-code development platform is popular: Forrester data shows that the global low-code platform market size reached 29 billion US dollars in 2023, with an annual growth rate of 28%. Low-code technology can improve form development efficiency by 5-10 times through visual modeling, making it possible for "business personnel to lead form design".

[0009] Entity association model technology matures: Graph databases (such as Neo4j) and knowledge graph technology break through the bottleneck of complex relationship modeling, supporting enterprises to build dynamic form models containing thousands of entities and their associated relationships.

[0010] Intelligent rule engine and automation: AI-based rule engine can automatically analyze business logic (such as dynamically hiding / displaying form fields based on the business domain of the customer), replacing traditional manual coding of rule configuration, and realizing real-time "data-driven decision-making".

[0011] Based on this, the existing technology uses the following technology to realize the automatic generation of forms: usually through the configuration of field dependency relationship to realize the dynamic association of entities, but it does not solve the problem of automatic generation of complex association rules, for example, the field linkage in the multi-association scenario needs to be manually configured. And in the existing technology, although JSON configuration of form fields is supported, there is a lack of unified management of entity association models, and it is impossible to automatically generate associated fields and rules.

[0012] Therefore, the existing technology has the following technical problems: Low development efficiency: Traditional form development requires a lot of coding to associate fields with business logic, resulting in a long development cycle. For example, it takes several weeks to develop an order form that includes a main-sub table association.

[0013] Lack of flexibility: When business requirements change, the form structure and logic need to be adjusted and re-coded. For example, adding "evaluation management rules" requires modifying the backend interface and front-end code.

[0014] High technical threshold: Non-technical personnel cannot participate in form design, and the cost of demand communication is high. Existing low-code platforms support dynamic field generation, but association rule configuration still requires manual code writing or complex configuration. SUMMARY

[0015] The technical problem to be solved by the present application is to provide a form construction method, device, equipment and medium based on an entity association model, which aims to solve at least one of the above technical problems.

[0016] In a first aspect, the technical solution of the present application to solve the above technical problems is as follows: A form construction method based on an entity association model, the method comprising: attribute information of a to-be-processed entity, the to-be-processed entity including a first entity, a second entity and a third entity having the same attribute information, the second entity and the third entity being applied to the first entity; constructing an entity association model according to the attribute information of the to-be-processed entity, the entity association model describing a first logical relationship between the first entity and other entities and a second logical relationship between each entity and attribute information of each entity; generating a form according to the entity association model and a business requirement.

[0017] The present application has the following beneficial effects: firstly, by obtaining the attribute information of the to-be-processed entity and constructing the entity association model, the first logical relationship between the first entity and other entities and the second logical relationship between each entity and attribute information can be clearly described, and this model construction method makes the structure of the form more clear and the logic more rigorous, providing a solid foundation for subsequent form generation and management. Secondly, generating the form according to the entity association model and the business requirement realizes the automation and intelligentization of form construction, greatly improves the efficiency of form construction and reduces the time and error rate of manual operation.

[0018] On the basis of the above technical solution, the present application can also be improved as follows.

[0019] Further, the first logical relationship includes an association relationship between the first entity and a second entity corresponding to the first entity, and a structural relationship between the first entity and other entities, and the second logical relationship includes a first self-relationship between the first entity and attribute information of the first entity, a second self-relationship between the second entity and attribute information of the second entity, and a third self-relationship between the third entity and attribute information of the third entity.

[0020] The beneficial effects of the above further solution are that by specifically defining the first logical relationship and the second logical relationship, the entity association model is more accurate and specific, and can more accurately reflect the complex relationship between the first entity, the second entity and the third entity, and the internal connection between each entity and its attribute information. This refined logical relationship definition helps to further improve the accuracy and adaptability of form construction, so that it can better meet the needs of different business scenarios. At the same time, the clear logical relationship is also conducive to subsequent logical verification and model adjustment, ensuring that the generated form is logically correct and reliable, thereby improving the stability and reliability of the entire form construction system.

[0021] Further, the above method further includes: performing logical verification on the entity association model; adjusting contents in the entity association model that do not pass the logical verification to obtain an adjusted entity association model.

[0022] The beneficial effect of adopting the further scheme is that after the entity association model is constructed, logical verification can be performed on the model to timely find logical errors, data conflicts or unreasonable places in the model, such as data duplication risk, relationship definition conflict and the like. Adjustment is performed on the content that does not pass the logical verification, which can optimize the model structure and make it more in line with business logic and actual needs. The verification and adjustment process not only improves the quality of the model, but also reduces the risk of form generation failure or data processing error caused by model errors, thereby ensuring the accuracy and stability of the form generated based on the model in actual application.

[0023] Further, the business requirement includes at least one of an addition requirement, a modification requirement, a query requirement, a deletion requirement and a general requirement; If the business requirement includes the addition requirement, a form is generated according to the entity association model and the business requirement, including: According to the addition content corresponding to the addition requirement, the content and the logical relationship in the entity association model are updated to obtain an updated entity association model; The form is generated according to the updated entity association model; If the business requirement includes the modification requirement, a form is generated according to the entity association model and the business requirement, including: According to the modification content corresponding to the modification requirement, the content and the logical relationship in the entity association model corresponding to the modification content are modified to obtain a modified entity association model; The form is generated according to the modified entity association model; If the business requirement includes the query requirement, the method further includes: According to the data query request corresponding to the query requirement, a multi-level association relationship between the form and target data is adopted to implement query on the target data corresponding to the data query request by using a cascade query manner; If the business requirement includes the deletion requirement, a form is generated according to the entity association model and the business requirement, including: According to the to-be-deleted content corresponding to the deletion requirement, the content and the logical relationship in the entity association model corresponding to the to-be-deleted content are deleted to obtain a new entity association model; The form is generated according to the new entity association model.

[0024] The beneficial effect of adopting the further scheme is that the method can also flexibly cope with different business requirements such as adding, modifying, querying, deleting, etc., so that the form can better adapt to the changes and development of enterprise business, and enhance the scalability and adaptability of the system. Finally, through the construction and application of the entity association model, the integration and sharing of internal enterprise data can also be promoted, the utilization and value of data can be improved, and more powerful support can be provided for enterprise decision-making.

[0025] Further, the method further comprises: According to the business requirements, a form service page is generated to complete the business requirements based on the form service page.

[0026] The beneficial effect of adopting the further scheme is that based on the interactive mode of the form service page, the convenience and efficiency of user operation are greatly improved, the learning cost and operation difficulty of users are reduced, and non-technical personnel can also easily perform operations such as adding, modifying, querying, deleting, etc. of the form. At the same time, through centralized management and execution of business requirements by the form service page, the consistency and standardization of business operations can be better guaranteed, and errors and data inconsistency problems caused by scattered operations can be avoided. In addition, the generation and use of the form service page.

[0027] Further, the agricultural machinery entity includes a first entity, a second entity and a third entity having the same attribute, and the first entity, the second entity and the third entity are agricultural machinery, equipment and farm tools, respectively.

[0028] The beneficial effect of adopting the further scheme is that in the field of agricultural machinery, the management effectiveness and accuracy of agricultural machinery data can be improved through the scheme.

[0029] In a second aspect, the present application also provides a form construction device based on an entity association model, which comprises: An acquisition module is configured to acquire attribute information of a to-be-processed entity, the to-be-processed entity including a first entity, a second entity and a third entity having the same attribute information, and the second entity and the third entity being applied to the first entity; An entity association model construction module is configured to construct an entity association model according to the attribute information of the to-be-processed entity, the entity association model describing a first logical relationship between the first entity and other entities, and a second logical relationship between each entity and the attribute information of each entity; A form generation module is configured to generate a form according to the entity association model and business requirements.

[0030] Thirdly, in order to solve the above-mentioned technical problems, the present invention also provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the form construction method based on the entity association model of the present application.

[0031] Fourthly, in order to solve the above-mentioned technical problems, the present invention also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the form construction method based on an entity association model of the present application.

[0032] Additional aspects and advantages of this application will be set forth in part in the description which follows, and will become apparent from the description or may be learned by practice of this application. Attached Figure Description

[0033] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments of the present invention will be briefly introduced below.

[0034] Figure 1 A flowchart illustrating a form construction method based on an entity association model, provided as an embodiment of the present invention; Figure 2 A business process diagram illustrating a form construction method based on an entity association model, provided as an embodiment of the present invention; Figure 3 A flowchart illustrating a form construction method based on business requirements, provided as an embodiment of the present invention; Figure 4 A schematic diagram of a form construction device based on an entity association model provided in one embodiment of the present invention; Figure 5 This is a schematic diagram of the structure of an electronic device provided in one embodiment of the present invention. Detailed Implementation

[0035] The principles and features of the present invention are described below. The examples given are only for explaining the present invention and are not intended to limit the scope of the present invention.

[0036] The technical solution of the present invention and how the technical solution of the present invention solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of the present invention will now be described with reference to the accompanying drawings.

[0037] The solution provided in this invention can be applied to any application scenario that requires generating forms related to agricultural machinery data. The solution provided in this invention can be executed by any electronic device, such as a user's terminal device, including at least one of the following: smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, smart TV, or smart vehicle device.

[0038] This invention provides a possible implementation, such as... Figure 1 The diagram shows a flowchart of a form construction method based on an entity association model. This method can be executed by any electronic device, such as a terminal device, or jointly by a terminal device and a server. For ease of description, the method provided in this embodiment will be described below using a terminal device as the execution subject as an example. Figure 1 The flowchart shown indicates that the method may include the following steps: S10, Obtain the attribute information of the entity to be processed. The entity to be processed includes a first entity, a second entity, and a third entity with the same attribute information. The second entity and the third entity are applied to the first entity. S20. Based on the attribute information of the entity to be processed, construct an entity association model. The entity association model describes the first logical relationship between the first entity and other entities, as well as the second logical relationship between each entity and the attribute information of each entity. S30 generates a form based on the entity association model and business requirements.

[0039] The method of this invention firstly obtains the attribute information of the entities to be processed and constructs an entity association model, which clearly describes the first logical relationship between the first entity and other entities, as well as the second logical relationship between each entity and the attribute information. This model-based construction method makes the form structure clearer and the logic more rigorous, providing a solid foundation for subsequent form generation and management. Secondly, by generating forms based on the entity association model and business requirements, the form construction is automated and intelligent, greatly improving the efficiency of form construction and reducing the time and error rate of manual operations.

[0040] The following specific embodiments further illustrate the solution of the present invention. In these embodiments, the traditional form development model has become a bottleneck in the digital transformation of enterprises. The low-code dynamic form intelligent construction method based on entity association model proposed in this invention precisely addresses the pain points of enterprises in the following scenarios: Complex business modeling: Unify the management of multi-dimensional data relationships through entity association models to avoid duplicate data entry and logical conflicts.

[0041] Agile Requirement Response: Business personnel can independently configure forms through a visual designer to achieve "minute-level" field adjustments and rule updates, adapting to high-frequency business changes.

[0042] Cross-system data linkage: By using an intelligent rule engine to connect data from heterogeneous systems, an end-to-end digital process closed loop is built.

[0043] Enterprise digital transformation is not merely a technological upgrade, but also a restructuring of business models and management thinking. This invention lowers the barrier to form development through technological innovation, improves data collection and process-driven efficiency, and becomes a core enabling tool for enterprises to achieve digital and intelligent transformation.

[0044] Based on this, see Figure 2 The form construction method based on an entity association model provided in this embodiment may include the following steps: S10, Obtain the attribute information of the entity to be processed. The entity to be processed includes a first entity, a second entity, and a third entity with the same attribute information. The second entity and the third entity are applied to the first entity. Here, the first entity, second entity, and third entity refer to three different types of entities. In different application scenarios, the first entity, second entity, and third entity represent different actual entities. Optionally, if the entity to be processed includes agricultural machinery entities, then the first entity, second entity, and third entity with the same attribute information included in the agricultural machinery entity are agricultural machinery, equipment, and agricultural implements, respectively. That is, in the field of agricultural machinery, the first entity can be agricultural machinery, the second entity can be equipment, and the third entity can be agricultural implements. In the field of aircraft, the first entity can be an aircraft, the second entity can be functional equipment, and the third entity can be aerial work equipment (such as a lidar turntable, radiation detector, etc.).

[0045] For ease of understanding, the entity to be processed in this application can be an agricultural machinery entity, the first entity is agricultural machinery, the second entity is equipment, and the third entity is agricultural implements. This application will be further explained below.

[0046] Among them, agricultural machinery refers to specific agricultural machinery, such as tractors, harvesters, and seeders; equipment refers to auxiliary devices or components that can be installed on agricultural machinery, such as navigation equipment and monitoring equipment; and agricultural implements refer to simple tools or auxiliary devices used in agricultural production, such as plows and seeders.

[0047] Different entities correspond to different attribute information. For example, the attribute information of agricultural machinery includes: Agricultural Machinery Number: a unique identifier for the agricultural machinery; Agricultural Machinery Model: the specific model of the agricultural machinery; Manufacturer: information about the manufacturer of the agricultural machinery; Status: the current status of the agricultural machinery, such as "online," "offline," or "under repair"; Other attributes: purchase date, maintenance records, usage duration, etc.

[0048] The equipment's attribute information includes: Equipment Number: A unique identifier for the equipment. Equipment Model: The specific model number of the equipment, used to distinguish different types of equipment. Manufacturer: Information about the equipment's manufacturer. Belonging Agricultural Machinery: The type of agricultural machinery to which the equipment belongs, used to establish the association between the equipment and the agricultural machinery. Equipment Status: The current status of the equipment, such as "online," "offline," or "under maintenance." Other Attributes: Depending on specific business needs, the equipment may also include other attribute information, such as purchase date, maintenance records, and usage duration.

[0049] The attribute information of agricultural machinery includes: Implement Number: A unique identifier for the implement. Implement Type: The specific type of implement. Manufacturer: Information about the manufacturer of the implement. Belonging Implement Number: The implement's corresponding agricultural machinery number, used to establish the association between the implement and the agricultural machinery. Status: The current status of the implement, such as "online," "offline," or "under repair." Other attributes: Purchase date, maintenance records, usage duration, etc.

[0050] In S10, the agricultural machinery entity can include different agricultural machines, different equipment, and different agricultural implements.

[0051] S20. Based on the attribute information of the entity to be processed, construct an entity association model. The entity association model describes the first logical relationship between agricultural machinery and other entities, as well as the second logical relationship between each entity and the attribute information of each entity. Among them, other entities refer to the second and third entities. It can be understood that the entity association model not only describes the first and second logical relationships, but also describes the attribute information of each entity.

[0052] Optionally, the first logical relationship mentioned above includes the association relationship between the first entity and the second entity corresponding to the first entity, as well as the structural relationship between the first entity and other entities. The second logical relationship includes the first self-relationship between the first entity and the attribute information of the first entity, the second self-relationship between the second entity and the attribute information of the second entity, and the third self-relationship between the third entity and the attribute information of the third entity.

[0053] As an example, if the first entity is agricultural machinery, the second entity is equipment, and the third entity is agricultural implements, then the first logical relationship mentioned above includes the association relationship between agricultural machinery and the corresponding equipment, as well as the structural relationship between agricultural machinery and other entities. The second logical relationship includes the first self-relationship between agricultural machinery and the attribute information of agricultural machinery, the second self-relationship between equipment and the attribute information of equipment, and the third self-relationship between agricultural implements and the attribute information of agricultural implements.

[0054] Among them, the association between agricultural machinery and its corresponding equipment refers to the correspondence between agricultural machinery and equipment, such as a one-to-one or one-to-many relationship, which means the correspondence between one agricultural machine and all the equipment installed on the agricultural machine; the structural relationship between agricultural machinery and its corresponding implements includes single entity relationship, attached entity relationship and tree entity relationship.

[0055] In this context, a single-entity relationship refers to a relationship where one entity is completely dependent on another entity. Typically, one entity exists as a subordinate part of another entity and cannot exist independently of the main entity. The function of the single entity depends entirely on the power or control provided by the main entity. Agricultural machinery is usually the main entity, and agricultural implements are the single entities.

[0056] As an example, agricultural machinery is the tractor, and agricultural implements are the seeders. The seeders rely on the tractor for power and traction to complete the sowing operation. The seeder, as a single entity of the tractor, depends entirely on the tractor for power and traction and cannot exist independently of the tractor.

[0057] A dependent entity relationship refers to a situation where a dependent entity exists as a subordinate part of a main entity. This relationship emphasizes the dependency of the dependent entity on the main entity. A dependent entity can typically exist independently of the main entity, but its functionality depends on the main entity. It serves to enhance the functionality of the main entity or provide specific auxiliary functions. Typically, agricultural machinery is the main entity, and equipment is the dependent entity; the dependent entity relationship specifically refers to the equipment being a component or extension of the agricultural machinery.

[0058] As an example, agricultural machinery is a tractor, and equipment is a navigation device. As an accessory to the tractor, the navigation device relies on the tractor for power and control, but the navigation device itself can exist independently and can be used on other devices.

[0059] Tree entity relationships refer to a hierarchical, tree-like structural relationship between entities. This relationship describes the hierarchical relationship between entities, where each entity can have multiple child entities, but each child entity can only have one parent entity. Child entities rely on their parent entities to provide functionality or data structure, but can have their own specific functionality or data. By explicitly defining this tree entity relationship, the hierarchical relationship between entities can be managed more clearly, enabling data linkage and synchronous updates, and improving the efficiency and accuracy of form construction.

[0060] As an example, suppose we have the following entities: agricultural machinery: tractor; equipment: navigation equipment, monitoring equipment; agricultural implements: plow, seeder, harrow; in this scenario, we can construct a tree entity relationship as follows: root entity (parent entity): tractor; child entities: navigation equipment and monitoring equipment; child entities: plow, seeder, and harrow.

[0061] Among them, any one of the first self-relation, the second self-relation, and the third self-relation includes at least one of the following: redundant relation, enumeration relation, value verification relation, formatted relation, and unique relation.

[0062] Redundant relationships refer to the practice in entity association models where the attribute information of certain entities is repeatedly stored or referenced in multiple places to ensure data consistency and integrity. This type of relationship is crucial in database design and data management, especially in scenarios where ensuring data synchronization and consistency is essential.

[0063] As an example, suppose we have the following entities: agricultural machinery: tractor; equipment: navigation device; agricultural implement: plow; in this scenario, the following different attribute information may exist: Agricultural machinery (tractors), attribute information: tractor number, model, manufacturer, status, etc.

[0064] Equipment (navigation equipment), attribute information: navigation equipment number, model, manufacturer, tractor number to which it belongs, status, etc.

[0065] Agricultural implements (plows), attribute information: plow number, type, manufacturer, tractor number, status, etc.

[0066] There is a redundant relationship between the "Tractor ID" attribute of the navigation device and the "Tractor ID" attribute of the tractor; there is also a redundant relationship between the "Tractor ID" attribute of the plow and the "Tractor ID" attribute of the tractor. This redundant storage ensures that the association between the navigation device and the tractor, and the association between the plow and the tractor, is recorded in multiple locations, facilitating querying and management.

[0067] An enumeration relation refers to an entity having a finite, predefined set of values ​​for a particular attribute or field. This type of relation is used to ensure data accuracy and consistency by limiting the range of attribute values ​​and avoiding invalid or erroneous data input.

[0068] As an example, suppose we have the following entities: agricultural machinery: tractor; equipment: navigation equipment; agricultural implements: plow; in this scenario, some attributes may have enumeration relationships, for example: Agricultural machinery status: Possible values ​​are "online", "offline", and "under maintenance".

[0069] Device status: Possible values ​​are "Online", "Offline", and "Under Maintenance".

[0070] Agricultural implement type: Possible values ​​are "plow", "seeder", and "harrow".

[0071] In other words, the enumerated values ​​corresponding to the agricultural machinery status attribute are "online", "offline", and "under maintenance".

[0072] Value validation relationships refer to the rules for validating and verifying the attribute values ​​of entities in an entity association model. These relationships ensure that the attribute values ​​of entities conform to predefined formats, ranges, or conditions, thereby guaranteeing the accuracy and integrity of the data. They can include data format validation, data range validation, and data condition validation. Data format validation rules aim to ensure that attribute values ​​conform to specific formats, such as date formats, phone number formats, and email formats. Data range validation rules aim to ensure that attribute values ​​are within predefined ranges, such as numerical ranges or date ranges. Data condition validation rules aim to ensure that attribute values ​​meet specific conditions, such as certain fields cannot be empty or certain field values ​​must be unique.

[0073] As an example, suppose we have the following entities: agricultural machinery: tractor; equipment: navigation equipment; agricultural implements: plow; in this scenario, some attributes may have value validation relationships, for example: Tractor serial number: must be unique and cannot be repeated.

[0074] Device status: Must be one of the predefined enumeration values ​​(such as "online", "offline", "under maintenance").

[0075] Farm implement type: must be one of the predefined enumeration values ​​(such as "plow", "seeder", "harrow").

[0076] Tractor production date: Must conform to date format (e.g., YYYY-MM-DD).

[0077] Formatting relationships refer to the requirement that the value of an entity's attribute or field must be stored and displayed according to a specific format. This relationship ensures data consistency and readability, facilitating system processing and user understanding. It can include formatting rules (attribute values ​​must conform to specific formatting specifications, such as date format, phone number format, email format, currency format, etc.) and display formats (attribute values ​​must be displayed in a specific format in the user interface or reports to improve user experience and data readability).

[0078] As an example, suppose we have the following entities: Agricultural machinery: Tractor; Equipment: Navigation equipment; Agricultural implements: Plow; In this scenario, some attributes may have formatted relationships, such as: Tractor production date: Must conform to date format (e.g., YYYY-MM-DD).

[0079] Equipment price: Must be in currency format (e.g., $1,234.56).

[0080] Tractor serial number: must conform to a specific serial number format (e.g., TR-001).

[0081] A unique relationship refers to the requirement that the value of a certain attribute or field in an entity association model must be unique within a specific range. This relationship ensures the uniqueness and consistency of data, avoids duplicate data, and thus guarantees the accuracy and integrity of the data. Specifically, it means that the value of a certain attribute or field must be unique within a specific range (such as the entire database, a table, or an entity), and there cannot be duplicate values.

[0082] As an example, suppose we have the following entities: agricultural machinery: tractor; equipment: navigation equipment; agricultural implements: plow; in this scenario, some attributes may have unique relationships, for example: Tractor serial number: Each tractor must have a unique serial number.

[0083] Device ID: Each navigation device must have a unique ID.

[0084] Farm implement serial number: Each farm implement must have a unique serial number.

[0085] Therefore, the entity association model can comprehensively and accurately describe the attribute information of each entity, as well as the logical relationships between entities and between entities and attribute information, which facilitates the generation of subsequent forms.

[0086] S30 generates a form based on the entity association model and business requirements.

[0087] Among them, business requirements refer to the requirements for meeting different business functions.

[0088] Optionally, after constructing the entity association model, the method further includes: Perform logical validation on the entity association model; Adjust the content in the entity association model that does not pass the logical check to obtain the adjusted entity association model.

[0089] The purpose of logically validating the constructed entity association model is to check for issues such as duplicate data entry and conflicting relationship definitions. For example, it verifies whether the attribute values ​​of the "equipment" entity associated with the "agricultural machinery" entity conform to the preset enumeration relationship (such as the agricultural machinery working status only being "online" or "offline"). If conflicts or unreasonable aspects are found, feedback is provided to business personnel or developers for model optimization and adjustment.

[0090] Optionally, the above business requirements include at least one of the following: adding requirements, modifying requirements, querying requirements, deleting requirements, and general requirements; each requirement corresponds to the implementation of a function.

[0091] If the business requirements include new requirements, generate a form based on the entity association model and the business requirements, including: Based on the new content corresponding to the new requirements, update the content and logical relationships in the entity association model to obtain the updated entity association model. Based on the updated entity association model, a form is generated. The "new requirement" refers to the ability to add new content to the form generated based on the entity association model. This new content can be a new entity, new attribute information, or a new logical relationship.

[0092] Specifically, when business personnel need to add new form content, the system can automatically configure the association of single entities or attached entities based on the entity association model and perform uniqueness checks. For example, when adding an attached entity field called "Equipment" associated with the "Agricultural Machinery" entity, the system checks whether the value of this field conflicts with the uniqueness of existing rule fields (such as the requirement that the code of the same agricultural machinery associated with the equipment must be unique), ensuring data accuracy.

[0093] For new content in the "agricultural machinery-equipment-implementation" association scenario, such as adding a form for equipment information associated with agricultural machinery, the corresponding implementation attributes of agricultural machinery and equipment can be quickly associated based on the logical relationship defined in the entity association model, and some default values ​​can be automatically filled in (based on formatted relationships, enumeration relationships, etc.), reducing manual data entry.

[0094] If the business requirements include modification requests, generate a form based on the entity association model and the business requirements, including: Based on the modification requirements, the content and logical relationships in the entity association model corresponding to the modification content are modified to obtain the modified entity association model; Based on the modified entity association model, a form is generated. The modification requirement refers to the ability to modify the content (including attribute information and logical relationships) of the form generated based on the entity association model. The modified content can be the entity's attribute information or its corresponding logical relationships.

[0095] Specifically, when business requirements necessitate data modification, information data can be modified based on the entity association model, and redundant updates (synchronously updating associated redundant data in the associated entities) can be performed, as well as a uniqueness check can be executed again to ensure data consistency.

[0096] If the business requirements include query requirements, this method also includes: Based on the data query requests corresponding to the query needs, a cascading query approach is adopted. Through the multi-level association between forms and target data, the system can retrieve the target data corresponding to the query request. This query method enables cross-system data linkage, ensuring data consistency and integrity while improving the efficiency and accuracy of data queries. By clearly defining this multi-level association, the system can more clearly manage the relationship between procurement forms and ERP material data, achieving data linkage and synchronous updates, thereby improving the enterprise's data management efficiency and decision support capabilities.

[0097] The forms in this application may include different types of forms, such as purchase forms and ERP material forms.

[0098] Multilevel association refers to the relationship between entities at multiple levels in an entity association model. This relationship describes complex dependencies and connections between entities and is typically used to represent indirect relationships between multiple entities. Multilevel association allows systems to query and manipulate data through entities at multiple levels, thereby enabling more complex data management and analysis.

[0099] Specifically, multi-level relationships can include: First-level association: direct association, where one entity is directly associated with another entity.

[0100] Secondary association: Through primary association, further connections are made to deeper-level entities.

[0101] Multi-level association: More complex entity relationships can be achieved through multiple levels of association.

[0102] Through multi-level relationships, you can start from one entity and query entity data at multiple levels related to it.

[0103] As an example, suppose we have the following entities: agricultural machinery: tractor; equipment: navigation equipment; agricultural implements: plow; materials: tractor parts, navigation equipment parts, plow parts; in this scenario, the following multi-level relationships may exist: Agricultural machinery (tractors): First-level association: The tractor is associated with the navigation device.

[0104] Secondary association: Navigation devices are associated with components of navigation devices.

[0105] Third-level association: The tractor is associated with the navigation equipment and its components through the navigation equipment.

[0106] Agricultural machinery (tractors): First-level association: Tractors are associated with plows.

[0107] Secondary association: Plows are associated with plow components.

[0108] Third-level association: The tractor is associated with the plow and its components.

[0109] Another example is cross-system data linkage. When querying ERP material data associated with OA procurement forms, the intelligent rule engine can realize cascading queries (i.e., multi-level data queries from procurement forms to ERP materials) based on the cross-system association definition of the entity association model.

[0110] Purchase orders are documents used by companies to record purchasing activities, typically including purchase order number, purchase date, purchasing personnel, supplier information, and details of purchased items. ERP material data is information used in the ERP system to manage materials (such as raw materials, parts, and finished products), typically including material number, material name, specifications, inventory quantity, price, and supplier.

[0111] In addition to cascading queries, dictionary queries can also be performed, which means using dictionary queries to quickly match standardized material codes, names and other dictionary data, thereby improving query efficiency and accuracy.

[0112] If the business requirements include deletion, generate a form based on the entity association model and the business requirements, including: Based on the content to be deleted corresponding to the deletion request, delete the content and logical relationships in the entity association model that correspond to the content to be deleted, and obtain a new entity association model; Generate a form based on the new entity association model.

[0113] The deletion requirement refers to the ability to delete content (including attribute information and logical relationships) from a form generated based on an entity association model. The content to be deleted can be entity attribute information or corresponding logical relationships.

[0114] Specifically, when performing a deletion operation, a logical deletion method can be used, and a deletion check can be performed. For example, when deleting the entity data of "agricultural machinery", check whether there is any associated entity data of "equipment". If so, determine whether deletion is allowed according to business rules (if deletion is not allowed, prompt that the associated data has not been processed) to avoid data logic breakage.

[0115] In this application, the general requirements refer to some common functions for forms, including form service interfaces, import, export, detail query, interface documentation generation, etc. Based on the entity association model and form service interface, standardized data import and export are realized (following the attribute format and association relationship defined by the model). The detail query function can quickly associate and query the detailed information of entities and related entities. The interface documentation generation function can automatically generate according to the model and service configuration, which is convenient for integration with other systems.

[0116] The implementation of the various business requirements mentioned above requires corresponding functionalities of different types. For example, the function type corresponding to the deletion requirement is deletion. The implementation process of each business requirement can generate a corresponding script. For details on the script generation process, please refer to [link to script generation process]. Figure 3 , Figure 3 In the process, after selecting a function type, the information in the entity association model (model data) can be analyzed in detail based on the information in the constructed entity association model. Then, a function processing link is constructed, which is the process of implementing the business requirements corresponding to the selected function type. Finally, based on the function processing link, a corresponding persistent operation script is generated. Running the script can automatically realize the business requirements corresponding to the selected function type.

[0117] Optionally, the above method further includes: Generate a form service page based on business requirements, and complete the business requirements based on the form service page.

[0118] The form service page can be configured based on its available functions to meet different business needs. Specifically, at least one of the following configurations can be performed on the form service page: Basic page information configuration: Business personnel configure the page names (such as "Agricultural Machinery Information Management" and "Work Order Information Management") and page codes (uniquely identifying the page for easy system identification and management) of the form service interface through the visual designer. Based on previous services, the system can intelligently identify the required information for relevant pages and set table information, including header configuration (associating entity attributes and determining the fields and names displayed in the header) and query configuration (defining query conditions, and setting cascading query conditions based on the relationship of the entity association model, such as querying equipment and implement information by agricultural machinery number).

[0119] Configure new information: Configure the associated interface (connect with the new function of the form service interface) and the form configuration (determine the field layout, display style, etc. of the new form). At the same time, set the validation rules (based on the redundant relationship, unique relationship, etc. of the entity association model, such as verifying the uniqueness of the equipment number and whether the agricultural machinery parameters meet the enumerated values ​​when adding equipment information) and the required field configuration (determine the required fields according to the business logic, such as the creation time of the agricultural machinery and the agricultural machinery number to which the equipment belongs).

[0120] Update information configuration: The modification function of the associated form service interface ensures that the update operation synchronously triggers logic such as redundant updates and uniqueness checks, so as to ensure the consistency of data displayed on the page and stored in the backend.

[0121] Configure deletion information: Associate with the deletion function of the form service interface, set deletion prompt logic (such as prompting about the processing status of associated data after deletion), and display the results of the associated data check before deletion on the front-end page according to the deletion check rules to avoid accidentally deleting critical data. For example, before deleting work order information, the page can prompt the business personnel to confirm whether to continue the deletion.

[0122] Based on the automatically generated page information configuration, business personnel can make detailed adjustments through the visual designer, such as deleting unnecessary fields from the page table and modifying the default values ​​of the selection criteria.

[0123] Additionally, it's worth noting that traditional database relational modeling can be used instead of entity association modeling: theoretically, table relationships in traditional relational databases can be used to simulate entity relationships. This involves creating multiple tables and using foreign key constraints to establish relationships between different entities. However, this approach becomes extremely complex when dealing with complex many-to-many relationships and dynamic association rules. Modifying the database structure and related code is costly when facing frequently changing business relationships, making it difficult to meet rapidly evolving business needs. Furthermore, it has limited capabilities for handling unstructured or semi-structured data and cannot flexibly define various relationship types (such as redundant or formatted relationships) like entity association modeling.

[0124] Low-code functionality can also be achieved using scripting languages: scripting languages ​​(such as Python scripts combined with web frameworks) can be used to rapidly develop forms. Developers can write generic script functions and define form fields, logic, and interface elements through configuration files, thus achieving a certain degree of low-code development. However, this approach still requires a certain level of programming ability from business personnel, making it difficult for non-technical personnel to easily adopt. Furthermore, in terms of implementing interactive functions of the visual designer and tight integration with the entity association model, it is not as convenient and intuitive as the method adopted in this invention, which is based on the deep integration of the visual designer and the entity association model. Additionally, systems implemented using scripting languages ​​may have certain disadvantages compared to the solution of this invention in terms of performance optimization, code reuse, and maintainability.

[0125] Therefore, although the above-mentioned alternatives exist, in summary, these solutions all have certain limitations in solving problems such as complex business modeling, agile demand response, and cross-system data linkage, and cannot achieve the invention's purpose as comprehensively and efficiently as the technical solution of this invention.

[0126] This invention presents a low-code dynamic form intelligent construction method based on an entity association model. In the process of enterprise digital transformation, it brings significant and comprehensive benefits to enterprises in multiple dimensions, including development efficiency, business response flexibility, and cross-system collaboration, as detailed below: I. Leapfrog improvement in development efficiency 1. Development cycle significantly shortened In traditional form development, creating an order form with master-child table relationships often takes weeks and involves extensive manual coding to establish the relationships between fields and business logic. This invention, however, leverages low-code intelligent construction and entity association models to highly automate and standardize the development process. Through predefined entity relationships, the system can automatically complete key steps such as field association and logic configuration during form development.

[0127] Practical application verification shows that the development cycle is reduced by 40% compared to the traditional model. Taking the development of a medium-complexity business form as an example, the development task that originally required 3 weeks can now be delivered and used in only about 1.8 weeks, which greatly accelerates the launch speed of enterprise digital applications and enables enterprises to respond more quickly to market changes and business innovation needs.

[0128] 2. Coding workload has been drastically reduced. In traditional development, developers need to write a lot of code to handle form field logic, relationship validation, and other tasks. This invention's low-code visual designer is deeply integrated with the entity association model, allowing business users to complete the core form construction work through visual operations (such as dragging and dropping fields and configuring association rules). Developers only need to perform a small amount of supplementary coding in special and complex logic scenarios. This reduces coding workload by over 60%, not only reducing labor costs but also lowering the probability of code errors due to the reduced code volume, shortening the code debugging and maintenance cycle, and further improving overall efficiency from the development side.

[0129] II. Agile Response to Business Needs 1. Rapid adaptation to changes in high-frequency services In scenarios involving frequent business changes, such as report statistics, business needs evolve rapidly. Traditionally, such changes require modifications to backend interfaces and frontend code, involving collaboration across multiple technical aspects, resulting in long response times and often failing to keep pace with business needs. This invention empowers business personnel to independently configure forms through a visual designer. Based on entity association models, business personnel can complete field adjustments and rule updates within minutes. For example, when adding a field related to "agricultural machinery," business personnel simply need to associate the corresponding "agricultural machinery" entity and attributes in the visual interface, configure the association relationship with the agricultural machinery entity, and set validation rules. This takes effect quickly, eliminating the need to wait for lengthy code modifications and deployment processes by technical personnel. This allows businesses to respond nimbly to business fluctuations and seize marketing opportunities in a highly competitive market.

[0130] Zero cost of demand communication In the traditional model, non-technical personnel often struggle to participate in form design due to high technical barriers. Requirements must be relayed through multiple layers to reach technical staff, leading to misunderstandings, information loss, and high communication costs. This invention's visual designer lowers the technical barrier, allowing business personnel to intuitively design forms and configure logic based on business scenarios. It directly transforms business requirements into visual form models, eliminating the need for complex technical jargon translation. Business and technical personnel can confirm requirements using the same entity association model and visual interface, achieving a "what you see is what you get" experience. Communication costs are reduced by over 80%, significantly improving the accuracy and efficiency of requirement delivery and ensuring that business requirements are implemented accurately and quickly.

[0131] In summary, this invention, through technological innovation, comprehensively reshapes the digital model of enterprise form construction and business processes, from development efficiency to business response. It provides core enabling tools for enterprise digital transformation, helping enterprises build competitive advantages in cost reduction, efficiency improvement, and innovative response, and accelerating the release of digital value and the upgrading of business models.

[0132] Based on and Figure 1 Using the same principle as the method shown, this embodiment of the invention also provides a form construction device 20 based on an entity association model, such as... Figure 4 As shown, the form construction device 20 based on the entity association model may include an acquisition module 210, an entity association model construction module 220, and a form generation module 230, wherein: The acquisition module 210 is used to acquire the attribute information of the entity to be processed. The entity to be processed includes a first entity, a second entity, and a third entity with the same attribute information. The second entity and the third entity are applied to the first entity. The entity association model construction module 220 is used to construct an entity association model based on the attribute information of the entity to be processed. The entity association model describes the first logical relationship between the agricultural machinery and other entities, as well as the second logical relationship between each entity and the attribute information of each entity. The form generation module 230 is used to generate forms based on the entity association model and business requirements.

[0133] Optionally, the first logical relationship mentioned above includes the association relationship between the first entity and the second entity corresponding to the first entity, as well as the structural relationship between the first entity and other entities. The second logical relationship includes the first self-relationship between the first entity and the attribute information of the first entity, the second self-relationship between the second entity and the attribute information of the second entity, and the third self-relationship between the third entity and the attribute information of the third entity.

[0134] Optionally, the above-mentioned device further includes: The validation module is used to perform logical validation on the entity association model; it adjusts the content in the entity association model that fails the logical validation to obtain the adjusted entity association model.

[0135] Optionally, the above-mentioned business requirements include at least one of the following: adding requirements, modifying requirements, querying requirements, deleting requirements, and general requirements; If the business requirements include new requirements, the form generation module 230, when generating the form based on the entity association model and business requirements, is specifically used for: Based on the new content corresponding to the new requirements, update the content and logical relationships in the entity association model to obtain the updated entity association model. Generate a form based on the updated entity association model; If the business requirements include modification requirements, the form generation module 230, when generating the form based on the entity association model and business requirements, is specifically used for: Based on the modification requirements, the content and logical relationships in the entity association model corresponding to the modification content are modified to obtain the modified entity association model; Generate a form based on the modified entity association model; If the business requirements include query requirements, and the forms include different types of forms, the above-mentioned device also includes: The query module is used to query the target data corresponding to the query request based on the query requirements. It adopts a cascading query method and realizes the query of the target data corresponding to the data query request through the multi-level association between the form and the target data. If the business requirements include deletion, the form generation module 230, when generating the form based on the entity association model and business requirements, is specifically used for: Based on the content to be deleted corresponding to the deletion request, delete the content and logical relationships in the entity association model that correspond to the content to be deleted, and obtain a new entity association model; Generate a form based on the new entity association model.

[0136] Optionally, the above-mentioned device further includes: The form service page generation module is used to generate form service pages based on business requirements, so that business requirements can be fulfilled based on the form service pages.

[0137] Optionally, if the entity to be processed includes an agricultural machinery entity, then the first entity, the second entity, and the third entity with the same attribute information included in the agricultural machinery entity are agricultural machinery, equipment, and agricultural implements, respectively.

[0138] The form construction device based on the entity association model in this embodiment of the invention can execute the form construction method based on the entity association model provided in this embodiment of the invention. The implementation principle is similar. The actions performed by each module and unit in the form construction device based on the entity association model in each embodiment of the invention correspond to the steps in the form construction method based on the entity association model in each embodiment of the invention. For detailed functional descriptions of each module of the form construction device based on the entity association model, please refer to the descriptions in the corresponding form construction method based on the entity association model shown above, which will not be repeated here.

[0139] The aforementioned form building device based on the entity association model can be a computer program (including program code) running on a computer device, such as an application software; the device can be used to execute the corresponding steps in the method provided in the embodiments of the present invention.

[0140] In some embodiments, the form construction device based on the entity association model provided in this invention can be implemented using a combination of hardware and software. As an example, the form construction device based on the entity association model provided in this invention can be a processor in the form of a hardware decoding processor, which is programmed to execute the form construction method based on the entity association model provided in this invention. For example, the processor in the form of a hardware decoding processor can be one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components.

[0141] In other embodiments, the form construction apparatus based on the entity association model provided in this invention can be implemented in software. Figure 4 An entity association model-based form building apparatus is shown stored in a memory. It can be software in the form of programs and plug-ins, and includes a series of modules, including an acquisition module 210, an entity association model building module 220, and a form generation module 230, for implementing the entity association model-based form building method provided in the embodiments of the present invention.

[0142] The modules described in the embodiments of the present invention can be implemented in software or hardware. The names of the modules are not, in some cases, limiting the scope of the module itself.

[0143] Based on the same principles as the methods shown in the embodiments of the present invention, the embodiments of the present invention also provide an electronic device, which may include, but is not limited to: a processor and a memory; the memory for storing computer programs; and the processor for executing the methods shown in any embodiment of the present invention by invoking the computer programs.

[0144] In one alternative embodiment, an electronic device is provided, such as Figure 5 As shown, Figure 5 The illustrated electronic device 4000 includes a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, for example, via a bus 4002. Optionally, the electronic device 4000 may further include a transceiver 4004, which can be used for data interaction between the electronic device and other electronic devices, such as sending and / or receiving data. It should be noted that in practical applications, the transceiver 4004 is not limited to one type, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of the present invention.

[0145] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this invention. Processor 4001 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0146] Bus 4002 may include a pathway for transmitting information between the aforementioned components. Bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Bus 4002 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 5 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0147] The memory 4003 may be ROM (Read Only Memory) or other types of static storage devices capable of storing static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices capable of storing information and instructions, or EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto.

[0148] The memory 4003 stores application code (computer program) for executing the present invention, and its execution is controlled by the processor 4001. The processor 4001 executes the application code stored in the memory 4003 to implement the content shown in the foregoing method embodiments.

[0149] Among these, electronic devices can also be terminal devices. Figure 5 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments of the present invention.

[0150] This invention provides a computer-readable storage medium storing a computer program that, when run on a computer, enables the computer to execute the corresponding content in the aforementioned method embodiments.

[0151] According to another aspect of the present invention, a computer program product or computer program is also provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various embodiments described above.

[0152] Computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0153] It should be understood that the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of methods and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0154] The computer-readable storage medium provided in this invention can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0155] The aforementioned computer-readable storage medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the method shown in the above embodiments.

[0156] The above description is merely a preferred embodiment of the present invention and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure in this invention is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-disclosed concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this invention.

Claims

1. A form construction method based on an entity association model, characterized in that, include: Obtain the attribute information of the entity to be processed, wherein the entity to be processed includes a first entity, a second entity, and a third entity having the same attribute information, and the second entity and the third entity are applied to the first entity; Based on the attribute information of the entity to be processed, an entity association model is constructed. The entity association model describes the first logical relationship between the first entity and other entities, and the second logical relationship between each entity and the attribute information of each entity. Based on the entity association model and business requirements, generate a form.

2. The method according to claim 1, characterized in that, The first logical relationship includes the association between the first entity and the second entity corresponding to the first entity, and the structural relationship between the first entity and other entities. The second logical relationship includes the first self-relationship between the first entity and the attribute information of the first entity, the second self-relationship between the second entity and the attribute information of the second entity, and the third self-relationship between the third entity and the attribute information of the third entity.

3. The method according to claim 1, characterized in that, The method further includes: Perform logical verification on the entity association model; The content in the entity association model that fails the logical verification is adjusted to obtain the adjusted entity association model.

4. The method according to any one of claims 1 to 3, characterized in that, The business requirements include at least one of the following: adding requirements, modifying requirements, querying requirements, deleting requirements, and general requirements; If the business requirements include new requirements, generating a form based on the entity association model and the business requirements includes: Based on the new content corresponding to the new requirements, update the content and logical relationships in the entity association model to obtain the updated entity association model. Generate a form based on the updated entity association model; If the business requirement includes a modification requirement, generating a form based on the entity association model and the business requirement includes: Based on the modification requirements, the content and logical relationships in the entity association model corresponding to the modification content are modified to obtain the modified entity association model. Generate a form based on the modified entity association model; If the business requirement includes a query requirement, the method further includes: Based on the data query request corresponding to the query requirement, a cascading query method is adopted to realize the query of the target data corresponding to the data query request through the multi-level association relationship between the form and the target data; If the business requirement includes a deletion requirement, the step of generating a form based on the entity association model and the business requirement includes: Based on the content to be deleted corresponding to the deletion request, delete the content and logical relationships in the entity association model that correspond to the content to be deleted, and obtain a new entity association model; A form is generated based on the new entity association model.

5. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Based on the stated business requirements, a form service page is generated to fulfill the stated business requirements.

6. The method according to any one of claims 1 to 3, characterized in that, The entity to be processed includes agricultural machinery entities, and the first entity, the second entity, and the third entity with the same attribute information included in the agricultural machinery entities are agricultural machinery, equipment, and agricultural implements, respectively.

7. A form construction device based on an entity association model, characterized in that, include: The acquisition module is used to acquire attribute information of the entity to be processed. The entity to be processed includes a first entity, a second entity, and a third entity with the same attribute information. The second entity and the third entity are applied to the first entity. The entity association model construction module is used to construct an entity association model based on the attribute information of the entity to be processed. The entity association model describes the first logical relationship between the first entity and other entities, and the second logical relationship between each entity and the attribute information of each entity. The form generation module is used to generate forms based on the entity association model and business requirements.

8. The apparatus according to claim 7, characterized in that, The first logical relationship includes the association between the first entity and the second entity corresponding to the first entity, and the structural relationship between the first entity and other entities. The second logical relationship includes the first self-relationship between the first entity and the attribute information of the first entity, the second self-relationship between the second entity and the attribute information of the second entity, and the third self-relationship between the third entity and the attribute information of the third entity.

9. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method of any one of claims 1-6.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method of any one of claims 1-6.

Images