Low-code form generation method, system and device based on visual configuration and dynamic logic

Abstract

A low-code form generation method based on visual configuration and dynamic logic, comprising the following steps: a form designer module performs design-time configuration, providing a software module with visual configuration functions; a form rendering engine module performs run-time parsing and rendering, parses and executes form configuration; and a form description protocol module performs connection between design and operation, forms a structured and standardized data format as a contract between the designer and the rendering engine.

Description

Technical Field

[0001] This invention relates to the field of computers, and more particularly to a low-code form generation method, system, and device based on visual configuration and dynamic logic. Background Technology

[0002] In existing software development and business system construction, forms are a core component for data collection and user interaction. Traditional form development methods mainly fall into two patterns:

[0003] Manual coding development method: Developers use front-end technologies such as HTML, CSS, and JavaScript, combined with back-end logic, to write every element, style, and interaction behavior of the form from scratch. While this development method is flexible, it has significant drawbacks:

[0004] Development efficiency is extremely low: Even simple forms require writing a lot of repetitive and tedious code, from layout to validation, which consumes a lot of manpower and time, and the entire development process (coding, debugging, testing) is lengthy.

[0005] High technical threshold: It requires developers to have comprehensive front-end and back-end technical skills, and business personnel cannot participate, resulting in high communication costs and inaccurate conversion of business requirements.

[0006] High maintenance and iteration costs: The form logic is deeply coupled with the business code. When business requirements change, developers need to modify the source code, retest and deploy, resulting in slow response speed, easy introduction of new errors, and the formation of "technical debt".

[0007] Poor consistency and standardization: Relying on the personal habits of developers, forms written by different people are difficult to unify in terms of style, interaction and validation rules, which affects user experience and system professionalism.

[0008] Early form builder or low-code platform development methods attempted to improve efficiency by providing graphical interfaces to generate forms. However, these existing methods still have many shortcomings:

[0009] Dynamic interaction implementation methods are complex: most methods can only generate static forms. For scenarios that require dynamic display / hiding of fields based on user input, linked dropdown options, real-time calculations, and other complex business logic, existing methods usually require developers to write a large amount of custom scripts or intrusive code, failing to truly achieve the original intention of "low code," and maintaining dynamic logic remains difficult.

[0010] The data collection process is rigid: its technical architecture usually only supports a simple process of "filling in once and submitting as a whole", which is difficult to adapt to complex business scenarios such as step-by-step filling, draft storage, and data backfilling and revision through configuration, thus limiting the scope of application of the method.

[0011] Tight coupling between front-end and back-end: Forms generated using this method are often strongly bound to specific back-end data models and interfaces. The high degree of coupling between the form description information and the runtime environment makes it difficult to reuse the generated form as an independent, standardized module in other systems, which is not conducive to integration under a microservice architecture.

[0012] Poor scalability: When a business requires the introduction of a special component that is not in the standard component library, the existing methods lack a unified and low-intrusion extension mechanism, forcing developers to return to the old path of manual coding and disrupting the uniformity of the development process. Summary of the Invention

[0013] One of the objectives of this invention is to provide a low-code form generation method, system, and device based on visual configuration and dynamic logic, which can achieve efficient, dynamic, flexible, easy-to-maintain, and easy-to-integrate form development.

[0014] One of the objectives of this invention is to provide a low-code form generation method, system, and device based on visual configuration and dynamic logic, which can provide a systematic low-code form development method and technology system.

[0015] One of the objectives of this invention is to provide a low-code form generation method, system, and device based on visual configuration and dynamic logic. It can provide a technical system that separates design-time configuration from runtime parsing. Through a declarative configuration scheme and a unified dynamic rule engine, it completely decouples the UI, logic, and data model of the form, and reconstructs the form development, delivery, and integration process.

[0016] One of the objectives of this invention is to provide a low-code form generation method, system, and device based on visual configuration and dynamic logic, which can significantly reduce the technical threshold and development cost.

[0017] One of the objectives of this invention is to provide a low-code form generation method, system, and device based on visual configuration and dynamic logic. Non-technical personnel, such as business personnel, can directly participate in form construction and quickly configure fully functional forms, freeing developers from repetitive coding work and shortening the entire form delivery cycle by more than 80%.

[0018] One of the objectives of this invention is to provide a low-code form generation method, system, and device based on visual configuration and dynamic logic, which can easily configure forms that support various business scenarios such as step-by-step wizards, draft saving, data backfilling, and batch editing, greatly improving the applicability and practicality of form solutions.

[0019] One of the objectives of this invention is to provide a low-code form generation method, system, and device based on visual configuration and dynamic logic. The generated form can be used as an independent, standardized module that can be easily integrated into any backend system via API, achieving high reusability and integrability, perfectly matching modern microservices and platform architecture.

[0020] One of the objectives of this invention is to provide a low-code form generation method, system, and device based on visual configuration and dynamic logic, which transforms the UI, layout, and static attributes of a form into a structured configuration data (such as JSON) through visual operations, realizing a paradigm shift from "coding" to "configuration".

[0021] One of the objectives of this invention is to provide a low-code form generation method, system, and device based on visual configuration and dynamic logic, which supports configuring complex business logic rules through a graphical interface and has them parsed and executed by a unified runtime engine, thereby realizing the dynamic behavior of form elements.

[0022] One of the objectives of this invention is to provide a low-code form generation method, system, and device based on visual configuration and dynamic logic, enabling forms to independently manage their complete filling status and lifecycle, thereby natively supporting various complex data collection processes such as step-by-step, draft, and backfilling.

[0023] One of the objectives of this invention is to provide a low-code form generation method, system, and device based on visual configuration and dynamic logic. It specifies a set of form description standards and provides a corresponding renderer, enabling forms to be managed, distributed, and integrated across systems as standard data assets.

[0024] One of the objectives of this invention is to provide a low-code form generation method, system, and device based on visual configuration and dynamic logic. Through a systematic, non-coding configuration method, enterprise-level forms that can handle complex business logic and are easy to integrate can be developed efficiently, thus reshaping the form development paradigm.

[0025] The low-code form generation method, system, and device based on visual configuration and dynamic logic described in this invention have the following advantages compared with the prior art:

[0026] In contrast to existing methods based on traditional manual coding, which begin with code writing, rely on compilation, building, and deployment, have long cycles, and are difficult to modify, this invention begins with visual configuration and outputs immediately usable configuration data, greatly simplifying the process.

[0027] In contrast to existing methods based on hybrid form builders, which interrupt the process when encountering dynamic logic and require switching to script writing mode, thus disrupting the flow's continuity and low-code characteristics, this invention maintains the integrity and consistency of the process through declarative rule configuration.

[0028] In contrast to existing methods based on tightly coupled form platforms, which produce forms bound to specific platform runtime environments and unable to be integrated independently, this invention, through standardized protocols and an independent rendering engine, enables forms to become freely distributable "digital assets."

[0029] To achieve at least one objective of this invention, the present invention provides a low-code form generation method based on visual configuration and dynamic logic, the low-code form generation method based on visual configuration and dynamic logic comprising the following steps:

[0030] The form designer module performs design-time configuration and provides a software module with visual configuration capabilities.

[0031] The form rendering engine module performs runtime parsing and rendering, parsing and executing form configurations; and

[0032] The form description protocol module executes the connection between design and operation, forming a structured and standardized data format, which serves as a contract between the designer and the rendering engine;

[0033] The low-code form generation method based on visual configuration and dynamic logic further includes the following steps:

[0034] Visual design and DSL construction steps: In the designer module, in response to the operations of dragging and dropping components to the canvas and configuring component properties in the property panel, the form is constructed, and the series of operations on the interactive end are converted into structured data objects that are internally maintained and conform to the form description protocol in real time.

[0035] The configuration and execution steps of declarative dynamic rules are as follows: The form designer module executes the rule configuration function; it obtains the rules defined by the user through the graphical interface on the interactive end. Each rule contains a trigger condition and an execution action. The logical expression based on the form data state serves as the trigger condition, and the modification of the UI state or data state serves as the execution action.

[0036] In some embodiments, the low-code form generation method based on visual configuration and dynamic logic further includes the following steps: the rules in the configuration and execution steps of the declarative dynamic rules are serialized and stored in the overall form configuration as part of the configuration; at runtime, the rendering engine listens for data changes, parses and executes these rules.

[0037] In some embodiments, the low-code form generation method based on visual configuration and dynamic logic further includes the step of: unified scheduling and isolation of the rendering engine UI, data, and process execution.

[0038] In some embodiments, the low-code form generation method based on visual configuration and dynamic logic further includes the step of: performing standardized delivery and integration system construction.

[0039] In some embodiments, the low-code form generation method based on visual configuration and dynamic logic further includes the step of: during runtime, the rendering engine internally maintains the UI, data, and process in three mutually independent and isolated core states.

[0040] In some embodiments, the domain-specific language constructed to describe the form is implemented to create a JSON Schema, and the form designer module serializes graphical operations into a configuration file conforming to that Schema.

[0041] According to another aspect of the present invention, the present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the steps of the low-code form generation method based on visual configuration and dynamic logic.

[0042] According to another aspect of the present invention, the present invention also provides a low-code form generation device based on visual configuration and dynamic logic, comprising:

[0043] Memory, used to store software applications.

[0044] A processor is used to execute the software application, wherein each program of the software application correspondingly executes each step of the low-code form generation method based on visual configuration and dynamic logic.

[0045] According to another aspect of the present invention, the present invention also provides a low-code form generation system based on visual configuration and dynamic logic, which applies the aforementioned low-code form generation method based on visual configuration and dynamic logic. The low-code form generation system based on visual configuration and dynamic logic includes a form designer unit, a form rendering engine unit, and a form description protocol unit. The form designer unit performs design-time configuration and provides a software module with visual configuration functionality. The form rendering engine unit performs runtime parsing and rendering, parsing and executing form configurations. The form description protocol unit performs the connection between design and runtime, forming a structured and standardized data format as a contract between the designer and the rendering engine.

[0046] In some embodiments, the low-code form generation system based on visual configuration and dynamic logic is equipped with a unified scheduling and isolation unit for the rendering engine, which is configured to execute: When the rendering engine is running, it internally maintains the UI, data, and process in three independent and isolated core states. The UI state is a visual state that controls the display, hiding, and disabling of each component; the data state stores the current values ​​of all fields in the form; and the process state stores the process information of the current step and whether it has been saved as a draft. Attached Figure Description

[0047] Figure 1 This is an example configuration diagram of a low-code form generation method based on visual configuration and dynamic logic according to an embodiment of the present invention.

[0048] Figure 2 This is an example rule configuration diagram of the low-code form generation method based on visual configuration and dynamic logic according to the above embodiments of the present invention. Detailed Implementation

[0049] The following description is intended to disclose the present invention and enable those skilled in the art to implement it. The preferred embodiments described below are merely examples, and other obvious variations will occur to those skilled in the art. The basic principles of the invention defined in the following description can be applied to other embodiments, modifications, improvements, equivalents, and other technical solutions that do not depart from the spirit and scope of the invention.

[0050] It is understood that the term "a" should be understood as "at least one" or "one or more", that is, in one embodiment, the number of an element can be one, while in another embodiment, the number of the element can be multiple, and the term "a" should not be understood as a limitation on the number.

[0051] This invention relates to computer programs. For example... Figure 1The diagram shows a flowchart of a low-code form generation method based on visual configuration and dynamic logic according to the present invention. It illustrates a solution to the problems proposed in this invention, based on computer program processing flow, whereby a computer executes a computer program compiled according to the above flow to control or process external or internal objects of the computer. This low-code form generation method based on visual configuration and dynamic logic of the present invention can utilize computer systems to provide a systematic low-code form development method and technical system; it can provide a technical system that separates design-time configuration from runtime parsing, and through a declarative configuration scheme and a unified dynamic rule engine, it completely decouples the UI, logic, and data model of the form, reconstructing the form development, delivery, and integration process; it can significantly reduce the technical threshold and development cost; even non-technical personnel such as business personnel can directly participate in form construction, quickly configuring fully functional forms, freeing developers from repetitive coding work, and shortening the entire form delivery cycle by more than 80%; it can easily configure forms supporting various business scenarios such as step-by-step wizards, draft saving, data backfilling, and batch editing, greatly improving the applicability and practicality of the form solution. Usability: The generated form can be easily integrated into any backend system via API as an independent, standardized module, achieving high reusability and integrability, perfectly matching modern microservices and middle-platform architecture; the form's UI, layout, and static attributes are transformed into structured configuration data (such as JSON) through visual operations, realizing a paradigm shift from "coding" to "configuration"; it supports configuring complex business logic rules through a graphical interface, and is parsed and executed by a unified runtime engine, realizing dynamic behavior of form elements; it enables forms to independently manage their complete filling status and lifecycle, thus natively supporting various complex data collection processes such as step-by-step, draft, and backfill; it defines a set of form description specifications and provides a matching renderer, enabling forms to be managed, distributed, and integrated across systems as standard data assets. This invention integrates the advantages of existing solutions, enabling the efficient development of enterprise-level forms that can handle complex business logic and are easy to integrate through a systematic, non-coding configuration method, reshaping the form development paradigm. It is understood that the term "computer" in this invention refers not only to desktop computers, laptops, tablets, and other devices, but also to other intelligent electronic devices that can run programs and process data.

[0052] like Figure 1 As shown, the low-code form generation method based on visual configuration and dynamic logic includes the following steps:

[0053] S110: The Form Designer module performs design-time configuration and provides a software module with visual configuration capabilities;

[0054] S120: The form rendering engine module performs runtime parsing and rendering, parsing and executing form configurations;

[0055] S130: The Form Description Protocol module executes the connection between design and operation, forming a structured, standardized data format as a contract between the designer and the rendering engine.

[0056] The low-code form generation method based on visual configuration and dynamic logic also includes the following visual design and DSL construction steps:

[0057] In the designer module, in response to the user's actions of dragging and dropping components onto the canvas and configuring component properties (such as labels, validation rules, etc.) in the property panel, the form is constructed. Thus, the series of operations on the user's end are converted in real time into internally maintained structured data objects that conform to the form description protocol.

[0058] More specifically, in a particular embodiment, the visual design and DSL construction step involves building a domain-specific language to describe the form, for example, implemented as creating a JSON Schema, and the form designer module serializing graphical operations into a configuration file conforming to that Schema. Figure 1 The example configuration shown is a specific implementation of the method output.

[0059] In other specific embodiments, the form description protocol in the form description protocol module can be JSON, XML, YAML, or any other structured data format. The visual designer built in the visual design and DSL construction steps can be a web application, a desktop application, or a plugin integrated into an IDE. The component library can be implemented based on any front-end framework (such as Vue, React, Angular) or native technologies.

[0060] It is worth mentioning that, through the visual design and DSL construction steps described in this invention, low-code form construction based on a visual designer and a domain-specific language (DSL) can be provided, transforming the UI, layout, and static attributes of the form into a structured configuration data (such as JSON) through visual operations, thus realizing a paradigm shift from "coding" to "configuration".

[0061] The low-code form generation method based on visual configuration and dynamic logic also includes the following declarative dynamic rule configuration and execution steps:

[0062] The form designer module performs rule configuration functions; it obtains the rules defined by the user through the graphical interface on the interactive end. Each rule contains a trigger condition (a logical expression based on the form data state) and an execution action (modification of the UI state or data state).

[0063] More specifically, the low-code form generation method based on visual configuration and dynamic logic further includes the following steps: the rules in the configuration and execution steps of the declarative dynamic rules are serialized and stored in the overall form configuration as part of the configuration; at runtime, the rendering engine listens for data changes, parses and executes these rules. Figure 2 The example rule configuration shown is a method output in a specific implementation.

[0064] In other specific embodiments, the conditional expression is based on JavaScript or a custom simplified expression language or logic tree. In other specific embodiments, the action type is extensible, including but not limited to "setting a value," "requesting an interface," "triggering validation," and "executing a function." In other specific embodiments, the rule engine's execution strategy is implemented "when the value changes," or "during form initialization" or "before submission."

[0065] It is worth mentioning that, through the configuration and execution steps of the declarative dynamic rules described in this invention, a method for implementing a dynamic rule engine based on declarative configuration is provided. This method enables the configuration of complex business logic rules through a graphical interface, which are then parsed and executed by a unified runtime engine, thereby realizing the dynamic behavior of form elements and replacing the traditional method of writing script code for form logic.

[0066] The low-code form generation method based on visual configuration and dynamic logic also includes the following unified scheduling of the rendering engine and isolation of UI, data, and process steps: During runtime, the rendering engine internally maintains three independent core states: UI, data, and process. The UI state controls the display, hiding, and disabling of various components; the data state stores the current values ​​of all form fields; and the process state stores process information such as the current step and whether it has been saved as a draft. These three states are uniformly scheduled by the rendering engine but isolated from each other. In this unified scheduling and isolation of UI, data, and process steps, dynamic rules change the UI state based on changes in the data state; form submission or save operations only concern themselves with the current data state; and the process controller manages the process state and determines which part of the form fields to render. This architecture is the foundation for implementing complex processes.

[0067] In other specific embodiments, process control can not only implement step-by-step guidance, but also achieve more complex approval process integration by interfacing with external workflow engines.

[0068] It is worth mentioning that, through the unified scheduling and isolation of UI, data, and process steps by the rendering engine described in this invention, a form runtime architecture that separates UI state, data model, and process control is constructed. This architecture enables forms to independently manage their complete filling state and lifecycle, thereby natively supporting various complex data collection processes such as step-by-step, draft, and backfilling.

[0069] The low-code form generation method based on visual configuration and dynamic logic also includes the following standardized delivery and integration system construction steps: generating a configuration file that conforms to a predefined form description protocol; and publishing this file to a storage service. Any client application that integrates the corresponding form rendering engine can fully render and run the form simply by obtaining this configuration file through the form ID.

[0070] More specifically, the rendering engine acts as a pure logic interpreter, receiving configurations and outputting interactive form instances; it communicates with backend services through a standard HTTP client to submit data or obtain remote options, but it is itself unrelated to any specific business backend.

[0071] In other specific embodiments, the rendering engine is implemented as a web component, mini-program component, or native mobile component to achieve cross-platform support. Configuration file storage and distribution are implemented using various databases, configuration centers, or API gateways.

[0072] It is worth mentioning that, through the standardized delivery and integration system construction steps described in this invention, a form delivery and integration system based on a standardized form configuration protocol and an independent rendering engine is provided. This system specifies a set of form description specifications and provides a matching renderer, enabling forms to be managed, distributed, and integrated across systems as standard data assets.

[0073] Those skilled in the art will understand that embodiments of the present invention can be provided in the form of methods, systems, or computer program products. Therefore, the present invention can take the form of an all-hardware embodiment, an all-software embodiment, or an embodiment combining software and hardware.

[0074] This invention can be embedded in a computer program product, comprising all the features that enable the implementation of the low-code form generation method based on visual configuration and dynamic logic described herein. The computer program product is contained in one or more computer-readable storage media having computer-readable program code contained therein. According to another aspect of the invention, a computer-readable storage medium is also provided, on which a computer program is stored, which, when executed by a processor, is capable of performing the steps of the method of the invention. A computer storage medium is a medium in a computer memory used to store some discontinuous physical quantity. Computer storage media include, but are not limited to, semiconductors, disk drives, magnetic cores, magnetic drums, magnetic tapes, laser disks, etc. Those skilled in the art will understand that computer storage media are not limited to the foregoing examples, which are merely illustrative and not limited to the present invention.

[0075] According to another aspect of the present invention, a low-code form generation device based on visual configuration and dynamic logic is also provided. This device includes: a software application, a memory for storing the software application, and a processor for executing the software application. Each program within the software application is capable of correspondingly executing the steps in the low-code form generation method based on visual configuration and dynamic logic of the present invention.

[0076] A typical combination of hardware and software can be a general-purpose computer system with computer programs. When the programs are loaded and executed, they control the computer system so that the low-code form generation method based on visual configuration and dynamic logic disclosed in this invention can be performed.

[0077] Those skilled in the art will understand that the device can be embodied in a desktop computer, laptop, mobile smart device, etc., but the foregoing is merely an example, and also includes other intelligent analysis devices equipped with the software application of the present invention.

[0078] Those skilled in the art will understand that the low-code form generation method based on visual configuration and dynamic logic of the present invention can be implemented by hardware, software, or a combination of both. The present invention can be implemented centrally in at least one computer system, or distributed in a decentralized manner by different parts distributed across several interconnected computer systems. Any computer system or other device capable of implementing the method is applicable. A common combination of hardware and software can be a general-purpose computer system with computer programs installed, controlling the computer system to operate according to the low-code form generation method based on visual configuration and dynamic logic by installing and executing the programs.

[0079] Corresponding to the embodiments of the method of the present invention, according to another aspect of the present invention, a low-code form generation system based on visual configuration and dynamic logic is also provided. This low-code form generation system based on visual configuration and dynamic logic is an application of the low-code form generation method based on visual configuration and dynamic logic of the present invention in computer program improvement. The low-code form generation system based on visual configuration and dynamic logic can provide a systematic low-code form development method and technical system; it can provide a technical system that separates design-time configuration from runtime parsing, and through a declarative configuration scheme and a unified dynamic rule engine, it completely decouples the UI, logic, and data model of the form, reconstructing the form development, delivery, and integration process; it can significantly reduce the technical threshold and development cost; non-technical personnel such as business personnel can also directly participate in form construction, quickly configuring fully functional forms, freeing developers from repetitive coding work, and shortening the entire form delivery cycle by more than 80%; it can easily configure forms that support various business scenarios such as step-by-step wizards, draft saving, data backfilling, and batch editing, greatly improving the applicability and practicality of the form solution; the generated form can be used as an independent, standardized module, easily integrated into any [system / app / system] via API. The backend system achieves high reusability and integrability, perfectly aligning with modern microservices and middle-platform architectures. It transforms the UI, layout, and static attributes of forms into structured configuration data (such as JSON) through visual operations, realizing a paradigm shift from "coding" to "configuration." It supports configuring complex business logic rules through a graphical interface, with unified runtime engine parsing and executing them, enabling dynamic behavior of form elements. Forms can independently manage their complete filling status and lifecycle, natively supporting various complex data collection processes such as step-by-step, draft, and backfilling. It defines a set of form description specifications and provides a corresponding renderer, enabling forms to be managed, distributed, and integrated across systems as standard data assets. Through a systematic, non-coding configuration method, it efficiently develops enterprise-level forms that can handle complex business logic and are easy to integrate, reshaping the form development paradigm.

[0080] Specifically, the low-code form generation system based on visual configuration and dynamic logic includes a form designer unit, a form rendering engine unit, and a form description protocol unit. The form designer unit performs design-time configuration and provides a software module with visual configuration functionality. The form rendering engine unit performs runtime parsing and rendering, parsing and executing form configurations. The form description protocol unit connects design and runtime to form a structured and standardized data format, serving as a contract between the designer and the rendering engine.

[0081] The low-code form generation system based on visual configuration and dynamic logic also includes a visual design and DSL construction unit, configured to perform the following actions in the designer module: responding to dragging components to the canvas and configuring component properties (e.g., labels, validation rules) in the property panel from the interactive end, form construction is completed. Thus, the series of operations from the interactive end are converted in real-time into internally maintained structured data objects conforming to the form description protocol. In a specific embodiment, the domain-specific language used to describe the form, constructed by the visual design and DSL construction unit, is implemented as creating a JSON Schema. The form designer unit serializes the graphical operations into a configuration file conforming to this Schema.

[0082] It is understood that, in other variations, the form description protocol in the form description protocol unit can be implemented as JSON, XML, YAML, or any other structured data format. The visual designer built in the visual design and DSL building unit can be a web application, a desktop application, or a plugin integrated into an IDE. The component library can be implemented based on any front-end framework (such as Vue, React, Angular) or native technologies.

[0083] The visual design and DSL construction unit described in this invention provides low-code form construction based on a visual designer and a domain-specific language (DSL). It transforms the UI, layout, and static attributes of the form into a structured configuration data (such as JSON) through visual operations, realizing a paradigm shift from "coding" to "configuration".

[0084] The low-code form generation system based on visual configuration and dynamic logic is also equipped with a declarative dynamic rule configuration and execution unit, which is configured to execute: call the form designer unit to execute the rule configuration function; obtain the rules defined by the user on the interactive end through the graphical interface, wherein each rule includes a trigger condition (a logical expression based on the form data state) and an execution action (modification of the UI state or data state).

[0085] The rules in the configuration and execution unit of the declarative dynamic rules are serialized and stored in the overall form configuration as part of the configuration. At runtime, the rendering engine listens for data changes, parses and executes these rules. In other variations, the conditional expressions are based on JavaScript or a custom simplified expression language or logic tree. In other specific embodiments, the action types are extensible, including but not limited to "setting value," "requesting interface," "triggering validation," and "executing function." In other specific embodiments, the rule engine's execution strategy is implemented "when the value changes," or "when the form is initialized" or "before submission." The configuration and execution unit of the declarative dynamic rules provides a method for implementing a dynamic rule engine based on declarative configuration. It enables the configuration of complex business logic rules through a graphical interface, which are then parsed and executed by a unified runtime engine, realizing the dynamic behavior of form elements and replacing the traditional method of writing script code for form logic.

[0086] The low-code form generation system based on visual configuration and dynamic logic also includes a unified scheduling and isolation unit for the rendering engine, used to uniformly schedule and isolate the UI, data, and process. This unified scheduling and isolation unit is configured to execute the following: During runtime, the rendering engine internally maintains three independent core states: UI, data, and process. The UI state controls the display, hiding, and disabling of various components; the data state stores the current values ​​of all form fields; and the process state stores process information such as the current step and whether it has been saved as a draft. These three states are uniformly scheduled by the rendering engine but isolated from each other. Within the unified scheduling and isolation unit, dynamic rules change the UI state based on changes in the data state; form submission or saving operations only consider the current data state; and the process controller manages the process state and determines which part of the form fields to render. In other adaptable embodiments, process control can not only implement step-by-step wizards but also integrate more complex approval processes by interfacing with external workflow engines. The unified scheduling and isolation unit constructs a form runtime architecture that separates UI state, data model, and process control. This architecture enables forms to independently manage their complete filling status and lifecycle, thus natively supporting various complex data collection processes such as step-by-step, draft, and backfill.

[0087] The low-code form generation system based on visual configuration and dynamic logic also includes a standardized delivery and integration system building unit, configured to: generate a configuration file conforming to a predefined form description protocol; and publish the file to a storage service. Any client application integrating the corresponding form rendering engine can fully render and run the form simply by obtaining this configuration file through the form ID. The rendering engine, acting as a pure logic interpreter, receives configuration, outputs interactive form instances, and communicates with the backend service through a standard HTTP client to submit data or obtain remote options, but it is independent of any specific business backend. In other adaptable embodiments, the rendering engine is implemented as a web component, mini-program component, or mobile native component to achieve cross-platform support. The storage and distribution of the configuration file are implemented using various databases, configuration centers, or API gateways. Through the standardized delivery and integration system building unit, a form delivery and integration system based on a standardized form configuration protocol and an independent rendering engine is provided. This system defines a set of form description specifications and provides a matching renderer, enabling forms to be managed, distributed, and integrated across systems as standard data assets.

[0088] Those skilled in the art will understand that the invention has been described with reference to flowchart illustrations and / or block diagrams of methods, systems, and computer program products according to the invention. Each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can obviously be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing apparatus to produce a machine, thereby instructing (the instructions via the processor of the computer or other programmable data processing apparatus) to generate means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or block diagrams.

[0089] Those skilled in the art should understand that the embodiments of the present invention described above and shown in the accompanying drawings are merely examples and do not limit the present invention. The objectives of the present invention have been fully and effectively achieved. The functional and structural principles of the present invention have been demonstrated and explained in the embodiments, and any modifications or variations of the embodiments of the present invention may be made without departing from these principles.

Claims

1. A low-code form generation method based on visual configuration and dynamic logic, characterized in that, The low-code form generation method based on visual configuration and dynamic logic includes the following steps: The form designer module performs design-time configuration and provides a software module with visual configuration capabilities. The form rendering engine module performs runtime parsing and rendering, parsing and executing form configurations; and The form description protocol module executes the connection between design and operation, forming a structured and standardized data format, which serves as a contract between the designer and the rendering engine; The low-code form generation method based on visual configuration and dynamic logic further includes the following steps: Visual design and DSL construction steps: In the designer module, in response to the operations of dragging and dropping components to the canvas and configuring component properties in the property panel, the form is constructed, and the series of operations on the interactive end are converted into structured data objects that are internally maintained and conform to the form description protocol in real time. The configuration and execution steps of declarative dynamic rules are as follows: The form designer module executes the rule configuration function; it obtains the rules defined by the user through the graphical interface on the interactive end. Each rule contains a trigger condition and an execution action. The logical expression based on the form data state serves as the trigger condition, and the modification of the UI state or data state serves as the execution action.

2. The low-code form generation method based on visual configuration and dynamic logic as described in claim 1, wherein the low-code form generation method based on visual configuration and dynamic logic further includes the steps of: the rules in the configuration and execution steps of the declarative dynamic rules are serialized and stored in the overall form configuration as part of the configuration; during runtime, the rendering engine listens for data changes, parses and executes these rules.

3. The low-code form generation method based on visual configuration and dynamic logic as described in claim 1, wherein the low-code form generation method based on visual configuration and dynamic logic further includes the step of: unified scheduling and isolation of the rendering engine UI, data, and process execution.

4. The low-code form generation method based on visual configuration and dynamic logic as described in claim 1, wherein the low-code form generation method based on visual configuration and dynamic logic further includes the step of: performing standardized delivery and integration system construction.

5. The low-code form generation method based on visual configuration and dynamic logic as described in claim 4, wherein the low-code form generation method based on visual configuration and dynamic logic further includes the step of: when the rendering engine is running, it internally maintains the UI, data, and process in three mutually independent and isolated core states.

6. The low-code form generation method based on visual configuration and dynamic logic as described in any one of claims 1 to 5, wherein the domain-specific language constructed to describe the form is implemented to create a JSON Schema, and the form designer module serializes graphical operations into a configuration file conforming to the Schema.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it performs the steps of the low-code form generation method based on visual configuration and dynamic logic as described in any one of claims 1 to 6.

8. A low-code form generation device based on visual configuration and dynamic logic, characterized in that, include: Memory, used to store software applications. A processor for executing the software application, wherein each program of the software application correspondingly performs a step of the low-code form generation method based on visual configuration and dynamic logic as described in any one of claims 1 to 6.

9. A low-code form generation system based on visual configuration and dynamic logic, employing the low-code form generation method based on visual configuration and dynamic logic as described in any one of claims 1 to 6, characterized in that, The low-code form generation system based on visual configuration and dynamic logic includes a form designer unit, a form rendering engine unit, and a form description protocol unit. The form designer unit performs design-time configuration and provides a software module with visual configuration functions. The form rendering engine unit performs runtime parsing and rendering, parsing and executing form configurations. The form description protocol unit connects design and runtime, forming a structured and standardized data format as a contract between the designer and the rendering engine.

10. The low-code form generation system based on visual configuration and dynamic logic as described in claim 9, wherein, The low-code form generation system based on visual configuration and dynamic logic is equipped with a unified scheduling and isolation unit for the rendering engine, which is configured to execute: When the rendering engine is running, it internally maintains the UI, data, and process in three independent and isolated core states. The UI state is the visual state that controls the display, hiding, and disabling of each component; the data state stores the current values ​​of all fields in the form; and the process state stores the process information of the current step and whether it has been saved as a draft.

Images