Construction method and device of query page, storage medium and electronic equipment

Abstract

The invention discloses a construction method and device of a query page, a storage medium and electronic equipment, and relates to the technical field of man-machine interaction interface design. The method comprises the steps that a user request is received, and the user request is used for changing a plurality of query conditions currently displayed in a display page or newly adding query conditions in the display page; a query condition configuration list is displayed in the runtime page, the query condition configuration list comprises N preset query conditions, and N is an integer larger than 1; according to the user request, multiple target query conditions meeting the user request are determined from a query condition configuration list, and the multiple target query conditions represent query conditions needing to be displayed to the user after responding to the user request; and rendering the runtime page according to the plurality of target query conditions to obtain a target query page. The technical problems of high repeatability and low efficiency of the creation process of the query page in the prior art are solved.

Description

Technical Field

[0001] The present application relates to the technical field of human-computer interaction interface design, and in particular to a method, device, storage medium and electronic device for constructing a query page. Background Art

[0002] In human-computer interaction design, especially in the field of information retrieval and data query, quickly and flexibly constructing query conditions is the key to achieving efficient data screening and information acquisition. Query pages usually have query conditions for different elements to obtain corresponding query results. Traditional query page designs often provide static input interfaces for specific query elements, such as text input boxes, selection boxes, or sliders. These interfaces have fixed display forms, input types, and parameter configurations during design, and cannot be flexibly adjusted according to actual needs.

[0003] Specifically, when users need to perform complex queries based on multiple factors, such as on e-commerce websites, users want to search based on multiple dimensions such as product category, price range, sales location, user reviews, etc., each query factor not only involves different input devices (for example, product category requires a drop-down selection box, while price range may require a numeric slider), but may also contain specific configuration details, such as the default value of the input device, optional comparison operators (such as >, <, =), and input order, etc. Whenever the user needs a different query factor, a new page needs to be recreated. It is impossible to flexibly and quickly create a page corresponding to the configuration based on the required query factor, and the new creation process involves a lot of repetitive work. Simply changing the name of a query parameter or the input type will create a new query page.

[0004] The root cause of these problems lies in the complexity of query parameter configuration and the duplication of page creation. There are different types of query parameters, each type corresponds to a different input, and the input has different configuration parameters, such as default values ​​and user modifiability. At the same time, in order to display different query conditions, it is often necessary to create multiple similar but different query pages. This way of creating query pages is not only inefficient and wastes storage resources, but also affects the operating efficiency of the application.

[0005] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0006] The present application provides a query page construction method, device, storage medium and electronic device to at least solve the technical problems of high repetitiveness and low efficiency in the query page creation process in the prior art.

[0007] According to one aspect of the present application example, a method for constructing a query page is provided, including: receiving a user request, wherein the user request is used to change multiple query conditions currently displayed in a display page or to add a new query condition in the display page; displaying a query condition configuration list in a runtime page, wherein the query condition configuration list includes N preset query conditions, wherein N is an integer greater than 1; determining multiple target query conditions that meet the user request from the query condition configuration list according to the user request, wherein the multiple target query conditions represent query conditions that need to be displayed to the user after responding to the user request; rendering the runtime page according to the multiple target query conditions to obtain a target query page, wherein the target query page is used to centrally display the multiple target query conditions in one page.

[0008] Optionally, the query condition configuration list is obtained by the following steps: obtaining N query parameters; performing configuration operations on the N query parameters respectively to obtain N metadata corresponding to the N query parameters, wherein the metadata is used to characterize the attributes of the query parameters; determining N preset query conditions based on the N metadata; and determining the query condition configuration list based on the N preset query conditions.

[0009] Optionally, the configuration operation includes at least any one of the following operations: a first operation, wherein the first operation is used to configure the input type of the query parameter; a second operation, wherein the second operation is used to configure the input format of the query parameter; a third operation, wherein the third operation is used to configure the relationship between the query parameter and the target query value, wherein the target query value is content input by the user; a fourth operation, wherein the fourth operation is used to configure the default value according to the query parameter; and a fifth operation, wherein the fifth operation is used to configure the display order of the query parameters on the page.

[0010] Optionally, N preset query conditions are determined based on N metadata, including: configuring a target identifier for each metadata to obtain N target identifiers, wherein the target identifier is used to identify and reference query parameters corresponding to the metadata; determining a preset query condition based on each metadata and the target identifier corresponding to the metadata to obtain N preset query conditions.

[0011] Optionally, after determining the query condition configuration list according to N preset query conditions, the query page construction method also includes: configuring a generator, wherein the generator is used to perform format conversion on metadata and target identifiers; performing data conversion processing on the metadata and target identifiers in each preset query condition in the query condition configuration list according to the generator and preset rules to obtain first data, wherein the first data is data that can be stored and queried by the server; and storing the first data in the server.

[0012] Optionally, multiple target query conditions that meet the user request are determined from the query condition configuration list based on the user request, including: extracting multiple target parameters from the user request, wherein the target parameters are used to characterize identifiers of query parameters displayed by the user request; detecting whether each target parameter is the same as a target identifier of each preset query condition in the query condition configuration list; and when it is detected that the target parameter is the same as the target identifier of any preset query condition, using the preset query condition as a target query condition.

[0013] Optionally, a runtime page is rendered according to multiple target query conditions to obtain a target query page, including: configuring a converter, wherein the converter is used to convert metadata in the target query conditions into data required by a preset format; performing data format conversion processing on the target query conditions according to the converter to obtain second data, wherein the second data is data that can be recognized and rendered by the page; and rendering the runtime page according to the second data to obtain the target query page.

[0014] According to another aspect of the present application, a query page construction device is also provided, including: a receiving unit, receiving a user request, wherein the user request is used to change multiple query conditions currently displayed in the display page or to add a new query condition in the display page; a display unit, displaying a query condition configuration list in the runtime page, wherein the query condition configuration list includes N preset query conditions; a determination unit, determining multiple target query conditions that meet the user request from the query condition configuration list according to the user request, wherein the multiple target query conditions represent query conditions that need to be displayed to the user after responding to the user request; a processing unit, rendering the runtime page according to the multiple target query conditions to obtain a target query page, wherein the target query page is used to centrally display multiple target query conditions in one page.

[0015] According to another aspect of the present application, a computer-readable storage medium is provided, wherein a computer program is stored in the computer-readable storage medium, wherein when the computer program runs, the device where the computer-readable storage medium is located executes the above-mentioned query page construction method.

[0016] According to another aspect of the present application, an electronic device is also provided, wherein the electronic device includes one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs are executed by one or more processors, the one or more processors execute the above-mentioned query page construction method.

[0017] In the present application, by receiving a user request, wherein the user request is used to change multiple query conditions currently displayed in a display page or to add a new query condition in the display page, a query condition configuration list is displayed in a runtime page, wherein the query condition configuration list includes N preset query conditions, wherein N is an integer greater than 1, and then multiple target query conditions that meet the user request are determined from the query condition configuration list according to the user request, wherein the multiple target query conditions represent query conditions that need to be displayed to the user after responding to the user request, and finally the same runtime page is rendered according to the multiple target query conditions to obtain the query page required by the user, wherein the target query page is used to centrally display multiple target query conditions in one page, thereby achieving the purpose of dynamically constructing a query page on the same page according to the query condition configuration list, thereby achieving the technical effect of reducing the repeatability of query page construction and improving the low efficiency of query page construction, thereby solving the technical problems of high repeatability and low efficiency in the creation process of query pages in the prior art. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0019] Figure 1 is a flowchart of an optional method for constructing a query page according to an embodiment of the present application;

[0020] Figure 2 It is a schematic diagram of an optional query page construction device according to an embodiment of the present application. DETAILED DESCRIPTION

[0021] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0022] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0023] It should also be noted that the information and data collected by this application are authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data comply with the relevant laws, regulations and standards of the relevant regions, take necessary confidentiality measures, do not violate public order and good customs, and provide corresponding operation portals for users to choose to authorize or refuse. For example, an interface is set up between this system and relevant users or institutions. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or institution through the interface, and obtain relevant information after receiving the consent information fed back by the aforementioned user or institution.

[0024] According to an embodiment of the present application, an embodiment of a method for constructing a query page is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0025] It should be noted that an intelligent construction system is used as the execution subject of the query page construction method of the embodiment of the present application. It is understandable that the query page construction method provided in the embodiment of the present application can also be executed by other systems or devices, and the embodiment of the present application does not specifically limit this.

[0026] Figure 1 is a flowchart of an optional method for constructing a query page according to an embodiment of the present application, such as Figure 1 As shown, the method comprises the following steps:

[0027] Step S101, receiving a user request.

[0028] In step S101, the user requests to change a plurality of query conditions currently displayed on a display page or to add a new query condition to the display page.

[0029] Optionally, the user request involves changing the currently displayed query condition or adding a new query condition.

[0030] Optionally, the user sends a signal to the system through interface operations (such as clicking, sliding, inputting, etc.) to express his or her need to modify or add query conditions. For example, the user may want to add a "sales location" query element to the existing query conditions, or adjust the scope of the "price range" query element.

[0031] Step S102: displaying a query condition configuration list in the runtime page.

[0032] In step S102, the query condition configuration list includes N preset query conditions.

[0033] In step S102, N is an integer greater than 1.

[0034] Optionally, during the runtime initialization phase, a list of query condition configurations that have been configured is displayed.

[0035] Step S103: determining multiple target query conditions that meet the user request from the query condition configuration list according to the user request.

[0036] In step S103 , the plurality of target query conditions represent query conditions that need to be displayed to the user after responding to the user request.

[0037] Optionally, when a user issues a request to modify or add a query condition, the intelligent construction system receives and understands the user request, and intelligently selects query conditions that match the user request from a preset query condition configuration list based on parameter information in the request.

[0038] Optionally, the target query condition refers to a set of query conditions that are screened out from a preset query condition configuration list by the system according to a user request and that need to be displayed to the user.

[0039] Step S104, rendering the runtime page according to the multiple target query conditions to obtain the target query page.

[0040] In step S104, the target query page is used to centrally display multiple target query conditions in one page.

[0041] Optionally, after determining the target query condition, the intelligent construction system re-renders the runtime page to reflect the latest query condition configuration, and finally generates the target query page required by the user.

[0042] Optionally, when the user modifies the query conditions of the query page, re-rendering is performed on the same running page to obtain the corresponding query page.

[0043] It can be known from the contents of step S101 to step S104 that in the present application, by receiving a user request, wherein the user request is used to change multiple query conditions currently displayed in the display page or to add a new query condition in the display page, a query condition configuration list is displayed in the runtime page, wherein the query condition configuration list includes N preset query conditions, wherein N is an integer greater than 1, and then multiple target query conditions that meet the user request are determined from the query condition configuration list according to the user request, wherein the multiple target query conditions represent the query conditions that need to be displayed to the user after responding to the user request, and finally the same runtime page is rendered according to the multiple target query conditions to obtain the query page required by the user, wherein the target query page is used to centrally display multiple target query conditions in one page, thereby achieving the purpose of dynamically constructing a query page on the same page according to the query condition configuration list, thereby achieving the technical effect of reducing the repeatability of query page construction and improving the low efficiency of query page construction, thereby solving the technical problems of high repeatability and low efficiency in the creation process of query pages in the prior art.

[0044] In an optional embodiment, the intelligent construction system first obtains N query parameters, then performs configuration operations on the N query parameters respectively to obtain N metadata corresponding to the N query parameters, wherein the metadata is used to characterize the attributes of the query parameters, and then determines N preset query conditions based on the N metadata, and finally determines a query condition configuration list based on the N preset query conditions.

[0045] Optionally, the intelligent construction system first obtains multiple query parameters, wherein the multiple query parameters refer to a set of parameters that are pre-set in the system and can be used to construct query conditions. For example, for an online shopping platform, the query parameters may include product name, price range, sales location, etc., and then configures the multiple query parameters respectively. Through this operation, each query parameter is assigned a set of detailed configuration information to form its own metadata, and then determines multiple preset query conditions based on the multiple metadata, wherein the preset query condition is a set of query elements that have been configured based on the metadata. The metadata of each query parameter is converted into a preset query condition, which includes detailed information such as the type, input method, and logical relationship of the parameter. Finally, a query condition configuration list is determined based on the multiple preset query conditions, wherein the query condition configuration list is a summary and organization of all preset query conditions, which arranges various query conditions in a certain logical order to form a complete query condition set. This configuration list is the basis for the system runtime interface display and query logic processing, which allows the system to quickly extract and display the corresponding query conditions according to user requests.

[0046] Optionally, the intelligent construction system constructs a set of unified and reusable parameter configuration information by abstracting the properties of query parameters. Specifically, query parameter metadata is data that describes and configures query parameters, which includes multiple properties and characteristics of query parameters, which are the basis for displaying and interacting with query parameters on the user interface.

[0047] Optionally, the entry point for query parameter configuration is the query condition page, which is mainly used to manage all query condition configurations. The query condition configuration page is accessed through the setting button. Due to the large number of query parameters and the hierarchical relationship between some of them, the intelligent construction system lays out the query parameters through a tree structure. The query condition configuration page is mainly responsible for managing all query parameter configurations. The left side of the page is a tree structure, and the right side is a form format. All configured query parameters will be displayed above the right form. Here you can quickly view and edit the configured query parameters. By clicking on the query parameter, you can switch to the corresponding configuration. Click the close button on the right side of the query parameter name after the configuration is completed to delete the query parameter configuration. When you click or check the query parameter, you can set the corresponding configuration in the right form, such as query name, input, default value, edit, etc. You can also add query parameters by checking the tree structure on the left, and click the tree node to continue loading the next level of nodes.

[0048] From the above content, it can be seen that the intelligent construction system configures metadata for each query parameter, and finally obtains a query condition configuration list based on multiple metadata. Among them, the query parameter metadata defines a set of detailed properties and behaviors for each query parameter, which not only includes the basic information of the query parameter (such as type and default value), but also covers the details of the parameter in interface display and logical processing (such as input and comparison operator). These metadata provide the basis for the dynamic construction and display of query conditions, so that the system can quickly generate and adjust the query page according to these configuration information during runtime to meet the user's diverse query needs, while avoiding the tediousness and inefficiency of repeatedly creating and maintaining query pages in traditional methods.

[0049] In an optional embodiment, the configuration operation includes at least any one of the following operations: a first operation, wherein the first operation is used to configure the input type of the query parameter; a second operation, wherein the second operation is used to configure the input format of the query parameter; a third operation, wherein the third operation is used to configure the relationship between the query parameter and the target query value, wherein the target query value is content input by the user; a fourth operation, wherein the fourth operation is used to configure the default value according to the query parameter; and a fifth operation, wherein the fifth operation is used to configure the display order of the query parameters on the page.

[0050] Optionally, the configuration operation includes but is not limited to configuring the type, inputter, comparison operator, default value, and display order of each query parameter.

[0051] Optionally, the first operation is to configure the type of query parameter. The query parameter type refers to the data type represented by the parameter, for example, it can be text, number, date, Boolean value, etc. Different data types determine the input and processing methods of the parameter, and also affect the element selection of the user interface, such as text input, number input, drop-down selection, date selection, etc. By configuring the query parameter type, the intelligent construction system can select the most appropriate input method for each parameter, thereby improving the accuracy and efficiency of user input. For example, for the query parameter of the product name, text input may be selected, and for the query parameter of the price range, a digital slider may be selected.

[0052] Optionally, the second operation is to configure an input device for query parameters, where the input device refers to a specific component on the user interface for inputting or selecting query parameter values, such as a text input box, a number input box, a drop-down selection menu, a multiple-selection box, a sliding bar, a date selector, etc. The selection and configuration of the input device directly affects the user's interactive experience with the system and the convenience of data input.

[0053] Optionally, the third operation is to configure a comparison operator for the query parameters. The comparison operator refers to a logical operator used to compare the query parameter value with the value in the data set during the query process. Common comparison operators include equal to (=), not equal to (!=), greater than (>), less than (<), and contained (in). By configuring the comparison operator, the system can adjust the logic of the query conditions according to user needs to ensure the accuracy of the query results. For example, if the user enters a price range when querying a product, the system needs to configure a corresponding comparison operator (such as "greater than or equal to" and "less than or equal to") to ensure that the query results contain all qualified products.

[0054] Optionally, the fourth operation is to configure the default value of the query parameter. The default value refers to the value preset by the system when the user does not explicitly enter or select the query parameter value. The configuration of the default value helps to provide an initial query state, reduce the user's operation burden, and quickly generate basic query results. For example, for the query parameter of the date range, the system may configure the default value to "the most recent week", so that when the user opens the query page, the data within the most recent week is automatically displayed.

[0055] Optionally, the fifth operation is to configure the display order of the query parameters, which refers to the order in which the query parameters are arranged on the user interface. A reasonable display order can guide users to set query conditions according to a logical process, improving the fluency and efficiency of user operations. For example, placing the "product category" query parameter at the top of the page as the first step of the user's query, followed by parameters such as "price range" and "sales location", this order helps users quickly locate and set key query conditions, so as to find the required information faster.

[0056] From the above content, it can be seen that the intelligent construction system realizes efficient dynamic construction and display of query conditions by configuring the input type, format, relationship with user input value, default value and display order of query parameters. This not only improves the flexibility, accuracy and efficiency of the query, but also significantly optimizes the user experience and system performance.

[0057] In an optional embodiment, the intelligent construction system configures a target identifier for each metadata to obtain N target identifiers, wherein the target identifier is used to identify and reference the query parameters corresponding to the metadata, and then determines a preset query condition according to each metadata and the target identifier corresponding to the metadata to obtain N preset query conditions.

[0058] Optionally, the intelligent construction system obtains metadata of all query parameters from the configuration period. The metadata includes key attributes such as the query parameter type, input, comparison operator, default value and display order, and then automatically configures a unique identifier for the metadata of each query parameter. This identifier serves as an internal reference to the query parameter, ensuring the uniqueness of each query parameter in the system, facilitating the dynamic construction of pages and the processing of query conditions in the subsequent runtime period. Next, the system determines multiple preset query conditions based on the metadata of each query parameter and the corresponding identifier.

[0059] From the above content, it can be seen that the intelligent construction system configures an identifier for each query parameter. The identifier is used as a unique identity proof of the query parameter. It can uniquely identify and distinguish each query parameter in the system, and provides a basis for subsequently storing the query conditions on the server. The system stores different query parameter configuration information on the server, and each configuration information is associated with the corresponding identifier. In this way, when needed, the system can quickly locate and extract specific query parameter configurations without traversing the entire database or configuration list, thereby improving the efficiency of data retrieval and configuration management.

[0060] In an optional embodiment, the intelligent construction system is configured to obtain a generator, wherein the generator is used to perform format conversion on metadata and target identifiers, and then perform data conversion processing on the metadata and target identifiers in each preset query condition in the query condition configuration list according to the generator and preset rules to obtain first data, wherein the first data is data that can be stored and queried by the server, and the first data is stored in the server.

[0061] Optionally, when the user completes the editing of query parameters during the configuration period, including configurations such as input type, format, default value, display order, etc., and clicks the Save button, the configuration generator in the intelligent construction system is activated. The task of the configuration generator is to convert the query parameter metadata and identifiers configured by the user into specific format data according to preset query parameter abstract rules to adapt to the storage and query requirements of the server, and then store the converted metadata and identifiers in the server.

[0062] Optionally, the preset rule, i.e. the query parameter abstraction rule mentioned above, is a mechanism for analyzing and standardizing query parameters. It identifies and extracts the common features and configuration elements of these query parameters by conducting in-depth analysis of most common query conditions (such as text, numbers, dates, etc.) and a small number of special query conditions (such as geographic location, multiple selections, etc.). Specifically, the abstraction rule models multiple dimensions from the query parameter name, inputter (i.e., the interface component for users to input data), inputter configuration details (such as limiting the number of characters, selection range, etc.), query parameter default values, and more advanced query condition configurations (such as whether to disable the parameter, whether to edit the parameter, display or hide the parameter, selected comparison operator, etc.). The establishment of this rule enables the system to uniformly handle different types of query parameters and convert them into a unified format that the server can understand and store.

[0063] Optionally, the configuration generator will query the metadata of the query parameters one by one according to the query parameter abstraction rules and perform format conversion. This process includes extracting the information in the metadata and converting it into the format required by the server storage, such as JSON (JavaScript Object Notation, a lightweight data exchange format), XML (eXtensibleMarkup Language) or other customized data structures. The converted specific format data not only contains the basic information of the query parameters, but also contains the advanced configuration information set by the user, such as disabling a parameter, editing parameter values, selecting comparison operators, etc. This information will be used to build preset query conditions and dynamically generate and adjust the query interface at runtime. The converted specific format data will be marked and stored according to the corresponding identifier according to the conditions of the page. The identifier is a label used to uniquely identify the query condition configuration, which enables the server to quickly retrieve and apply the corresponding query condition according to the identifier. By storing the query condition configuration data in the server, the system realizes the persistence of configuration information, ensuring that the query condition configuration can still be accurately retrieved and applied even in different sessions or time points.

[0064] From the above content, we can see that the intelligent construction system converts query parameter metadata into specific format data according to query parameter abstraction rules through the configuration generator, and then uses the corresponding identifier to store this data to the server. This process not only standardizes the configuration of query parameters, but also optimizes data storage and retrieval, providing a solid foundation for the rapid construction and display of query conditions during runtime.

[0065] In an optional embodiment, the intelligent construction system extracts multiple target parameters from the user request, wherein the target parameter is used to characterize the identifier of the query parameter displayed by the user request, and detects whether each target parameter is the same as the target identifier of each preset query condition in the query condition configuration list. When it is detected that the target parameter is the same as the target identifier of any preset query condition, the preset query condition is used as a target query condition.

[0066] Optionally, the intelligent construction system obtains specific parameters through url (Uniform Resource Locator) to obtain corresponding query condition list data, converts it into the configuration of the corresponding query condition using a query parameter converter, and then organizes and adapts it into data that can be rendered by the page.

[0067] Optionally, the intelligent construction system parses multiple target parameters from the user request. These target parameters are selected or input by the user in the query application and are used to identify the specific query conditions that the user wants to see in the query interface. The essence of the target parameter is the target identifier of the query parameter, which is the basis for the system to identify and locate the query condition configuration. Next, each target parameter extracted from the user request will be detected and matched with the target identifier in the query condition configuration list generated and stored in the server during the configuration period. This process compares the target parameter with the target identifier of the preset query condition to identify whether the query parameter mentioned in the user request exists in the configuration list. If during the detection process, the intelligent construction system finds that a target parameter in the user request matches the target identifier of a preset query condition in the configuration list, then the preset query condition will be identified as the target query condition, which means that the system can quickly locate and identify the query parameters that the user wants to display and the configuration information of these parameters according to the user request. Once the target query condition is determined, the intelligent construction system will dynamically build the query interface according to the metadata and data conversion rules in these target query conditions. The interface will only display query parameters that match the target query condition, avoiding unnecessary parameter loading and improving the response speed and user experience of the query interface.

[0068] From the above content, it can be seen that the intelligent construction system realizes the rapid identification of query conditions and the dynamic construction of query interface by extracting target parameters from user requests and matching them with preset query conditions, which greatly improves the query efficiency and user experience, ensures that the system can quickly identify and locate query parameters in user requests, reduces the time and complexity of query condition construction, and improves the efficiency of query page construction. Users can freely select and combine query parameters according to their needs, and the system can flexibly generate and display the corresponding query interface to meet diverse query needs.

[0069] In an optional embodiment, the intelligent construction system is configured to obtain a converter, wherein the converter is used to convert metadata in the target query condition into data required by a preset format, and then the target query condition is converted into a data format according to the converter to obtain second data, wherein the second data is data that can be recognized and rendered by the page, and finally the runtime page is rendered according to the second data to obtain the target query page.

[0070] Optionally, the intelligent construction system obtains the corresponding query list data saved from the server using an identifier during runtime, converts it through a query parameter converter (the above-mentioned converter) to form corresponding query condition data, and then organizes it into the data format of the query page for rendering, and finally obtains the target query page.

[0071] Optionally, the query parameter converter is tasked with converting the metadata in the query configuration list into specific query condition data. This process may include parsing the metadata and generating corresponding query logic based on the type and configuration of the query parameters, such as setting comparison operators, handling default values, etc.

[0072] Optionally, after the intelligent construction system obtains the target query conditions that meet the user's request from the server through a specific identifier, it converts the data format of the target query conditions through a converter to obtain processed data, and then further processes and organizes the processed data into a format that can be understood and rendered by the query page. Finally, the intelligent construction system uses the organized data to render the query page, and the page dynamically generates and displays the query form based on the received data, including user interface elements such as input boxes, drop-down menus, check boxes, and their layout, style, and interaction logic.

[0073] From the above content, it can be seen that the intelligent construction system realizes the dynamic construction and display of query pages, which not only improves the flexibility and response speed of the system, but also improves the efficiency of query page construction, while reducing the repetitive operations of page construction. There is no need to create different query pages due to different query conditions, which will cause performance problems and application volume problems.

[0074] According to another aspect of an embodiment of the present application, a schematic diagram of a query page construction device is also provided. Figure 2 is a schematic diagram of an optional query page construction device according to an embodiment of the present application, such as Figure 2 As shown, the query page construction device includes: a receiving unit 201, a display unit 202, a determination unit 203, and a processing unit 204.

[0075] Optionally, a receiving unit 201 is used to receive a user request, wherein the user request is used to change multiple query conditions currently displayed in a display page or to add a new query condition in the display page; a display unit 202 is used to display a query condition configuration list in a runtime page, wherein the query condition configuration list includes N preset query conditions, wherein N is an integer greater than 1; a determination unit 203 is used to determine, according to the user request, from the query condition configuration list multiple target query conditions that meet the user request, wherein the multiple target query conditions represent query conditions that need to be displayed to the user after responding to the user request; a processing unit 204 is used to render the runtime page according to the multiple target query conditions to obtain a target query page, wherein the target query page is used to centrally display multiple target query conditions in one page.

[0076] Optionally, the display unit 202 includes: a first acquisition subunit, a first configuration subunit, a first determination subunit, and a second determination subunit. The first acquisition subunit is used to acquire N query parameters; the first configuration subunit is used to configure the N query parameters respectively to obtain N metadata corresponding to the N query parameters, wherein the metadata is used to characterize the attributes of the query parameters; the first determination subunit is used to determine N preset query conditions according to the N metadata; and the second determination subunit is used to determine a query condition configuration list according to the N preset query conditions.

[0077] Optionally, the first configuration subunit includes: a first operation, wherein the first operation is used to configure the input type of the query parameter; a second operation, wherein the second operation is used to configure the input format of the query parameter; a third operation, wherein the third operation is used to configure the relationship between the query parameter and the target query value, wherein the target query value is content input by the user; a fourth operation, wherein the fourth operation is used to configure a default value based on the query parameter; and a fifth operation, wherein the fifth operation is used to configure the display order of the query parameters on the page.

[0078] Optionally, the first determination subunit includes: a first configuration module and a first determination module. The first configuration module is used to configure a target identifier for each metadata to obtain N target identifiers, wherein the target identifier is used to identify and reference query parameters corresponding to the metadata; the first determination module is used to determine a preset query condition according to each metadata and the target identifier corresponding to the metadata to obtain N preset query conditions.

[0079] Optionally, the second determination subunit includes: a second configuration module, a first processing module, and a first storage module. The second configuration module is used to configure a generator, wherein the generator is used to perform format conversion on metadata and target identifiers; the first processing module is used to perform data conversion processing on metadata and target identifiers in each preset query condition in the query condition configuration list according to the generator and preset rules to obtain first data, wherein the first data is data that can be stored and queried by the server; and the first storage module is used to store the first data in the server.

[0080] Optionally, the determination unit 203 includes: a first extraction subunit, a first detection subunit, and a first processing subunit. The first extraction subunit is used to extract multiple target parameters from the user request, wherein the target parameter is used to characterize the identifier of the query parameter displayed by the user request; the first detection subunit is used to detect whether each target parameter is the same as the target identifier of each preset query condition in the query condition configuration list; the first processing subunit is used to, when it is detected that the target parameter is the same as the target identifier of any preset query condition, use the preset query condition as a target query condition.

[0081] Optionally, the processing unit 204 includes: a second configuration subunit, a second processing subunit, and a third processing subunit. The second configuration subunit is used to configure a converter, wherein the converter is used to convert metadata in the target query condition into data required by a preset format; the second processing subunit is used to convert the data format of the target query condition according to the converter to obtain second data, wherein the second data is data that can be recognized and rendered by the page; and the third processing subunit is used to render the runtime page according to the second data to obtain the target query page.

[0082] According to another aspect of the present application, a computer-readable storage medium is provided, wherein a computer program is stored in the computer-readable storage medium, wherein when the computer program is executed, the device where the computer-readable storage medium is located executes the above-mentioned query page construction method.

[0083] According to another aspect of the present application, an electronic device is also provided, wherein the electronic device includes one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the above-mentioned query page construction method.

[0084] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0085] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0086] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0087] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0088] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0089] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0090] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for constructing a query page, characterized in that: include: Receiving a user request, wherein the user request is used to change a plurality of query conditions currently displayed in a display page or to add a new query condition in the display page; Displaying a query condition configuration list in the runtime page, wherein the query condition configuration list includes N preset query conditions, wherein N is an integer greater than 1; Determining, according to the user request, a plurality of target query conditions satisfying the user request from the query condition configuration list, wherein the plurality of target query conditions represent query conditions that need to be displayed to the user after responding to the user request; The runtime page is rendered according to the multiple target query conditions to obtain a target query page, wherein the target query page is used to centrally display the multiple target query conditions in one page.

2. The method for constructing a query page according to claim 1, characterized in that: The query condition configuration list is obtained by following the steps below: Get N query parameters; Performing configuration operations on the N query parameters respectively to obtain N metadata corresponding to the N query parameters, wherein the metadata is used to characterize the attributes of the query parameters; Determine N preset query conditions according to the N metadata; The query condition configuration list is determined according to the N preset query conditions.

3. The method for constructing a query page according to claim 2, characterized in that: The configuration operation includes at least one of the following operations: A first operation, wherein the first operation is used to configure an input type of the query parameter; A second operation, wherein the second operation is used to configure an input format of the query parameter; A third operation, wherein the third operation is used to configure a relationship between the query parameter and a target query value, wherein the target query value is content input by a user; A fourth operation, wherein the fourth operation is used to configure a default value according to the query parameter; A fifth operation, wherein the fifth operation is used to configure the display order of the query parameters on the page.

4. The method for constructing a query page according to claim 2, characterized in that: Determining the N preset query conditions according to the N metadata includes: Configuring a target identifier for each metadata to obtain N target identifiers, wherein the target identifier is used to identify and reference the query parameter corresponding to the metadata; A preset query condition is determined according to each metadata and a target identifier corresponding to the metadata, to obtain N preset query conditions.

5. The method for constructing a query page according to claim 4, characterized in that: After determining the query condition configuration list according to the N preset query conditions, the query page construction method further includes: The generator is configured to convert the metadata and the target identifier into a format; According to the generator and the preset rules, data conversion processing is performed on the metadata and the target identifier in each of the preset query conditions in the query condition configuration list to obtain first data, wherein the first data is data that can be stored and queried by the server; The first data is stored in a server.

6. The method for constructing a query page according to claim 4, characterized in that: Determining, according to the user request, a plurality of target query conditions satisfying the user request from the query condition configuration list includes: Extracting a plurality of target parameters from the user request, wherein the target parameters are used to represent identifiers of query parameters displayed by the user request; Detecting whether each of the target parameters is identical to a target identifier of each of the preset query conditions in the query condition configuration list; When it is detected that the target parameter is identical to a target identifier of any one of the preset query conditions, the preset query condition is used as a target query condition.

7. The method for constructing a query page according to claim 1, characterized in that: Rendering the runtime page according to the multiple target query conditions to obtain a target query page includes: A converter is configured, wherein the converter is used to convert the metadata in the target query condition into data required by a preset format; The converter performs data format conversion processing on the target query condition to obtain second data, wherein the second data is data that can be recognized and rendered by the page; The runtime page is rendered according to the second data to obtain the target query page.

8. A device for constructing a query page, characterized in that: include: A receiving unit, receiving a user request, wherein the user request is used to change a plurality of query conditions currently displayed in a display page or to add a new query condition in the display page; A display unit, which displays a query condition configuration list in a runtime page, wherein the query condition configuration list includes N preset query conditions; a determining unit, which determines, according to the user request, from the query condition configuration list, a plurality of target query conditions that satisfy the user request, wherein the plurality of target query conditions represent query conditions that need to be displayed to the user after responding to the user request; The processing unit renders the runtime page according to the multiple target query conditions to obtain a target query page, wherein the target query page is used to centrally display the multiple target query conditions in one page.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein when the computer program is executed, the device where the computer-readable storage medium is located executes the query page construction method according to any one of claims 1 to 7.

10. An electronic device, characterized in that: It includes one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the query page construction method described in any one of claims 1 to 7.

Images