Implementation method, device and equipment of low-code platform, medium and product

Abstract

According to the low-code platform implementation method and device, the equipment, the medium and the product provided by the invention, the first component information of the first component and the second component information of the second component are determined in response to the component selection operation of the user; obtaining parameter editing information of the user on the first component and formula editing information of the second component; according to the first component information of the first component, performing verification analysis on the parameter editing information of the first component to obtain a verification result; obtaining a to-be-verified formula according to the verification result and the formula editing information of the second component; determining a target formula according to the second component information of the second component and the to-be-verified formula; and the target formula is deployed into the formula library of the low-code platform to obtain the target low-code platform, so that the flexibility of autonomously configuring components and formulas by a user is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computers, and in particular to a low-code platform implementation method, device, equipment, medium and product. BACKGROUND

[0002] Low-code platforms are widely used in enterprise digital transformation processes. They replace traditional handwritten code with visual drag-and-drop components and configuration operations, significantly reducing the application development threshold, allowing business personnel to participate in system building, and improving development efficiency. They are particularly suitable for fast iteration business scenarios and have become an important technical solution for enterprises to respond to high-frequency demand changes and optimize resource allocation.

[0003] Existing low-code platforms can achieve simple linkage, embed Excel formula calculation capabilities, or implement logic functions by developers writing code to achieve component linkage.

[0004] However, the formula types of the above platforms are fixed and rely on developers to write code to achieve component linkage, which cannot meet complex business needs and reduces the development efficiency and applicability of low-code platforms. SUMMARY

[0005] The present application provides a low-code platform implementation method, device, equipment, medium and product to solve the technical problems of low development efficiency and narrow application range of existing low-code platforms.

[0006] In a first aspect, the present application provides a low-code platform implementation method, comprising:

[0007] In response to a component selection operation of a user, determining first component information of a first component and second component information of a second component, the first component information comprising selectable parameter information, and the second component information comprising selectable formula information;

[0008] Obtaining parameter editing information of the first component and formula editing information of the second component of the user;

[0009] According to the first component information of the first component, the parameter editing information of the first component is verified and analyzed to obtain a verification result;

[0010] According to the verification result and the formula editing information of the second component, a to-be-verified formula is obtained;

[0011] According to the second component information of the second component and the to-be-verified formula, a target formula is determined;

[0012] The target formula is deployed to a formula library of the low-code platform to obtain a target low-code platform.

[0013] Furthermore, the method also includes:

[0014] In response to the user's custom formula editing operation, determine the custom formula information;

[0015] Based on the custom formula information, the custom formula is obtained;

[0016] The custom formula is updated to the formula library of the low-code platform, which provides formula selection for users.

[0017] Further, based on the custom formula information, a custom formula is obtained, including:

[0018] Based on the custom formula information, generate custom template code, optional formulas, and optional parameters;

[0019] The custom template code, the optional formula, and the optional parameters are displayed to the user. The custom template code includes the formula name, input parameters, output parameters, and code comments.

[0020] In response to the user's editing and selection operations on the custom template code, the optional formula, and the optional parameters, a custom formula is obtained;

[0021] Furthermore, based on the first component information of the first component, the parameter editing information of the first component is verified and analyzed to obtain the verification results, including:

[0022] Based on the first component information of the first component, determine the optional parameter information;

[0023] Based on the optional parameter information, the parameter editing information of the first component is verified and analyzed to obtain the verification result.

[0024] Further, based on the verification result and the formula editing information of the second component, the formula to be verified is obtained, including:

[0025] Based on the verification results, determine the matching result between the parameter editing information and the optional parameter information;

[0026] If the matching result indicates that the parameter editing information matches the optional parameter information, then the parameter editing information is compared with the preset parameter requirements to obtain the comparison result. The preset parameter requirements include parameter validity requirements and parameter type requirements.

[0027] If the comparison result indicates that the parameter editing information meets the preset parameter requirements, then the formula to be verified is obtained according to the formula editing information of the second component.

[0028] Further, based on the second component information of the second component and the formula to be verified, the target formula is obtained;

[0029] Based on the second component information of the second component, determine the optional formula information;

[0030] The optional formula information is matched with the formula to be verified to obtain the matching result;

[0031] If the matching result indicates that the formula to be verified matches the optional formula information, then a syntax tree verification analysis is performed on the formula to be verified to obtain the syntax tree analysis result.

[0032] If the syntax tree analysis result indicates that the formula to be verified meets the formula structure requirements, then the target formula is obtained. The formula structure requirements include parameter type requirements and nested logic requirements.

[0033] Further, after matching the optional formula information with the formula to be verified to obtain a matching result, the method further includes:

[0034] If the matching result indicates that the formula to be verified does not match the optional formula information, then based on the big data algorithm, formula correction information is generated;

[0035] The information regarding the formula to be corrected will be displayed to the user.

[0036] In response to the user's modification operation on the formula to be verified, a target formula is determined.

[0037] Furthermore, in response to the user's component selection action, the method further includes:

[0038] Obtain the component to be assigned a value by the user;

[0039] Based on the component to be assigned a value, determine the formula and parameters corresponding to the component to be assigned a value;

[0040] The formula is calculated based on the parameters to obtain the component value of the component to be assigned, and the component value is used to represent the configuration of the component to be assigned.

[0041] The component value of the component to be assigned is displayed to the user so that the user can select the corresponding component based on the component value.

[0042] Secondly, this application provides an implementation apparatus for a low-code platform, comprising:

[0043] The component information determination module is used to determine the first component information of the first component and the second component information of the second component in response to the user's component selection operation.

[0044] The editing information acquisition module is used to acquire the user's parameter editing information for the first component and the formula editing information for the second component;

[0045] The verification result acquisition module is used to perform verification analysis on the parameter editing information of the first component based on the first component information of the first component, and obtain the verification result;

[0046] The module for obtaining the formula to be verified is used to perform verification analysis on the parameter editing information of the first component based on the verification result and the formula editing information of the second component, so as to obtain the formula to be verified.

[0047] The target formula determination module is used to determine the target formula based on the second component information of the second component and the formula to be verified;

[0048] The low-code platform implementation module is used to deploy the target formula to the formula library of the low-code platform to obtain the target low-code platform.

[0049] Thirdly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0050] The memory stores computer-executed instructions;

[0051] The processor executes computer execution instructions stored in the memory to implement the method as described in any of the first aspects.

[0052] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method described in any of the first aspects.

[0053] Fifthly, this application provides a computer program product including a computer program that, when executed by a processor, implements the method described in any of the first aspects.

[0054] The low-code platform implementation method, apparatus, device, medium, and product provided in this application, in response to a user's component selection operation, determine the first component information of a first component and the second component information of a second component; obtain the user's parameter editing information for the first component and the formula editing information for the second component; perform verification analysis on the parameter editing information of the first component based on the first component information to obtain a verification result; obtain the formula to be verified based on the verification result and the formula editing information of the second component; determine the target formula based on the second component information of the second component and the formula to be verified; and deploy the target formula to the formula library of the low-code platform to obtain the target low-code platform, thereby improving the flexibility of users in configuring components and formulas independently. Attached Figure Description

[0055] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0056] Figure 1 A schematic diagram of the overall architecture of the low-code platform provided for this application;

[0057] Figure 2 A flowchart illustrating an embodiment of the low-code platform implementation method provided in this application;

[0058] Figure 3 A flowchart illustrating a second embodiment of the low-code platform implementation method provided in this application;

[0059] Figure 4 A flowchart illustrating Embodiment 3 of the implementation method for the low-code platform provided in this application;

[0060] Figure 5 A schematic diagram of the structure of the implementation device for the low-code platform provided in this application;

[0061] Figure 6 A schematic diagram of the structure of the electronic device provided in this application.

[0062] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0063] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0064] Currently, low-code platforms generally lack the ability to validate the types of parameters in formulas and analyze their syntax structure, which makes it easy for users to make type or structural errors during editing, leading to runtime failures. Secondly, formula validation in existing systems mostly relies on manual judgment and cannot achieve automated capabilities such as syntax tree analysis and automatic structure derivation, resulting in technical problems such as low configuration efficiency and inaccurate linkage of low-code platforms.

[0065] To address the aforementioned issues, this invention constructs a structured and intelligent processing flow. By structuring component information into "component information objects" and introducing parameter validation analysis, formula syntax tree verification, and structure matching mechanisms, dynamic legality analysis of user-input formulas is achieved. Simultaneously, it supports users in automatically completing and generating input parameters, formula structures, and comments through an editor, thereby improving formula construction efficiency and realizing full lifecycle management and intelligent linkage of formula logic. This significantly enhances the configuration capabilities and interactive performance of low-code platforms.

[0066] The technical solutions of this application and how they solve the aforementioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. It should be understood that unless a specific unit, module, or component is specifically indicated as the executing entity, the operation steps, processing flow, and system behavior in this invention are all executed by the entire system belonging to the low-code platform. The embodiments of this application will now be described with reference to the accompanying drawings.

[0067] Figure 1 A schematic diagram of the system architecture of the low-code platform provided in this application. Figure 1 As shown, the low-code platform 100 includes a component management unit 101, a formula engine unit 102, a big data algorithm unit 103, and a formula customization unit 104.

[0068] The component management unit 101 is a backend service used to manage which components make up the low-code form and their display order. When relationships between two or more components are configured, the component management unit 101 needs to record these relationships. For the current component, it records which components on the current page are used as calculation parameters and which formulas are used to calculate the value of the current component. In addition, the component management unit 101 also stores all the form's components. These components can be used to calculate the values ​​of other components, and when formula editing is triggered, these components are queried as parameters for formula editing. The component management unit 101 manages all formulas supported by the low-code platform 100, including their names, descriptions, categories, and the types and number of input and output parameters. It is because of these functions of the component management unit 101 that the form can be fully rendered when it is actually used.

[0069] Formula Engine Unit 102 ensures the correct execution of user-defined formulas. It parses the calculation parameters and logic of user-edited formulas and ensures correct calculation during use. The core capability of Formula Engine Unit 102 is syntax tree parsing. Syntax tree parsing treats the entire edited formula as the root node, the outermost method as the execution method of the node, and the parameters of this method (also composed of formulas) as subtrees of the root node. The number of subtrees corresponds to the number of parameters, until a form parameter (consisting of values ​​from other form components) is encountered, which becomes the actual node of the syntax tree. The syntax tree is generated by iteratively processing the user-input formula. In the final generated syntax tree, except for the leaf nodes which are form component parameters, each non-leaf node represents a formula. The logic for validating the user-input formula involves processing each non-leaf node of the syntax tree, checking if the input parameters of each node match the formula definition. Similarly, when the form is used, the values ​​of the corresponding configuration components are obtained by performing layer-by-layer calculations on the syntax tree from the bottom to the root node.

[0070] The big data algorithm unit 103 collects all the information of the components, the context of the components, and the user's usage information. When the user edits the formula, it provides a specific solution for formula repair based on the user's specific operation and the specific errors in the syntax tree analysis.

[0071] Formula customization unit 104 allows you to configure the input and output parameters of the formula, as well as the specific implementation Python script, Shell script, etc., and dynamically call the formula implementation to calculate the value during syntax tree parsing and component rendering.

[0072] Figure 2 This is a flowchart illustrating an embodiment of the low-code platform implementation method provided in this application. Figure 2 ,include:

[0073] S201. In response to the user's component selection operation, determine the first component information of the first component and the second component information of the second component.

[0074] In this application, the overall architecture of the low-code platform is divided into a front-end and a back-end server. The front-end provides users with an operable functional space, while the back-end server implements the storage and computation of logic. Furthermore, the low-code platform refers to a web-based or desktop development platform where users can create page components through drag-and-drop operations and set data sources and logical formulas for the components without writing traditional code. Simultaneously, the front-end interface provides users with various components, which are structured data definitions, including single-line input boxes, numeric input boxes, radio buttons, and formula editing boxes. The first and second components described in this step do not refer to a single component, but rather to components with a linked and subordinate relationship. The information of the first component includes optional parameter information, i.e., all parameters available to the first component, and the information of the second component includes optional formula information, i.e., all formulas available to the second component. Specifically, the information corresponding to all parameters includes data type, input / output parameters, and dependencies, with dependencies referring to the relationship between the first and second components. Additionally, based on the aforementioned first and second components, a list of commonly used formulas corresponding to these components can be determined.

[0075] Specifically, when a user drags and drops a component in the low-code platform, the component management unit 101 captures the component's creation event. The backend server then automatically generates a unique identifier for the component and queries the component metadata table in the database. The component information includes the component type (text input box, numeric input box, dropdown list, table, etc.), optional parameter information (the output values ​​and data types that the current component can expose), and optional formula information (the set of system formulas that can be matched with this type of component).

[0076] If a user specifies the relationship between two components in the front-end interface design, such as "a change in the input of component A triggers an update in component B," the back-end server will automatically register A as the "first component" and B as the "second component." At this point, the component management unit 101 writes a linkage record (A, B) into the component mapping table, forming a master-slave dependency chain and providing a structured foundation for formula binding. This step transforms the user's visual operations into a programmable data structure, making the component relationships machine-recognizable, thus providing context for formula editing.

[0077] S202. Obtain the user's parameter editing information for the first component and the formula editing information for the second component.

[0078] When a user opens the "Formula Configuration" panel in the front-end formula editor, the low-code platform 100 requests the component management unit 101 via API to obtain the parameter set of all components on the current page, the formula templates accessible to the current user, and a recommended list of frequently used formulas. Simultaneously, it uses a WebSocket channel to synchronize user input in real time. Whenever the user types a character, the front-end sends the edited content as an event stream to the formula engine unit 102.

[0079] Formula engine unit 102 uses a lexical analyzer to break down the input into "tokens" and searches for matching formulas in the local cache. When the token stream triggers a "(" or ",", the formula engine unit 102 immediately queries the list of acceptable parameter types. If the user-inputted component does not match, an error is displayed in red in the editor. Through these steps, real-time parameter recommendations and syntax warnings can be achieved, allowing users to correctly construct logic without understanding formula syntax.

[0080] S203. Based on the information of the first component, perform verification analysis on the parameter editing information of the first component to obtain the verification result.

[0081] Specifically, based on the information of the first component, the optional parameter information is determined. In this step, the component management unit 101 retrieves the parameter definitions bound to the first component from the backend component metadata table. Each parameter definition includes the parameter name, type, data source, range of optional values, whether it is a required field, and its business context information. For example, the optional parameter information of a numeric input box component may include type, maximum / minimum value, and whether it can be empty, while the parameter information of a user selection component includes type, field, and user name.

[0082] Based on the optional parameter information, the parameter editing information of the first component is validated and analyzed to obtain the validation result. Specifically, after determining the optional parameter information, the formula engine unit 102 will perform validation and analysis on the parameter editing information input by the user based on the optional parameter information.

[0083] The verification analysis is specifically divided into three layers: parameter layer verification, type layer verification, and semantic layer verification. Specifically, parameter layer verification first compares the parameter identifiers referenced by the user in the formula with the parameter set in the component definition to ensure that the referenced parameters exist and are valid. For example, when the user inputs ADD(input box 1, input box 2), the system will confirm whether "input box 1" and "input box 2" are registered components and verify whether they are within the dependency scope of the first component. If it is found that the user has mistakenly inputted an unregistered variable or component (such as "input box x"), a front-end error message will be immediately triggered, returning the error message "parameter does not exist". It should be noted that the above process uses a hash index fast matching algorithm. The component management unit 101 establishes a parameter hash table for each component during initialization. Through key-value pair mapping, the existence of parameters can be determined in O(1) time, significantly improving parameter verification efficiency.

[0084] For type-level validation, after the parameter names are confirmed, the formula engine unit 102 performs type matching analysis on each parameter. It reads the type identifier of each parameter through the leaf nodes of the syntax tree and compares it with the parameter type requirements in the formula definition. When a type conflict occurs, error context information is generated, including the error node, expected type, actual type, and suggested replacement. These steps can detect type mismatch issues in real time during the formula editing stage, prevent runtime errors, and provide users with automatic type repair suggestions.

[0085] Once the type validation passes, semantic-level validation will be performed. This stage primarily checks the legality of the parameters' business logic and their contextual dependencies. For example, if the first component represents "department selection," but the formula entered by the user references the "employee salary" parameter, then the business context is determined to be mismatched, and a logic conflict error is returned. If the parameter involves cross-module references (such as a component on page A referencing data on page B), its accessibility is verified through a dependency graph.

[0086] This step, through the aforementioned multi-level verification mechanism, solves the technical problems in existing low-code platforms such as the lack of component parameter validity verification, type mismatch leading to runtime errors, and cross-component logic inconsistency. It provides reliable input for subsequent formula verification, and the algorithm-level optimization improves the level of intelligence, significantly enhancing both the formula editing experience and execution reliability.

[0087] S204. Based on the verification results and the formula editing information of the second component, the formula to be verified is obtained.

[0088] Specifically, based on the verification results, the matching result between the parameter editing information and the optional parameter information is determined. That is, it further determines whether the parameters edited by the user actually exist within the set of parameters allowed in the current context of the component. This step is equivalent to establishing a mapping judgment between "user intent" and "system capability," and the verification result is a structured data object output by the formula engine unit 102, containing the verification status of each parameter. The "optional parameter information" of the first component returned by the component management unit 101 is used as the comparison basis; the core logic of the matching is to determine whether the "parameter editing information set" is a subset of the "optional parameter set."

[0089] For example, the system internally constructs two sets: Set A: all parameters used by the user in the formula; Set B: valid parameters exposed in the current context of the first component (maintained by the component management unit 101). An intersection / inclusion relationship judgment is performed on the sets to obtain the matching result. The judgment output is: if an invalid parameter exists (i.e., Set A contains members that do not belong to Set B), the matching fails, and an error branch is entered; otherwise, it is considered a "match successful".

[0090] If the matching result indicates that the parameter editing information matches the optional parameter information, the parameter editing information is compared with the preset parameter requirements to obtain the comparison result. The preset parameter requirements include parameter validity requirements and parameter type requirements. Parameter validity requirements, based on the correct parameter type, constrain the range, format, and logic of parameter values ​​to prevent invalid or erroneous data from entering the system. These requirements include format validation, range validation, length validation, and dependency validation. Parameter type requirements define the data form of the parameters and are the basic parameters for data flow and processing in the low-code platform, including requirements for basic data types and complex data types. In this step, the comparison process is initiated by the formula engine unit 102 calling its internal "formula definition library," which maintains a parameter constraint description table (Parameter Schema) for each system-supported formula. The comparison steps include generating a structured object {parameter name, type, current value} for each user-edited parameter; comparing it with the expected definition {type requirements, whether nullables are allowed, value range} in the Schema; if all fields match, the comparison passes; otherwise, an error message or correction mechanism is initiated.

[0091] If the comparison result indicates that the parameter editing information meets the preset parameter requirements, then the formula to be verified is obtained based on the formula editing information of the second component. This step can only proceed after the above two stages have been successful, allowing the assembly of these parameters and formula structures into the formula to be verified. For example, the formula engine unit 102 is called to construct an abstract syntax tree (AST): the function name is used as the root node; each parameter is used as a leaf node; if nested formulas exist, a subtree (nesting level) is constructed; and metadata such as "component reference context," "type signature," and "validation flag" are attached to the formula to be verified. It should be noted that the formula to be verified has not yet been executed; it is only an intermediate state after the structural and logical legality has been constructed, pending further advanced verification such as syntax rules, nested structures, and parameter connectivity.

[0092] This step avoids the hidden danger of "formulas that appear to be valid but fail to run" in low-code platforms, and truly ensures consistency in structure, semantics, and context.

[0093] S205. Based on the information of the second component and the formula to be verified, the target formula is obtained.

[0094] In this step, a series of in-depth validations of the structure, type, and logic of the formula to be verified, constructed in the previous step, are performed to confirm whether it meets the deployment conditions. If it does, the formula is identified as the "target formula," and can then be added to the system formula library, bound to components, and used in execution. The specific implementation steps are as follows:

[0095] Based on the information of the second component, the optional formula information is determined. Specifically, before analyzing the formula to be verified, it is necessary to determine the contextual constraints related to the second component, that is, the set of formulas allowed by the second component, which is called the optional formula information. Further, the component management unit 101 queries the component type of the second component, such as a numeric box, string label, table, date control, etc.; based on the component type, it accesses the formula binding rule table and returns a list of all formula functions supported by the component. Each formula also includes meta-attributes such as its output type, parameter type, and maximum number of parameters.

[0096] Then, the optional formula information is matched with the formula to be verified to obtain the matching result. Specifically, this step is used to verify whether the "formula to be verified" belongs to the formula type used by the second component and whether its parameters are consistent with the expected type. Further, the formula engine unit 102 extracts the function name and parameter structure from the formula to be verified; compares it with each formula definition in the optional formula information; the checks include whether the function name exists, whether the number of parameters is consistent, whether the parameter types are completely matched, whether the return value type is consistent with the type acceptable to the second component, and whether the parameter format is correct.

[0097] If the matching result shows that the formula to be verified matches the optional formula information, then the formula to be verified is subjected to syntax tree verification analysis to obtain the syntax tree analysis result. Specifically, if the formula matches successfully, it proves that the formula to be verified does not need to be modified, and only syntax tree structure verification is required. Therefore, the next step is to perform syntax structure verification to ensure that the formula logic will not have errors during execution. Further, the core algorithm step executed by the formula engine unit 101 is called syntax tree verification analysis. Its main functions are to convert the formula into a syntax tree structure and perform structural integrity checks; verify whether the input and output types of each node are compliant; verify whether the nested logic meets the formula definition specifications (such as not being able to nest formulas without return values); and ensure that the entire syntax tree can be executed correctly from bottom to top.

[0098] If the syntax tree analysis results indicate that the formula to be verified meets the formula structure requirements, then the target formula is obtained. The formula structure requirements include parameter type requirements and nested logic requirements. This step is the final step in determining whether the formula to be verified is valid. That is, after the syntax tree verification analysis passes, the system will determine that the formula fully complies with the platform specifications in terms of syntax, parameter types, and nested structure; and upgrade the "formula to be verified" to the "target formula"; finally, it will be included in the deployable object, ready to enter the formula library and bind to the second component.

[0099] In this step, there is another scenario: the formula to be verified does not match the optional formula information. In this case, intelligent path repair is required, and the specific steps are as follows:

[0100] If the matching result indicates that the formula to be verified does not match the available formula information, then based on a big data algorithm, information on formula correction is generated. Specifically, the system trains a recommendation model based on a large amount of user formula editing behavior. The goal is to intelligently infer the user's intent when they write an incorrect formula and recommend the most appropriate correction scheme. The model input includes all component types on the current page, the current formula input content (including the error location), the formulas most frequently used by historical users in this scenario, and the error types (incorrect type, incorrect structure, incorrect format). The model output includes a list of recommended formulas (sorted in descending order of similarity), suggested replacement parameters, error descriptions, and correction prompts.

[0101] Then, the formula correction information is displayed to the user. That is, through the formula editor front end, correction suggestions are fed back to the user in the form of prompts, warnings or candidate formula drop-down lists.

[0102] Finally, in response to user modifications to the formula to be validated, once the user adopts the modification suggestions, re-edits the formula to meet the matching and structural requirements, the system re-executes the syntax tree validation process. If successful, the target formula is generated.

[0103] This step combines big data recommendation systems to achieve intelligent formula repair; it also accurately defines the target state of the formula, clarifies deployment boundaries, and ensures the operational security of the low-code platform.

[0104] S206. Deploy the target formula to the formula library of the low-code platform to obtain the target low-code platform.

[0105] In this step, the verified target formula is written into the formula library of the low-code platform and bound to the corresponding component to realize the automatic driving and linkage update of the formula logic.

[0106] The low-code platform implementation method in this application, by introducing mechanisms such as parameter validation, syntax tree parsing, component dependency matching, and big data intelligent recommendation, achieves full-process automation and intelligence from component selection and parameter editing to formula generation and deployment. This not only significantly reduces the threshold for user configuration logic but also effectively avoids type conflicts, syntax errors, and runtime failures during formula configuration, ensuring that formulas can be accurately bound to target components and drive interaction in real time. This significantly improves the configuration efficiency, stability, and maintainability of the low-code platform.

[0107] Figure 3 This is a flowchart illustrating a second embodiment of the low-code platform implementation method provided in this application. Figure 3 ,include:

[0108] S301. In response to the user's custom formula editing operation, determine the custom formula information.

[0109] When a user creates a new formula logic in the low-code platform that is not part of the system's built-in templates, the low-code platform records the user's custom formula editing operation. Specifically, the formula customization unit 104 triggers this step when the user opens the "New Formula" page or clicks the "Custom Formula" button. The recording of the custom formula editing operation includes the user filling in the basic information of the custom formula, namely, a description of the problem to be solved, the language of implementation, component binding information (binding target component, triggering event), parameter structure and input requirements, the user's expected output format (e.g., retaining two decimal places, symbols, etc.), and accompanying explanatory comments or documentation.

[0110] This step enables standardized input for custom logic, facilitating subsequent validation; it also avoids format ambiguity or naming conflicts during user creation.

[0111] S302. Generate custom template code, optional formulas, and optional parameters based on the custom formula information.

[0112] In this step, the system automatically converts the user-provided formula into a template object with a code structure to improve editing efficiency. The custom template code is generated based on the user's confirmation of the formula's basic information, including the formula name, input parameters, output parameters, and code comments.

[0113] Specifically, the formula customization unit 104 automatically assigns placeholders, type labels, and format restrictions to parameters, and combines the existing formula library in the low-code platform to recommend relevant optional parameters for reference, thereby extracting all bound components from the user's current page as optional parameters.

[0114] S303: Display custom template code, optional formulas, and optional parameters to the user.

[0115] In this step, the low-code platform displays the content generated in the previous step in a structured manner on the front end, providing users with custom implementations of formulas for fine-tuning. Specifically, it uses visual graphics to display the code editor window (allowing for parameter insertion and drag-and-drop components), the optional parameter area (displaying input components on the current page, such as text boxes and radio buttons), the optional formula recommendation area (categorized by keywords, such as mathematics, logic, and text processing), and the input / output parameter structure tree (supporting drag-and-drop adjustment and type preview), along with a real-time formula preview window to show the execution results or type matching status.

[0116] This step can improve the efficiency of user formula design; help users gain a clear understanding of the execution path and dependent components of the formula; provide structural visualization, and reduce configuration errors.

[0117] S304. In response to the user's editing and selection operations on the custom template code, optional formula, and optional parameters, the custom formula is obtained.

[0118] This step involves the user actually editing the formula. The system can dynamically record and verify the changes made by the user, thereby generating a structured custom formula. For example, it can acquire changes in user code input in real time, parse the input into an abstract syntax tree, automatically identify parameter types, check whether valid components are referenced, and verify logical validity (such as division by zero, nested structure errors), and finally generate a compilable object.

[0119] S305. Update the custom formula to the formula library of the low-code platform.

[0120] The formula library is used to provide users with formula options. This step updates the aforementioned custom formulas into candidate formulas that can be invoked by other users in the low-code platform and makes them available for reference by other components and pages.

[0121] This application's embodiments, by collecting user editing intent, intelligently generate formula templates and provide visual editing support, achieving automated processing from formula logic construction and parameter selection to syntax structure verification, greatly reducing the technical threshold for formula configuration. Simultaneously, custom formulas, after being generated in a structured manner, can be deployed to the formula library, supporting cross-page reuse and team sharing, effectively improving the flexibility, scalability, and business adaptability of the low-code platform, and meeting the formula configuration needs of complex business scenarios.

[0122] Figure 4 The flowchart of Embodiment 3 of the implementation method of the low-code platform provided in this application is shown in the figure. Figure 4 In response to a user's component selection action, the following includes:

[0123] S401. Obtain the component to be assigned a value selected by the user.

[0124] Among them, components to be assigned values ​​refer to target components that have not yet been bound to an explicit data source or logical formula, and are typically used to display results or receive indirect assignments. Common types include output text boxes, charts, and summary value displays.

[0125] Specifically, users click on a component on the page and select "Configure Source for this Component" in the editing panel; the component management unit 101 records the information of the currently selected component; the system extracts the component's context information, including the current component type (numerical, string, time, etc.), the range of acceptable data types, whether there is already a binding relationship, and the degree of association with other components on the page (dependency path). This step establishes the target landing point of the calculation logic, provides the starting point for reverse derivation of formulas, and reduces the number of steps users need to manually find the calculation source.

[0126] S402. Based on the component to be assigned, determine the formula and parameters corresponding to the component to be assigned.

[0127] The core of this step lies in building the reverse computation logic environment. The low-code platform needs to deduce the formulas that may be used for assignment and the required parameters based on the data requirements of the target component.

[0128] Specifically, based on the data type of the target component, all formulas in the formula library that can output that type are filtered; existing component parameters on the page are retrieved and analyzed to see if they can be used as input for the formula; and the most likely formula structure is intelligently recommended by combining factors such as the frequency of use of common formulas, page layout, and semantic relationships.

[0129] S403. Calculate the formula based on the parameters to obtain the component value of the component to be assigned.

[0130] This step executes the predictive calculation process of the above formula, helping users preview the possible calculation results of each candidate formula before configuration, thereby assisting them in determining which formula is most suitable for binding the current component. The component value represents the configuration of the component to be assigned a value.

[0131] For example, the system iterates through all recommended formulas, taking the component parameters already entered on the current page as input, and executes the formula logic (which may involve addition, subtraction, multiplication, division, date processing, string concatenation, etc.). The formula output value is then used as a candidate value for the "component to be assigned a value". In addition, the system caches each calculation result and labels its calculation path, confidence level, or hit rate.

[0132] This step allows users to preview the results in advance, assisting them in making selections, while also preventing page errors caused by incorrect logic binding, and providing explanation and transparency for the formulas.

[0133] S404. Display the component value of the component to be assigned to the user so that the user can select the corresponding component based on the component value.

[0134] This step is the final component result display stage, which can help users manually or intelligently select the appropriate formula for binding based on the aforementioned calculation results.

[0135] Specifically, the interface displayed to users can provide the following functions: a list of recommended formulas; each formula displays the input parameters, source components, and calculation path; users can click the corresponding bind formula button to formally bind the formula to the component to be assigned a value; if users need to fine-tune the formula, they can also jump back to the formula editor for adjustment.

[0136] This step enhances the user's choice by providing computational transparency and a feedback mechanism, and allows for multi-formula comparison and decision-making, thereby improving configuration efficiency.

[0137] This application implements an automatic recommendation and calculation mechanism based on "target component reverse derivation," effectively solving the core problems of "difficulty in finding component value sources, difficulty in configuring formulas, and lack of logical transparency" in low-code platforms. Through real-time parameter capture, intelligent formula matching, calculation result preview, and interactive binding, it significantly improves user configuration efficiency and accuracy, making it particularly suitable for page design scenarios with complex business scenarios and dense component linkages.

[0138] Figure 5 A schematic diagram of the structure of the implementation device for the low-code platform provided in this application. Figure 5 As shown, the low-code platform implementation device 50 includes a component information determination module 501, an editing information acquisition module 502, a verification result acquisition module 503, a formula to be verified acquisition module 504, a target formula determination module 504, and a low-code platform implementation module 505. Among them,

[0139] The component information determination module 501 is used to determine the first component information of the first component and the second component information of the second component in response to the user's component selection operation;

[0140] The editing information acquisition module 502 is used to acquire the user's parameter editing information for the first component and the formula editing information for the second component;

[0141] The verification result acquisition module 503 is used to perform verification analysis on the parameter editing information of the first component based on the first component information of the first component, and obtain the verification result;

[0142] The module 504, which obtains the formula to be verified, is used to perform verification analysis on the parameter editing information of the first component based on the verification result and the formula editing information of the second component, and obtain the formula to be verified.

[0143] The target formula determination module 505 is used to determine the target formula based on the second component information of the second component and the formula to be verified.

[0144] The low-code platform implementation module 506 is used to deploy the target formula to the formula library of the low-code platform to obtain the target low-code platform.

[0145] Furthermore, the implementation apparatus for low-code platforms is also used for:

[0146] In response to the user's custom formula editing operation, determine the custom formula information;

[0147] Based on the custom formula information, obtain the custom formula;

[0148] Update custom formulas to the formula library of the low-code platform, which provides users with formula options.

[0149] Furthermore, the implementation apparatus for low-code platforms is also used for:

[0150] Generate custom template code, optional formulas, and optional parameters based on the custom formula information;

[0151] The custom template code, optional formulas, and optional parameters are displayed to the user. The custom template code includes the formula name, input parameters, output parameters, and code comments.

[0152] The custom formula is generated in response to the user's editing and selection of custom template code, optional formulas, and optional parameters.

[0153] Furthermore, the verification result obtaining module 503 is also used for:

[0154] Based on the information of the first component of the first component, determine the optional parameter information;

[0155] Based on the optional parameter information, the parameter editing information of the first component is verified and analyzed to obtain the verification results.

[0156] Furthermore, module 504, which obtains the formula to be verified, is also used for:

[0157] Based on the verification results, determine the matching result between the parameter editing information and the optional parameter information;

[0158] If the matching result indicates that the parameter editing information matches the optional parameter information, then the parameter editing information is compared with the preset parameter requirements to obtain the comparison result. The preset parameter requirements include parameter validity requirements and parameter type requirements.

[0159] If the comparison result indicates that the parameter editing information meets the preset parameter requirements, then the formula to be verified is obtained according to the formula editing information of the second component.

[0160] Furthermore, the target formula determination module 505 is also used for:

[0161] Based on the information from the second component of the second component, determine the optional formula information;

[0162] The optional formula information is matched with the formula to be verified to obtain the matching results;

[0163] If the matching result shows that the formula to be verified matches the optional formula information, then the formula to be verified is subjected to syntax tree verification analysis to obtain the syntax tree analysis result;

[0164] If the syntax tree analysis results indicate that the formula to be verified meets the formula structure requirements, then the target formula is obtained. The formula structure requirements include parameter type requirements and nested logic requirements.

[0165] Furthermore, the target formula determination module 505 is also used for:

[0166] If the matching result indicates that the formula to be verified does not match the optional formula information, then based on the big data algorithm, formula correction information is generated;

[0167] Display the formula correction information to the user;

[0168] In response to the user's modification of the formula to be verified, the target formula is determined.

[0169] Furthermore, the component information determination module 501 is also used for:

[0170] Retrieve the component selected by the user to be assigned a value;

[0171] Based on the component to be assigned, determine the formula and parameters corresponding to the component;

[0172] The formula is calculated based on the parameters to obtain the component value of the component to be assigned. The component value is used to determine the target formula.

[0173] Display the component values ​​of the components to be assigned to the user so that the user can select the corresponding component based on the component values.

[0174] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 6 As shown, the electronic device 60 includes:

[0175] The electronic device 60 may include a processor 601 with one or more processing cores, a memory 602 with one or more computer-readable storage media, a communication component 603, and other components. The processor 601, memory 602, and communication component 603 are connected via a bus 604.

[0176] In the specific implementation process, at least one processor 601 executes computer execution instructions stored in memory 602, causing at least one processor 601 to execute the low-code platform implementation method described above.

[0177] The specific implementation process of processor 601 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0178] In the above Figure 6 In the illustrated embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0179] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0180] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0181] In some embodiments, a computer program product is also provided, comprising a computer program or instructions that, when executed by a processor, implement the steps in any of the above-described low-code platform implementation methods.

[0182] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0183] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0184] Therefore, embodiments of this application provide a computer-readable storage medium storing a plurality of instructions that can be loaded by a processor to execute steps in any of the low-code platform implementation methods provided in embodiments of this application.

[0185] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0186] Since the instructions stored in the storage medium can execute the steps in any of the low-code platform implementation methods provided in the embodiments of this application, the beneficial effects that any of the low-code platform implementation methods provided in the embodiments of this application can achieve can be realized, as detailed in the preceding embodiments, and will not be repeated here.

[0187] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0188] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0189] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for implementing a low-code platform, characterized in that, include: In response to the user's component selection operation, the first component information of the first component and the second component information of the second component are determined. The first component information includes optional parameter information, and the second component information includes optional formula information. Obtain the user's parameter editing information for the first component and the formula editing information for the second component; Based on the first component information of the first component, the parameter editing information of the first component is verified and analyzed to obtain the verification result; Based on the verification results and the formula editing information of the second component, the formula to be verified is obtained; Based on the second component information of the second component and the formula to be verified, the target formula is determined; The target formula is deployed to the formula library of the low-code platform to obtain the target low-code platform.

2. The method according to claim 1, characterized in that, The method further includes: In response to the user's custom formula editing operation, determine the custom formula information; Based on the custom formula information, the custom formula is obtained; The custom formula is updated to the formula library of the low-code platform, which provides formula selection for users.

3. The method according to claim 2, characterized in that, Based on the custom formula information, the custom formula is obtained, including: Based on the custom formula information, generate custom template code, optional formulas, and optional parameters; The custom template code, the optional formula, and the optional parameters are displayed to the user. The custom template code includes the formula name, input parameters, output parameters, and code comments. In response to the user's editing and selection operations on the custom template code, the optional formula, and the optional parameters, a custom formula is obtained.

4. The method according to any one of claims 1 to 3, characterized in that, Based on the first component information of the first component, the parameter editing information of the first component is verified and analyzed to obtain the verification results, including: Based on the first component information of the first component, determine the optional parameter information; Based on the optional parameter information, the parameter editing information of the first component is verified and analyzed to obtain the verification result.

5. The method according to any one of claims 1 to 3, characterized in that, Based on the verification result and the formula editing information of the second component, the formula to be verified is obtained, including: Based on the verification results, determine the matching result between the parameter editing information and the optional parameter information; If the matching result indicates that the parameter editing information matches the optional parameter information, then the parameter editing information is compared with the preset parameter requirements to obtain the comparison result. The preset parameter requirements include parameter validity requirements and parameter type requirements. If the comparison result indicates that the parameter editing information meets the preset parameter requirements, then the formula to be verified is obtained according to the formula editing information of the second component.

6. The method according to any one of claims 1 to 3, characterized in that, Based on the second component information of the second component and the formula to be verified, the target formula is obtained, including: Based on the second component information of the second component, determine the optional formula information; The optional formula information is matched with the formula to be verified to obtain the matching result; If the matching result indicates that the formula to be verified matches the optional formula information, then a syntax tree verification analysis is performed on the formula to be verified to obtain the syntax tree analysis result. If the syntax tree analysis result indicates that the formula to be verified meets the formula structure requirements, then the target formula is obtained. The formula structure requirements include parameter type requirements and nested logic requirements.

7. The method according to claim 6, characterized in that, After matching the optional formula information with the formula to be verified to obtain the matching result, the method further includes: If the matching result indicates that the formula to be verified does not match the optional formula information, then based on the big data algorithm, formula correction information is generated; The information regarding the formula to be corrected will be displayed to the user. In response to the user's modification operation on the formula to be verified, a target formula is determined.

8. The method according to any one of claims 1 to 3, characterized in that, Following the user's component selection action, the method further includes: Obtain the component to be assigned a value by the user; Based on the component to be assigned a value, determine the formula and parameters corresponding to the component to be assigned a value; The formula is calculated based on the parameters to obtain the component value of the component to be assigned, and the component value is used to represent the configuration of the component to be assigned. The component value of the component to be assigned is displayed to the user so that the user can select the corresponding component based on the component value.

9. An implementation apparatus for a low-code platform, characterized in that, include: The component information determination module is used to determine the first component information of the first component and the second component information of the second component in response to the user's component selection operation. The editing information acquisition module is used to acquire the user's parameter editing information for the first component and the formula editing information for the second component; The verification result acquisition module is used to perform verification analysis on the parameter editing information of the first component based on the first component information of the first component, and obtain the verification result; The module for obtaining the formula to be verified is used to perform verification analysis on the parameter editing information of the first component based on the verification result and the formula editing information of the second component, so as to obtain the formula to be verified. The target formula determination module is used to determine the target formula based on the second component information of the second component and the formula to be verified; The low-code platform implementation module is used to deploy the target formula to the formula library of the low-code platform to obtain the target low-code platform.

10. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 8.

12. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method as described in any one of claims 1 to 8.

Images