Method and system for obtaining target form

Abstract

This invention discloses a method and system for obtaining a target form, relating to the field of computer software technology. The method includes: after adding a new form, obtaining a set of coordinates used to define the business boundaries of the form; inserting an independent associated record for each coordinate in the set of coordinates in a pre-constructed form element coordinate table; and in response to a request to obtain a target form, obtaining a target coordinate set and searching for the target form corresponding to the target coordinate set in the form element coordinate table. This helps to solve the problem that existing technologies cannot achieve accurate and efficient acquisition of target forms.

Description

Technical Field

[0001] This invention relates to the field of computer software technology, and in particular to a method and system for obtaining a target form. Background Technology

[0002] In existing technologies, form retrieval often relies on fixed code association or simple classification storage, without establishing a clear business boundary definition mechanism. When business changes generate new forms, it is necessary to manually filter vague information such as form names and business descriptions to locate them, which is prone to problems such as incorrect or missing form selection. If the number of forms is large, it is also necessary to check the matching degree between the form configuration and business requirements one by one, which is time-consuming and labor-intensive. Moreover, traditional form storage methods are not deeply bound to business boundary information, resulting in low data query efficiency.

[0003] Therefore, there is an urgent need for a method that can accurately and efficiently obtain target forms. Summary of the Invention

[0004] In view of this, the present invention proposes a method and system for obtaining target forms, which can achieve accurate and efficient acquisition of target forms.

[0005] To achieve the above objectives, the present invention provides the following technical solution:

[0006] A method for obtaining a target form, comprising:

[0007] After adding a new form, obtain the set of coordinates used to define the business boundaries of the form;

[0008] Insert an independent associated record for each coordinate in the coordinate set in the pre-built form element coordinate table;

[0009] In response to a request to retrieve a target form, a target coordinate set is obtained, and the target form corresponding to the target coordinate set is searched in the form element coordinate table.

[0010] Based on the above technical solution, the present invention can be further improved as follows:

[0011] Optionally, the newly added form includes:

[0012] In response to a form creation request, the form creation requirements are obtained, and specific content matching the form creation requirements is populated into a pre-set set of custom rule attributes to generate form parameters;

[0013] The form parameters are combined based on predefined form configuration attributes to generate a form.

[0014] Optionally, the step of adding a new form includes:

[0015] Monitor the lifecycle status of the newly added form, which includes pending modification, pending publication, published, and deactivated.

[0016] When the lifecycle status of the newly added form or its parameters changes to "published", the newly added form is stored in the archive repository, and an archive form identifier is generated for the newly added form to distinguish between different versions of the form.

[0017] Optionally, the form element coordinate table includes a primary key, a referencing form element identifier, a referencing element type, a coordinate field name, a field value, and a creation date.

[0018] Optionally, inserting an independent associated record for each coordinate in the coordinate set in the pre-built form element coordinate table includes:

[0019] Assign the value of the referenced form element identifier to a unique identifier for the new form or new form parameter;

[0020] Assign the type of the referenced element to the type of the new object. When the type of the referenced element is 1, the type of the new object is a form parameter. When the type of the referenced element is 2, the type of the new object is a form.

[0021] Assign the coordinate field name to the key name of the current coordinate;

[0022] Assign the field value to the key value of the current coordinate;

[0023] Assign the creation date to the record creation time.

[0024] Optionally, the step of searching for the target form corresponding to the target coordinate set in the form element coordinate table includes:

[0025] Obtain the target element type and target coordinate set of the target form to be searched. The target coordinate set includes key-value pairs, and the key-value pairs include coordinate names and coordinate values. The target element type includes forms and form parameters.

[0026] In the form element coordinate table, filter out records whose reference element type matches the target element type;

[0027] Group the filtered records according to the referenced form element identifier, so that all coordinate records of the same form or form parameter are grouped together;

[0028] Filter out groups whose number of coordinate field names is equal to the number of coordinates in the target coordinate set;

[0029] Iterate through each coordinate in the target coordinate set one by one, and verify whether there is a record in the group whose coordinate field name is equal to the current coordinate name and whose reference element type is equal to the current coordinate value. If all target coordinates in the group are successfully matched, return the reference form element identifier corresponding to the group as the query result.

[0030] Optionally, the method for obtaining the target form further includes:

[0031] Retrieve the form configuration of the target form and configure the target form as a standardized set of attributes that can be recognized by the front-end components.

[0032] A system for obtaining a target form, comprising:

[0033] The coordinate acquisition module is used to obtain a set of coordinates used to define the business boundaries of the form after a new form is added.

[0034] The coordinate recording module is used to insert an independent associated record for each coordinate in the coordinate set in a pre-built form element coordinate table;

[0035] The form query module is used to respond to a request to obtain a target form, retrieve a set of target coordinates, and search for the target form corresponding to the set of target coordinates in the form element coordinate table.

[0036] An electronic device includes a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor executes the computer program to implement the steps of the method described herein.

[0037] A non-transitory computer-readable storage medium having a computer program stored thereon, the computer program implementing the steps of the method when executed by a processor.

[0038] The present invention has the following advantages:

[0039] The method for obtaining target forms in this invention defines the business boundaries of forms through a set of coordinates, solving the problem of the lack of a clear boundary mechanism in existing technologies and avoiding incorrect or missed form selections. It relies on a coordinate table of form elements to store coordinate association records. When responding to an acquisition request, it accurately finds the corresponding form based on the target coordinate set, eliminating the need for manual filtering of ambiguous information, significantly improving positioning efficiency, and adapting to scenarios with a large number of forms. Simultaneously, the deep binding between coordinates and forms allows for rapid association of target forms at specific business stages during subsequent maintenance and historical data backtracking, improving the problems of inefficient queries and chaotic management. Attached Figure Description

[0040] For illustrative and not limiting purposes, the present invention will now be described in conjunction with embodiments and accompanying drawings, wherein:

[0041] Figure 1This is a flowchart illustrating the method for obtaining the target form in an embodiment of the present invention;

[0042] Figure 2 This is a schematic diagram of the main components of the target form acquisition system in an embodiment of the present invention;

[0043] Figure 3 This is a schematic diagram illustrating the state transitions of the target form in an embodiment of the present invention.

[0044] Figure 4 This is a schematic diagram illustrating the acquisition of the target form in an embodiment of the present invention;

[0045] Figure 5 This is a schematic diagram of the physical structure of the electronic device provided by the present invention. Detailed Implementation

[0046] To enable those skilled in the art to better understand the present invention, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0047] It should be noted that the terms "first," "second," etc., in the specification and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be used interchangeably where appropriate for the embodiments of the invention described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0048] It should be noted that, where there is no conflict, the embodiments and features of the present invention can be combined with each other. The embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0049] Figure 1 This is a flowchart illustrating the method for obtaining the target form in an embodiment of the present invention, as shown below. Figure 1 As shown, the method for obtaining the target form provided in this embodiment of the invention includes the following steps S101 to S103.

[0050] S101, after adding a new form, obtain the set of coordinates used to define the business boundaries of the form.

[0051] In response to a form creation request, the form creation requirements are obtained, and specific content matching the form creation requirements is populated into a pre-set set of custom rule attributes to generate form parameters;

[0052] The form parameters are combined based on predefined form configuration attributes to generate a form.

[0053] Form definition rules are the core protocol specifications of dynamic form systems, defining field type constraints, data validation rules, and component interaction logic based on JSON Schema. Form parameters are the instantiation of these rules in specific business scenarios, forming operable data collection units by filling in the attribute set defined by the rules (such as label / placeholder). The two form a dependent relationship of "specification and implementation," as shown in Table 1. Form definition rules provide structured templates for parameters, and form parameters carry business semantics through attribute assignment.

[0054] Table 1

[0055]

[0056] One example is as follows: For a "Name" form parameter collection item, the form parameter configuration content constructed according to the form definition rules is as follows:

[0057] {

[0058] "category":"item",

[0059] "type":"Input",

[0060] "label":"Name",

[0061] "name":"name",

[0062] "required":1,

[0063] "placeholder":"Please enter your name",

[0064] "max":10

[0065] }

[0066] In this implementation, it is represented as a single-line input box, which is a required field during data collection. The prompt message is "Please enter your name," and the maximum input length is 10 characters. When submitting the collected information, the field name for this data is "name."

[0067] Form definition rules establish general technical specifications, while form parameters are the concrete implementation of these specifications in specific business scenarios. Together, they constitute the core support of a dynamic form system, enabling business users to achieve agile responses to data collection needs through configuration without modifying the code.

[0068] Multiple form parameters can be generated based on the form definition rules, such as name and gender parameters. These form parameters can be referenced when designing the form. For example, when a form is configured with form parameters such as "name" and "gender," a complete business data collection form with mature interaction logic can be formed according to the field type constraints, data validation rules, and component interaction logic set by these form parameters.

[0069] In terms of data structure, a form is a collection of form configuration attributes and various form parameters. Essentially, it is a series of JSON arrays composed according to the form definition rules.

[0070] One embodiment is as follows: A form for applying for leave is configured as follows: [

[0072] {

[0073] "title":"",

[0074] "list": [

[0075] {

[0076] "category":"text",

[0077] "type":"Tip",

[0078] "label":"Important Information",

[0079] "name":"applyNotice",

[0080] "level":"333333",

[0081] "info": "Please fill in the application information according to the requirements of the 'Leave Application'"

[0082] },

[0083] {

[0084] "category":"item",

[0085] "type":"Input",

[0086] "label":"Name",

[0087] "name":"name",

[0088] "required":"1",

[0089] "placeholder":"Please enter your name",

[0090] "max": 10,

[0091] "encryptState":"2",

[0092] "pattern":"none"

[0093] },

[0094] {

[0095] "category":"item",

[0096] "type":"InputNumber",

[0097] "label":"Employee ID",

[0098] "name":"user identifier",

[0099] "required":"1",

[0100] "placeholder":"Please enter your employee ID",

[0101] "precision": 0

[0102] },

[0103] {

[0104] "category":"item",

[0105] "type":"Select",

[0106] "label":"Department",

[0107] "name":"organ",

[0108] "required":"1",

[0109] "placeholder":"Please select your department",

[0110] "childType":"SelectOption",

[0111] "optionType":"1",

[0112] "options": [

[0113] {

[0114] "value":"1",

[0115] "label":"R&D Center"

[0116] },

[0117] {

[0118] "value":"2",

[0119] "label":"Product Center"

[0120] },

[0121] {

[0122] "value":"3",

[0123] "label":"Test Center"

[0124] } ]

[0126] },

[0127] {

[0128] "category":"item",

[0129] "type":"DatePicker",

[0130] "label":"Leave start date",

[0131] "name":"startDate",

[0132] "required":"1",

[0133] "placeholder":"Please select the start date of your leave",

[0134] "picker":"date"

[0135] },

[0136] {

[0137] "category":"item",

[0138] "type":"DatePicker",

[0139] "label":"Leave end date",

[0140] "name":"endDate",

[0141] "required":"1",

[0142] "placeholder":"Please select the end date of your leave",

[0143] "picker":"date"

[0144] },

[0145] {

[0146] "category":"item",

[0147] "type":"Input",

[0148] "label":"Location during leave",

[0149] "name":"localInfo",

[0150] "required":"1",

[0151] "placeholder":"Please enter your location during your leave period"

[0152] The form contains multiple input fields: Name (text input, required, maximum 10 characters), Employee ID (numeric input, required), Department (drop-down selection, including R&D Center, Product Center, and Testing Center options), Leave start date (date selection, required), Leave end date (date selection, required), and Location during leave (text input, required).

[0153] Each field has defined attributes such as type, label, name, and required fields, which can be used by the form rendering engine to automatically generate the corresponding interactive interface.

[0154] Before the steps when adding a new form, include:

[0155] As shown in Table 2, the lifecycle status of the newly added form is monitored. The lifecycle status includes pending modification, pending publication, published, and deactivated.

[0156] Table 2

[0157]

[0158] When the lifecycle status of the newly added form or its parameters changes to "published", the newly added form is stored in the archive repository, and an archive form identifier is generated for the newly added form to distinguish between different versions of the form.

[0159] The transition methods for each state are as follows: Figure 3 As shown, when the status of a specified form is changed to "Published", a copy of the current form configuration will be automatically copied to the archive repository, generating a unique archive form ID. The form data is associated with the most recent archive form ID.

[0160] like Figure 4 As shown, taking the application form for "Outstanding Young Talents under the Application Plan Project" as an example, the dynamic form system matches the corresponding form data through coordinates, and the form data is associated with the latest archived form identifier, so the corresponding archived form identifier can be returned to the front-end project for rendering.

[0161] By employing automatic archiving based on form status and a mechanism that retrieves the latest archived form identifier based on coordinates, newly added data collection items under specific business requirements can utilize the latest form configuration. Simultaneously, after the business system associates the collected data with the archived form identifier, it can retrieve the corresponding archived form configuration at any time to display the collected data. This achieves the effect of historical data backtracking.

[0162] S102, insert an independent associated record for each coordinate in the coordinate set in the pre-built form element coordinate table.

[0163] As shown in Table 3, the form element coordinate table includes a primary key, a reference form element identifier, a reference element type, a coordinate field name, a field value, and a creation date.

[0164] Table 3

[0165]

[0166] When adding new form parameters or forms, you need to pass a set of coordinates to the corresponding API. For example, when creating a form, if you specify the coordinate data as: {"service identifier":"10","business identifier":"301","businessType":"300"}), three coordinate data will be inserted.

[0167] Among them, QUOTE_ELEMENT_ is the identifier of the referenced form element, QUOTA_ELEMENT_TYPE is the type of the referenced element, COORDINATE_NAME is the name of the coordinate field of the example coordinate parameter, COORDINATE_VALUE is the field value of the example coordinate parameter, and CREATION_DATE is the creation date.

[0168] In the talent introduction program business, service=10 represents the program business, business=301 represents the "Outstanding Young Talent" type business, and businessType=300 represents the application program business. The business interpretation of the three coordinates is the "Outstanding Young Talent Application" form under the program.

[0169] When retrieving forms, the business system can directly obtain the forms at the corresponding coordinates using the `coordinates` parameter. Since it's necessary to strictly match the number of coordinates and the key-value pairs of each coordinate to the corresponding form identifier, the following SQL template is used for querying:

[0170] SELECT QUOTE_ELEMENT_Identifier

[0171] FROM COORDINATE_INFO

[0172] <where>

[0173] QUOTA_ELEMENT_TYPE = #{quotaElementType}

[0174] < / where>

[0175] GROUP BY QUOTE_ELEMENT_logo

[0176] HAVING

[0177] COUNT(COORDINATE_NAME) = #{coordinatesSize}

[0178] <if test="coordinates != null and coordinates.size()>0" >

[0179] AND

[0180] <foreach collection="coordinates" index="key" item="value" separator="and">

[0181] SUM(CASE WHEN COORDINATE_NAME = #{key} AND COORDINATE_VALUE =#{value} THEN 1 ELSE 0 END)>0

[0182] < / foreach>

[0183] < / if>

[0184] By using WHERE QUOTA_ELEMENT_TYPE = #{quotaElementType}, you can first filter out records of a specified type (such as searching only "form" or only "form parameters").

[0185] The GROUP BY QUOTE_ELEMENT_ flag groups all coordinate records of the same form / form parameter together, ensuring that each group corresponds to a unique form.

[0186] HAVING COUNT(COORDINATE_NAME) = #{coordinatesSize} ensures that the number of coordinates in the group is exactly the same as the number of coordinates in the target set to be queried (for example, if the target has 3 coordinates, only the group containing 3 coordinates will be kept).

[0187] When there are specific coordinates, check each coordinate in a loop: use SUM(CASE...)>0 to determine if there is a record in the group where "coordinate name = the passed key and coordinate value = the passed value", to ensure that all coordinates can be matched accurately.

[0188] Assign the value of the referenced form element identifier to a unique identifier for the new form or new form parameter;

[0189] Assign the type of the referenced element to the type of the new object. When the type of the referenced element is 1, the type of the new object is a form parameter. When the type of the referenced element is 2, the type of the new object is a form.

[0190] Assign the coordinate field name to the key name of the current coordinate;

[0191] Assign the field value to the key value of the current coordinate;

[0192] Assign the creation date to the record creation time.

[0193] S103, in response to the request to retrieve the target form, retrieve the target coordinate set and search for the target form corresponding to the target coordinate set in the form element coordinate table.

[0194] Obtain the target element type and target coordinate set of the target form to be searched. The target coordinate set includes key-value pairs, and the key-value pairs include coordinate names and coordinate values. The target element type includes forms and form parameters.

[0195] In the form element coordinate table, filter out records whose reference element type matches the target element type;

[0196] Group the filtered records according to the referenced form element identifier, so that all coordinate records of the same form or form parameter are grouped together;

[0197] Filter out groups whose number of coordinate field names is equal to the number of coordinates in the target coordinate set;

[0198] Iterate through each coordinate in the target coordinate set one by one, and verify whether there is a record in the group whose coordinate field name is equal to the current coordinate name and whose reference element type is equal to the current coordinate value. If all target coordinates in the group are successfully matched, return the reference form element identifier corresponding to the group as the query result.

[0199] The method for obtaining the target form also includes:

[0200] Retrieve the form configuration of the target form and configure the target form as a standardized set of attributes that can be recognized by the front-end components.

[0201] The form rendering engine is the core component of this invention, enabling the transformation from dynamic configuration to a visual interface. It automatically generates interactive form interfaces by parsing form definition rules (JSON configuration) and performs data backfilling when collected information is available. This engine adopts a layered architecture design, achieving complete decoupling between business logic and the presentation layer.

[0202] The workflow of the form rendering engine is as follows Figure 4 As shown, after the client (the front end of the business system) obtains the form configuration, the configuration parser converts the form definition rules into a standardized set of attributes that can be recognized by the front-end components. Subsequently, the component mapping layer dynamically associates predefined Vue component libraries based on the component type declarations in the rules (such as Input / Select), generating a virtual DOM node tree through rendering functions. The engine creates the real DOM structure based on this node tree, while simultaneously establishing a reactive dependency tracking mechanism to ensure that the DOM state is synchronized with the data model in real time. Finally, the browser rendering engine maps the virtual nodes to interactive UI elements and injects data binding logic, achieving automated construction from structured configuration to a complete business data collection form.

[0203] This invention focuses on addressing the non-functional R&D and maintenance costs caused by constantly changing information collection forms in specific business scenarios. It completely eliminates the need for hard-coding to adapt systems to changing requirements. By utilizing a universal form definition, combined with multi-dimensional coordinate matching, form archiving mechanisms, and a form rendering engine, it achieves highly efficient development with immediate updates. Through a unified technical solution and operational process, it eliminates the uncertainty of system changes caused by business variations, significantly reducing team investment and R&D / maintenance cycles.

[0204] As shown in Table 4, the present invention is compared with the traditional solution as follows:

[0205]

[0206] Although the dynamic form system constructed by this invention was initially designed for talent introduction project application scenarios, it forms a universal technical framework that transcends specific business scenarios through the organic coupling of coordinate isolation mechanisms, standardized form definition rules, versioned archiving schemes, and configuration-driven rendering engines. Theoretically, this framework is applicable to any business system requiring data collection and historical backtracking, whether it's government administrative approval, corporate compliance application, medical information registration, or education assessment reporting. As long as there is a need for form definition, business boundaries can be defined through multi-dimensional key-value combinations of the coordinate system, collection parameters can be quickly constructed using general form definition rules, and data version consistency can be ensured by a state-driven archiving mechanism. Finally, zero-coding form delivery is achieved through the rendering engine. Even in scenarios where business forms are stable over a long period, this system can replace the traditional manual coding, testing, and deployment process with visual configuration, compressing the form building cycle from weeks to hours. It also completely eliminates the risk of technical comprehension gaps caused by personnel turnover, providing out-of-the-box, life-sustainable standardized data collection infrastructure for cross-domain scenarios such as finance and insurance, industrial manufacturing, and scientific research management.

[0207] Figure 2 This is a schematic diagram of the main components of the target form acquisition system in an embodiment of the present invention. For example... Figure 2 As shown, the target form acquisition system 1 provided in this embodiment of the invention includes a coordinate acquisition module 10, a coordinate recording module 20, and a form query module 30.

[0208] The coordinate acquisition module 10 is used to obtain a set of coordinates used to define the business boundaries of the form after a new form is added.

[0209] The coordinate recording module 20 is used to insert an independent associated record for each coordinate in the coordinate set in a pre-built form element coordinate table;

[0210] The form query module 30 is used to respond to the request to obtain the target form, obtain the target coordinate set, and search for the target form corresponding to the target coordinate set in the form element coordinate table.

[0211] Figure 5 This is a schematic diagram of the physical structure of an electronic device provided in an embodiment of the present invention, such as... Figure 5 As shown, the electronic device 40 includes: a processor 401, a memory 402, and a bus 403;

[0212] The processor 401 and the memory 402 communicate with each other via the bus 403.

[0213] The processor 401 is used to call program instructions in the memory 402 to execute the methods provided in the above-described method embodiments, and to execute the methods provided in the embodiments of the present invention.

[0214] This embodiment provides a non-transitory computer-readable storage medium that stores computer instructions, which cause a computer to execute the method provided in this embodiment of the invention.

[0215] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various storage media capable of storing program code, such as ROM, RAM, magnetic disk, or optical disk.

[0216] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for obtaining a target form, characterized in that, include: After adding a new form, obtain the set of coordinates used to define the business boundaries of the form; Insert a separate associated record for each coordinate in the pre-built form element coordinate table, including: Assign the value of the referenced form element identifier to a unique identifier for the new form or new form parameter; Assign the type of the referenced element to the type of the new object. When the type of the referenced element is 1, the type of the new object is a form parameter. When the type of the referenced element is 2, the type of the new object is a form. Assign the coordinate field name to the key name of the current coordinate; Assign the field value to the key value of the current coordinate; Assign the creation date to the record creation time; The form element coordinate table includes a primary key, a referencing form element identifier, a referencing element type, a coordinate field name, a field value, and a creation date; In response to a request to retrieve a target form, a target coordinate set is obtained, and the target form corresponding to the target coordinate set is searched in the form element coordinate table.

2. The method for obtaining the target form according to claim 1, characterized in that, The newly added forms include: In response to a form creation request, the form creation requirements are obtained, and specific content matching the form creation requirements is populated into a pre-set set of custom rule attributes to generate form parameters; The form parameters are combined based on predefined form configuration attributes to generate a form.

3. The method for obtaining the target form according to claim 2, characterized in that, The following is included after adding a new form: Monitor the lifecycle status of the newly added form, which includes pending modification, pending publication, published, and deactivated. When the lifecycle status of the newly added form or its parameters changes to "published", the newly added form is stored in the archive repository, and an archive form identifier is generated for the newly added form to distinguish between different versions of the form.

4. The method for obtaining the target form according to claim 3, characterized in that, The step of searching for the target form corresponding to the target coordinate set in the form element coordinate table includes: Obtain the target element type and target coordinate set of the target form to be searched. The target coordinate set includes key-value pairs, and the key-value pairs include coordinate names and coordinate values. The target element type includes forms and form parameters. In the form element coordinate table, filter out records whose reference element type matches the target element type; Group the filtered records according to the referenced form element identifier, so that all coordinate records of the same form or form parameter are grouped together; Filter out groups whose number of coordinate field names is equal to the number of coordinates in the target coordinate set; Iterate through each coordinate in the target coordinate set one by one, and verify whether there is a record in the group whose coordinate field name is equal to the current coordinate name and whose reference element type is equal to the current coordinate value. If all target coordinates in the group are successfully matched, return the reference form element identifier corresponding to the group as the query result.

5. The method for obtaining the target form according to claim 1, characterized in that, The method for obtaining the target form also includes: Retrieve the form configuration of the target form and configure the target form as a standardized set of attributes that can be recognized by the front-end components.

6. A system for obtaining a target form, characterized in that, include: The coordinate acquisition module is used to obtain a set of coordinates used to define the business boundaries of the form after a new form is added. The coordinate recording module is used to insert an independent associated record for each coordinate in the coordinate set in a pre-built form element coordinate table; The coordinate recording module is also used for: Assign the value of the referenced form element identifier to a unique identifier for the new form or new form parameter; Assign the type of the referenced element to the type of the new object. When the type of the referenced element is 1, the type of the new object is a form parameter. When the type of the referenced element is 2, the type of the new object is a form. Assign the coordinate field name to the key name of the current coordinate; Assign the field value to the key value of the current coordinate; Assign the creation date to the record creation time; The form element coordinate table includes a primary key, a referencing form element identifier, a referencing element type, a coordinate field name, a field value, and a creation date; The form query module is used to respond to a request to obtain a target form, retrieve a set of target coordinates, and search for the target form corresponding to the set of target coordinates in the form element coordinate table.

7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method as described in any one of claims 1 to 5.

8. A non-transitory computer-readable medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 5.

Images