A configuration method and device of an account query page and a medium

Abstract

The application discloses a configuration method and device of a table query page and a medium, wherein the method comprises the following steps: obtaining user identity information, organization information and required function types of a target user, and generating a query page loading request; sending the query page loading request to a back end to determine a default display scheme of a main form, a target subform which needs to be rendered, a target field in the target subform and a target field value corresponding to the target field based on a JSON string returned by the back end; and rendering the main form and the target subform based on the default display scheme of the main form and the JSON string to obtain a table query page. By combining multiple simple interfaces together, complex and variable requirements can be realized, customer use requirements can be met to a greater extent, a friendly interactive interface is provided, and users can conveniently perform query operations.

Description

Technical Field

[0001] This application relates to the field of information technology, specifically to a method, device, and medium for configuring an account query page. Background Technology

[0002] The complex interface for account and statement queries is an interface that can be dynamically adjusted according to user needs. It can flexibly display data and provide interactive functions based on the user's selected query conditions and display requirements.

[0003] First, the complex interface for account and report queries is composed of multiple simple interfaces. Each simple interface is responsible for displaying and processing specific query conditions or data presentation. By combining different simple interfaces, complex query functions can be achieved. For example, one simple interface can be used to select the time range for the query, another simple interface can be used to select the department or project for the query, and yet another simple interface can be used to select the data type for the query, and so on. By combining these simple interfaces together, users can create different query conditions according to their needs, achieving more flexible and accurate queries.

[0004] Secondly, complex account query interfaces need to achieve seamless data interaction and display between multiple interfaces. When a user selects query criteria on one interface, other related interfaces need to update their displayed content accordingly. For example, if a user selects a one-week time range for the query, the data displayed on other interfaces also needs to be updated to reflect that time range. This requires the complex account query interface to acquire and update data in real time and then pass the data to other interfaces for display.

[0005] Meanwhile, complex account and report query interfaces also need to ensure the correctness and consistency of data and page configuration. After a user selects query criteria, the interface needs to perform the corresponding data query based on the user's selection and display the results to the user. This requires the interface to accurately acquire and process data and ensure the accuracy of the query results. Furthermore, complex account and report query interfaces also need to maintain consistency in page configuration, meaning that the interface layout and style should remain consistent across different query criteria and display methods to provide a good user experience.

[0006] Because the query conditions on the interface change dynamically with user needs, the simple query interface in the existing technology cannot meet the ever-changing query needs of users. Summary of the Invention

[0007] To address the aforementioned issues, this application proposes a configuration method, device, and medium for an account statement query page, wherein the method includes:

[0008] Obtain the target user's identity information, organization information, and required function types, and generate a query page loading request; send the query page loading request to the backend, and determine the default display scheme of the main form, the target sub-form to be rendered, the target fields in the target sub-form, and the target field values ​​corresponding to the target fields based on the JSON string returned by the backend; render the main form and the target sub-form based on the default display scheme of the main form and the JSON string to obtain the account query page.

[0009] In one example, the query page loading request includes a basic data request and a dynamic default value request. Determining the default display scheme of the main form, the target sub-form to be rendered, the target field within the target sub-form, and the target field value corresponding to the target field based on the JSON string returned by the backend specifically includes: determining the first JSON string returned by the backend based on the basic data request and the second JSON string returned based on the dynamic default value request; determining the target sub-form, the target field, the target field value, and the pre-stored default value using the first JSON string; determining the dynamic default value using the second JSON string; and determining the default display scheme of the main form based on the pre-stored default value and the dynamic default value.

[0010] In one example, rendering the main form and the target sub-form based on the default display scheme of the main form and the JSON string specifically includes: rendering the main form using the default display scheme of the main form and displaying the default values ​​of each field in the main form; filling the target field values ​​into the corresponding target fields of the target sub-form; and rendering the target sub-form asynchronously.

[0011] In one example, filling the target field value into the corresponding target field of the target form specifically includes: determining that the default value of the target field in the form has multiple enumeration values; determining the target field value corresponding to the target field through the JSON string; if the target field value is not included among the multiple enumeration values, then converting the target field value into the target enumeration value among the multiple enumeration values ​​through data mapping, and filling it into the target field.

[0012] In one example, after rendering the main form and the target sub-form based on the default display scheme of the main form and the JSON string to obtain the account query page, the method further includes: if there is a parameter modification action in the target form, determining the modified parameters of the target form; determining the linked form of the modified parameters and the linked fields in the linked form; modifying the linked fields based on the modified parameters, and refreshing the linked form.

[0013] In one example, after rendering the main form and the target sub-form to obtain the account query page, the method further includes: receiving a query request initiated by the user; filling in the query conditions corresponding to the query request in the account query page based on the query request; and initiating a query to the backend based on the query conditions to obtain the query results returned by the backend.

[0014] In one example, after obtaining the query results returned by the backend, the method further includes: rendering a query results page based on the query results and presenting the query results page to the user; the query results page includes a list of subjects and query ledgers corresponding to different subjects; receiving a subject selection request initiated by the user, and based on the subject selection request, determining the target query ledger corresponding to the target subject from the query ledgers corresponding to multiple subjects; and presenting the target query ledger and the list of subjects to the user.

[0015] In one example, after obtaining the query results returned by the backend, the method further includes: receiving a query condition rendering request sent by the user, and obtaining a third JSON string returned by the backend based on the query condition rendering request; rendering the query condition interface corresponding to the current result page based on the third JSON string, and presenting the query condition interface to the user.

[0016] This application also provides a configuration device for an account query page, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform: obtaining user identity information, organization information, and required function types of a target user, generating a query page loading request; sending the query page loading request to a backend to determine, based on the JSON string returned by the backend, the default display scheme of the main form, the target sub-form to be rendered, the target field within the target sub-form, and the target field value corresponding to the target field; and rendering the main form and the target sub-form based on the default display scheme of the main form and the JSON string to obtain the account query page.

[0017] This application also provides a non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured to: obtain the user identity information, organization information, and required function types of a target user; generate a query page loading request; send the query page loading request to a backend to determine the default display scheme of the main form, the target sub-form to be rendered, the target field in the target sub-form, and the target field value corresponding to the target field based on the JSON string returned by the backend; and render the main form and the target sub-form based on the default display scheme of the main form and the JSON string to obtain the account query page.

[0018] The method proposed in this application can bring the following benefits: combining multiple simple interfaces together can meet complex and varied needs, better satisfy customer usage requirements, provide a user-friendly interactive interface, and enable users to easily perform query operations. At the same time, asynchronous rendering of multiple forms can improve rendering speed. Attached Figure Description

[0019] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments of this application and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0020] Figure 1 This is a flowchart illustrating a method for configuring an account query page according to an embodiment of this application.

[0021] Figure 2 This is a schematic diagram of the main form of an account query page in an embodiment of this application;

[0022] Figure 3 This is a schematic diagram of three forms on an account query page in an embodiment of this application;

[0023] Figure 4 This is a schematic diagram of the configuration device for an account query page in an embodiment of this application. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0025] The technical solutions provided by the various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0026] Figure 1 This diagram illustrates a configuration method for an account statement query page provided in one or more embodiments of this specification. This method can be applied to account statement queries in different business areas, such as internet finance, e-commerce, instant messaging, gaming, and government services. The process can be executed by the corresponding computing device (e.g., a risk control server or smart mobile terminal for payment services), and certain input parameters or intermediate results in the process can be manually adjusted to help improve accuracy.

[0027] The analysis method involved in the embodiments of this application can be implemented by a terminal device or a server, and this application does not impose any special limitations on it. For ease of understanding and description, the following embodiments are all described in detail using a server as an example.

[0028] It should be noted that the server can be a single device or a system composed of multiple devices, i.e., a distributed server. This application does not make any specific limitations in this regard.

[0029] like Figure 1 As shown in the figure, this application embodiment provides a configuration method for an account statement query page, including:

[0030] S101: Obtain the target user's identity information, organization information, and required function types, and generate a query page loading request.

[0031] First, when generating a query page, the front-end needs to obtain the target user's identity information, organization information, and required functionalities to generate a query page loading request. For user identity information, the front-end needs to obtain the user's login information or other verification information to determine the user's identity and permissions. This information can include username, password, access token, etc. By obtaining the user's identity information, the front-end can perform corresponding permission verification to ensure that only legitimate users can perform query operations. Additionally, the front-end also needs to obtain the user's organization information. This information can include organization name, organization number, organization type, etc. By obtaining the user's organization information, the front-end can generate different query pages according to the needs of different organizations to meet their query requirements. Furthermore, the front-end also needs to obtain the user's functionalities requirements. Functionalities can include query type, query conditions, etc. By obtaining the user's functionalities requirements, the front-end can generate corresponding query pages based on the user's selections and load the query conditions into the page so that the back-end can perform corresponding data query operations based on the user's choices.

[0032] S102: Send the query page loading request to the backend to determine the default display scheme of the main form, the target sub-form to be rendered, the target field in the target sub-form, and the target field value corresponding to the target field based on the JSON string returned by the backend.

[0033] After the query page loading request is generated, the generated query page loading request is sent from the front end to the back end, and the JSON string returned by the back end is obtained. The default display scheme of the main form, the target sub-form to be rendered, the target fields in the target sub-form, and the target field values ​​corresponding to the target fields are determined by the JSON string.

[0034] In one embodiment, the query page loading request is divided into two parts: the first part is a basic data request for the solution, as... Figure 2 The main form shown is a list of plans, primarily displaying the plan's name and type (public plan, personal plan, organizational plan, etc.). The basic plan data request retrieves the plan's basic data types, such as the plan's name, type, and some of its fields (previously stored in the database with default values). The second part is a dynamic default value request, which modifies some default values ​​based on the current user, such as organizational ledgers. These fields are not simply true or false; they are dynamic data that differs with each environment setup, thus requiring a new query from the database.

[0035] Therefore, when determining the default display scheme, after obtaining the JSON string, it is necessary to determine the first JSON string returned by the backend based on the basic data request of the scheme, and the second JSON string returned based on the dynamic default value request; the target form, target field, target field value, and pre-stored default value are determined by the first JSON string; the dynamic default value is determined by the second JSON string; finally, the default display scheme of the main form can be determined based on the pre-stored default value and the dynamic default value.

[0036] S103: Based on the default display scheme of the main form and the JSON string, render the main form and the target sub-form to obtain the account query page.

[0037] With the above information, the main form and the target secondary form can be rendered to obtain the account query page. Specifically, after rendering, the result will be as follows: Figure 2 The main form shown contains, for example, the following: Figure 3 The three forms shown are for common conditions, advanced conditions, and filtering.

[0038] During rendering, the main form is rendered using the default display scheme, and the default values ​​of each field in the main form and each target form are displayed. The target field values ​​are then filled into the corresponding target fields of the target forms. When rendering the target forms, asynchronous rendering is used to improve rendering speed.

[0039] Furthermore, when filling the target field value into the target form, if the default value of the target field in the form has multiple enumeration values, the target field value corresponding to the target field is determined by the JSON string; if the target field value is not included among the multiple enumeration values, the target field value is converted into the target enumeration value among the multiple enumeration values ​​through data mapping and then filled into the target field.

[0040] In one embodiment, after obtaining the account statement query page, if one form modifies its parameters, the other forms should be modified accordingly to ensure the accuracy of the data. Specifically, if the target form has parameter modification actions, the modified parameters of the target form are determined; the linked forms with the modified parameters and the linked fields within the linked forms are determined; based on the modified parameters, the linked fields are modified, and the linked forms are refreshed.

[0041] In one embodiment, after obtaining the account query page, when performing a query, it is necessary to receive the query request initiated by the user; based on the query request, fill in the query conditions corresponding to the query request in the account query page; based on the query conditions, send a query to the backend to obtain the query results returned by the backend.

[0042] Furthermore, after obtaining the query results, the query results page needs to be rendered and presented to the user. This query results page includes a list of subjects and the corresponding query ledgers for each subject. Users can select subjects to query the corresponding query ledgers for each subject. Specifically, the system receives the subject selection request from the user, determines the target query ledger for the target subject from the multiple query ledgers for each subject, and presents the target query ledger and the subject list to the user.

[0043] In one embodiment, after obtaining the query results, if the user wants to view the query conditions corresponding to the current query results, a query condition rendering request can be sent. After receiving the request, the front end will send the request to the back end and receive the third JSON string returned by the back end. At this time, the query condition interface corresponding to the current results page can be rendered based on the third JSON string and presented to the user.

[0044] like Figure 4 As shown in the illustration, this application embodiment also provides a configuration device for an account statement query page, including:

[0045] At least one processor; and,

[0046] A memory communicatively connected to the at least one processor; wherein,

[0047] The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to:

[0048] Obtain the target user's identity information, organization information, and required function types, and generate a query page loading request; send the query page loading request to the backend, and determine the default display scheme of the main form, the target sub-form to be rendered, the target fields in the target sub-form, and the target field values ​​corresponding to the target fields based on the JSON string returned by the backend; render the main form and the target sub-form based on the default display scheme of the main form and the JSON string to obtain the account query page.

[0049] This application embodiment also provides a non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0050] Obtain the target user's identity information, organization information, and required function types, and generate a query page loading request; send the query page loading request to the backend, and determine the default display scheme of the main form, the target sub-form to be rendered, the target fields in the target sub-form, and the target field values ​​corresponding to the target fields based on the JSON string returned by the backend; render the main form and the target sub-form based on the default display scheme of the main form and the JSON string to obtain the account query page.

[0051] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the device and medium embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the description of the method embodiments.

[0052] The devices and media provided in this application are one-to-one with the methods. Therefore, the devices and media also have similar beneficial technical effects as their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0053] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0054] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0055] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0056] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0057] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0058] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0059] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0060] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0061] The above description is merely an embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of this application should be included within the scope of the claims of this application.

Claims

1. A method for configuring an account statement query page, characterized in that, include: Obtain the target user's identity information, organization information, and required functionalities, and generate a query page loading request; The query page loading request is sent to the backend to determine the default display scheme of the main form, the target sub-form to be rendered, the target field in the target sub-form, and the target field value corresponding to the target field based on the JSON string returned by the backend. Based on the default display scheme of the main form and the JSON string, the main form and the target secondary form are rendered to obtain the account query page; The query page loading request includes a basic data request for the solution and a dynamic default value request; The process of determining the default display scheme of the main form, the target sub-form to be rendered, the target fields within the target sub-form, and the target field values ​​corresponding to the target fields based on the JSON string returned by the backend specifically includes: Determine the first JSON string returned by the backend based on the basic data request of the scheme, and the second JSON string returned based on the dynamic default value request; The target form, the target field, the target field value, and the pre-stored default value are determined by the first JSON string; The dynamic default value is determined by the second JSON string; Based on the pre-stored default values ​​and the dynamic default values, the default display scheme of the main form is determined; The rendering of the main form and the target secondary form based on the default display scheme of the main form and the JSON string specifically includes: The main form is rendered using its default display scheme, and the default values ​​for each field within the main form are displayed. Populate the target field value into the corresponding target field of the target form; When rendering the target from the form, rendering is performed asynchronously.

2. The method according to claim 1, characterized in that, The step of filling the target field value into the corresponding target field of the target form specifically includes: It is determined that the default value of the target field in the form has multiple enumerated values; The target field value corresponding to the target field is determined by the JSON string; If the target field value is not included in the plurality of enumerated values, the target field value is converted into a target enumerated value among the plurality of enumerated values ​​through data mapping and then filled into the target field.

3. The method according to claim 1, characterized in that, After rendering the main form and the target sub-form based on the default display scheme of the main form and the JSON string to obtain the account query page, the method further includes: If the target form has parameter modification actions, then determine the modified parameters of the target form; Determine the linked form for the modified parameters and the linked fields within the linked form; Based on the modified parameters, the linked fields are modified, and the linked form is refreshed.

4. The method according to claim 1, characterized in that, After rendering the main form and the target sub-form to obtain the account query page, the method further includes: Receive query requests initiated by users; Based on the query request, enter the query conditions corresponding to the query request on the account query page; Based on the query conditions, a query is initiated to the backend to obtain the query results returned by the backend.

5. The method according to claim 4, characterized in that, After obtaining the query results returned by the backend, the method further includes: Based on the query results, render the query results page and present it to the user; The query results page includes a list of subjects and corresponding query ledgers for each subject. Receive a subject selection request initiated by a user, and based on the subject selection request, determine the target query table corresponding to the target subject from the query tables corresponding to multiple subjects respectively; The target query table and the list of accounts are presented to the user.

6. The method according to claim 4, characterized in that, After obtaining the query results returned by the backend, the method further includes: Receive a query condition rendering request sent by the user, and obtain a third JSON string returned by the backend based on the query condition rendering request; Based on the third JSON string, the query condition interface corresponding to the current results page is rendered and presented to the user.

7. A configuration device for an account statement query page, characterized in that, include: At least one processor; And, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to perform: a configuration method for an account query page as described in any one of claims 1-6.

8. A non-volatile computer storage medium storing computer-executable instructions, characterized in that, The computer-executable instructions are configured to execute the configuration method for an account query page as described in any one of claims 1-6.

Images