A front-end page input control configuration method and a related device thereof

Abstract

The application discloses an input control configuration method of a front-end page and a related device thereof, and belongs to the technical field of research and development management. The application establishes a data dictionary table in a back-end database. In the front-end page, the data dictionary information is obtained by calling the back-end interface, and is rendered to dynamically generate the input control. The control configuration information in the data dictionary table is classified, the dependency relationship between various control configuration attributes is analyzed, and a configuration attribute dependency graph is constructed according to the dependency relationship. The requirement information of the front-end page is obtained, the target control configuration information is matched in the data dictionary table according to the requirement information, the configuration priority rule is formulated according to the target control configuration information and the configuration attribute dependency graph, the target control configuration information is rendered according to the configuration priority rule, and the current front-end page is obtained. The application also relates to the technical field of blockchains, and the requirement information is stored in a blockchain network. The application improves the flexibility and reusability of the front-end control configuration.

Description

Technical Field

[0001] This application belongs to the field of R&D management technology, specifically relating to a method for configuring input controls on a front-end page and related equipment. Background Technology

[0002] Input controls on a front-end webpage are elements in the user interface that allow users to input or select data. These controls are typically located in forms on a webpage or application and are used to collect and process user information. Input controls are an important component of building interactive and dynamic webpages, enabling users to interact with the webpage, input data, or make selections.

[0003] In front-end web page development, managing the configuration of input controls has always been a complex and error-prone issue. The traditional approach is to hard-code the configuration information of all controls into the front-end code. However, this not only increases the workload of development and maintenance but also easily leads to redundancy and inconsistencies in the configuration information. Moreover, when business requirements change, modifying this scattered configuration information is extremely difficult. Summary of the Invention

[0004] The purpose of this application is to provide a method, apparatus, computer device, and storage medium for configuring input controls on a front-end page, so as to solve the technical problems that existing front-end page input control configuration schemes have a large workload for development and maintenance, and are prone to redundancy and inconsistency of configuration information.

[0005] To address the aforementioned technical problems, this application provides a method for configuring input controls on a front-end page, employing the following technical solution:

[0006] A method for configuring input controls on a front-end page involves establishing a data dictionary table in a back-end database to store key-value pair information for the input controls. On the front-end page, the required data dictionary information is retrieved by requesting a back-end API, and the data dictionary information is rendered to dynamically generate the input controls. The method specifically includes:

[0007] The control configuration information in the data dictionary table is categorized and organized, and the control configuration attributes corresponding to each information category are obtained;

[0008] Analyze the dependencies between control configuration properties and construct a configuration property dependency graph based on these dependencies;

[0009] Obtain the input control requirements information of the current front-end page, and match the target control configuration information in the data dictionary table based on the input control requirements information;

[0010] Develop configuration priority rules based on the target control configuration information and configuration attribute dependency graph;

[0011] In the preset control rendering engine, the configuration information of the target control is rendered according to the configuration priority rules to obtain the current front-end page.

[0012] Furthermore, the steps of classifying and organizing the control configuration information in the data dictionary table, and obtaining the control configuration attributes corresponding to each information category, specifically include:

[0013] Define a hierarchical structure model for the data dictionary, which includes a functional configuration layer, a business configuration layer, and a role configuration layer.

[0014] The hierarchical structure model is used to classify and organize the control configuration information in the data dictionary table, resulting in functional control configuration information, business control configuration information, and role control configuration information.

[0015] The attribute data of the configuration information of functional control, business control, and role control are statistically analyzed separately to obtain the control configuration attributes corresponding to each information category. The attribute data includes data type, value range, constraints, and default value.

[0016] Furthermore, the steps of analyzing the dependencies between control configuration properties and constructing a configuration property dependency graph based on these dependencies specifically include:

[0017] Identify the dependencies between control configuration properties and import these dependencies into a preset directed acyclic graph to obtain an initial property dependency graph;

[0018] The graph traversal algorithm is used to read the initial property dependency graph and parse it to determine whether there are dependency conflicts between control configuration properties.

[0019] If there are dependency conflicts between control configuration properties, the values ​​of the control configuration properties will be optimized.

[0020] The initial property dependency graph is adjusted based on the optimized control configuration properties until dependency conflicts are eliminated, thus obtaining the property dependency graph.

[0021] Furthermore, the steps of using a graph traversal algorithm to read and parse the initial attribute dependency graph, and determining whether there are dependency conflicts between control configuration properties, specifically include:

[0022] The graph traversal algorithm is used to traverse the nodes and edges of the initial attribute dependency graph, where nodes represent control configuration attributes and edges represent the logical relationships between control configuration attributes.

[0023] The nodes and edges of the initial attribute dependency graph are parsed to obtain the control configuration attributes and the logical relationships between the control configuration attributes;

[0024] Determine whether there are dependency conflicts between control configuration properties based on the control configuration properties and the logical relationships between them.

[0025] Furthermore, after determining whether there are dependency conflicts between control configuration properties based on the control configuration properties and the logical relationships between them, the process also includes:

[0026] Determine whether the logical relationship between control configuration properties is a preset conflict relationship. Conflict relationships include property mutual exclusion, logical errors, hierarchical dependencies, and type or scope conflicts.

[0027] When there is one or more conflicting logical relationships between control configuration properties, determine whether there is a dependency conflict between the control configuration properties.

[0028] Furthermore, the steps for formulating configuration priority rules based on the target control configuration information and configuration attribute dependency graph specifically include:

[0029] Based on the decision tree algorithm, the configuration information of the control associated with the target control configuration information is identified in the configuration attribute dependency graph, and the associated control configuration information is obtained.

[0030] Calculate the correlation value between the target control configuration information and the associated control configuration information;

[0031] The configuration information of the associated controls is sorted according to the relevance value to obtain the sequence of associated controls;

[0032] Configuration priority rules are established based on the sequence of associated controls, whereby the configuration priority rules determine the configuration order of the target control and associated controls.

[0033] Furthermore, in the preset control rendering engine, the steps of rendering the target control configuration information according to the configuration priority rules to obtain the current front-end page specifically include:

[0034] The configuration order of the target input control and associated controls is determined according to the configuration priority rules;

[0035] Parse the target control configuration information to obtain the target input control's control properties, layout properties, and style properties;

[0036] Based on the target input control's control properties, layout properties, and style properties, the control rendering engine is invoked to generate the target input control on the current front-end page;

[0037] Parse the configuration information of the associated controls to obtain the control properties, layout properties, and style properties configured for the associated controls;

[0038] Based on the control properties, layout properties, and style properties configured for the associated controls, and in accordance with the configuration order, the control rendering engine is invoked to generate the associated controls on the current front-end page.

[0039] To address the aforementioned technical problems, this application also provides a front-end page input control configuration device, which employs the following technical solution:

[0040] A configuration device for input controls on a front-end page includes: establishing a data dictionary table in a back-end database to store key-value pair information of the input controls; retrieving the required data dictionary information from the back-end interface via a request in the front-end page; rendering the data dictionary information; and dynamically generating the input controls. The device specifically includes:

[0041] The information classification module is used to classify and organize the control configuration information in the data dictionary table, and to obtain the control configuration attributes corresponding to each information classification.

[0042] The property dependency module is used to analyze the dependencies between control configuration properties and construct a configuration property dependency graph based on these dependencies.

[0043] The information matching module is used to obtain the input control requirement information of the current front-end page, and match the target control configuration information in the data dictionary table based on the input control requirement information;

[0044] The configuration rules module is used to formulate configuration priority rules based on the target control configuration information and the configuration attribute dependency graph.

[0045] The control rendering module is used to render the configuration information of the target control according to the configuration priority rules in the preset control rendering engine to obtain the current front-end page.

[0046] To address the aforementioned technical problems, this application also provides a computer device that employs the following technical solution:

[0047] A computer device includes a memory and a processor, the memory storing computer-readable instructions, wherein the processor, when executing the computer-readable instructions, implements the steps of the input control configuration method for a front-end page as described in any of the preceding claims.

[0048] To address the aforementioned technical problems, this application also provides a computer-readable storage medium, employing the technical solution described below:

[0049] A computer-readable storage medium storing computer-readable instructions, which, when executed by a processor, implement the steps of the input control configuration method for a front-end page as described in any of the above-described methods.

[0050] Compared with the prior art, the embodiments of this application have the following main advantages:

[0051] This application discloses a method for configuring input controls on a front-end page and related equipment, belonging to the field of R&D management technology. This application effectively reduces the repetition and redundancy of control configuration by classifying and organizing control configuration information in a data dictionary table and analyzing dependencies. By constructing a configuration attribute dependency graph, it models the dependencies between control configuration attributes, enabling control configuration information to be dynamically generated on demand and automatically meeting the control requirements of the front-end page during rendering. The introduction of configuration priority rules ensures configuration consistency under different dependency conditions, avoiding inconsistencies caused by manual configuration. By using a preset control rendering engine, it achieves automatic rendering of target controls, simplifying the configuration management process and reducing the complexity of development and maintenance. This application improves the flexibility and reusability of configuration while reducing redundant workload in configuring input controls on the front-end page, thereby improving the overall development efficiency and maintainability of the system. Attached Figure Description

[0052] To more clearly illustrate the solutions in this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0053] Figure 1 An exemplary system architecture diagram is shown, in which this application can be applied;

[0054] Figure 2 A flowchart illustrating an embodiment of a front-end page input control configuration method according to this application is shown;

[0055] Figure 3 A schematic diagram of the structure of an embodiment of an input control configuration device for a front-end page according to this application is shown;

[0056] Figure 4 A schematic diagram of the structure of one embodiment of a computer device according to this application is shown. Detailed Implementation

[0057] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains; the terminology used herein in the specification of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "comprising" and "having," and any variations thereof, in the specification, claims, and foregoing drawings of this application, are intended to cover non-exclusive inclusion. The terms "first," "second," etc., in the specification, claims, or foregoing drawings of this application are used to distinguish different objects, not to describe a particular order.

[0058] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0059] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.

[0060] like Figure 1 As shown, system architecture 100 may include terminal device 101, network 102, and server 103. Terminal device 101 may be a laptop 1011, tablet 1012, or mobile phone 1013. Network 102 is used as a medium to provide a communication link between terminal device 101 and server 103. Network 102 may include various connection types, such as wired, wireless communication links, or fiber optic cables.

[0061] Users can use terminal device 101 to interact with server 103 via network 102 to receive or send messages, etc. Various communication client applications can be installed on terminal device 101, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social media platform software, etc.

[0062] Terminal device 101 can be various electronic devices with a display screen and support web browsing. In addition to laptops 1011, tablets 1012, or mobile phones 1013, terminal device 101 can also be e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III), MP4 players (Moving Picture Experts Group Audio Layer IV), laptops, and desktop computers.

[0063] Server 103 can be a server that provides various services, such as a backend server that provides support for the pages displayed on terminal device 101.

[0064] It should be noted that the input control configuration method for the front-end page provided in this application embodiment is generally executed by the server / terminal device, and correspondingly, the input control configuration device for the front-end page is generally set in the server / terminal device.

[0065] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative; the system can have any number of terminal devices, networks, and servers depending on implementation needs.

[0066] A method for configuring input controls on a front-end page involves establishing a data dictionary table in a back-end database to store key-value pair information of the input controls. On the front-end page, the required data dictionary information is obtained by requesting and calling the back-end interface, and the data dictionary information is rendered to dynamically generate the input controls.

[0067] In this embodiment, a data dictionary table is established in the backend database to centrally store the key-value pair information of the input controls. The frontend page dynamically obtains and renders the data dictionary information through an interface to generate the required input controls. This eliminates the need for hard-coding the frontend control configuration in the page; instead, it relies on the dynamic transmission and configuration of the backend data dictionary, providing greater flexibility. It supports centralized management and unified updates of control configurations, reducing repetitive configuration work between the frontend and backend. Simultaneously, it can dynamically adapt to changes in requirements, making it suitable for scenarios that require frequent adjustments to input control configurations. This reduces the workload of frontend development to a certain extent and improves the consistency and maintainability of control configurations.

[0068] Suppose a backend management system needs to manage input controls for a "Country / Region" list. Administrators can centrally manage this list as an enumeration set through a newly added data dictionary menu. First, the administrator can create a unique identifier named "countryCodes" (ddkey) and add attributes such as key (country code), value (country name), description, status (enabled / disabled), type (string, number, etc.), and sorting for each country or region in this enumeration set. For example, "US" represents the United States, with the key "US," the value "United States," the description "United States country code," and the status "enabled." If it's necessary to add countries or edit existing country information later, the administrator can find this enumeration set by querying "countryCodes" and add or modify specific country code entries in the "Add Dictionary" menu. Furthermore, permission settings can ensure that only authorized administrators can add, edit, or delete data dictionary entries, thus guaranteeing the security and controllability of system configuration. By establishing a data dictionary table, the maintenance and updating of input control information becomes efficient and centralized, facilitating unified management and dynamic front-end calls.

[0069] Continue to refer to Figure 2 The diagram illustrates a flowchart of an embodiment of a method for configuring input controls on a front-end page according to this application. The method for configuring input controls on a front-end page includes the following steps:

[0070] S201, categorize and organize the control configuration information in the data dictionary table, and obtain the control configuration attributes corresponding to each information category.

[0071] Specifically, the system extracts all control configuration information from the data dictionary table and meticulously categorizes them according to purpose, function, and data type. For example, by control type, they can be divided into text boxes, selection boxes, checkboxes, etc.; by data type, they can be divided into string, number, boolean, etc. Each type of control configuration has specific attribute requirements, such as the maximum input length and prompt message for text boxes, while selection boxes include data source information for selectable options. Through configuration information categorization, the system can quickly identify the general and special configuration attributes of each control. At the same time, this categorization process ensures consistency in the configuration of similar controls, facilitates the construction of flexible dynamic forms, reduces maintenance difficulty, and improves development efficiency.

[0072] S202, analyze the dependencies between control configuration properties, and construct a configuration property dependency graph based on the dependencies between control configuration properties.

[0073] Specifically, logical dependencies often exist between control configuration properties. The system analyzes these dependencies to ensure the dynamism and correctness of the form. For example, in a form, when "Country" is selected, the options in the "City" checkbox need to be dynamically updated based on the country value. This dependency relationship is usually manifested between "parent" and "child" fields. The system analyzes the dependencies between configuration properties to determine which control configurations are related and constructs a dependency graph. The dependency graph clarifies the priority order and triggering relationship between the various control properties, providing a basis for the dynamic loading and updating of configuration properties during rendering. Through dependency graph management, the system can better handle complex form requirements, making the loading and display of control configurations more logical and hierarchical.

[0074] S203: Obtain the input control requirement information of the current front-end page, and match the target control configuration information in the data dictionary table based on the input control requirement information.

[0075] Specifically, the system automatically extracts the required control configuration information from the data dictionary table based on the actual input control needs of the front-end page. For example, if the current page requires a text input box, a dropdown selection box, and a date picker, the system will find the corresponding configuration attributes for the text box, selection box, and date picker in the data dictionary table and filter and match these attributes one by one. During the matching process, redundant configuration information that does not meet the current page requirements will also be filtered out to ensure that the final set of configuration information loaded is a simplified set that meets the page requirements. This automated matching reduces manual intervention, making the control configuration of the page more flexible and efficient, and also ensuring data consistency and dynamism.

[0076] S204, Develop configuration priority rules based on the target control configuration information and configuration attribute dependency graph.

[0077] Specifically, after matching control requirements, the system sets priority rules for each control's configuration properties based on the constructed dependency graph. These priority rules clarify the execution order of each control during loading and rendering, ensuring correct dependencies. For example, if the "City" control depends on the "Country" control, the priority rule will ensure that the country control's options are loaded before the city control's update is triggered. Furthermore, priority rules can avoid conflicts between configuration properties and prevent data inconsistencies caused by incorrect control loading order. By setting configuration priorities, the system can accurately control the rendering sequence of controls, improving page loading stability and the accuracy of configuration rendering.

[0078] S205, in the preset control rendering engine, renders the target control configuration information according to the configuration priority rules to obtain the current front-end page.

[0079] Specifically, in this stage, the system entrusts all target control configuration information to the control rendering engine for processing, rendering each control sequentially according to the previously defined priority rules. Based on the control configuration attributes and rules in the dependency graph, the rendering engine generates functional input controls on the page. The engine processes the configuration data, combining control information (such as options, default values, and states) with the front-end display, and progressively completes the rendering of each control, ensuring accurate presentation. If some control configurations have dependencies, the rendering engine monitors their changes in real time during dynamic rendering to ensure synchronized responses to user actions in the form. Finally, after processing by the control rendering engine, the front-end page presents dynamic input controls that meet the requirements, achieving efficient interaction and responsiveness.

[0080] In the above embodiments, this application effectively reduces the repetition and redundancy of control configuration by classifying and organizing the control configuration information in the data dictionary table and analyzing its dependencies. By constructing a configuration attribute dependency graph, the dependency relationships between control configuration attributes are modeled, enabling control configuration information to be dynamically generated on demand and automatically meeting the control requirements of the front-end page during rendering. The introduction of configuration priority rules ensures configuration consistency under different dependency conditions, avoiding inconsistencies caused by manual configuration. By using a preset control rendering engine, automatic rendering of target controls is achieved, simplifying the configuration management process and reducing the complexity of development and maintenance. This application not only improves the flexibility and reusability of configuration but also reduces the redundant workload when inputting control configurations on the front-end page, thereby improving the overall development efficiency and maintainability of the system.

[0081] Furthermore, the steps of classifying and organizing the control configuration information in the data dictionary table, and obtaining the control configuration attributes corresponding to each information category, specifically include:

[0082] Define a hierarchical structure model for the data dictionary, which includes a functional configuration layer, a business configuration layer, and a role configuration layer.

[0083] The hierarchical structure model is used to classify and organize the control configuration information in the data dictionary table, resulting in functional control configuration information, business control configuration information, and role control configuration information.

[0084] The attribute data of the configuration information of functional control, business control, and role control are statistically analyzed separately to obtain the control configuration attributes corresponding to each information category. The attribute data includes data type, value range, constraints, and default value.

[0085] In this embodiment, a hierarchical structure model is defined to clearly categorize the control configuration information of the data dictionary. This model includes a functional configuration layer, a business configuration layer, and a role configuration layer. The functional configuration layer mainly involves the appearance and basic attributes of general controls, such as display format and size. The business configuration layer focuses on the configuration of control attributes related to business logic, such as value range and business data source, to adapt to the needs of different business scenarios. The role configuration layer configures control attributes related to different user roles or permissions, such as editability and hide / show control permissions. After classifying the control configurations through the hierarchical structure model, the system can sequentially extract the specific attribute data of each type of configuration information, and separately statistically analyze the data types, value ranges, constraints, and default values ​​contained in the functional, business, and role-based control configuration information, ensuring the completeness and consistency of attribute settings for each control across different application layers.

[0086] Through the above steps, by defining a hierarchical structure model, the control configuration information of the data dictionary is clearly classified. The control configuration information of the data dictionary table can be managed in a structured manner, which is convenient for dynamic calling, and the control configuration has good scalability and consistency.

[0087] Furthermore, the steps of analyzing the dependencies between control configuration properties and constructing a configuration property dependency graph based on these dependencies specifically include:

[0088] Identify the dependencies between control configuration properties and import these dependencies into a preset directed acyclic graph to obtain an initial property dependency graph;

[0089] The graph traversal algorithm is used to read the initial property dependency graph and parse it to determine whether there are dependency conflicts between control configuration properties.

[0090] If there are dependency conflicts between control configuration properties, the values ​​of the control configuration properties will be optimized.

[0091] The initial property dependency graph is adjusted based on the optimized control configuration properties until dependency conflicts are eliminated, thus obtaining the property dependency graph.

[0092] In this embodiment, the dependencies between control configuration properties are first identified. For example, the "City" control depends on the value of the "Country" control. These dependencies are then imported into a Directed Acyclic Graph (DAG) to generate an initial property dependency graph, which clearly presents the hierarchical relationship of the control configuration properties. Next, a graph traversal algorithm is used to read the nodes and edges in the initial property dependency graph one by one to parse the dependency paths of each property, ensuring the logical integrity of all dependencies. During this process, the system automatically determines whether there are dependency conflicts between properties. For example, when two properties depend on each other, a circular dependency is formed, leading to a conflict. If a dependency conflict is detected, the system will prompt the developers to make adjustments or optimizations, reallocating the values ​​or dependency directions of the control configuration properties. After optimization, the initial property dependency graph is updated to become an acyclic, conflict-free dependency graph, ensuring that each property can be parsed and rendered sequentially during control rendering, eliminating potential dependency issues.

[0093] By constructing an attribute dependency graph through the above steps, a clear logical relationship between control attributes is provided, reducing configuration conflicts and improving the accuracy of control rendering and the stability of page response.

[0094] Furthermore, the steps of using a graph traversal algorithm to read and parse the initial attribute dependency graph, and determining whether there are dependency conflicts between control configuration properties, specifically include:

[0095] The graph traversal algorithm is used to traverse the nodes and edges of the initial attribute dependency graph, where nodes represent control configuration attributes and edges represent the logical relationships between control configuration attributes.

[0096] The nodes and edges of the initial attribute dependency graph are parsed to obtain the control configuration attributes and the logical relationships between the control configuration attributes;

[0097] Determine whether there are dependency conflicts between control configuration properties based on the control configuration properties and the logical relationships between them.

[0098] In this embodiment, the system first uses a graph traversal algorithm to traverse and analyze the nodes and edges in the initial attribute dependency graph. Each node represents a control configuration attribute, and edges represent dependencies or logical constraints between two attributes. By traversing each node and its outgoing edges, the system can parse the hierarchy and dependency order of the control configuration attributes. During this process, traversal algorithms such as Depth-First Search (DFS) or Breadth-First Search (BFS) are used to check the path of each node to construct a complete attribute dependency chain. If a loop path is detected during traversal, it indicates that there is a circular dependency between the control configuration attribute and other attributes. At this time, the system will determine that there is a dependency conflict and further refine the analysis of the conflict source, such as redefining the priority of the control configuration attribute, adjusting the dependency path between attributes, or splitting the mutually dependent logical chains. After optimization, the dependency graph will be updated to an acyclic structure, ensuring that the dependency relationships of attributes are clear.

[0099] For example, in a user registration page, the dependency relationships of control attributes might involve the configuration attributes of the "Country" control and the "City" control. The user's selection of a country affects the options in the city control; therefore, the "City" control depends on the option value of the "Country" control. Using a graph traversal algorithm, the system treats the "Country" control configuration attribute as one node and the "City" control as another node, with a directed edge connecting them, indicating that the "City" control can only be rendered after the "Country" control's options have been loaded. If a "Region" control configuration attribute is added, it might depend on the options in the "City" control; the dependency graph will automatically expand to the "Country -> City -> Region" link. During the traversal, the system checks for and prevents closed loops. For example, if it finds that the "Country" control unexpectedly depends on the "Region" control, it marks this loop as a dependency conflict, and the system then optimizes the dependency relationships to ensure that controls load sequentially according to their logical order, thereby achieving stable page rendering and dynamic interaction.

[0100] Through the above steps, the system can accurately identify and eliminate dependency conflicts between configuration attributes, making the control dependency logic clearer and improving the stability of page rendering and the efficiency of configuration maintenance.

[0101] Furthermore, after determining whether there are dependency conflicts between control configuration properties based on the control configuration properties and the logical relationships between them, the process also includes:

[0102] Determine whether the logical relationship between control configuration properties is a preset conflict relationship. Conflict relationships include property mutual exclusion, logical errors, hierarchical dependencies, and type or scope conflicts.

[0103] When there is one or more conflicting logical relationships between control configuration properties, determine whether there is a dependency conflict between the control configuration properties.

[0104] In this embodiment, when analyzing the logical relationships between control configuration attributes, the system focuses on identifying preset conflict relationships. These conflict relationships include, but are not limited to, attribute mutual exclusion, logical errors, gap dependencies, and type or range conflicts. For example, if there are two control attributes "A" and "B" that are set to a mutual exclusion relationship, meaning the user cannot select both options simultaneously in the same form, the system will mark this attribute mutual exclusion conflict. If control "B" depends on control "A," but the logical relationship is not satisfied in the actual configuration, the system will identify it as a logical error. Furthermore, if the input range of the "City" control is set to "New York," but logically the user selects the "Country" control as "United Kingdom," a range conflict will occur. For these conflict relationships, the system will comprehensively determine whether there are dependency conflicts so as to correct them in a timely manner. When a conflict relationship exists, the system will prompt the user to make adjustments or provide optimization solutions to ensure that the control configuration attributes can operate logically consistently, eliminating potential errors and inconvenience to user operations.

[0105] Through the above steps, the system can fully identify and handle logical conflicts in control configurations, improve the smoothness of user interaction, and ensure reasonable dependencies and stability between controls.

[0106] Furthermore, the steps for formulating configuration priority rules based on the target control configuration information and configuration attribute dependency graph specifically include:

[0107] Based on the decision tree algorithm, the configuration information of the control associated with the target control configuration information is identified in the configuration attribute dependency graph, and the associated control configuration information is obtained.

[0108] Calculate the correlation value between the target control configuration information and the associated control configuration information;

[0109] The configuration information of the associated controls is sorted according to the relevance value to obtain the sequence of associated controls;

[0110] Configuration priority rules are established based on the sequence of associated controls, whereby the configuration priority rules determine the configuration order of the target control and associated controls.

[0111] In this embodiment, the system uses a decision tree algorithm to analyze the configuration attribute dependency graph to identify control configuration information associated with the target control's configuration information. For example, assuming the target control is the "submit button," the system traces back to all controls it depends on, such as "username," "password," and "verification code," obtaining a set of associated control configuration information. Next, the system calculates the correlation degree between the target control and these associated controls, quantifying the impact of each control on the "submit button" in the final rendering. For example, the username control might have a higher correlation degree because it is a required field for user submission, while the verification code might have a slightly lower correlation degree. Based on the calculated correlation degree values, the system sorts the associated control information, forming a sequence of associated controls. Finally, based on this sequence, a configuration priority rule is established to clarify the rendering order, ensuring that key controls (such as username and password) are loaded before the "submit button," thereby achieving the correct logical flow and user interaction experience.

[0112] In its implementation, the system first constructs a decision tree, identifying relevant attributes of the target control's configuration information by analyzing nodes and edges in the configuration attribute dependency graph. For example, if the target control is a "submit button," the root node of the decision tree represents that button. It then traverses all its dependent nodes, such as "username," "password," and "email," analyzing them layer by layer. Each node generates a feature vector based on its position in the dependency graph and its relationship to the target control, reflecting its importance and influence. Next, the system calculates the association degree between each control and the target control, typically based on factors such as attribute dependency depth, type matching, and configuration completeness. The association degree indicates the extent of a control's influence on the target control, thus establishing priority relationships between controls. Finally, the system sorts the controls based on these values, forming an ordered list of controls.

[0113] Through the above steps, the system can effectively manage the configuration priority between controls, improve the logic of control rendering and the smoothness of user operation, and ensure the consistency of user experience.

[0114] Furthermore, in the preset control rendering engine, the steps of rendering the target control configuration information according to the configuration priority rules to obtain the current front-end page specifically include:

[0115] The configuration order of the target input control and associated controls is determined according to the configuration priority rules;

[0116] Parse the target control configuration information to obtain the target input control's control properties, layout properties, and style properties;

[0117] Based on the target input control's control properties, layout properties, and style properties, the control rendering engine is invoked to generate the target input control on the current front-end page;

[0118] Parse the configuration information of the associated controls to obtain the control properties, layout properties, and style properties configured for the associated controls;

[0119] Based on the control properties, layout properties, and style properties configured for the associated controls, and in accordance with the configuration order, the control rendering engine is invoked to generate the associated controls on the current front-end page.

[0120] In this embodiment, the system first determines the rendering order of the target input control and its associated controls according to the previously established configuration priority rules. Taking the user registration page as an example, if the "Submit Button" is the target control, and "Username" and "Password" are its associated controls, the system will render the "Username" and "Password" controls first. Next, the system parses the configuration information of the target control, including control attributes (such as control type), layout attributes (such as position and size), and style attributes (such as font and color), to ensure that the control meets the design requirements. Subsequently, the control rendering engine is invoked to convert these attributes into actual front-end elements, generating the "Submit Button". When processing associated controls, the system similarly parses the attributes of these controls, obtains the corresponding control information and style requirements, and renders these controls one by one according to the previously determined configuration order. In this way, the system ensures that the presentation of controls conforms to the logical order and maintains a consistent visual style, ultimately generating a complete front-end page.

[0121] Through the above steps, the system achieves orderly rendering of controls, improves user experience and the smoothness of page interaction, and ensures that the logic and aesthetics of the front-end page are both taken into account.

[0122] In the above embodiments, this application discloses a method for configuring input controls on a front-end page, belonging to the field of R&D management technology. This application effectively reduces the repetition and redundancy of control configuration by classifying and organizing control configuration information in a data dictionary table and analyzing its dependencies. By constructing a configuration attribute dependency graph, it models the dependencies between control configuration attributes, enabling control configuration information to be dynamically generated on demand and automatically meeting the control requirements of the front-end page during rendering. The introduction of configuration priority rules ensures configuration consistency under different dependency conditions, avoiding inconsistencies caused by manual configuration. By using a preset control rendering engine, it achieves automatic rendering of target controls, simplifying the configuration management process and reducing the complexity of development and maintenance. This application not only improves the flexibility and reusability of configuration but also reduces redundant workload in configuring input controls on the front-end page, thereby improving the overall development efficiency and maintainability of the system.

[0123] In this embodiment, the input control configuration method of the front-end page runs on an electronic device (e.g., Figure 1The server shown can receive instructions or acquire data via wired or wireless connection. It should be noted that the aforementioned wireless connection methods may include, but are not limited to, 3G / 4G connections, WiFi connections, Bluetooth connections, WiMAX connections, Zigbee connections, UWB (ultra-wideband) connections, and other currently known or future wireless connection methods.

[0124] It should be emphasized that, to further ensure the privacy and security of the aforementioned requirements information, this information can also be stored in a blockchain node.

[0125] The blockchain referred to in this application is a novel application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms. Essentially, a blockchain is a decentralized database, a chain of data blocks linked together using cryptographic methods. Each data block contains information about a batch of network transactions, used to verify the validity of the information (anti-counterfeiting) and generate the next block. A blockchain can include an underlying blockchain platform, a platform product service layer, and an application service layer.

[0126] The embodiments of this application can acquire and process relevant data based on artificial intelligence technology. Artificial intelligence (AI) refers to the theories, methods, technologies, and application systems that use digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use that knowledge to obtain optimal results.

[0127] Foundational technologies for artificial intelligence generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing, operating / interactive systems, and mechatronics. AI software technologies mainly encompass computer vision, robotics, biometrics, speech processing, natural language processing, and machine learning / deep learning.

[0128] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing related hardware with computer-readable instructions. These computer-readable instructions can be stored in a computer-readable storage medium. When executed, the program can include the processes of the embodiments of the above methods. The aforementioned storage medium can be a non-volatile storage medium such as a magnetic disk, optical disk, or read-only memory (ROM), or random access memory (RAM).

[0129] It should be understood that although the steps in the flowcharts of the accompanying figures are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the accompanying figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0130] Further reference Figure 3 As a response to the above Figure 2 The implementation of the method shown in this application provides an embodiment of a front-end page input control configuration device, which is similar to... Figure 2 Corresponding to the method embodiments shown, this device can be specifically applied to various electronic devices.

[0131] like Figure 3 As shown, the input control configuration device 300 for the front-end page described in this embodiment establishes a data dictionary table in the back-end database to store the key-value pair information of the input controls. In the front-end page, the required data dictionary information is obtained by requesting and calling the back-end interface, and the data dictionary information is rendered to dynamically generate the input controls. The input control configuration device 300 for the front-end page specifically includes:

[0132] The information classification module 301 is used to classify and organize the control configuration information in the data dictionary table, and to obtain the control configuration attributes corresponding to each information classification.

[0133] The attribute dependency module 302 is used to analyze the dependency relationships between control configuration attributes and construct a configuration attribute dependency graph based on the dependency relationships between control configuration attributes.

[0134] The information matching module 303 is used to obtain the input control requirement information of the current front-end page and match the target control configuration information in the data dictionary table according to the input control requirement information;

[0135] The configuration rule module 304 is used to formulate configuration priority rules based on the target control configuration information and the configuration attribute dependency graph.

[0136] The control rendering module 305 is used to render the configuration information of the target control according to the configuration priority rules in the preset control rendering engine to obtain the current front-end page.

[0137] Furthermore, the information classification module 301 is specifically used for:

[0138] Define a hierarchical structure model for the data dictionary, which includes a functional configuration layer, a business configuration layer, and a role configuration layer. Use the hierarchical structure model to classify and organize the control configuration information in the data dictionary tables, resulting in functional control configuration information, business control configuration information, and role control configuration information. Statistically analyze the attribute data of functional control configuration information, business control configuration information, and role control configuration information respectively to obtain the control configuration attributes corresponding to each information category. The attribute data includes data type, value range, constraints, and default value.

[0139] Furthermore, the attribute dependency module 302 is specifically used for:

[0140] Identify the dependencies between control configuration properties and import them into a pre-defined directed acyclic graph to obtain an initial property dependency graph. Use a graph traversal algorithm to read and parse the initial property dependency graph, and determine whether there are dependency conflicts between control configuration properties. If there are dependency conflicts between control configuration properties, optimize the values ​​of the control configuration properties. Adjust the initial property dependency graph based on the optimized control configuration properties until the dependency conflicts are eliminated, thus obtaining the property dependency graph.

[0141] Furthermore, the attribute dependency module 302 is further used for:

[0142] The graph traversal algorithm is used to traverse the nodes and edges of the initial attribute dependency graph, where nodes represent control configuration attributes and edges represent the logical relationships between control configuration attributes.

[0143] The nodes and edges of the initial attribute dependency graph are parsed to obtain the control configuration attributes and the logical relationships between the control configuration attributes;

[0144] Determine whether there are dependency conflicts between control configuration properties based on the control configuration properties and the logical relationships between them.

[0145] Furthermore, the input control configuration device 300 of the front-end page also includes a dependency conflict judgment module, which is specifically used for:

[0146] Determine whether the logical relationship between control configuration properties is a preset conflict relationship. Conflict relationships include property mutual exclusion, logical error, hierarchical dependency, type or scope conflict. When there is one or more conflict relationships between control configuration properties, determine whether there is a dependency conflict between control configuration properties.

[0147] Furthermore, the configuration rule module 304 is specifically used for:

[0148] Based on the decision tree algorithm, the configuration information of the control associated with the target control configuration information is identified in the configuration attribute dependency graph, and the associated control configuration information is obtained.

[0149] Calculate the correlation value between the target control configuration information and the associated control configuration information;

[0150] The configuration information of the associated controls is sorted according to the relevance value to obtain the sequence of associated controls;

[0151] Configuration priority rules are established based on the sequence of associated controls, whereby the configuration priority rules determine the configuration order of the target control and associated controls.

[0152] Furthermore, the control rendering module 305 is specifically used for:

[0153] The configuration order of the target input control and associated controls is determined according to the configuration priority rules;

[0154] Parse the target control configuration information to obtain the target input control's control properties, layout properties, and style properties;

[0155] Based on the target input control's control properties, layout properties, and style properties, the control rendering engine is invoked to generate the target input control on the current front-end page;

[0156] Parse the configuration information of the associated controls to obtain the control properties, layout properties, and style properties configured for the associated controls;

[0157] Based on the control properties, layout properties, and style properties configured for the associated controls, and in accordance with the configuration order, the control rendering engine is invoked to generate the associated controls on the current front-end page.

[0158] In the above embodiments, this application discloses a front-end page input control configuration device, belonging to the field of R&D management technology. This application effectively reduces the repetition and redundancy of control configuration by classifying and organizing control configuration information in a data dictionary table and analyzing its dependencies. By constructing a configuration attribute dependency graph, it models the dependencies between control configuration attributes, enabling control configuration information to be dynamically generated on demand and automatically meeting the control requirements of the front-end page during rendering. The introduction of configuration priority rules ensures configuration consistency under different dependency conditions, avoiding inconsistencies caused by manual configuration. By using a preset control rendering engine, it achieves automatic rendering of target controls, simplifying the configuration management process and reducing the complexity of development and maintenance. This application not only improves the flexibility and reusability of configuration but also reduces redundant workload in configuring front-end page input controls, thereby improving the overall development efficiency and maintainability of the system.

[0159] To address the aforementioned technical problems, embodiments of this application also provide a computer device. Please refer to [link / reference needed]. Figure 4 , Figure 4 This is a basic structural block diagram of the computer device in this embodiment.

[0160] The computer device 4 includes a memory 41, a processor 42, and a network interface 43 that are interconnected via a system bus. It should be noted that only the computer device 4 with memory 41, processor 42, and network interface 43 is shown in the figure; however, it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented alternatively. Those skilled in the art will understand that the computer device described here is a device capable of automatically performing numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes, but is not limited to, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0161] The computer device can be a desktop computer, laptop, handheld computer, or cloud server, etc. The computer device can interact with the user via a keyboard, mouse, remote control, touchpad, or voice control.

[0162] The memory 41 includes at least one type of readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 41 may be an internal storage unit of the computer device 4, such as the hard disk or memory of the computer device 4. In other embodiments, the memory 41 may also be an external storage device of the computer device 4, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the computer device 4. Of course, the memory 41 may include both the internal storage unit and its external storage device of the computer device 4. In this embodiment, the memory 41 is typically used to store the operating system and various application software installed on the computer device 4, such as computer-readable instructions for configuring input controls on the front-end page. In addition, the memory 41 can also be used to temporarily store various types of data that have been output or will be output.

[0163] In some embodiments, the processor 42 may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other data processing chip. The processor 42 is typically used to control the overall operation of the computer device 4. In this embodiment, the processor 42 is used to execute computer-readable instructions stored in the memory 41 or to process data, such as executing computer-readable instructions for configuring the input controls of the front-end page.

[0164] The network interface 43 may include a wireless network interface or a wired network interface, which is typically used to establish communication connections between the computer device 4 and other electronic devices.

[0165] In the above embodiments, this application discloses a computer device belonging to the field of R&D management technology. This application effectively reduces the repetition and redundancy of control configuration by classifying and organizing control configuration information in a data dictionary table and analyzing its dependencies. By constructing a configuration attribute dependency graph, it models the dependencies between control configuration attributes, enabling control configuration information to be dynamically generated on demand and automatically meeting the control requirements of the front-end page during rendering. The introduction of configuration priority rules ensures configuration consistency under different dependency conditions, avoiding inconsistencies caused by manual configuration. By using a preset control rendering engine, it achieves automatic rendering of target controls, simplifying the configuration management process and reducing the complexity of development and maintenance. This application not only improves the flexibility and reusability of configuration but also reduces redundant workload when inputting control configurations on the front-end page, thereby improving the overall development efficiency and maintainability of the system.

[0166] This application also provides another embodiment, namely, providing a computer-readable storage medium storing computer-readable instructions that can be executed by at least one processor to cause the at least one processor to perform the steps of the input control configuration method for the front-end page as described above.

[0167] In the above embodiments, this application discloses a computer-readable storage medium, belonging to the field of R&D management technology. This application effectively reduces the repetition and redundancy of control configuration by classifying and organizing control configuration information in a data dictionary table and analyzing its dependencies. By constructing a configuration attribute dependency graph, it models the dependencies between control configuration attributes, enabling control configuration information to be dynamically generated on demand and automatically meeting the control requirements of the front-end page during rendering. The introduction of configuration priority rules ensures configuration consistency under different dependency conditions, avoiding inconsistencies caused by manual configuration. By using a preset control rendering engine, it achieves automatic rendering of target controls, simplifying the configuration management process and reducing the complexity of development and maintenance. This application not only improves the flexibility and reusability of configuration but also reduces redundant workload when inputting control configurations on the front-end page, thereby improving the overall development efficiency and maintainability of the system.

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

[0169] This application can be used in a wide variety of general-purpose or special-purpose computer system environments or configurations. Examples include: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics devices, network PCs, minicomputers, mainframe computers, and distributed computing environments including any of the above systems or devices. This application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform specific tasks or implement specific abstract data types. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0170] Obviously, the embodiments described above are only some embodiments of this application, not all embodiments. The accompanying drawings show preferred embodiments of this application, but do not limit the patent scope of this application. This application can be implemented in many different forms; rather, the purpose of providing these embodiments is to provide a more thorough and comprehensive understanding of the disclosure of this application. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing specific embodiments, or make equivalent substitutions for some of the technical features. Any equivalent structures made using the content of this application's specification and drawings, directly or indirectly applied to other related technical fields, are similarly within the scope of patent protection of this application.

Claims

1. A method for configuring input controls on a front-end page, characterized in that, A data dictionary table is established in the backend database to store the key-value pair information of the input control. In the frontend page, the required data dictionary information is obtained by requesting and calling the backend interface, and the data dictionary information is rendered to dynamically generate the input control. The method specifically includes: The control configuration information in the data dictionary table is categorized and organized, and the control configuration attributes corresponding to each information category are obtained; Analyze the dependencies between the control configuration properties, and construct a configuration property dependency graph based on the dependencies between the control configuration properties; Obtain the input control requirement information of the current front-end page, and match the target control configuration information in the data dictionary table according to the input control requirement information; Develop configuration priority rules based on the target control configuration information and the configuration attribute dependency graph; In the preset control rendering engine, the configuration information of the target control is rendered according to the configuration priority rules to obtain the current front-end page; The step of classifying and organizing the control configuration information in the data dictionary table and obtaining the control configuration attributes corresponding to each information category specifically includes: Define a hierarchical structure model for the data dictionary, wherein the hierarchical structure model includes a functional configuration layer, a business configuration layer, and a role configuration layer; The hierarchical structure model is used to classify and organize the control configuration information in the data dictionary table to obtain functional control configuration information, business control configuration information and role control configuration information. The attribute data of the configuration information of the functional control, the configuration data of the business control, and the configuration data of the role control are statistically analyzed to obtain the control configuration attributes corresponding to each information category. The attribute data includes data type, value range, constraint conditions, and default value. The step of analyzing the dependencies between the control configuration properties and constructing a configuration property dependency graph based on the dependencies between the control configuration properties specifically includes: Identify the dependencies between the control configuration properties and import the dependencies between the control configuration properties into a preset directed acyclic graph to obtain an initial property dependency graph; The initial attribute dependency graph is read using a graph traversal algorithm, and the initial attribute dependency graph is parsed to determine whether there are dependency conflicts between the control configuration attributes. If there are dependency conflicts between the control configuration properties, the values ​​of the control configuration properties will be optimized. The initial attribute dependency graph is adjusted based on the optimized control configuration properties until the dependency conflict is eliminated, thus obtaining the attribute dependency graph.

2. The method for configuring input controls on a front-end page as described in claim 1, characterized in that, The steps of using a graph traversal algorithm to read the initial attribute dependency graph, parsing the initial attribute dependency graph, and determining whether there are dependency conflicts between the control configuration attributes specifically include: The graph traversal algorithm is used to traverse the nodes and edges of the initial attribute dependency graph, where nodes represent control configuration attributes and edges represent the logical relationships between control configuration attributes. The nodes and edges of the initial attribute dependency graph are parsed to obtain the control configuration attributes and the logical relationships between the control configuration attributes; Determine whether there is a dependency conflict between the control configuration properties based on the control configuration properties and the logical relationship between them.

3. The method for configuring input controls on a front-end page as described in claim 2, characterized in that, After the step of determining whether there is a dependency conflict between the control configuration properties based on the control configuration properties and the logical relationship between the control configuration properties, the method further includes: Determine whether the logical relationship between the configuration properties of the control is a preset conflict relationship, wherein the conflict relationship includes property mutual exclusion, logical error, hierarchical dependency, type or scope conflict; When there is one or more conflicting logical relationships between the control configuration properties, it is determined whether there is a dependency conflict between the control configuration properties.

4. The method for configuring input controls on a front-end page as described in claim 1, characterized in that, The step of formulating configuration priority rules based on the target control configuration information and the configuration attribute dependency graph specifically includes: Based on the decision tree algorithm, the control configuration information associated with the target control configuration information is identified in the configuration attribute dependency graph to obtain the associated control configuration information; Calculate the correlation value between the target control configuration information and the associated control configuration information; The associated control configuration information is sorted according to the associated degree value to obtain an associated control sequence; The configuration priority rule is formulated based on the sequence of associated controls, wherein the configuration priority rule determines the configuration order of the target control and associated controls.

5. The method for configuring input controls on a front-end page as described in claim 4, characterized in that, The step of rendering the target control configuration information according to the configuration priority rules in the preset control rendering engine to obtain the current front-end page specifically includes: The configuration order of the target input control and the associated control is determined according to the configuration priority rules; Parse the target control configuration information to obtain the control properties, layout properties, and style properties of the target input control; Based on the control properties, layout properties, and style properties of the target input control, the control rendering engine is invoked to generate the target input control on the current front-end page; Parse the configuration information of the associated control to obtain the control attributes, layout attributes, and style attributes configured for the associated control; Based on the control properties, layout properties, and style properties configured for the associated controls, and in accordance with the configuration order, the control rendering engine is invoked to generate the associated controls on the current front-end page.

6. A configuration device for input controls on a front-end page, characterized in that, A data dictionary table is established in the backend database to store the key-value pair information of the input control. In the frontend page, the required data dictionary information is obtained by requesting and calling the backend interface, and the data dictionary information is rendered to dynamically generate the input control. The device implements the steps of the input control configuration method of the frontend page as described in any one of claims 1 to 5, and the device specifically includes: The information classification module is used to classify and organize the control configuration information in the data dictionary table, and to obtain the control configuration attributes corresponding to each information classification. The attribute dependency module is used to analyze the dependencies between the configuration attributes of the controls and construct a configuration attribute dependency graph based on the dependencies between the configuration attributes of the controls. The information matching module is used to obtain the input control requirement information of the current front-end page, and match the target control configuration information in the data dictionary table according to the input control requirement information; The configuration rules module is used to formulate configuration priority rules based on the target control configuration information and the configuration attribute dependency graph. The control rendering module is used to render the target control configuration information according to the configuration priority rules in a preset control rendering engine to obtain the current front-end page.

7. A computer device, characterized in that, The device includes a memory and a processor, wherein the memory stores computer-readable instructions, and the processor executes the computer-readable instructions to implement the steps of the input control configuration method for a front-end page as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the input control configuration method for the front-end page as described in any one of claims 1 to 5.

Images