Query page rendering methods, devices, equipment, storage media, and program products.

Through the collaborative mechanism of anchor identifiers and persistent configuration, dynamic condition rendering of enterprise-level backend query pages is realized, solving the problems of low query efficiency and high maintenance costs, and providing flexible condition layout and stable system upgrade capabilities.

CN123114469APending Publication Date: 2026-11-17YEELION ONLINE NETWORK TECH BEIJING
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611447422.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-17
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

When faced with multiple query conditions, the query page of the enterprise-level back-end management system cannot meet the different usage habits of different users, resulting in low query efficiency and high maintenance costs. The existing fixed layout solution requires frequent code modifications to adapt to business iterations.

Method used

Through the collaborative mechanism of anchor identifiers and persistent configuration, the runtime dynamic orchestration and rendering of query conditions are realized. Users can adjust the persistent and collapsed conditions according to their own preferences. The configuration data is decoupled from the page template, and the flexible layout and persistent storage of conditions are supported.

Benefits of technology

It improves the flexibility and efficiency of the query page, reduces development and maintenance costs, ensures the stability and ease of use of the system during business iterations, and allows users to customize the condition layout to improve operational efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123114469A_ABST
    Figure CN123114469A_ABST
Patent Text Reader

Abstract

This application relates to a method, apparatus, device, storage medium, and program product for querying page rendering. The method includes: constructing an available condition identifier set based on anchor identifiers of input page components in the acquired default slot content; if the target historical condition configuration is successfully read, filtering out a valid persistent condition set and a valid additional condition set from the historical configuration based on the available condition identifier set; generating rendering instructions for each condition item in the valid condition set based on the current collapsed / expanded state of the valid additional condition set; for each rendering instruction, finding an input page component whose condition identifier matches the condition item corresponding to the rendering instruction, controlling the visual arrangement position by applying a style layout attribute corresponding to the arrangement number in the rendering instruction to the input page component, and controlling the display or hiding by applying a display / hidden control instruction corresponding to the display / hidden flag in the rendering instruction. This method can balance system usability, robustness, and query efficiency.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a query page rendering method, apparatus, device, storage medium, and program product. Background Technology

[0002] The query function of an enterprise-level backend management system is a core entry point for daily business operations. As business complexity increases, a single query page often carries more than ten query conditions. Organizing and presenting these conditions within limited screen space has become a common challenge for front-end engineers. Currently, the most common approach is to directly write the type, tag, and default value of all query conditions into the page template. The number, order, and grouping of conditions are fixed in the code by the developer, and users cannot adjust them at runtime. If business requirements change, the developer must modify the template code and redeploy, and each query page maintains its own independent list of conditions. However, this fixed layout cannot meet the diverse usage habits of different users. Each business iteration requires modifying repetitive code on multiple pages, resulting in high maintenance costs. Users face the same condition arrangement every time they visit, and frequent users must repeatedly search for their target conditions among a large number of low-priority conditions, leading to low operational efficiency. Summary of the Invention

[0003] Therefore, it is necessary to provide a query page rendering method, apparatus, device, storage medium, and program product that can balance system usability, robustness, and query efficiency to address the aforementioned technical problems.

[0004] Firstly, this application provides a method for rendering a query page, the method comprising:

[0005] The default slot content of the query page is obtained through the browser panel component of the query page to be rendered; the default slot content includes multiple currently valid input page components, each of which carries an anchor identifier;

[0006] Construct an available condition identifier set; the available condition identifier set contains anchor identifiers of the plurality of input page components;

[0007] The target historical condition configuration of the query page is read from the persistent storage space; the target historical condition configuration includes a historical persistent condition set and a historical more condition set; each condition entry in the historical persistent condition set is set to be displayed by default; each condition entry in the historical more condition set is set to be collapsed and hidden by default; each condition entry contains a condition identifier.

[0008] If the read is successful, then from the historical persistent condition set and the historical more condition set, the condition entries whose condition identifiers fall into the available condition identifier set are filtered out to obtain the effective persistent condition set and the effective more condition set.

[0009] Based on the current collapsed / expanded state of the effective more condition set, a corresponding rendering instruction is generated for each condition entry in the effective resident condition set and the effective more condition set; the rendering instruction includes an arrangement number and a show / hide flag;

[0010] For each rendering instruction, an input page component matching the condition identifier of the condition entry corresponding to the rendering instruction is found from the default slot content. The visual arrangement position of the found input page component is controlled by applying a style layout attribute corresponding to the arrangement number in the rendering instruction, and its display or hiding on the query page is controlled by applying a display control instruction corresponding to the display flag in the rendering instruction.

[0011] In one embodiment, the method further includes:

[0012] If the read fails, the condition configuration array is obtained through the browser panel component; the condition configuration array contains multiple condition entries, each of which contains a condition identifier and a persistent identifier; the persistent identifier is used to indicate whether the condition entry in the condition configuration array is displayed persistently by default or collapsed and hidden by default.

[0013] Based on the persistent identifier, the multiple condition entries are divided into an initial persistent condition set and an initial more condition set; each condition entry in the initial persistent condition set is set to be displayed persistently by default; each condition entry in the initial more condition set is set to be collapsed and hidden by default.

[0014] From the initial resident condition set and the initial more condition set, condition entries whose condition identifiers fall into the available condition identifier set are selected to obtain the effective resident condition set and the effective more condition set.

[0015] In one embodiment, each condition entry in the valid persistent condition set is stored sequentially in the persistent condition array of the browser panel component; each condition entry in the valid more condition set is stored sequentially in the more condition array of the browser panel component; the method further includes:

[0016] In response to the user's grouping, migration and / or sequential dragging operations on the condition entries in the configuration pop-up window of the query page, the resident condition array and the more condition array are updated in real time;

[0017] In response to the user's save configuration command, each condition entry in the resident condition array and the more condition array is serialized to obtain the serialized string corresponding to the query page;

[0018] The page path of the query page and the component name of the browser panel component are concatenated to generate the storage key of the query page;

[0019] The serialized string is associated with the storage key and stored in the persistent storage space.

[0020] In one embodiment, reading the target historical condition configuration of the query page from persistent storage includes:

[0021] The page path of the query page and the component name of the browser panel component are concatenated to generate the storage key of the query page;

[0022] Retrieve the serialized string associated with the storage key from the persistent storage space;

[0023] If the serialized string exists and is in the correct format, then the serialized string is parsed.

[0024] If the parsing is successful, it is determined that the target historical condition configuration of the query page has been successfully read, and the parsing result of the serialized string is used as the target historical condition configuration;

[0025] If the serialized string does not exist, the serialized string exists but the format is abnormal, or the parsing fails, then it is determined that the target historical condition configuration of the query page has failed to be read.

[0026] In one embodiment, each condition entry in the valid persistent condition set is stored sequentially in the persistent condition array of the browser panel component; each condition entry in the valid more condition set is stored sequentially in the more condition array of the browser panel component.

[0027] Based on the current collapsed / expanded state of the effective more condition set, the process generates corresponding rendering instructions for each condition entry in the effective persistent condition set and the effective more condition set, including:

[0028] Traverse each condition entry in the resident condition array according to the storage order, assign an incrementing sequence number starting from 0 to each condition entry in the resident condition array, and set its corresponding visibility flag to always visible, thereby obtaining the rendering instructions corresponding to each condition entry in the resident condition array.

[0029] Traverse each condition entry in the more condition array according to the storage order. Based on the arrangement number assigned to the last condition entry in the resident condition array, continue to assign an incremental arrangement number to each condition entry in the more condition array, and set its corresponding visibility flag to be synchronized with the current folded / expanded state of the effective more condition set, so as to hide when folded and be visible when expanded, and obtain the rendering instructions corresponding to each condition entry in the more condition array.

[0030] In one embodiment, each of the input page components in the default slot content serves as a direct child node of the default slot of the query page, constituting a virtual node tree of the query page; the anchor identifier is the data-id anchor attribute value of each child node in the virtual node tree, used to declare the global uniqueness of the child node in the virtual node tree.

[0031] In one embodiment, the style layout attribute is the order attribute of the browser layout engine; the visibility control instruction is the v-show instruction of the browser layout engine; the v-show instruction controls the display and hiding of the real DOM node by keeping the real DOM node of the input page component in the page DOM tree of the query page and only updating the style visibility attribute of the real DOM node, so that the real DOM node is not destroyed and rebuilt during the display switching and sorting adjustment process.

[0032] Secondly, this application provides a query page rendering apparatus, the apparatus comprising:

[0033] The acquisition module is used to acquire the default slot content of the query page through the browser panel component of the query page to be rendered; the default slot content includes multiple currently valid input page components, each of which carries an anchor identifier;

[0034] A construction module is used to construct an available condition identifier set; the available condition identifier set contains anchor identifiers of the plurality of input page components;

[0035] The reading module is used to read the target historical condition configuration of the query page from the persistent storage space; the target historical condition configuration includes a historical persistent condition set and a historical more condition set; each condition entry in the historical persistent condition set is set to be displayed by default; each condition entry in the historical more condition set is set to be collapsed and hidden by default; each condition entry contains a condition identifier.

[0036] The filtering module is used to filter out the condition entries whose condition identifiers fall into the available condition identifier set from the historical persistent condition set and the historical more condition set, respectively, if the reading is successful, to obtain the effective persistent condition set and the effective more condition set.

[0037] The generation module is used to generate corresponding rendering instructions for each condition entry in the effective persistent condition set and the effective more condition set based on the current collapsed / expanded state of the effective more condition set; the rendering instructions include an arrangement number and a show / hide flag;

[0038] The rendering module is used to, for each rendering instruction, search the default slot content for an input page component that matches the condition identifier of the condition entry corresponding to the rendering instruction, control the visual arrangement position of the found input page component on the query page by applying a style layout attribute corresponding to the arrangement number in the rendering instruction, and control its display or hiding on the query page by applying a display control instruction corresponding to the display flag in the rendering instruction.

[0039] Thirdly, this application provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the various method embodiments of this application.

[0040] Fourthly, this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps in the various method embodiments of this application.

[0041] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the steps in the various method embodiments of this application.

[0042] The aforementioned query page rendering method, device, equipment, storage medium, and program products break away from the traditional code-fixed layout of query conditions, significantly improving the flexibility of enterprise-level backend query pages. By introducing a collaborative mechanism of anchor identifiers and persistent configuration, this solution achieves runtime dynamic orchestration and rendering of query conditions. Users can freely adjust persistent and collapsed conditions according to their usage frequency and preferences, making high-frequency conditions readily accessible and solving the pain point of low query efficiency caused by slow searching due to numerous conditions. Simultaneously, the decoupling of configuration data and page templates eliminates the need to modify repetitive code across multiple pages during business iterations; only configuration data needs to be maintained for unified effectiveness, greatly reducing development and maintenance costs. Furthermore, this application's solution fully considers the validity and fault tolerance of condition configurations, ensuring page stability during system upgrades or field changes, balancing system usability, robustness, and query efficiency. Attached Figure Description

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

[0044] Figure 1 This is an application environment diagram of a query page rendering method in one embodiment;

[0045] Figure 2 This is a flowchart illustrating a page rendering method in one embodiment;

[0046] Figure 3 Here is a system architecture diagram of the query system in one embodiment;

[0047] Figure 4 This is a schematic diagram illustrating the configuration declaration receiving and tag mapping establishment process in one embodiment;

[0048] Figure 5 This is a schematic diagram of the local storage configuration reading and format verification process in one embodiment.

[0049] Figure 6 This is a schematic diagram illustrating the process of conditional filtering and determining the set of available condition identifiers in one embodiment;

[0050] Figure 7 This is a schematic diagram of the sorting calculation and rendering state generation process in one embodiment;

[0051] Figure 8 This is a schematic diagram of the virtual node identifier anchor point routing and content rendering process in one embodiment;

[0052] Figure 9 This is a schematic diagram of the data transformation link from condition declaration to rendering in one embodiment;

[0053] Figure 10 This is a schematic diagram of the persistent condition display and query operation interface in one embodiment;

[0054] Figure 11 This is a schematic diagram illustrating the operation of expanding more conditions and completing a combined query in one embodiment;

[0055] Figure 12 This is a schematic diagram illustrating drag-and-drop sorting and cross-category migration conditions in a pop-up window in one embodiment.

[0056] Figure 13 This is a schematic diagram of the final rendering effect of the query page after personalized configuration has been completed in one embodiment;

[0057] Figure 14 This is a schematic diagram comparing the configuration effectiveness recovery before and after a version iteration in one embodiment;

[0058] Figure 15 This is a schematic diagram illustrating the automatic execution of condition validity verification and silent filtering by the system after version iteration in one embodiment;

[0059] Figure 16 This is a schematic diagram illustrating how a user can seamlessly use the restored valid configuration in a new version of the page, as shown in one embodiment.

[0060] Figure 17 This is a schematic diagram showing the overall linkage of innovative points in one embodiment;

[0061] Figure 18 This is a structural block diagram of a query page rendering apparatus in one embodiment;

[0062] Figure 19 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0063] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0064] The query page rendering method provided in this application can be applied to, for example... Figure 1 In the application environment shown, terminal 102 communicates with server 104 via a network. The data storage system can be set up separately and can store the data that server 104 needs to process. The data storage system can be integrated into server 104 or placed in the cloud or on other servers. Terminal 102 can be, but is not limited to, various desktop computers, laptops, smartphones, tablets, vehicle terminals, etc. Server 104 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, cloud security, host security and other network security services, CDN, and basic cloud computing services such as big data and artificial intelligence platforms. Terminal 102 and server 104 can be directly or indirectly connected via wired or wireless communication, which is not limited herein.

[0065] Terminal 102 can obtain the default slot content of the query page from server 104 through the browser panel component of the query page to be rendered; the default slot content includes multiple currently valid input page components, each input page component carrying an anchor identifier; terminal 102 can construct an available condition identifier set; the available condition identifier set contains anchor identifiers of multiple input page components; read the target historical condition configuration of the query page from persistent storage space; the target historical condition configuration includes a historical persistent condition set and a historical more condition set; each condition item in the historical persistent condition set is set to be displayed by default; each condition item in the historical more condition set is set to be collapsed and hidden by default; the condition item contains a condition identifier; if the reading is successful, terminal 102 can retrieve the historical persistent condition set and the historical more condition set respectively. In the set of items, condition entries whose condition identifiers fall into the set of available condition identifiers are filtered out to obtain the valid resident condition set and the valid more condition set. Based on the current folded / expanded state of the valid more condition set, the terminal 102 can generate corresponding rendering instructions for each condition entry in the valid resident condition set and the valid more condition set. The rendering instructions include an arrangement number and a show / hide flag. For each rendering instruction, the terminal 102 can search for an input page component that matches the condition identifier of the condition entry corresponding to the rendering instruction from the default slot content, and control its visual arrangement position on the query page by applying style layout attributes corresponding to the arrangement number in the rendering instruction to the found input page component, and control its display or hiding on the query page by applying show / hide control instructions corresponding to the show / hide flag in the rendering instruction.

[0066] It is understood that this embodiment does not impose any limitations on this. Figure 1 The application scenarios shown are for illustrative purposes only and are not limited to these.

[0067] In one embodiment, such as Figure 2 As shown, a query page rendering method is provided. This embodiment applies this method to... Figure 1 Taking the terminal in the example, the explanation includes the following steps:

[0068] Step 202: Obtain the default slot content of the query page through the browser panel component of the query page to be rendered; the default slot content includes multiple currently valid input page components, each of which carries an anchor identifier.

[0069] The query criteria panel component is a piece of front-end software code running in the browser. The default slot content is the actual query control (such as an input box or dropdown list) that the developer directly writes inside the component tag when calling the query criteria panel component. The anchor identifier is a globally unique attribute value (such as `data-id`) pre-set on each input-type page component in the slot. It is a unique identifier used by the query criteria panel component to accurately identify, locate, and match the actual control without deeply analyzing the internal structure of the query control.

[0070] Specifically, a browser runs on the terminal, and the browser panel component in the browser can receive the default slot content of the query page to be rendered from the outside. The default slot content includes multiple currently valid input page components, such as input boxes and dropdown lists.

[0071] Step 204: Construct a set of available condition identifiers; the set of available condition identifiers contains anchor identifiers for multiple input page components.

[0072] Specifically, the terminal can construct a set of available condition identifiers based on the anchor identifiers of each input page component contained in the default slot content. It can be understood that the set of available condition identifiers consists of the anchor identifiers of each input page component contained in the default slot content.

[0073] Step 206: Read the target historical condition configuration of the query page from the persistent storage space; the target historical condition configuration includes the historical persistent condition set and the historical more condition set; each condition entry in the historical persistent condition set is set to be displayed by default; each condition entry in the historical more condition set is set to be collapsed and hidden by default; the condition entry contains a condition identifier.

[0074] "Default persistent display" means the query result is displayed consistently on the search page by default. "Default collapsed and hidden" means the query result is collapsed and hidden by default, and only displayed when the query page is expanded. The condition identifier is a string used to uniquely identify a condition entry.

[0075] In one embodiment, the persistent storage space can be the browser's local persistent storage space.

[0076] In one embodiment, the persistent storage space can also be the terminal's local persistent storage space.

[0077] Step 208: If the reading is successful, then filter out the condition entries whose condition identifiers fall into the available condition identifier set from the historical resident condition set and the historical more condition set respectively, to obtain the effective resident condition set and the effective more condition set.

[0078] Among them, "the identifier falls into the available condition identifier set" means that there is an anchor identifier in the available condition identifier set that is consistent with the condition identifier.

[0079] In one embodiment, if the terminal successfully reads the target historical condition configuration of the query page from the persistent storage space, the terminal can filter out the condition entries whose condition identifiers fall into the available condition identifier set from the historical resident condition set to obtain a valid resident condition set, and filter out the condition entries whose condition identifiers fall into the available condition identifier set from the historical more condition set to obtain a valid more condition set.

[0080] Step 210: Based on the current collapsed / expanded state of the effective more condition set, generate corresponding rendering instructions for each condition entry in the effective resident condition set and the effective more condition set; the rendering instructions include an arrangement number and a visibility flag.

[0081] The current collapsed / expanded state includes both collapsed and expanded states. When the current collapsed / expanded state is collapsed, all condition entries in the "more valid conditions" set are set to be collapsed and hidden on the query page. When the current expanded / expanded state is expanded, all condition entries in the "more valid conditions" set are set to be expanded and displayed on the query page. The sequence number indicates the display position of the condition entry on the query page. The show / hide flag indicates whether the condition entry is shown or hidden on the query page. It can be understood that the show / hide flags corresponding to each condition entry in the "permanently visible" condition set are set to always be visible (persistent display); the show / hide flags corresponding to each condition entry in the "more valid conditions" set are set to be synchronized with the current collapsed / expanded state of the "more valid conditions" set, so that they are hidden when collapsed and visible when expanded.

[0082] Step 212: For each rendering instruction, find the input page component that matches the condition identifier of the condition entry corresponding to the rendering instruction from the default slot content, and control its visual arrangement position on the query page by applying style layout attributes corresponding to the arrangement number in the rendering instruction to the found input page component, and control its display or hiding on the query page by applying the display control instruction corresponding to the display flag in the rendering instruction.

[0083] Among them, the input page component that matches the condition identifier of the condition entry corresponding to the rendering instruction is one whose anchor identifier (such as data-id="orderNo") is consistent with the condition identifier (id="orderNo") of the condition entry corresponding to the rendering instruction.

[0084] The aforementioned query page rendering method breaks away from the traditional fixed code pattern for query condition layout, significantly improving the flexibility of enterprise-level backend query pages. By introducing a collaborative mechanism of anchor identifiers and persistent configuration, this solution achieves runtime dynamic orchestration and rendering of query conditions. Users can freely adjust persistent and collapsed conditions according to their usage frequency and preferences, making high-frequency conditions readily accessible and solving the pain point of low query efficiency caused by slow searching due to numerous conditions. Simultaneously, the decoupling of configuration data and page templates eliminates the need to modify repetitive code across multiple pages during business iterations; only configuration data needs to be maintained for unified effectiveness, greatly reducing development and maintenance costs. Furthermore, this application's solution fully considers the validity and fault tolerance of condition configurations, ensuring page stability during system upgrades or field changes, balancing system usability and robustness.

[0085] In one embodiment, the method further includes: if the reading fails, obtaining a condition configuration array through a browser panel component; the condition configuration array contains multiple condition entries, each condition entry containing a condition identifier and a persistent identifier; the persistent identifier is used to indicate whether the condition entries in the condition configuration array are displayed persistently by default or hidden by default; based on the persistent identifier, the multiple condition entries are divided into an initial persistent condition set and an initial more condition set; each condition entry in the initial persistent condition set is set to be displayed persistently by default; each condition entry in the initial more condition set is set to be hidden by default; and from the initial persistent condition set and the initial more condition set, condition entries whose condition identifiers fall into the available condition identifier set are filtered out to obtain a valid persistent condition set and a valid more condition set.

[0086] The condition configuration array is a structured data collection that is passed from the parent component outside the browser panel component to the browser panel component. It describes the initialization properties of all query conditions and is carried in the form of an array.

[0087] Specifically, if the terminal fails to read the target historical condition configuration from the persistent storage space, the terminal can receive an externally passed condition configuration array through the browser panel component. The condition configuration array contains multiple condition entries, each containing a condition identifier and a persistent identifier. The persistent identifier indicates whether the condition entry in the condition configuration array is displayed persistently by default or hidden by default. For each condition entry, if the persistent identifier indicates that the condition entry is displayed persistently by default, the terminal can assign the condition entry to the initial persistent condition set; if the persistent identifier indicates that the condition entry is hidden by default, the terminal can assign the condition entry to the initial more condition set. Furthermore, the terminal can filter out condition entries whose condition identifiers fall into the available condition identifier set from the initial persistent condition set to obtain a valid persistent condition set, and filter out condition entries whose condition identifiers fall into the available condition identifier set from the initial more condition set to obtain a valid more condition set.

[0088] In one embodiment, each array element (i.e. each condition entry) contains a condition identifier (id), a display label (label), and a permanent identifier (permanent).

[0089] In the above embodiments, when historical configuration reading fails, the default layout can be automatically parsed from the built-in conditional configuration array, and the persistent and collapsed areas can be intelligently divided based on the persistent identifier, while invalid fields are filtered out. This mechanism ensures that the page can still render normally when it is first loaded or when there is data error, ensuring the robustness of the system, and at the same time laying a data foundation for subsequent user-defined configurations.

[0090] In one embodiment, each condition item in the valid persistent condition set is stored sequentially in the persistent condition array of the browser panel component; each condition item in the valid more condition set is stored sequentially in the more condition array of the browser panel component; the method further includes: in response to the user's grouping migration and / or sequential dragging operation of condition items in the configuration pop-up of the query page, updating the persistent condition array and the more condition array in real time; in response to the user's save configuration instruction, serializing each condition item in the persistent condition array and the more condition array to obtain the serialized string corresponding to the query page; concatenating the page path of the query page and the component name of the browser panel component to generate the storage key of the query page; and associating the serialized string with the storage key and storing it in the persistent storage space.

[0091] In one embodiment, the string is serialized as JSON data.

[0092] In the above embodiments, through drag-and-drop and group migration operations, users can flexibly customize the layout and order of persistent and collapsed areas according to their personal habits, and the interactive feedback takes effect immediately. At the same time, a reliable persistent storage link is provided to serialize user-personalized configurations and associate them with page paths and component names, ensuring that the configurations are accurately loaded upon refresh or revisit.

[0093] In one embodiment, reading the target historical condition configuration of the query page from persistent storage includes: concatenating the page path of the query page and the component name of the browser panel component to generate a storage key for the query page; querying the serialized string associated with the storage key from persistent storage; if the serialized string exists and is in the correct format, parsing the serialized string; if parsing is successful, it is determined that the target historical condition configuration of the query page has been successfully read, and the parsing result of the serialized string is used as the target historical condition configuration; if the serialized string does not exist, exists but is in the wrong format, or parsing fails, it is determined that the target historical condition configuration of the query page has failed to be read.

[0094] In the above embodiments, pages and components are accurately associated through storage keys, ensuring accurate acquisition of configuration data. Simultaneously, this solution fully considers various abnormal scenarios such as missing data, abnormal formatting, and parsing failures, and formulates clear failure judgment and degradation strategies, effectively avoiding page rendering errors caused by corrupted or missing configuration data, and ensuring the system's high stability and robustness in complex operating environments.

[0095] In one embodiment, the condition entries in the effective persistent condition set are stored sequentially in the persistent condition array of the browser panel component; the condition entries in the effective more condition set are stored sequentially in the more condition array of the browser panel component; based on the current collapsed / expanded state of the effective more condition set, corresponding rendering instructions are generated for each condition entry in the effective persistent condition set and the effective more condition set, including: traversing each condition entry in the persistent condition array in storage order, assigning each condition entry in the persistent condition array an incrementing sequence number starting from 0, and setting its corresponding visibility flag to always visible, thereby obtaining the rendering instructions corresponding to each condition entry in the persistent condition array; traversing each condition entry in the more condition array in storage order, based on the sequence number assigned to the last condition entry in the persistent condition array, continuing to increment the sequence number assigned to each condition entry in the more condition array, and setting its corresponding visibility flag to synchronize with the current collapsed / expanded state of the effective more condition set, so as to be hidden when collapsed and visible when expanded, thereby obtaining the rendering instructions corresponding to each condition entry in the more condition array.

[0096] In one embodiment, if the effective persistent condition set = ["orderNo", "status"], the effective additional condition set = ["createTime"], and the current collapsed / expanded state = false, then the rendering instruction table consisting of multiple rendering instructions is [{id:"orderNo", order:0, visible:true}, {id:"status", order:1, visible:true}, {id:"createTime", order:2, visible:false}]. Here, `order` represents the sequence number; `visible` represents the visibility flag, where a value of `true` indicates that the corresponding condition item is visible, and a value of `false` indicates that the corresponding condition item is collapsed / hidden. It can be understood that the `visible` value for each condition item in the effective persistent condition set is always `true`.

[0097] In the above embodiments, the ordered array storage and sequential numbering mechanism provide a clear and definite instruction generation logic for rendering query conditions. Persistent conditions are always visible, and the linkage between more condition states and collapsing / expanding ensures the orderliness of the interface layout and the consistency of interaction. Simultaneously, ordered traversal and consecutive numbering guarantee the accurate restoration of the order after dragging and sorting, achieving stable and efficient rendering of user-defined layouts and improving system response performance and user experience smoothness.

[0098] In one embodiment, each input page component in the default slot content serves as a direct child node of the default slot panel of the query page, forming a virtual node tree for the query page; the anchor identifier is the data-id anchor attribute value of each child node in the virtual node tree, used to declare the global uniqueness of the child node in the virtual node tree.

[0099] In the above embodiments, a clear virtual node tree structure is constructed by setting input page components as direct child nodes (VNodes) of the panel's default slots. The data-id anchor attribute is used to declare a globally unique identifier, providing a precise and stable positioning basis for each conditional component. This design enables rendering instructions to efficiently match and manipulate corresponding components, achieving dynamic control and state synchronization of the conditional layout, and laying a solid technical foundation for the flexible and reliable operation of the entire query condition orchestration system.

[0100] In one embodiment, the style layout property is the order property of the browser layout engine; the visibility control directive is the v-show directive of the browser layout engine; the v-show directive controls the display and hiding of the real DOM node by keeping the real DOM node of the input page component in the page DOM tree of the query page, and only by updating the style visibility property of the real DOM node, so that the real DOM node is not destroyed and rebuilt during the display switching and sorting adjustment process.

[0101] In the above embodiments, lightweight layout control is achieved using the browser's native `order` and `v-show` directives. The `order` attribute efficiently adjusts the visual order, avoiding the overhead of DOM reflow; `v-show` ensures that no nodes are destroyed or rebuilt during frequent collapse, expansion, and sorting operations by preserving DOM nodes and switching styles to show or hide them, thereby reducing page repaint performance loss and ensuring smooth interaction and responsiveness.

[0102] In one embodiment, such as Figure 3As shown, the query system adopts a four-layer architecture: external interface layer, interaction layer, presentation layer, and data storage layer. The external interface layer is the entry point exposed by the browser panel component, responsible for receiving two types of data from the outside. One type is a condition configuration array, where developers declare all query conditions in array form. Each condition contains three fields: a unique identifier (condition identifier), a display label, and a persistent identifier indicating whether it is persistent. The browser panel component relies on this configuration to determine the initial grouping and display logic for each condition. The other type is node slots (default slot content). The parent component of the browser panel component places the actual input boxes, dropdown lists, date pickers, and other form components (input-type page components) into the default slots. Each component carries an anchor identifier corresponding to the condition identifier. The panel finds the corresponding component node through this anchor identifier, without needing to know the node's internal type or behavior. These two types of input together constitute the raw data source for the browser panel component's operation. The interaction layer is responsible for responding to user actions, translating user intent into state changes. It is divided into two sub-functions. The first is the expand / collapse control: the panel only displays persistent conditions by default. A toggle button at the top center allows switching between the two modes, with the button displaying the number of currently collapsed conditions in real time, allowing users to easily see how many conditions are hidden. The second is the configuration panel: clicking the settings button opens a pop-up window. This pop-up divides all conditions into two groups: a persistent area and a more advanced area, categorized by labels. Users can drag condition labels within the same group to adjust their order, or click the close button on a condition label to move it to another group. After completion, the configuration is saved. The presentation layer is the core bridge connecting data and the page, responsible for translating abstract categorized data into specific rendering instructions. It calculates two values ​​for each condition based on the current condition grouping state: arrangement position (arrangement number) and visibility (visibility indicator). The arrangement position determines the order of conditions on the page, controlled by the layout order attribute, without needing to move the physical position of nodes; visibility is determined by whether the condition is currently in collapsed or expanded mode. Persistent conditions are always displayed, while more advanced conditions are displayed based on the expanded state. After calculation, the presentation layer uses the unique identifier of each condition to accurately locate the corresponding real node from the slot and renders it to the specified position. The entire process is transparent and imperceptible to the internal workings of the node. The data storage layer is responsible for ensuring that the user's configuration is automatically restored after refreshing the page or logging in again, solving the problem of "having to reset every time." It consists of two parts: initialization and saving. Initialization occurs when the page loads: the component uses a combination of the page path and the component name as the unique storage key to read the previously saved group configuration (historical condition configuration) from the browser's local persistent storage space. Then, it verifies one by one whether each condition identifier still exists in the current version of the slot, filters out outdated conditions, and only restores the still valid configuration. If there is no local cache, the initial configuration passed in from outside is used directly.Saving occurs when the user clicks the save button in the configuration pop-up: the current group state is written to the local cache, and a reset operation clears the cache and returns to the initial state.

[0103] In one embodiment, such as Figure 4 As shown, the condition configuration array `conditions` can be represented as `conditions=[{id:"orderNo",label:"Order Number",permanent:true},{id:"status",label:"Status",permanent:true},{id:"createTime",label:"Creation Time",permanent:false}]`. Here, `permanent` being true indicates that the condition item is set to be displayed permanently by default, while `false` indicates that the condition item is hidden by default. Therefore, the initial set of permanent conditions can include condition items belonging to `orderNo` and `status`; the initial set of additional conditions can include condition items belonging to `creation Time`.

[0104] In one embodiment, such as Figure 5 As shown, the terminal can concatenate the page path of the query page and the component name of the browser panel component to generate the storage key of the query page; query the serialized string associated with the storage key from the persistent storage space; if the serialized string exists and is in the correct format, it is parsed; if the parsing is successful, it is determined that the target historical condition configuration of the query page has been successfully read, and the parsing result of the serialized string is used as the target historical condition configuration; if the serialized string does not exist, exists but is in the wrong format, or the parsing fails, it is determined that the target historical condition configuration of the query page has failed to be read.

[0105] In one embodiment, such as Figure 6As shown, if the read is successful, the terminal can filter out condition entries whose condition identifiers fall into the available condition identifier set from the historical persistent condition set and the historical more condition set, respectively, to obtain the valid persistent condition set and the valid more condition set. If the read fails, the condition configuration array is obtained through the browser panel component; the condition configuration array contains multiple condition entries, each containing a condition identifier and a persistent identifier; the persistent identifier is used to indicate whether the condition entries in the condition configuration array are displayed persistently by default or collapsed and hidden by default; based on the persistent identifier, the multiple condition entries are divided into the initial persistent condition set and the initial more condition set; each condition entry in the initial persistent condition set is set to be displayed persistently by default; each condition entry in the initial more condition set is set to be collapsed and hidden by default; condition entries whose condition identifiers fall into the available condition identifier set are filtered out from the initial persistent condition set and the initial more condition set, respectively, to obtain the valid persistent condition set and the valid more condition set.

[0106] In one embodiment, such as Figure 7 As shown, the condition entries in the valid persistent condition set are stored sequentially in the persistent condition array of the browser panel component; the condition entries in the valid more condition set are stored sequentially in the more condition array of the browser panel component. The terminal can iterate through the condition entries in the persistent condition array in storage order, assigning each condition entry an incrementing sequence number starting from 0, and setting its corresponding visibility flag to always visible, thus obtaining the rendering instructions corresponding to each condition entry in the persistent condition array. Then, it iterates through the condition entries in the more condition array in storage order, continuing to assign incrementing sequence numbers to each condition entry in the more condition array based on the sequence number assigned to the last condition entry in the persistent condition array, and setting its corresponding visibility flag to synchronize with the current collapsed / expanded state of the valid more condition set, so that it is hidden when collapsed and visible when expanded, thus obtaining the rendering instructions corresponding to each condition entry in the more condition array. The rendering instructions include the sequence number and the visibility flag.

[0107] In one embodiment, such as Figure 8 As shown, for each rendering instruction in the rendering instruction table, the input page component that matches the condition identifier of the condition entry corresponding to the rendering instruction is searched from the default slot content. The visual arrangement position of the found input page component is controlled by applying style layout attributes corresponding to the arrangement number in the rendering instruction, and the display or hiding of the component on the query page is controlled by applying display control instructions corresponding to the display flag in the rendering instruction.

[0108] In one embodiment, such as Figure 9As shown, the terminal can obtain the default slot content of the query page through the browser panel component of the query page to be rendered; the default slot content includes multiple currently valid input page components, each input page component carrying an anchor identifier; construct an available condition identifier set; the available condition identifier set contains anchor identifiers of multiple input page components; read the target historical condition configuration of the query page from the persistent storage space; the target historical condition configuration includes a historical persistent condition set and a historical more condition set; each condition item in the historical persistent condition set is set to be displayed by default; each condition item in the historical more condition set is set to be collapsed and hidden by default; the condition item contains a condition identifier; if the reading is successful, the condition identifiers falling into the available slots are filtered from the historical persistent condition set and the historical more condition set, respectively. The condition entries in the identifier set are used to obtain the valid persistent condition set and the valid more condition set. If the reading fails, the condition configuration array is obtained through the browser panel component. The condition configuration array contains multiple condition entries, each containing a condition identifier and a persistent identifier. The persistent identifier is used to indicate whether the condition entries in the condition configuration array are displayed persistently by default or collapsed and hidden by default. Based on the persistent identifier, the multiple condition entries are divided into an initial persistent condition set and an initial more condition set. Each condition entry in the initial persistent condition set is set to be displayed persistently by default. Each condition entry in the initial more condition set is set to be collapsed and hidden by default. From the initial persistent condition set and the initial more condition set, condition entries whose condition identifiers fall into the available condition identifier set are filtered out to obtain the valid persistent condition set and the valid more condition set. Each condition item in the valid persistent condition set is stored sequentially in the persistent condition array of the browser panel component; each condition item in the valid more condition set is stored sequentially in the more condition array of the browser panel component; in response to the user's grouping, migration and / or sequential dragging operations on the condition items in the configuration pop-up of the query page, the persistent condition array and the more condition array are updated in real time; in response to the user's save configuration command, each condition item in the persistent condition array and the more condition array is serialized to obtain the serialized string (JSON data) corresponding to the query page; the page path of the query page and the component name of the browser panel component are concatenated to generate the storage key of the query page; the serialized string and the storage key are associated and stored in the persistent storage space. Based on the current collapsed / expanded state of the effective more condition set, a corresponding rendering instruction is generated for each condition entry in the effective resident condition set and the effective more condition set. The rendering instruction includes an arrangement number and a show / hide flag. For each rendering instruction, an input page component that matches the condition identifier of the condition entry corresponding to the rendering instruction is searched from the default slot content. The visual arrangement position of the found input page component on the query page is controlled by applying style layout attributes corresponding to the arrangement number in the rendering instruction, and its display or hiding on the query page is controlled by applying show / hide control instructions corresponding to the show / hide flag in the rendering instruction.

[0109] To facilitate understanding of the technical solution of this application, scenarios A and B are used as examples. Scenario A: Daily query operation (permanent conditions are displayed first). Scenario B: Seamless configuration restoration after system version iteration. For scenario A, step A1: Operations staff member Xiao Wang opens the order management page (query page). The panel component only displays three permanent conditions: "order number", "customer name" and "order status". The bottom displays the "Expand more conditions (3)" button, indicating that there are 3 more conditions that are collapsed. Xiao Wang fills in the query value in the three permanent conditions and clicks the "query" button. The system triggers a query event. After collecting the condition values, the query page initiates a data request, such as Figure 10 As shown. Step A2: Xiao Wang needs to filter by date range. Click the "Expand More Conditions (3)" button. The panel expands down to display three more conditions: "Creation Time", "Creator", and "Amount Range". After Xiao Wang selects the date range, he submits the query along with the resident conditions. Clicking the "Reset" button can clear the values ​​of all filled conditions and trigger the clearing logic of the parent page, such as Figure 11 As shown. Step A3: Xiao Wang discovered in the settings that "Customer Name" was actually a condition he didn't use often. He clicked the settings button to open the configuration pop-up. The pop-up displays the currently used conditions at the top and more conditions at the bottom. Xiao Wang moved "Customer Name" from the used conditions area to the more conditions area by clicking the close button, moved "Creation Time" from the more conditions area to the used conditions area, and then dragged and dropped "Order Number" to the top. He then clicked "Save Configuration" to complete the process. The panel then displayed the new condition layout in real time, as shown below. Figure 12 As shown and Figure 13 As shown.

[0110] Scenario Switching Explanation: Scenario B demonstrates the system's automatic adaptation capability after backend business version iterations. When the configuration saved in Scenario A contains conditions that have been discontinued in the new version, the system does not rely on manual user correction but automatically performs validity filtering during the page loading phase, such as... Figure 14 As shown. For scenario B, step B1: After one business iteration, the "amount range" condition is removed from the page. On the next visit, during the component mounting phase, the configuration saved by Xiao Wang is read, and each condition ID in the configuration is verified to have a corresponding node in the current slot content. The node corresponding to "amount range" no longer exists, so the system silently removes it from the configuration. The remaining four conditions retain their original categories and order, such as... Figure 15 As shown. Step B2: Xiao Wang opens the page and sees a panel displaying four conditions, the layout of which is exactly the same as his previous settings, except that the "Amount Range" condition is missing. Xiao Wang did not encounter any error pop-ups or blank placeholder areas and started the query normally, completely unaware of the version change. Figure 16 As shown in the diagram. The overall overview of the innovative aspects of this application is illustrated below. Figure 17As shown, it demonstrates the end-to-end mapping relationship between GUI operation, background processing mechanism, and three core innovations.

[0111] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially, these steps are not necessarily executed in that order. Unless otherwise expressly 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 of the steps in the above embodiments 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. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the sub-steps or stages of other steps.

[0112] Based on the same inventive concept, this application also provides a query page rendering apparatus for implementing the query page rendering method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more query page rendering apparatus embodiments provided below can be found in the limitations of the query page rendering method described above, and will not be repeated here.

[0113] In one embodiment, such as Figure 18 As shown, a query page rendering device 1800 is provided, which specifically includes:

[0114] The acquisition module 1802 is used to obtain the default slot content of the query page through the browser panel component of the query page to be rendered; the default slot content includes multiple currently valid input page components, each of which carries an anchor identifier;

[0115] Module 1804 is used to build the set of available condition identifiers; the set of available condition identifiers contains anchor identifiers for multiple input page components;

[0116] The reading module 1806 is used to read the target historical condition configuration of the query page from the persistent storage space; the target historical condition configuration includes the historical persistent condition set and the historical more condition set; each condition entry in the historical persistent condition set is set to be displayed by default; each condition entry in the historical more condition set is set to be collapsed and hidden by default; the condition entry contains a condition identifier.

[0117] The filtering module 1808 is used to filter out the condition entries whose condition identifiers fall into the available condition identifier set from the historical resident condition set and the historical more condition set respectively, if the reading is successful, to obtain the effective resident condition set and the effective more condition set.

[0118] The generation module 1810 is used to generate corresponding rendering instructions for each condition entry in the effective resident condition set and the effective more condition set based on the current collapse and unfold state of the effective more condition set; the rendering instructions include the arrangement number and the visibility flag.

[0119] The rendering module 1812 is used to find, for each rendering instruction, an input page component that matches the condition identifier of the condition entry corresponding to the rendering instruction from the default slot content, and to control the visual arrangement position of the found input page component on the query page by applying style layout attributes corresponding to the arrangement number in the rendering instruction, and to control its display or hiding on the query page by applying display control instructions corresponding to the display flag in the rendering instruction.

[0120] In one embodiment, the filtering module 1808 is further configured to, if the reading fails, obtain a condition configuration array through a browser panel component; the condition configuration array contains multiple condition entries, each condition entry containing a condition identifier and a persistent identifier; the persistent identifier is used to indicate whether the condition entries in the condition configuration array are displayed persistently by default or hidden by default; based on the persistent identifier, the multiple condition entries are divided into an initial persistent condition set and an initial more condition set; each condition entry in the initial persistent condition set is set to be displayed persistently by default; each condition entry in the initial more condition set is set to be hidden by default; and condition entries whose condition identifiers fall into the available condition identifier set are filtered from the initial persistent condition set and the initial more condition set respectively to obtain a valid persistent condition set and a valid more condition set.

[0121] In one embodiment, the condition entries in the valid persistent condition set are stored sequentially in the persistent condition array of the browser panel component; the condition entries in the valid more condition set are stored sequentially in the more condition array of the browser panel component; the apparatus further includes:

[0122] The storage module is used to respond to user grouping, migration, and / or sequential dragging operations of condition items in the configuration pop-up window of the query page, and to update the resident condition array and more condition array in real time; in response to the user's save configuration command, it serializes each condition item in the resident condition array and more condition array to obtain the serialized string corresponding to the query page; it concatenates the page path of the query page and the component name of the browser panel component to generate the storage key of the query page; and it associates the serialized string with the storage key and stores it in the persistent storage space.

[0123] In one embodiment, the reading module 1806 is further configured to concatenate the page path of the query page and the component name of the browser panel component to generate the storage key of the query page; query the serialized string associated with the storage key from the persistent storage space; if the serialized string exists and is in a normal format, then the serialized string is parsed; if the parsing is successful, then the target historical condition configuration of the query page is determined to have been read successfully, and the parsing result of the serialized string is used as the target historical condition configuration; if the serialized string does not exist, the serialized string exists but is in a wrong format, or the parsing fails, then the target historical condition configuration of the query page is determined to have failed to be read.

[0124] In one embodiment, each condition item in the effective resident condition set is stored sequentially in the resident condition array of the browser panel component; each condition item in the effective more condition set is stored sequentially in the more condition array of the browser panel component; the generation module 1810 is further configured to traverse each condition item in the resident condition array according to the storage order, assign an incrementing sequence number starting from 0 to each condition item in the resident condition array, and set its corresponding visibility flag to always visible, thereby obtaining the rendering instructions corresponding to each condition item in the resident condition array; traverse each condition item in the more condition array according to the storage order, and based on the sequence number assigned to the last condition item in the resident condition array, continue to increment the sequence number assigned to each condition item in the more condition array, and set its corresponding visibility flag to be synchronized with the current folded / expanded state of the effective more condition set, so as to be hidden when folded and visible when expanded, thereby obtaining the rendering instructions corresponding to each condition item in the more condition array.

[0125] In one embodiment, each input page component in the default slot content serves as a direct child node of the default slot panel of the query page, forming a virtual node tree for the query page; the anchor identifier is the data-id anchor attribute value of each child node in the virtual node tree, used to declare the global uniqueness of the child node in the virtual node tree.

[0126] In one embodiment, the style layout property is the order property of the browser layout engine; the visibility control directive is the v-show directive of the browser layout engine; the v-show directive controls the display and hiding of the real DOM node by keeping the real DOM node of the input page component in the page DOM tree of the query page, and only by updating the style visibility property of the real DOM node, so that the real DOM node is not destroyed and rebuilt during the display switching and sorting adjustment process.

[0127] The aforementioned query page rendering mechanism breaks away from the traditional fixed code layout of query conditions, significantly improving the flexibility of enterprise-level backend query pages. By introducing a collaborative mechanism of anchor identifiers and persistent configuration, this solution achieves runtime dynamic orchestration and rendering of query conditions. Users can freely adjust persistent and collapsed conditions according to their usage frequency and preferences, making high-frequency conditions readily accessible and solving the pain point of low query efficiency caused by slow searching due to numerous conditions. Simultaneously, the decoupling of configuration data and page templates eliminates the need to modify repetitive code across multiple pages during business iterations; only configuration data needs to be maintained for unified implementation, greatly reducing development and maintenance costs. Furthermore, this application's solution fully considers the validity and fault tolerance of condition configurations, ensuring page stability during system upgrades or field changes, balancing system usability and robustness.

[0128] Each module in the aforementioned query page rendering device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0129] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 19 As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When executed by the processor, the computer program implements a query page rendering method. The display unit of the computer device is used to form a visually visible image. It can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0130] Those skilled in the art will understand that Figure 19The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0131] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0132] In one embodiment, a computer-readable storage medium is provided storing a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0133] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0134] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0135] 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 a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0136] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0137] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for rendering a query page, characterized in that, The method includes: The default slot content of the query page is obtained through the browser panel component of the query page to be rendered; the default slot content includes multiple currently valid input page components, each of which carries an anchor identifier; Construct an available condition identifier set; the available condition identifier set contains anchor identifiers of the plurality of input page components; The target historical condition configuration of the query page is read from the persistent storage space; the target historical condition configuration includes a historical persistent condition set and a historical more condition set; each condition entry in the historical persistent condition set is set to be displayed by default; each condition entry in the historical more condition set is set to be collapsed and hidden by default; each condition entry contains a condition identifier. If the read is successful, then from the historical persistent condition set and the historical more condition set, the condition entries whose condition identifiers fall into the available condition identifier set are filtered out to obtain the effective persistent condition set and the effective more condition set. Based on the current collapsed / expanded state of the effective more condition set, a corresponding rendering instruction is generated for each condition entry in the effective resident condition set and the effective more condition set; the rendering instruction includes an arrangement number and a show / hide flag; For each rendering instruction, an input page component matching the condition identifier of the condition entry corresponding to the rendering instruction is found from the default slot content. The visual arrangement position of the found input page component is controlled by applying a style layout attribute corresponding to the arrangement number in the rendering instruction, and its display or hiding on the query page is controlled by applying a display control instruction corresponding to the display flag in the rendering instruction.

2. The method according to claim 1, characterized in that, The method further includes: If the read fails, the condition configuration array is obtained through the browser panel component; the condition configuration array contains multiple condition entries, each of which contains a condition identifier and a persistent identifier; the persistent identifier is used to indicate whether the condition entry in the condition configuration array is displayed persistently by default or collapsed and hidden by default. Based on the persistent identifier, the multiple condition entries are divided into an initial persistent condition set and an initial more condition set; each condition entry in the initial persistent condition set is set to be displayed persistently by default; each condition entry in the initial more condition set is set to be collapsed and hidden by default. From the initial resident condition set and the initial more condition set, condition entries whose condition identifiers fall into the available condition identifier set are selected to obtain the effective resident condition set and the effective more condition set.

3. The method according to claim 2, characterized in that, Each condition entry in the effective persistent condition set is stored sequentially in the persistent condition array of the browser panel component; Each condition entry in the effective set of more conditions is stored sequentially in the more conditions array of the browser panel component; The method further includes: In response to the user's grouping, migration and / or sequential dragging operations on the condition entries in the configuration pop-up window of the query page, the resident condition array and the more condition array are updated in real time; In response to the user's save configuration command, each condition entry in the resident condition array and the more condition array is serialized to obtain the serialized string corresponding to the query page; The page path of the query page and the component name of the browser panel component are concatenated to generate the storage key of the query page; The serialized string is associated with the storage key and stored in the persistent storage space.

4. The method according to claim 1, characterized in that, The step of reading the target historical condition configuration of the query page from persistent storage includes: The page path of the query page and the component name of the browser panel component are concatenated to generate the storage key of the query page; Retrieve the serialized string associated with the storage key from the persistent storage space; If the serialized string exists and is in the correct format, then the serialized string is parsed. If the parsing is successful, it is determined that the target historical condition configuration of the query page has been successfully read, and the parsing result of the serialized string is used as the target historical condition configuration; If the serialized string does not exist, the serialized string exists but the format is abnormal, or the parsing fails, then it is determined that the target historical condition configuration of the query page has failed to be read.

5. The method according to claim 1, characterized in that, Each condition entry in the valid persistent condition set is stored sequentially in the persistent condition array of the browser panel component; each condition entry in the valid more condition set is stored sequentially in the more condition array of the browser panel component. Based on the current collapsed / expanded state of the effective more condition set, the process generates corresponding rendering instructions for each condition entry in the effective persistent condition set and the effective more condition set, including: Traverse each condition entry in the resident condition array according to the storage order, assign an incrementing sequence number starting from 0 to each condition entry in the resident condition array, and set its corresponding visibility flag to always visible, thereby obtaining the rendering instructions corresponding to each condition entry in the resident condition array. Traverse each condition entry in the more condition array according to the storage order. Based on the arrangement number assigned to the last condition entry in the resident condition array, continue to assign an incremental arrangement number to each condition entry in the more condition array, and set its corresponding visibility flag to be synchronized with the current folded / expanded state of the effective more condition set, so as to hide when folded and be visible when expanded, and obtain the rendering instructions corresponding to each condition entry in the more condition array.

6. The method according to claim 1, characterized in that, Each of the input page components in the default slot content serves as a direct child node of the default slot panel of the query page, forming a virtual node tree of the query page; the anchor identifier is the data-id anchor attribute value of each child node in the virtual node tree, used to declare the global uniqueness of the child node in the virtual node tree.

7. The method according to claim 1, characterized in that, The style layout attribute is the order attribute of the browser layout engine; the visibility control instruction is the v-show instruction of the browser layout engine; the v-show instruction retains the real DOM node of the input page component in the page DOM tree of the query page, and controls the display and hiding only by updating the style visibility attribute of the real DOM node, so that the real DOM node is not destroyed and rebuilt during the display switching and sorting adjustment process.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

9. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.