Low-code configuration efficiency improving system based on HTTP interface drive

Abstract

The invention discloses a low-code configuration efficiency improving system based on HTTP interface driving, relates to the technical field of low-code development, and aims to solve the technical problem of low efficiency caused by lack of a unified mechanism in component and HTTP interface association configuration in a low-code platform, comprising a low-code platform designer module and a special designer module, and a low-code construction platform module. The special designer module is connected with the low-code platform designer module and comprises an interface selection and acquisition unit, an interface data structure analysis unit, a data mapping engine unit, a rendering component matching unit, a configuration preview and generation unit and a standardized data source storage unit. According to the invention, through deep integration of a special designer and an HTTP management platform, and in combination with an interface automatic analysis and data automatic mapping mechanism, a traditional manual configuration process is replaced. Automatic conversion from input parameters to form configuration and from output parameters to display component configuration is realized.

Description

Technical Field

[0001] This invention relates to the field of low-code development technology, and more specifically, to a low-code configuration efficiency improvement system based on HTTP interface drivers. Background Technology

[0002] In the current wave of digital transformation sweeping the globe, enterprises are placing higher demands on the efficiency, flexibility, and cost control of application development. Low-code development technology has emerged and quickly become a focus of industry attention. With its core features such as visual drag-and-drop operation and graphical configuration interface, low-code platforms break away from the strong reliance on specialized technical skills inherent in traditional code development, significantly lowering the technical threshold for application development and effectively shortening project delivery cycles. They have been widely applied in various scenarios, including enterprise internal management systems, customer relationship management, and business process automation.

[0003] However, in actual enterprise application development, the integration efficiency of low-code platforms with existing backend systems still faces significant bottlenecks, especially in the configuration of components and HTTP (Hypertext Transfer Protocol) interfaces. Existing technical solutions reveal numerous problems that urgently need to be addressed. Currently, mainstream low-code platforms still rely heavily on manual operations by developers when handling the connection between components and HTTP interfaces. Specifically, after selecting a target component, developers need to manually configure the component's data source to point to a specific HTTP interface, manually write the relevant code for interface calls, manually set the parameter configuration of the interface's input and output parameters, and map the response data returned by the interface to the component's display properties one by one. More importantly, different types of components (such as tables, forms, description lists, etc.) lack a unified interface configuration mechanism, requiring each component to undergo a repetitive configuration process. In view of this, we propose a low-code configuration efficiency improvement system based on HTTP interface-driven architecture. Summary of the Invention

[0004] The purpose of this invention is to overcome the shortcomings of the prior art, adapt to the needs of reality, and provide a low-code configuration efficiency improvement system based on HTTP interface driver, so as to solve the technical problem of low efficiency caused by the lack of a unified mechanism for the configuration of components and HTTP interfaces in the current low-code platform.

[0005] To solve the above technical problems, the present invention provides the following technical solution: a low-code configuration efficiency improvement system based on HTTP interface driver, including a low-code platform designer module, a special designer module, and a low-code platform building module; The special designer module is connected to the low-code platform designer module and is used to respond to the activation command and execute the interface configuration process. It includes an interface selection and acquisition unit, an interface data structure parsing unit, a data mapping engine unit, a rendering component matching unit, a configuration preview and generation unit, and a standardized data source storage unit. The interface selection and acquisition unit is used to obtain an interface list and detailed definition information of the selected interface from an external HTTP management platform; The interface data structure parsing unit is connected to the interface selection and acquisition unit, and is used to parse the detailed definition information and extract the structured description of the interface's request parameters and response data. The data mapping engine unit is connected to the interface data structure parsing unit and is used to map the parsed request parameter structure to the configuration of the front-end query form and the response data structure to the configuration of the data display component according to the preset mapping rules. The rendering component matching unit is connected to the data mapping engine unit and is used to match the corresponding front-end rendering component for each form item in the query form configuration according to the data type of the request parameters. The configuration preview and generation unit is connected to the data mapping engine unit and the rendering component matching unit, respectively, and is used to generate the configuration preview interface and send and store the final standardized configuration data to the standardized data source storage unit.

[0006] Preferably, the low-code platform designer module is used to provide a visual development interface, receive user selection operations on target components, and send an activation command to the special designer module in response to user trigger operations on associated data interfaces.

[0007] Preferably, the low-code platform module includes a runtime environment unit and a rendering engine unit; The runtime environment unit is connected to the standardized data service unit and is used to call the standardized data service unit to obtain standardized configuration data during application runtime.

[0008] Preferably, the rendering engine unit is used to perform rendering based on the acquired standardized configuration data, specifically including: Based on the query form configuration obtained from the mapping and the matching rendering component type, the corresponding form elements are generated on the interface; Based on the data table column configuration obtained from the mapping, dynamically render the table header and data rows; Generate and bind the pagination controller based on the pagination configuration obtained from the mapping.

[0009] Preferably, the standardized data service unit is connected to the standardized data source storage unit to provide a data access interface.

[0010] Preferably, the interface selection and acquisition unit is configured as follows: Supports fuzzy search, advanced filtering, and categorized viewing via the interface; Supports API version management to allow selection of different API versions; Provides interface testing functionality to verify the availability of the interface and the data return format.

[0011] Preferably, the interface data structure parsing unit is specifically configured to parse interface definition files conforming to the OpenAPI specification to extract detailed information including parameter names, parameter locations, data types, whether they are required, and data structure definitions.

[0012] Preferably, the pre-defined mapping rules within the data mapping engine unit include: Map the array fields representing the data list in the interface response data to the column configuration of the data table component; Map the field representing the total number of pages in the API response data to the total number of items configured in the pagination control.

[0013] Preferably, the rendering component matching unit is configured to match the form item with the rendering component based on a predefined matching rule, which is defined as follows: When the data type of the request parameter is a string and contains an enumeration value attribute, a dropdown selector component is matched for the corresponding form item; When the data type is a boolean value, the switch component is matched; When the data type is string and there are no non-enumerated special attributes, it matches the input box component and can support multi-line text or password formats based on the subtype; When the data type is numeric, it matches the numeric input box component and supports configuration of integers, decimals, and range limits; When the data type is date, it matches the date picker component and supports date range selection and timestamp conversion; When the data type is an object, nested form components are matched to automatically generate subforms with their attributes for rendering; When the data type is an array, it matches dynamic table or list components and supports adding, deleting, modifying, and querying array items.

[0014] Preferably, the configuration preview and generation unit is configured to provide real-time differential rendering technology, configuration version management, difference comparison and configuration verification mechanism.

[0015] Compared with the prior art, the beneficial effects of the present invention are: 1. This invention deeply integrates a specialized designer with an HTTP management platform, combining automatic interface parsing and automatic data mapping mechanisms to replace the traditional manual configuration process. Specifically, the interface selection and retrieval unit implements intelligent caching management of interface metadata, reducing the time consumption caused by repeated requests. This allows developers to quickly obtain target interfaces and push interfaces that meet component requirements, avoiding invalid filtering. The data mapping engine unit, based on a rule engine mapping framework, supports dynamic rule loading and hot updates, achieving automated conversion of input parameters to form configurations and output parameters to display component configurations. This solves the problem of low efficiency caused by the lack of a unified mechanism for configuring components and HTTP interfaces in low-code platforms.

[0016] 2. This invention also utilizes an interface data structure parsing unit to accurately parse interface documents of specifications such as Swagger and OpenAPI, comprehensively extracting structured information such as parameter names, data types, and nesting relationships, thus avoiding errors caused by manual parameter entry from the source. The data mapping engine unit employs a transaction mechanism to ensure consistency in the mapping process, while supporting multi-level mapping at the field, structure, and business levels, effectively solving problems such as inconsistent parameter names and mismatched data types. The rendering component matching unit combines preset parameter types with rendering component mapping rules to intelligently match the optimal rendering component, further ensuring the accuracy of the configuration.

[0017] 3. This invention also automatically identifies component data requirements through a component feature analysis engine, intelligently displays operation entry points, and adapts to different user and project scenarios with context awareness capabilities. Developers do not need to deeply understand the underlying configuration rules and interface call logic; they only need to complete component selection and interface association through a visual interface. Simultaneously, the system constructs a unified interface association mechanism, ensuring that different types of components follow a consistent configuration process. This avoids the learning burden caused by differentiated configurations, allowing new developers to quickly get started, significantly lowering the technical threshold and improving the platform's usability and adaptability. Attached Figure Description

[0018] Figure 1 This is a schematic diagram of the overall modular structure of the system of the present invention; Figure 2 This is a schematic diagram of the core business process interaction of the present invention. Detailed Implementation

[0019] Example: Figures 1 to 2 As shown, the present invention relates to a low-code configuration efficiency improvement system based on HTTP interface driver, including a low-code platform designer module, a special designer module, a standardized data source storage unit, a standardized data service unit, and a low-code building platform module; The low-code platform designer module provides a visual development interface, receives user selections of target components, and responds to user triggering of the "associated data interface" by sending activation commands to the special designer module. Specifically, this module serves as the user interaction entry point, employing a micro-frontend architecture based on Web Components, supporting multi-framework integration, and providing a visual drag-and-drop interface. The low-code platform designer module internally manages the component lifecycle, including component instantiation, state management, and destruction. When users interact with components in the design canvas, the module ensures a WYSIWYG effect through a real-time rendering engine. Simultaneously, it automatically identifies the data requirements of components through a component feature analysis engine. This identification process is based on predefined data binding identifiers and event listener configurations in the component's metadata, dynamically detecting component configuration requirements and intelligently displaying the "Associated Data Interface" entry in the property panel. The module also integrates context-aware capabilities, adaptively adjusting the interface layout based on project type and user role to ensure precise interaction and consistent user experience.

[0020] The special designer module is connected to the low-code platform designer module and is used to respond to activation commands and execute the interface configuration process. It includes an interface selection and acquisition unit, an interface data structure parsing unit, a data mapping engine unit, a rendering component matching unit, and a configuration preview and generation unit. Specifically, upon receiving the activation command, the module establishes a secure connection with the HTTP management platform via the OAuth 2.0 protocol to ensure the security of interface access. The various sub-units within the module communicate loosely via a message bus, improving the system's maintainability and scalability.

[0021] The interface selection and acquisition unit implements an intelligent caching strategy. This unit supports fuzzy search and advanced filtering of interfaces. Based on a multi-dimensional interface evaluation system, including interface stability, performance indicators, and document completeness, this unit generates a personalized recommendation list. It also combines collaborative filtering and content filtering to ensure the accuracy of interface selection and provides interface quality evaluation functions, including response time statistics, success rate monitoring, and other indicator displays. This is used to obtain the interface list and detailed definition information of the selected interfaces from an external HTTP management platform. Specifically, this unit communicates with the API interface of the HTTP management platform to obtain a list of HTTP interfaces available to the current user or project. The interface list includes basic information such as interface name, description, URL, and request method, making it convenient for developers to select. Implementation details include: The designer supports API search, filtering, and categorized viewing, making it easy for developers to quickly locate target APIs; Supports API version management, allowing developers to select different versions of APIs for configuration; Provides interface testing functionality to verify the availability of the interface and the basic data return format.

[0022] The interface data structure parsing unit is connected to the interface selection and retrieval unit. It is used to parse detailed definition information and extract a structured description of the interface's request parameters and response data. The specific workflow is as follows: Once the developer selects a specific HTTP interface, this unit automatically calls the parser to perform deep parsing of the interface. The parsing process includes: Parse the Swagger / OpenAPI documentation or other API description files for the API; Extract the input parameter information of the interface, including parameter name, data type, whether it is required, default value, description, etc. Extract the output parameter information of the interface, including data structure, field types, nesting relationships, etc.; Analyze the validation rules and business constraints of the parameters.

[0023] In terms of implementation details, the parser supports multiple interface document formats, such as Swagger 2.0 and OpenAPI 3.0. For interfaces without standard documentation, the system provides a function to manually supplement the data structure. The interface data structure parsing unit is specifically used to parse interface definition files that conform to the OpenAPI specification to extract detailed information including parameter names, parameter positions, data types, whether they are required, and data structure definitions.

[0024] The data mapping engine unit, connected to the interface data structure parsing unit, is used to map the parsed request parameter structure to the configuration of the front-end query form according to preset mapping rules, and to map the response data structure to the configuration of the data display component. The specific mapping logic depends on the component type. For table components: Map the API input parameters to the configuration data of the query form; Map the data list in the API output parameters to the column configuration data of a table; Map the pagination information in the API output parameters to the configuration data of the pagination control.

[0025] For form components: Map the API input parameters to configuration data for form fields; Map the API output parameters to the processing logic configuration after form submission.

[0026] For the description list component: Map the interface output parameters to configuration data for the description items.

[0027] Implementation details: The mapping process fully considers the hierarchical relationship of fields, supporting the mapping of nested objects and arrays. For complex data structures, the system automatically generates appropriate nested components. The data mapping engine unit has a built-in rule-based mapping framework that supports dynamic rule loading and hot updates. The mapping process uses a transaction mechanism to ensure the consistency of configuration generation. The engine also supports intelligent recognition of complex nested structures and business semantics, realizing multi-level mapping at the field, structure, and business levels. The pre-defined mapping rules within the data mapping engine unit include: Map the array fields representing the data list in the interface response data to the column configuration of the data table component; Map the field representing the total number of pages in the API response data to the total number of items configured in the pagination control.

[0028] The rendering component matching unit, connected to the data mapping engine unit, is used to match the corresponding front-end rendering component for each form item in the query form configuration according to the data type of the request parameters. Its core matching logic is shown in Table 1 below, which is a table of parameter types and rendering component mapping rules. Table 1. Parameter Type and Rendering Component Mapping Rules

[0029] The specific meanings of Table 1, the parameter type and rendering component mapping rule table, are as follows: When the data type of the request parameter is string and contains an enumeration value attribute, match the dropdown selector component for the corresponding form item; When the data type is a boolean value, the switch component is matched; When the data type is string and there are no non-enumerated special attributes, it matches the input box component and can support multi-line text or password formats based on the subtype; When the data type is numeric, it matches the numeric input box component and supports configuration of integers, decimals, and range limits; When the data type is date, it matches the date picker component and supports date range selection and timestamp conversion; When the data type is an object, nested form components are matched to automatically generate subforms with their attributes for rendering; When the data type is an array, it matches dynamic table or list components and supports adding, deleting, modifying, and querying array items.

[0030] This systematic matching mechanism ensures the accuracy, efficiency, and optimal performance of form configurations and components.

[0031] The configuration preview and generation unit is connected to the data mapping engine unit and the rendering component matching unit, respectively. It is used to generate the configuration preview interface and send and store the final standardized configuration data to the standardized data source storage unit. Specifically, the configuration preview and generation unit provides real-time differential rendering technology, re-rendering only the changed parts, significantly improving preview performance. The unit supports configuration version management and difference comparison, making it easy for users to track configuration change history, while integrating a verification mechanism to ensure the integrity and correctness of the generated configuration; The standardized data source storage unit adopts a distributed storage architecture, supporting versioned management and compressed storage of configuration data to ensure data efficiency and security. The unit implements data encryption and access control, and guarantees data reliability through regular backup and recovery mechanisms. A standardized data service unit, connected to a standardized data source storage unit, is used to provide a data access interface; Specifically, the standardized data service unit serves as a data access middleware layer, providing high-performance API interfaces, supporting concurrent access and load balancing. The unit integrates a caching mechanism to optimize frequently accessed data, reduce response latency, and simultaneously implement real-time notification of data changes to ensure the consistency of configuration data.

[0032] Low-code platform modules, including runtime environment units and rendering engine units; The runtime environment unit is connected to the standardized data service unit and is used to call the standardized data service unit during application runtime to obtain standardized configuration data; The rendering engine unit, integrated with the runtime environment unit, is used to automatically generate query forms, automatically render data tables, and automatically bind pagination controls based on the acquired standardized configuration data. When the rendering engine unit performs rendering based on standardized configuration data, it is specifically used for: Based on the query form configuration obtained from the mapping and the matching rendering component type, generate the corresponding form element at the specified location on the interface; Based on the data table column configuration obtained from the mapping, dynamically render the table header and data rows; Generate and bind the pagination controller based on the pagination configuration obtained from the mapping.

[0033] Specifically, the rendering engine unit automatically generates the user interface based on configuration data, enabling dynamic rendering of query forms, data tables, and pagination controls. The unit employs an incremental update strategy, re-rendering only the changed data portions to ensure smooth interface responsiveness. The engine also supports adaptive layout, optimizing display effects according to different device screen sizes.

[0034] The embodiments disclosed in this invention are preferred embodiments, but are not limited thereto. Those skilled in the art can easily understand the spirit of this invention based on the above embodiments and make different extensions and variations, but as long as they do not depart from the spirit of this invention, they are all within the protection scope of this invention.

Claims

1. A low-code configuration efficiency improvement system based on HTTP interface driver, characterized in that, It includes a low-code platform designer module, a special designer module, and a low-code platform building module; The special designer module is connected to the low-code platform designer module and is used to respond to activation commands and execute the interface configuration process. It includes an interface selection and acquisition unit, an interface data structure parsing unit, a data mapping engine unit, a rendering component matching unit, a configuration preview and generation unit, and a standardized data source storage unit. The interface selection and acquisition unit is used to obtain an interface list and detailed definition information of the selected interface from an external HTTP management platform; The interface data structure parsing unit is connected to the interface selection and acquisition unit, and is used to parse the detailed definition information and extract the structured description of the interface's request parameters and response data. The data mapping engine unit is connected to the interface data structure parsing unit and is used to map the parsed request parameter structure to the configuration of the front-end query form and the response data structure to the configuration of the data display component according to the preset mapping rules. The rendering component matching unit is connected to the data mapping engine unit and is used to match the corresponding front-end rendering component for each form item in the query form configuration according to the data type of the request parameters. The configuration preview and generation unit is connected to the data mapping engine unit and the rendering component matching unit, respectively, and is used to generate the configuration preview interface and send and store the final standardized configuration data to the standardized data source storage unit.

2. The low-code configuration efficiency improvement system based on HTTP interface driver according to claim 1, characterized in that, The low-code platform designer module provides a visual development interface, receives user selection operations on target components, and sends activation commands to the special designer module in response to user trigger operations on associated data interfaces.

3. The low-code configuration efficiency improvement system based on HTTP interface driver according to claim 1, characterized in that, The low-code platform module includes a runtime environment unit and a rendering engine unit; The runtime environment unit is connected to the standardized data service unit and is used to call the standardized data service unit to obtain standardized configuration data during application runtime.

4. The low-code configuration efficiency improvement system based on HTTP interface driver according to claim 3, characterized in that, The rendering engine unit is used to perform rendering based on the acquired standardized configuration data, specifically including: Based on the query form configuration obtained from the mapping and the matching rendering component type, the corresponding form elements are generated on the interface; Based on the data table column configuration obtained from the mapping, dynamically render the table header and data rows; Generate and bind the pagination controller based on the pagination configuration obtained from the mapping.

5. A low-code configuration efficiency improvement system based on HTTP interface driver according to claim 3, characterized in that, The standardized data service unit is connected to the standardized data source storage unit to provide a data access interface.

6. A low-code configuration efficiency improvement system based on HTTP interface driver according to claim 1, characterized in that, The interface selection and acquisition unit is configured as follows: Supports fuzzy search, advanced filtering, and categorized viewing via the interface; Supports API version management to allow selection of different API versions; Provides interface testing functionality to verify the availability of the interface and the data return format.

7. A low-code configuration efficiency improvement system based on HTTP interface driver according to claim 1, characterized in that, The interface data structure parsing unit is specifically configured to parse interface definition files that conform to the OpenAPI specification in order to extract detailed information including parameter names, parameter positions, data types, whether they are required, and data structure definitions.

8. A low-code configuration efficiency improvement system based on HTTP interface driver according to claim 1, characterized in that, The pre-defined mapping rules within the data mapping engine unit include: Map the array fields representing the data list in the interface response data to the column configuration of the data table component; Map the field representing the total number of pages in the API response data to the total number of items configured in the pagination control.

9. A low-code configuration efficiency improvement system based on HTTP interface driver according to claim 1, characterized in that, The rendering component matching unit is configured to match form items with rendering components based on predefined matching rules, which are defined as follows: When the data type of the request parameter is a string and contains an enumeration value attribute, a dropdown selector component is matched for the corresponding form item; When the data type is a boolean value, the switch component is matched; When the data type is string and there are no non-enumerated special attributes, it matches the input box component and can support multi-line text or password format according to the subtype; When the data type is numeric, it matches the numeric input box component and supports configuration of integers, decimals, and range limits; When the data type is date, it matches the date picker component and supports date range selection and timestamp conversion; When the data type is an object, nested form components are matched to automatically generate subforms with their attributes for rendering; When the data type is an array, it matches dynamic table or list components and supports adding, deleting, modifying, and querying array items.

10. A low-code configuration efficiency improvement system based on HTTP interface driver according to claim 1, characterized in that, The configuration preview and generation unit is configured to provide real-time differential rendering technology, configuration version management, difference comparison and configuration verification mechanism.

Images