Form generation method and device and form customizing system

Abstract

The invention discloses a form generation method and device and a form customizing system. The method comprises the steps that when a form creating request is received, form definition information of a target form is obtained, and the target form is a form needing to be generated; analyzing the form definition information to obtain fields and linkage rules of all function modules in the target form; a rule engine of the target form is obtained according to the linkage rule, and the rule engine is used for recognizing the relation between fields in the target form; a target field in the fields is determined, an event monitor is added to the target field, an initial form is obtained, and the target field is a field which can trigger a linkage rule corresponding to the linkage rule in the fields; and adding the rule engine to the initial form to obtain a target form. According to the method and the device, the technical problem that dynamic logic linkage between fields cannot be realized by a traditional form system in a configuration mode in the gateway technology is solved.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and more specifically, to a form generation method and apparatus, and a custom form system. Background Technology

[0002] Currently, custom form systems are widely used in various information management scenarios (such as data collection, approval processes, and business configuration). Their core function is to allow for free design of form layouts through drag-and-drop field components (such as input boxes, selection boxes, and text boxes) in a visual interface, and to support adjustments to basic field attributes (such as labels, placeholders, and validation rules). For example, existing technologies may design form interface prototypes by analyzing the characteristics of each field attribute required by the business scenario; create form templates and input business fields on the web front-end, bind the templates to corresponding business object instances, save the web application, input the user-configured form template information into the database, and then publish the form.

[0003] However, most of the above-mentioned form systems only support static field configurations and lack dynamic logic linkage mechanisms. For example, they cannot trigger the calculation or API call of field B based on the input value of field A, requiring external code development, which is inefficient; that is, the ability to link logic between fields is insufficient. In addition, existing systems are usually designed on a single form basis, and cannot save frequently used field combinations and their linkage logic as templates, leading to repeated development; that is, modular reuse is difficult. Furthermore, there is insufficient support for complex scenarios (such as numerical calculations, multi-field concatenation, and API interactions), requiring custom backend development, resulting in poor flexibility; that is, weak dynamic data processing capabilities.

[0004] There is currently no effective solution to the above problems. Summary of the Invention

[0005] This invention provides a form generation method and apparatus, and a custom form system, to at least solve the technical problem that traditional form systems cannot achieve dynamic logical linkage between fields through configuration.

[0006] According to one aspect of the present invention, a form generation method is provided, comprising: upon receiving a form creation request, obtaining form definition information of a target form, wherein the target form is the form to be generated; parsing the form definition information to obtain fields and linkage rules of each functional module in the target form; obtaining a rule engine for the target form according to the linkage rules, wherein the rule engine is used to identify the relationship between the fields in the target form; determining a target field in each field and adding an event listener to the target field to obtain an initial form, wherein the target field is the field in each field that triggers the linkage rule corresponding to the linkage rule; and adding the rule engine to the initial form to obtain the target form.

[0007] Optionally, obtaining the form definition information of the target form includes: upon receiving the form creation request, parsing the form creation request to obtain the form type of the target form; sending a form information retrieval request to the backend of the form customization system; and obtaining the form definition information searched by the backend based on the form information retrieval request.

[0008] Optionally, parsing the form definition information to obtain the fields and linkage rules of each functional module in the target form includes: converting the form definition information into a formatted form definition information; and extracting the fields and linkage rules from the formatted form definition information.

[0009] Optionally, obtaining the rule engine for the target form based on the linkage rules includes: parsing the linkage rules to obtain the linkage relationship between each of the fields; obtaining the association relationship between each of the fields based on the linkage relationship; and generating the rule engine based on the association relationship.

[0010] Optionally, determining the target field among the fields and adding an event listener to the target field to obtain an initial form includes: determining the field components, functional module components, and module linkage rules required for the target form based on the form definition information; pre-generating the form using a form designer based on the field components, functional module components, and module linkage rules to obtain a preview form; analyzing each field to obtain the target field among the fields that will trigger the linkage rule; and adding the event listener to the target field in the preview form to obtain the initial form.

[0011] Optionally, adding the rule engine to the initial form to obtain the target form includes: displaying all the fields in each of the functional modules in the initial form; configuring the linkage rules for the initial form according to the relationship between all the fields identified by the rule engine to obtain an intermediate form; performing linkage simulation on the intermediate form to obtain the linkage result of the intermediate form; and obtaining the target form when the linkage result indicates that the linkage of each field in the intermediate form meets the linkage requirements.

[0012] Optionally, the form generation method further includes: upon receiving a form call request, invoking the field information and functional module information of the target form; parsing the field information and functional module information to obtain a parsing result; after rendering the parsing result onto the current page, parsing the linkage rules of the target form according to the functional module information, and loading the linkage rules into the current page; listening for field trigger events of the target form in real time on the current page; upon listening for a field trigger event, obtaining the calculation method and interface call information in the target form; and loading the calculation method and interface call information into the listening trigger event of the target form.

[0013] Optionally, the form generation method further includes: after detecting a change in the trigger field of the target form, triggering the linkage rule of the target form to execute the calculation operation or interface call operation in the target form and obtain the execution result; updating the execution result to the target field, wherein the target field is the field pointed to by the linkage rule.

[0014] According to another aspect of the present invention, a form generation apparatus is also provided, comprising: a first acquisition unit, configured to acquire form definition information of a target form upon receiving a form creation request, wherein the target form is the form to be generated; a parsing unit, configured to parse the form definition information to obtain fields and linkage rules of each functional module in the target form; a second acquisition unit, configured to obtain a rule engine of the target form according to the linkage rules, wherein the rule engine is used to identify the relationship between the fields in the target form; a determining unit, configured to determine a target field among the fields and add an event listener to the target field to obtain an initial form, wherein the target field is the field among the fields that will trigger the linkage rule corresponding to the linkage rule; and a third acquisition unit, configured to add the rule engine to the initial form to obtain the target form.

[0015] Optionally, the first acquisition unit includes: a first parsing module, configured to parse the form creation request upon receiving the form creation request to obtain the form type of the target form; a sending module, configured to send a form information acquisition request to the backend of the form customization system; and a first acquisition module, configured to acquire the form definition information searched by the backend based on the form information acquisition request.

[0016] Optionally, the parsing unit includes: a conversion module, used to convert the form definition information into a format to obtain the converted form definition information; and an extraction module, used to extract the field and the linkage rule from the converted form definition information.

[0017] Optionally, the second acquisition unit includes: a second parsing module, used to parse the linkage rules to obtain the linkage relationship between each of the fields; a second acquisition module, used to obtain the association relationship between each of the fields based on the linkage relationship; and a first generation module, used to generate the rule engine based on the association relationship.

[0018] Optionally, the determining unit includes: a first determining module, configured to determine the field components, functional module components, and module linkage rules required for the target form based on the form definition information; a second generating module, configured to pre-generate the form using a form designer based on the field components, functional module components, and module linkage rules to obtain a preview form; an analysis module, configured to analyze each of the fields to obtain the target field that will trigger the linkage rule; and a third obtaining module, configured to add the event listener to the target field in the preview form to obtain the initial form.

[0019] Optionally, the third acquisition unit includes: a display module for displaying all the fields in each of the functional modules in the initial form; a configuration module for configuring the linkage rules for the initial form according to the relationship between all the fields identified by the rule engine, to obtain an intermediate form; a simulation module for performing linkage simulation on the intermediate form to obtain the linkage result of the intermediate form; and a fourth acquisition module for obtaining the target form when the linkage result indicates that the linkage of each of the fields in the intermediate form meets the linkage requirements.

[0020] Optionally, the form generation device further includes: a calling unit, used to call the field information and functional module information of the target form when a form calling request is received; a parsing unit, used to parse the field information and the functional module information to obtain a parsing result; a loading unit, used to parse the linkage rule of the target form according to the functional module information after rendering the parsing result to the current page, and load the linkage rule into the current page; a listening unit, used to listen for field trigger events of the target form in real time on the current page; a fourth acquisition unit, used to acquire the calculation method and interface call information in the target form when the field trigger event is detected; and a loading unit, used to load the calculation method and the interface call information into the listening trigger event of the target form.

[0021] Optionally, the form generation device further includes: a triggering unit, configured to trigger the linkage rule of the target form after detecting a change in the triggering field of the target form, so as to execute the calculation operation or interface call operation in the target form and obtain the execution result; and an updating unit, configured to update the execution result to the target field, wherein the target field is the field pointed to by the linkage rule.

[0022] According to another aspect of the present invention, a custom form system is also provided, which uses the form generation method described in any one of the above embodiments.

[0023] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored program, wherein the program executes the form generation method described in any one of the foregoing embodiments.

[0024] According to another aspect of the present invention, a processor is also provided, the processor being configured to run a program, wherein the program, when running, executes the form generation method described in any of the foregoing embodiments.

[0025] According to another aspect of the present invention, a computer program product is also provided, including computer instructions that, when executed by a processor, perform the form generation method described in any one of the above embodiments.

[0026] In this embodiment of the invention, upon receiving a form creation request, the form definition information of the target form is obtained, wherein the target form is the form to be generated; the form definition information is parsed to obtain the fields and linkage rules of each functional module in the target form; a rule engine for the target form is obtained based on the linkage rules, wherein the rule engine is used to identify the relationship between the fields in the target form; the target field in each field is determined, and an event listener is added to the target field to obtain the initial form, wherein the target field is the field in each field that triggers the linkage rule corresponding to the linkage rule; the rule engine is added to the initial form to obtain the target form. Through the technical solution provided by this invention, dynamic interaction between fields is achieved through the rule engine, while the event listener mechanism ensures that the rule engine can respond to user operations in real time, thereby greatly improving the flexibility and efficiency of form design, and solving the technical problem that traditional form systems cannot achieve dynamic logical linkage between fields through configuration. Attached Figure Description

[0027] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0028] Figure 1 This is a hardware structure block diagram of a mobile terminal for a form generation method according to an embodiment of the present invention.

[0029] Figure 2 This is a flowchart of a form generation method according to an embodiment of the present invention;

[0030] Figure 3 This is a schematic diagram of a custom form system according to an embodiment of the present invention;

[0031] Figure 4 This is a schematic diagram illustrating the configuration linkage rules according to an embodiment of the present invention;

[0032] Figure 5 This is a schematic diagram of the flow of the signature and approval form calling module according to an embodiment of the present invention;

[0033] Figure 6 This is a schematic diagram of a form generation apparatus according to an embodiment of the present invention. Detailed Implementation

[0034] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. 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.

[0035] It should be noted that the terms "first," "second," etc., in the specification, claims, 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 interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a 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.

[0036] As described in the background section, traditional form systems in related technologies suffer from the limitation of failing to achieve dynamic logical linkage between fields through configuration. Embodiments of this invention provide a form generation method and apparatus, a custom form system, a computer-readable storage medium, a processor, and a computer program product.

[0037] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

[0038] The methods and embodiments provided in this invention can be executed on a mobile terminal, a computer terminal, or a similar computing device. Taking running on a mobile terminal as an example, Figure 1 This is a hardware structure block diagram of a mobile terminal for a form generation method according to an embodiment of the present invention. Figure 1 As shown, a mobile terminal may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The mobile terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the mobile terminal described above. For example, the mobile terminal may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0039] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the form generation method in this embodiment of the invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thereby implementing the above-described method. The memory 104 may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the mobile terminal via a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof. The transmission device 106 is used to receive or send data via a network. Specific examples of the aforementioned networks may include wireless networks provided by the mobile terminal's communication provider. In one example, the transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to communicate with the Internet. In one example, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0040] Example 1

[0041] According to an embodiment of the present invention, a method embodiment for a form generation method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0042] Figure 2 This is a flowchart of a form generation method according to an embodiment of the present invention, such as... Figure 2 As shown, the form generation method includes the following steps:

[0043] Step S202: Upon receiving a form creation request, obtain the form definition information of the target form, wherein the target form is the form to be generated.

[0044] Optionally, the above form creation request is a form request initiated by the user based on actual application needs.

[0045] Optionally, the form definition information mentioned above refers to a data set describing the form's structure and behavior, typically including field attributes (such as type, tags, and validation rules), layout, style, and possible inter-field interaction rules. It serves as a blueprint for creating or editing forms, guiding how the front-end renders and how the back-end processes the form data.

[0046] In this embodiment, after receiving a form creation request from a user, the front-end of the custom form system retrieves the definition information of the target form by sending a GET request to the back-end. This information is returned in JSON format and includes field attributes, layout, styles, and cascading rules. The front-end uses JSON.parse() to parse the data, converting the JSON string into a manipulable JavaScript object.

[0047] For example, when a user (such as an administrative assistant, project manager, or website administrator) clicks the "New Form" button in a custom form system, the system receives a "Form Creation Request" initiated by the user. At this point, the front-end application will use an HTTP GET request to query the back-end server for the definition information of a specific type of target form. For instance, if the user wants to create an "Employee Leave Application Form," the request will carry "Leave Form" as a parameter. The back-end will return a JSON data packet containing the required fields for the leave application form (such as the number of leave days, reason for leave, and department head approval status) and their attributes (such as required fields, character length limits, and default values). The key to this process is accurately identifying the user's creation intent and efficiently retrieving matching form template information from the database.

[0048] Step S204: Parse the form definition information to obtain the fields and linkage rules of each functional module in the target form.

[0049] Optionally, the fields mentioned above are parts of the form used to collect specific types of information, such as text input boxes, number input boxes, drop-down selection boxes, etc. Each field has its specific attributes and uses, such as collecting user name, age, or selecting a certain option.

[0050] Optionally, the linkage rules here refer to the logical relationships and interactions between fields in the form; that is, how to automatically adjust the values ​​of other fields or trigger specific behaviors (such as calculations or API calls) when the value of one or more fields changes. For example, "Total price = Unit price * Quantity" is a common linkage rule.

[0051] In this embodiment, after receiving the JSON data returned by the backend, the frontend uses JSON parsing functions in JavaScript or other frontend frameworks (such as React or Vue) to read and understand the data, extracting field components and their properties, as well as the interaction rules between the fields (for example, when the number of leave days exceeds 3 days, a second approval from the department manager is required). The parsed information will be stored in the frontend's state manager, such as Redux or Vuex, for later use in the form designer and rule configuration panel. The core of parsing is to transform unstructured or semi-structured data into a format that the frontend can manipulate.

[0052] Step S206: Obtain the rule engine of the target form according to the linkage rules, wherein the rule engine is used to identify the relationship between the fields in the target form.

[0053] Optionally, the rules engine here is capable of determining or influencing the behavior of the application based on predefined rules. It can be responsible for identifying and enforcing linked rules in forms, ensuring the consistency and accuracy of form data.

[0054] In this embodiment, the front-end system uses the parsed linkage rules to build a rule engine. The rule engine can be a rule-based expert system or a state machine model, depending on the system's complexity and performance requirements. For example, for a leave application form, the rule engine will identify the logical relationship between the "Number of Leave Days" field and the "Department Approval" and "General Manager Approval" fields. When the rule engine is activated, it listens for field changes. Once the value of the "Number of Leave Days" field changes, the rule engine checks if it exceeds the 3-day threshold. If it does, it automatically triggers the next approval step. The design and implementation of the rule engine ensures the intelligent and automated execution of form linkage.

[0055] Step S208: Determine the target field in each field and add an event listener to the target field to obtain the initial form. The target field is the field in each field that will trigger the linkage rule corresponding to the linkage rule.

[0056] Optionally, an event listener is a programmatic mechanism used to listen for user actions or other events and execute predefined functions or logic under specific conditions. In a form system, adding an event listener to a "target field" means that the system will continuously monitor changes in the values ​​of these fields, and will execute corresponding actions according to the linkage rules once a change occurs.

[0057] In this embodiment, in the front-end form designer interface, the system determines which fields are target fields—that is, those fields that can trigger the linkage rules—based on the parsed fields and linkage rules. For example, in our leave application form, "Number of Leave Days" is a target field. The system adds event listeners, such as onChange or onInput events, to the DOM element corresponding to each target field to capture user input or modification of field values. Once an event is triggered, the listener will call the corresponding rule in the rule engine. For example, the listener for the "Number of Leave Days" field will check if the "Number of Leave Days" has changed; if it has, the rule engine will be activated to update the approval status. Event listeners are key to enabling dynamic interaction between fields; they ensure that the rule engine can respond to user actions in real time, rather than passively waiting for backend instructions.

[0058] Step S210: Add the rules engine to the initial form to obtain the target form.

[0059] In this embodiment, once the event listener is configured, the front-end system integrates the rule engine into the form, creating a dynamic form—the target form—with complete fields, linked logic, and real-time data processing capabilities. At this stage, all fields and rules are ready, and the user can begin entering data into the form. For example, if a user enters "4" in the "Number of Leave Days" field, the event listener detects the change and triggers the rule engine. The rule engine executes logical judgments and automatically modifies the approval process to include the "General Manager Approval" step. The integration of the rule engine ensures that the form can automatically and intelligently adjust and respond as the user enters data, providing a seamless and efficient interactive experience.

[0060] Furthermore, this process solves the problem of hard-coding field definitions and linkage rules in form systems. By dynamically acquiring and parsing form definition information, the configurability of form components and logic is achieved.

[0061] It is worth noting that, in this embodiment of the invention, a modular linkage field component library is provided. Specifically, field components (input boxes, selection boxes, etc.) and linkage logic (such as calculation rules and interface calls) can be encapsulated into independent modules, supporting on-demand combination and reuse. Each module includes a field attribute configuration interface and a linkage rule configuration interface (such as setting trigger conditions, calculation expressions, and interface addresses).

[0062] Additionally, a visual rule configurator is provided, allowing users to define inter-field linkage logic through drag-and-drop or expressions (e.g., field C = field A × field B or field D = call API (field A)). Multi-rule chaining is supported (e.g., field A change → triggers field B calculation → triggers field C API call). This multi-rule chaining primarily relies on front-end data monitoring. For example, by monitoring changes in field A, changes in field B are triggered; field B is also being monitored, and its change will also trigger the API call for field C.

[0063] Furthermore, this embodiment of the invention also provides a dynamic data processing module, which includes a built-in numerical calculation module (supporting addition, subtraction, multiplication, division, and aggregation operations), a string processing module (supporting concatenation, truncation, and formatting), and an interface call module (supporting HTTP requests and parameter mapping). It monitors changes in field values ​​in real time and automatically triggers the data processing flow.

[0064] As described above, in this embodiment of the invention, upon receiving a form creation request, the form definition information of the target form is obtained, where the target form is the form to be generated; the form definition information is parsed to obtain the fields and linkage rules of each functional module in the target form; the rule engine of the target form is obtained based on the linkage rules, where the rule engine is used to identify the relationship between the fields in the target form; the target field in each field is determined, and an event listener is added to the target field to obtain the initial form, where the target field is the field in each field that triggers the linkage rule corresponding to the linkage rule; the rule engine is added to the initial form to obtain the target form. This achieves dynamic interaction between fields through the rule engine, while utilizing the event listener mechanism to ensure that the rule engine can respond to user operations in real time, thereby greatly improving the flexibility and efficiency of form design.

[0065] Therefore, the technical solution provided by the embodiments of the present invention solves the technical problem that traditional form systems cannot achieve dynamic logical linkage between fields through configuration.

[0066] Figure 3 This is a schematic diagram of a custom form system according to an embodiment of the present invention, such as... Figure 3As shown, it includes a front-end and a back-end. The front-end includes a form designer, a rule parsing module, a data processing module, and a module library. The form designer allows dragging and dropping field components, module components, and configuring module linkage rules, providing form preview functionality. The rule parsing module can parse user-configured linkage rules (such as mathematical expressions and API calls). The data processing module may include a numerical calculation module, a string processing module, and an API call module. The module library can store commonly used field combinations and linkage rules. The back-end may include data storage and a data interface. Data storage is mainly responsible for storing form data, custom modules, and module configurations. The data interface provides simple data access functionality.

[0067] Specifically, the visual form designer includes a drag-and-drop interface that allows users to select fields (such as text boxes and dropdown lists) and modules (such as calculation modules and API call modules) from a component library. A configuration panel is provided, allowing users to set linkage rules for modules (such as "automatically calculate the total price when the unit price changes"), and a form preview function is implemented, enabling users to view the final form effect in real time during the design process.

[0068] Rule parsing module: Develop a rule parsing engine to support the parsing of user-configured linkage rules, including mathematical expressions (such as "total price = unit price * quantity") and interface calls (such as calling an external API to obtain city information), ensuring the accuracy and efficiency of rule parsing.

[0069] Data processing module: Implements a numerical calculation module, supporting basic mathematical operations (such as addition, subtraction, multiplication, and division); implements a string processing module, supporting string concatenation, truncation, and other operations; and can also implement an API call module, supporting calling external APIs via HTTP requests and processing the returned results.

[0070] Module Library: Develop a module library function that allows users to save commonly used field combinations and their linkage rules as modules for easy reuse later. It also provides a module management interface that supports adding, deleting, modifying, and querying modules.

[0071] Backend: Data Storage: Design the database table structure to store form data, custom modules, and module configurations, implementing data persistence to ensure that user-configured forms and modules can be saved long-term. Data Interface: Develop a RESTful API to provide access to form data and module configurations, ensuring interface security and supporting authentication and access control.

[0072] According to the above embodiments of the present invention, obtaining the form definition information of the target form may include: upon receiving a form creation request, parsing the form creation request to obtain the form type of the target form; sending a form information retrieval request to the backend of the form customization system; and obtaining the form definition information searched by the backend based on the form information retrieval request.

[0073] In this embodiment, when the front-end receives a form creation request, it parses the form type parameter in the request and sends a request to the back-end server. The back-end server retrieves the database based on the form type and returns the corresponding form definition information. This ensures that the definition information obtained at the time of form creation is up-to-date, avoiding form errors caused by using outdated definitions. This method enables dynamic switching of form types, allowing users to quickly create different types of forms as needed without reconfiguration or recoding.

[0074] For example, in an ERP system, when a user creates a purchase order, the front end retrieves form definition information of a specific type, "Purchase Order," from the back end. This information includes fields such as product name, supplier, quantity, unit price, and total amount, as well as the rules governing the interaction between these fields. For instance, the "Total Amount" field is automatically calculated based on changes in the values ​​of the "Quantity" and "Unit Price" fields.

[0075] According to the above embodiments of the present invention, parsing the form definition information to obtain the fields and linkage rules of each functional module in the target form includes: converting the form definition information into a format to obtain the format-converted form definition information; and extracting the fields and linkage rules from the format-converted form definition information.

[0076] In this embodiment, after receiving the raw JSON data returned by the backend, the frontend performs format conversion using a custom function to make it more consistent with the frontend's processing rules, facilitating further parsing and rendering. Format conversion ensures consistency and compatibility of the frontend and backend data structures, avoids parsing errors caused by data format mismatches, improves the speed and accuracy of the frontend in processing form definition information, and enhances the overall system performance and user experience.

[0077] For example, bank staff can use form designers to convert the original form definition information into a format suitable for loan application scenarios. This includes adding fields such as "Loan Amount," "Repayment Period," and "Interest Rate," and configuring linkage rules, such as "Monthly Repayment Amount = Loan Amount * Interest Rate / (1 - (1 + Interest Rate)^(-Repayment Period))". This format conversion and linkage rule configuration allows banks to quickly adapt to market changes and adjust the rules of their loan products.

[0078] According to the above embodiments of the present invention, obtaining a rule engine for a target form based on linkage rules includes: parsing the linkage rules to obtain the linkage relationship between each field; obtaining the association relationship between each field based on the linkage relationship; and generating a rule engine based on the association relationship.

[0079] In this embodiment, the front-end parses the linkage rules, identifies the logical relationships between fields, and generates a rule engine using a custom or third-party rule engine framework (such as Drools, rulesengine.js, etc.) to handle field changes in real time. The rule engine solves the problem of dynamically executing complex linkage rules between fields, eliminating the need for code modification or rewriting every time a field changes, greatly improving the flexibility and efficiency of form responses. This enhances the system's dynamic responsiveness, supports complex business logic, and improves the accuracy and real-time performance of user input data.

[0080] For example, e-commerce platforms use rule engines on product detail pages to manage the dynamic calculation of product prices. For instance, when a user selects different "product specifications" (such as color or size), the "product price" is automatically adjusted. The rule engine performs real-time calculations based on pre-configured linkage rules (such as "price = base price + specification surcharge") to ensure that the price seen by the user is accurate.

[0081] According to the above embodiments of the present invention, determining the target field in each field and adding an event listener to the target field to obtain an initial form includes: determining the field components, functional module components, and module linkage rules required for the target form based on the form definition information; pre-generating the form using a form designer based on the field components, functional module components, and module linkage rules to obtain a preview form; analyzing each field to obtain the target field in each field that will trigger the linkage rules; and adding an event listener to the target field in the preview form to obtain the initial form.

[0082] In this embodiment, the front-end application pre-generates the form interface using the form designer based on the fields and linkage rules in the form definition information, and adds event listeners to the "target fields." Target fields refer to those fields that can trigger linkage rules. The configuration of event listeners solves the problem of passively triggering linkage rules, ensuring that linkage logic is automatically executed when fields change. The form preview function allows developers to instantly view the appearance and linkage effects when creating a form, accelerating the development and debugging cycle.

[0083] For example, in project management software, a task assignment table is designed that needs to dynamically update task priorities and estimated completion dates. The system identifies the "task deadline" as the target field and adds an event listener to calculate the "remaining days" in real time, thereby affecting the value of the "priority" field. The calculation rule for the "priority" field could be: "When the remaining days are less than 7 days, the priority is set to high; otherwise, it is normal."

[0084] According to the above embodiments of the present invention, adding a rule engine to an initial form to obtain a target form includes: displaying all fields in each functional module of the initial form; configuring linkage rules for the initial form according to the relationship between all fields identified by the rule engine to obtain an intermediate form; performing linkage simulation on the intermediate form to obtain the linkage result of the intermediate form; and obtaining the target form when the linkage result indicates that the linkage of each field in the intermediate form meets the linkage requirements.

[0085] In this embodiment, the front-end simulates input data in preview mode, and the rule engine calculates the effect of field linkage in real time to ensure that all rules are correct and consistent with preset business requirements. Linkage simulation and verification ensure the correctness of the linkage logic of the form before formal deployment, avoiding system failures or data processing errors caused by incorrect rule configuration. Through simulation and verification, system reliability is enhanced, pre-deployment debugging costs are reduced, and user trust is increased.

[0086] For example, medical institutions use form systems to create medical record forms, which include fields such as "patient age," "blood pressure," and "heart rate." During the form design phase, the correctness of the linkage between the "blood pressure" and "heart rate" fields is confirmed through interactive simulation, ensuring that when the "patient age" exceeds 60 years old, the system automatically reminds the doctor to check whether the "blood pressure" and "heart rate" are abnormal.

[0087] Figure 4 This is a schematic diagram illustrating the configuration linkage rules according to an embodiment of the present invention, such as... Figure 4 As shown, the field list displays all fields in the current module (such as unit price, quantity, total price, and city). The rule configuration panel supports selecting the trigger field, target field, rule type (such as calculation, string concatenation, and API call), and specific configurations (such as mathematical expression and API address). The real-time preview area displays the simulated results of the linkage effect (e.g., unit price: 10, quantity: 2, total price: 20, city: Zhuhai). The module can be saved and used in custom forms; modules can coexist with single fields.

[0088] The field list displays all fields in the current module (such as unit price, quantity, total price, and city) on the left side of the interface, and supports field search and filtering functions.

[0089] Rule Configuration Panel: Provides a rule configuration interface where users can select the trigger field (such as "unit price"), target field (such as "total price"), and rule type (such as "calculation"). Based on the rule type, the corresponding configuration options are displayed (such as the mathematical expression "total price = unit price * quantity").

[0090] Real-time preview area: Displays the simulation results of the linkage rules on the right side of the interface (e.g., when the unit price is 10 and the quantity is 2, the total price is automatically calculated to be 20), ensuring the real-time nature and accuracy of the preview results.

[0091] Module saving and usage: A "Save Module" button is provided, allowing users to save the currently configured modules to the module library.

[0092] It should be noted that in custom forms, it is possible to use saved modules together with a single field.

[0093] According to the above embodiments of the present invention, the form generation method further includes: upon receiving a form call request, calling the field information and functional module information of the target form; parsing the field information and functional module information to obtain a parsing result; after rendering the parsing result onto the current page, parsing the linkage rules of the target form according to the functional module information, and loading the linkage rules into the current page; listening for field trigger events of the target form in real time on the current page; when a field trigger event is detected, obtaining the calculation method and interface call information in the target form; and loading the calculation method and interface call information into the listening trigger event of the target form.

[0094] In this embodiment, after receiving a form call request, the front end obtains the field information and functional module information of the target form from the back end, parses it, dynamically renders the form, and loads the linkage rules into the event listener. This solves the problem of form reuse in multiple scenarios, ensures that the correct field information and linkage rules can be loaded quickly for each form call, enhances the system's responsiveness, improves the efficiency and accuracy of form calls, and reduces user waiting time caused by data loading delays or misconfigurations.

[0095] For example, the HR department uses the system to create performance appraisal forms. The form request triggers the backend to return field information and functional module information, which the frontend then parses and dynamically renders. For instance, "Scoring Criteria" is a functional module, where "Skill Score," "Attitude Score," and "Performance Score" are target fields. When creating the appraisal form, the HR manager selects these fields by dragging and dropping, and configures linkage rules, such as "Total Score = Skill Score * 0.4 + Attitude Score * 0.3 + Performance Score * 0.3." After the rules are loaded onto the current page, the system monitors changes to these target fields in real time to ensure the total score is updated continuously.

[0096] Figure 5 This is a schematic diagram of the flow of the signature and approval form calling module according to an embodiment of the present invention, as shown below. Figure 5As shown, the frontend retrieves form field and module information from the backend; then, the page parses the field and module information and renders it on the page; next, it parses the linkage rules according to the module configuration information and loads them into the page's listening method; the page listens for changes in the corresponding trigger fields in real time and puts the calculation method or API call into the listening trigger method; when a change is detected in the trigger field, the linkage rule is triggered, and the listening method is called to perform the calculation or API call; the calculation result or API call result is updated to the target field; finally, the form field information is submitted to the backend for approval.

[0097] Among these, retrieving form information involves the front-end calling the back-end API to obtain the form's field and module information, ensuring efficient and stable data loading.

[0098] Page rendering: Parse field and module information and dynamically render it onto the page to ensure the rationality and aesthetics of the page layout.

[0099] Parse linkage rules: Based on the module configuration information, parse the linkage rules (such as "calculate the total price when the unit price changes") and load the parsed rules into the page listener method.

[0100] Page Listener: Real-time monitoring of changes in trigger fields (such as changes in the value of the unit price input box), and binding calculation methods or API call logic to the listener trigger method.

[0101] Trigger linkage rules: When the trigger field changes, the listener method is automatically called to perform calculations or API calls to ensure that the triggering logic of the linkage rules is correct.

[0102] Update target field: Update the target field with the calculation result or interface call result (e.g., display the calculated total price in the total price input box) to ensure that the target field is updated in a timely and accurate manner.

[0103] Submitting the form: After the user completes the form, they click the "Submit" button to submit the form field information to the backend. The backend receives the data and completes the approval process.

[0104] According to the above embodiments of the present invention, the form generation method may further include: after detecting a change in the trigger field of the target form, triggering the linkage rule of the target form to execute the calculation operation or interface call operation in the target form and obtain the execution result; updating the execution result to the target field, wherein the target field is the field pointed to by the linkage rule.

[0105] In this embodiment, the front end monitors any changes to the target field. Once a change is detected, the corresponding linkage rules, such as numerical calculations or API calls, are immediately executed through the rule engine. The results are then updated to the relevant fields. This solves the problem of delayed or incorrect execution of linkage rules when fields change, ensuring the real-time performance and accuracy of data processing, improving the immediate feedback of user input data, enhancing the smoothness of operation and the real-time data processing capability, and improving the user experience and overall system performance.

[0106] For example, when a warehouse administrator creates an "Inventory Management Form," the system uses a rule engine to identify the relationship between the "Inventory Quantity" field and its threshold. If the value of the "Inventory Quantity" field is detected to be below 100 units, a trigger rule is immediately activated, calling the backend's alert API to notify relevant departments to replenish stock. This mechanism ensures timely inventory replenishment and avoids production or sales interruptions due to insufficient inventory.

[0107] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0108] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0109] Example 2

[0110] According to an embodiment of the present invention, a form generation apparatus for implementing the above-described form generation method is also provided. Figure 6 This is a schematic diagram of a form generation apparatus according to an embodiment of the present invention, such as... Figure 6 As shown, the form generation device includes: a first acquisition unit 601, a parsing unit 603, a second acquisition unit 605, a determining unit 607, and a third acquisition unit 609. The form generation device will now be described.

[0111] The first acquisition unit 601 is used to acquire the form definition information of the target form when a form creation request is received, wherein the target form is the form to be generated.

[0112] Parsing unit 603 is used to parse the form definition information to obtain the fields and linkage rules of each functional module in the target form.

[0113] The second acquisition unit 605 is used to obtain the rule engine of the target form according to the linkage rules, wherein the rule engine is used to identify the relationship between the fields in the target form.

[0114] Unit 607 is used to determine the target field in each field and add an event listener to the target field to obtain the initial form. The target field is the field in each field that will trigger the linkage rule.

[0115] The third acquisition unit 609 is used to add the rule engine to the initial form to obtain the target form.

[0116] It should be noted that the first acquisition unit 601, the parsing unit 603, the second acquisition unit 605, the determining unit 607, and the third acquisition unit 609 mentioned above correspond to steps S202 to S210 in the above embodiments. The three modules and the corresponding steps implement the same instances and application scenarios, but are not limited to the content disclosed in the above embodiments.

[0117] As can be seen from the above, in the solution described in the above embodiments of the present invention, a first acquisition unit is used to acquire the form definition information of the target form when a form creation request is received, wherein the target form is the form to be generated; a parsing unit is used to parse the form definition information to obtain the fields and linkage rules of each functional module in the target form; a second acquisition unit is used to obtain the rule engine of the target form according to the linkage rules, wherein the rule engine is used to identify the relationship between the fields in the target form; a determining unit is used to determine the target field in each field and add an event listener to the target field to obtain the initial form, wherein the target field is the field in each field that will trigger the linkage rule corresponding to the linkage rule; a third acquisition unit is used to add the rule engine to the initial form to obtain the target form, thereby realizing the dynamic interaction between fields through the rule engine, and at the same time, the event listening mechanism ensures that the rule engine can respond to user operations in real time, thereby greatly improving the flexibility and efficiency of form design.

[0118] Therefore, the technical solution provided by the embodiments of the present invention solves the technical problem that traditional form systems cannot achieve dynamic logical linkage between fields through configuration.

[0119] Optionally, the first acquisition unit includes: a first parsing module, used to parse the form creation request upon receiving it to obtain the form type of the target form; a sending module, used to send a form information acquisition request to the backend of the form customization system; and a first acquisition module, used to acquire the form definition information searched by the backend based on the form information acquisition request.

[0120] Optionally, the parsing unit includes: a conversion module for converting the form definition information to obtain the converted form definition information; and an extraction module for extracting fields and linkage rules from the converted form definition information.

[0121] Optionally, the second acquisition unit includes: a second parsing module for parsing the linkage rules to obtain the linkage relationship between each field; a second acquisition module for obtaining the association relationship between each field based on the linkage relationship; and a first generation module for generating a rule engine based on the association relationship.

[0122] Optionally, the determining unit includes: a first determining module, used to determine the field components, functional module components, and module linkage rules required for the target form based on the form definition information; a second generating module, used to pre-generate the form using a form designer based on the field components, functional module components, and module linkage rules to obtain a preview form; an analysis module, used to analyze each field to obtain the target field that will trigger the linkage rule; and a third obtaining module, used to add event listeners to the target fields in the preview form to obtain the initial form.

[0123] Optionally, the third acquisition unit includes: a display module for displaying all fields in each functional module of the initial form; a configuration module for configuring linkage rules for the initial form based on the relationships between all fields identified by the rule engine, thereby obtaining an intermediate form; a simulation module for performing linkage simulation on the intermediate form to obtain the linkage result of the intermediate form; and a fourth acquisition module for obtaining the target form when the linkage result indicates that the linkage of each field in the intermediate form meets the linkage requirements.

[0124] Optionally, the form generation device further includes: a calling unit, used to call the field information and functional module information of the target form when a form calling request is received; a parsing unit, used to parse the field information and functional module information to obtain the parsing result; a loading unit, used to parse the linkage rules of the target form according to the functional module information after rendering the parsing result to the current page, and load the linkage rules into the current page; a listening unit, used to listen for the field trigger events of the target form in real time on the current page; a fourth acquisition unit, used to acquire the calculation method and interface call information in the target form when a field trigger event is detected; and a loading unit, used to load the calculation method and interface call information into the listening trigger event of the target form.

[0125] Optionally, the form generation device further includes: a triggering unit, used to trigger the linkage rule of the target form after detecting a change in the triggering field of the target form, so as to execute the calculation operation or interface call operation in the target form and obtain the execution result; and an updating unit, used to update the execution result to the target field, wherein the target field is the field pointed to by the linkage rule.

[0126] According to another aspect of the present invention, a custom form system is also provided, which uses any of the form generation methods described above.

[0127] According to another aspect of the present invention, a processor is also provided, which is used to run a program, wherein the program executes any of the above-described form generation methods during runtime.

[0128] According to another aspect of the present invention, a computer program product is also provided, including computer instructions that, when executed by a processor, perform any of the above-described form generation methods.

[0129] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored program, wherein the program executes the form generation method of any of the above.

[0130] Optionally, in this embodiment, the computer-readable storage medium may be located in any computer terminal in a group of computer terminals in a computer network, or in any communication device in a group of communication devices.

[0131] Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for performing the following steps: upon receiving a form creation request, obtaining form definition information of the target form, wherein the target form is the form to be generated; parsing the form definition information to obtain the fields and linkage rules of each functional module in the target form; obtaining the rule engine of the target form according to the linkage rules, wherein the rule engine is used to identify the relationship between the fields in the target form; determining the target field in each field and adding an event listener to the target field to obtain the initial form, wherein the target field is the field in each field that will trigger the linkage rule corresponding to the linkage rule; adding the rule engine to the initial form to obtain the target form.

[0132] Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for performing the following steps: upon receiving a form creation request, parsing the form creation request to obtain the form type of the target form; sending a form information retrieval request to the backend of the form customization system; and retrieving the form definition information searched by the backend based on the form information retrieval request.

[0133] Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for performing the following steps: converting the form definition information to obtain the converted form definition information; and extracting fields and linkage rules from the converted form definition information.

[0134] Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for performing the following steps: parsing the linkage rules to obtain the linkage relationship between each field; obtaining the association relationship between each field based on the linkage relationship; and generating a rule engine based on the association relationship.

[0135] Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for performing the following steps: determining the field components, functional module components, and module linkage rules required for the target form based on the form definition information; pre-generating the form using a form designer based on the field components, functional module components, and module linkage rules to obtain a preview form; analyzing each field to obtain the target field that will trigger the linkage rule; and adding an event listener to the target field in the preview form to obtain the initial form.

[0136] Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for performing the following steps: displaying all fields in each functional module of the initial form; configuring linkage rules for the initial form according to the relationship between all fields identified by the rule engine to obtain an intermediate form; performing linkage simulation on the intermediate form to obtain the linkage result of the intermediate form; and obtaining the target form when the linkage result indicates that the linkage of each field in the intermediate form meets the linkage requirements.

[0137] Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for performing the following steps: upon receiving a form call request, invoking the field information and functional module information of the target form; parsing the field information and functional module information to obtain the parsing result; after rendering the parsing result onto the current page, parsing the linkage rules of the target form according to the functional module information, and loading the linkage rules into the current page; listening for field trigger events of the target form in real time on the current page; when a field trigger event is detected, obtaining the calculation method and interface call information in the target form; and loading the calculation method and interface call information into the listening trigger event of the target form.

[0138] Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for performing the following steps: after detecting a change in the trigger field of the target form, triggering the linkage rule of the target form to perform a calculation operation or interface call operation in the target form and obtain an execution result; updating the execution result to the target field, wherein the target field is the field pointed to by the linkage rule.

[0139] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0140] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0141] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0142] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0143] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0144] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0145] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A form generation method, characterized in that, include: Upon receiving a form creation request, obtain the form definition information of the target form, wherein the target form is the form to be generated; The form definition information is parsed to obtain the fields and linkage rules of each functional module in the target form; The rule engine of the target form is obtained according to the linkage rules, wherein the rule engine is used to identify the relationship between the fields in the target form; Identify the target field among the fields and add an event listener to the target field to obtain the initial form. The target field is the field among the fields that will trigger the linkage rule corresponding to the linkage rule. The rule engine is added to the initial form to obtain the target form.

2. The form generation method according to claim 1, characterized in that, Retrieve the form definition information of the target form, including: Upon receiving the form creation request, the form creation request is parsed to obtain the form type of the target form; Send a request to retrieve form information to the backend of the form customization system; The backend retrieves the form definition information obtained from the request based on the form information.

3. The form generation method according to claim 1, characterized in that, The form definition information is parsed to obtain the fields and linkage rules of each functional module in the target form, including: The form definition information is converted to obtain the converted form definition information. The fields and the linkage rules are extracted from the form definition information after format conversion.

4. The form generation method according to claim 1, characterized in that, The rule engine for obtaining the target form based on the aforementioned linkage rules includes: The linkage rules are parsed to obtain the linkage relationships between the fields. The association relationships between the fields are obtained based on the aforementioned linkage relationships; The rule engine is generated based on the aforementioned relationships.

5. The form generation method according to claim 1, characterized in that, Identify the target field among the aforementioned fields, and add an event listener to the target field to obtain the initial form, including: Based on the form definition information, determine the field components, functional module components, and module linkage rules required for the target form; The form is pre-generated using the form designer based on the field components, the functional module components, and the module linkage rules, resulting in a preview form. Analyze each of the fields to obtain the target fields that will trigger the linkage rules; Add the event listener to the target field in the preview form to obtain the initial form.

6. The form generation method according to claim 1, characterized in that, Adding the rule engine to the initial form yields the target form, including: Display all the fields in each of the functional modules in the initial form; Based on the relationships between all the fields identified by the rule engine, the linkage rules are configured for the initial form to obtain the intermediate form; The intermediate form is simulated in a linked manner to obtain the linked result of the intermediate form; When the linkage result indicates that the linkage of each field in the intermediate form meets the linkage requirements, the target form is obtained.

7. The form generation method according to any one of claims 1 to 6, characterized in that, Also includes: Upon receiving a form request, the field information and functional module information of the target form are retrieved; The field information and the functional module information are parsed to obtain the parsing result; After rendering the parsing result to the current page, the linkage rules of the target form are parsed according to the functional module information, and the linkage rules are loaded into the current page; Listen for field trigger events of the target form in real time on the current page; When the field trigger event is detected, the calculation method and interface call information in the target form are obtained; The calculation method and the interface call information are loaded into the listener trigger event of the target form.

8. The form generation method according to claim 7, characterized in that, Also includes: After detecting a change in the trigger field of the target form, the linkage rule of the target form is triggered to execute the calculation operation or interface call operation in the target form and obtain the execution result; The execution result is updated to the target field, where the target field is the field pointed to by the linkage rule.

9. A form generation device, characterized in that, include: The first acquisition unit is used to acquire the form definition information of the target form when a form creation request is received, wherein the target form is the form to be generated; The parsing unit is used to parse the form definition information to obtain the fields and linkage rules of each functional module in the target form; The second acquisition unit is used to obtain the rule engine of the target form according to the linkage rule, wherein the rule engine is used to identify the relationship between the fields in the target form; The determining unit is used to determine the target field among the fields and add an event listener to the target field to obtain an initial form, wherein the target field is the field among the fields that will trigger the linkage rule corresponding to the linkage rule; The third acquisition unit is used to add the rule engine to the initial form to obtain the target form.

10. A custom form system, characterized in that, The custom form system uses the form generation method described in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein the program performs the form generation method according to any one of claims 1 to 8.

12. A processor, characterized in that, The processor is used to run a program, wherein the program executes the form generation method according to any one of claims 1 to 8 when it runs.

13. A computer program product comprising computer instructions, characterized in that, When the computer instructions are executed by the processor, the form generation method according to any one of claims 1 to 8 is performed.

Images