A menu test point configuration method and device, computer equipment and storage medium
By dividing the menu into resource groups and configuring them uniformly, the problems of high computational complexity and redundant configuration in existing technologies are solved, and efficient and flexible management of menu pilot configuration is achieved.
Patent Information
- Application Number
- CN202211258262.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-10-14
- Publication Date
- 2026-01-02
- Estimated Expiration
- 2042-10-14
AI Technical Summary
The existing menu pilot configuration method has high computational complexity and redundant configuration, resulting in low resource management efficiency.
Menus with the same menu function or pilot configuration type are grouped into the same resource group, and all menus in each resource group are uniformly piloted. The resource group is used to traverse and filter the user's historical menu list, and the filtered menu list is returned based on the user attribute information and the pilot configuration type of the resource group.
By dynamically adjusting the pilot configuration type of resource groups, the complexity of single-dimensional menu pilot configuration is reduced, redundancy of identical configurations is avoided, and the efficiency and flexibility of menu pilot configuration are improved.
Smart Images

Figure CN115509667B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of system management, in particular to a menu pilot configuration method and device, computer equipment and a storage medium. BACKGROUND
[0002] When a user accesses a system, the interface content and menu ultimately displayed to the user are menus (resources) or application lists filtered by the user under his own user attribute conditions. For example, there are 5 menus according to the user role, but the user belongs to an agency or other user attribute conditions, and the menu ultimately displayed to the user is only 3, that is, 2 of the 5 menus are filtered out under other user attribute conditions, and the menu filtering condition is the menu pilot configuration. The current menu pilot configuration method is to make one-to-one pilot configuration for each menu, which has the disadvantages of increasing the complexity of calculation and having many redundant pilot configurations of the same bundled menu. SUMMARY
[0003] The present application provides a menu pilot configuration method, device, computer equipment and storage medium, aiming to solve the technical problems of high calculation complexity and redundant configuration existing in the current menu pilot configuration method.
[0004] To solve the above technical problems, the technical scheme adopted by the present application is as follows:
[0005] A menu pilot configuration method comprises the following steps:
[0006] Collecting menus in a database that need to be pilot configured, dividing menus with the same menu function or pilot configuration type into the same resource group, and uniformly pilot configuring all menus in each resource group;
[0007] When a user accesses the database, obtaining user attribute information and a historical menu list of the user;
[0008] Using the resource group to traverse the historical menu list, judging whether the menus in the historical menu list exist in any resource group, if so, matching the user attribute information with the pilot configuration type of the resource group, filtering the historical menu list according to the matching result, and returning the filtered menu list to the user for display.
[0009] The technical scheme adopted by the present application also includes that the pilot configuration of all menus in each resource group is specifically as follows:
[0010] The resource group structure after the pilot configuration is: Map<menu code, resource group label ID>, Map<resource group label ID, pilot configuration type>, wherein the resource group label ID represents a set of all menu codes in the same resource group, the pilot configuration type represents a control condition for whether to display the menu in the same resource group, and the control condition includes an APP version, a network point, an institution, or / and a network point type.
[0011] The technical scheme adopted by the embodiment of the application further includes that the user attribute information includes a user code, a mobile phone number, a network point, an institution, an APP version, a channel, and a network point type, and the historical menu list includes a pilot menu with a pilot identifier and a non-pilot menu without a pilot identifier.
[0012] The technical scheme adopted by the embodiment of the application further includes that the iteration of the historical menu list by using the resource group is specifically:
[0013] The pilot menu with the pilot identifier in the historical menu list is obtained, and the pilot menu with the pilot identifier is iterated by using the resource group.
[0014] The technical scheme adopted by the embodiment of the application further includes that the iteration of the historical menu list by using the resource group is specifically:
[0015] The menu code of each pilot menu is searched in the resource group structure Map<menu code, resource group label ID>, it is judged whether the resource group label ID corresponding to the menu code is found, if the resource group label ID is not found, the pilot menu is filtered out from the historical menu list; if the resource group label ID is found, the user attribute information is matched with the pilot configuration type of the resource group.
[0016] The technical scheme adopted by the embodiment of the application further includes that the matching of the user attribute information with the pilot configuration type of the resource group is specifically:
[0017] The pilot configuration type corresponding to the pilot menu is found from the resource group structure Map<resource group label ID, pilot configuration type> according to the resource group label ID, the user attribute information is matched with the pilot configuration type, it is judged whether the user attribute information is consistent with the pilot configuration type, if the user attribute information is not consistent with the pilot configuration type, the pilot menu is filtered out from the historical menu list; if the user attribute information is consistent with the pilot configuration type, the next pilot menu is iterated, and after all the pilot menus are iterated, a menu list after the pilot menu is filtered is returned to the display interface of the user.
[0018] Another technical scheme adopted by the embodiment of the application is a menu pilot configuration device, which includes:
[0019] a resource grouping module, configured to collect menus in the database that need to be configured in a trial mode, divide menus with the same menu function or the same trial configuration type into a same resource group, and uniformly configure all menus in each resource group in the trial mode;
[0020] a menu collection module, configured to acquire user attribute information and a historical menu list of a user when the user accesses the database;
[0021] a menu filtering module, configured to traverse the historical menu list by using the resource group, determine whether a menu in the historical menu list exists in any resource group, if the menu exists, match the user attribute information with a trial configuration type of the resource group, filter the historical menu list according to a matching result, and return a filtered menu list to the user for display.
[0022] The technical solution adopted by the embodiment of the application further includes that the resource grouping module uniformly configures all menus in each resource group in the trial mode, and the configuration specifically includes:
[0023] The resource group structure after the trial configuration is: Map<menu code, resource group label ID>, Map<resource group label ID, trial configuration type>, wherein the resource group label ID represents a set of all menu codes in a same resource group, the trial configuration type represents a control condition for whether to display a menu in the same resource group, and the control condition includes an APP version, a network point, an organization, or / and a network point type.
[0024] A further technical solution adopted by the embodiment of the application is a computer device, which includes:
[0025] a memory in which executable program instructions are stored;
[0026] a processor connected with the memory;
[0027] The processor invokes the executable program instructions stored in the memory to execute the menu trial configuration method.
[0028] A further technical solution adopted by the embodiment of the application is a storage medium in which processor-executable program instructions are stored, and the program instructions are used to execute the menu trial configuration method.
[0029] This invention proposes a dynamic pilot configuration scheme based on resource groups, encompassing a menu pilot configuration method, apparatus, computer device, and storage medium. A menu pilot configuration center categorizes all menus requiring pilot configuration into resource groups based on menu function or pilot configuration type. Menus with the same function or pilot configuration type are grouped together, and all menus within each resource group undergo unified pilot configuration. When a user accesses the database, the system iterates through the user's historical menu list using the divided resource groups, matching user attribute information with the pilot configuration types in the resource groups. Based on the matching results, the user's historical menu list is filtered, and the filtered menu list is returned to the user for display. This embodiment of the application can control the display permissions of all menus within the same resource group under different user attribute information by dynamically adjusting the pilot configuration types corresponding to each resource group. This reduces single-dimensional menu pilot configuration and allows for dynamic expansion of menu pilot configuration, significantly reducing the complexity of menu pilot configuration. Simultaneously, it avoids redundancy caused by bundling menus with identical configurations. Attached Figure Description
[0030] Figure 1 This is a flowchart illustrating the menu pilot configuration method according to the first embodiment of the present invention;
[0031] Figure 2 This is a flowchart illustrating the menu pilot configuration method according to the second embodiment of the present invention;
[0032] Figure 3 This is a schematic diagram of the menu pilot configuration device according to an embodiment of the present invention;
[0033] Figure 4 This is a schematic diagram of the computer device structure according to an embodiment of the present invention;
[0034] Figure 5 This is a schematic diagram of the storage medium structure according to an embodiment of the present invention. Detailed Implementation
[0035] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.
[0036] The terms "first", "second", "third" in the present application are only for descriptive purpose, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the technical features indicated. Therefore, the features defined with "first", "second", "third" can explicitly or implicitly include at least one of the features. In the description of the present application, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise explicitly and specifically limited. All directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of the present application are only used to explain the relative position relationship, movement condition, etc. between components in a certain posture (as shown in the drawings), and if the certain posture changes, the directional indications also change accordingly. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but can optionally include steps or units not listed, or can optionally include other steps or units inherent to the process, method, product or device.
[0037] Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are they necessarily mutually exclusive or alternative embodiments. It is expressly understood that the embodiments described herein are combinable with each other.
[0038] Please refer to Figure 1 is a flowchart of a menu trial configuration method of the first embodiment of the present application. The menu trial configuration method of the first embodiment of the present application includes the following steps:
[0039] S100: Collecting menus in a database that need to be trial configured, dividing menus with the same menu function or trial configuration type into the same resource group, and uniformly performing trial configuration on all menus in each resource group;
[0040] S110: When a user accesses the database, obtaining user attribute information and a historical menu list of the user;
[0041] S120: Using the resource group to traverse the historical menu list, judging whether the menus in the historical menu list exist in any resource group, if so, matching the user attribute information with the trial configuration type of the resource group, filtering the historical menu list according to the matching result, and returning the filtered menu list to the user for display.
[0042] Based on the above, the menu test configuration method of the first embodiment of the present application proposes a dynamic test configuration scheme based on resource groups, all menus that need to be test configured are classified into resource groups according to menu functions or test configuration types by the menu test configuration center, menus with the same function or the same test configuration type are divided into a resource group, and all menus in each resource group are uniformly test configured, when a user accesses the database, the user's historical menu list is filtered by using the divided resource groups, and the filtered menu list is returned to the user for display. The embodiment of the present application can control the display permission of all menus in the same resource group under different user attribute information by dynamically adjusting the test configuration type corresponding to each resource group, reduce the single-dimensional menu test configuration, and dynamically expand the test configuration of the menu, greatly reduce the complexity of the menu test configuration.
[0043] Referring to Figure 2 is a flowchart of the menu test configuration method of the second embodiment of the present application. The menu test configuration method of the second embodiment of the present application comprises the following steps:
[0044] S220: Collect all menus in the database that need to be test configured;
[0045] S210: Classify the collected menus into resource groups according to menu functions or test configuration types by the menu test configuration center, divide menus with the same function or the same test configuration type into a resource group, and uniformly test configure all menus in each resource group;
[0046] In this step, the test configuration type represents whether the menus in the same resource group are controlled to be displayed or not, and the control condition is composed of different types of test dimensions such as APP version, network point, institution or / and network point type, for example, the existing A, B, C, D four menus are open, and the C, D two menus are new online menus, which are only test displayed to users of a set institution and using the latest APP version, and the C, D two menus cannot be displayed to users of other institutions and not updating the APP version, so the test configuration type of the menu is: set network point and latest APP version. The resource group structure finally generated by the menu test configuration center is: Map<menu code, resource group tag ID>, Map<resource group tag ID, test configuration type>, wherein the resource group tag ID represents a set of all menu codes in the same resource group, the parent-child menus with the same function or the menus with the same test configuration type are uniformly managed through the resource group tag ID, and then all menus in the same resource group are uniformly test configured, thereby greatly reducing the calculation amount of single menu test configuration.
[0047] Specifically, still taking the two new online menus C and D as examples, assuming that the resource groups are classified according to the functions of the C and D menus, first, the two menus C and D are bundled and classified as one resource group, and the resource group tag ID of the resource group is generated, that is: C+D=labelAgent, and then the pilot configuration type of the C and D menus in the resource group is set according to the resource group tag ID, assuming that the pilot configuration type of the C and D menus is: (less than 1.20.1) APP version users cannot display the C and D menus, and the C and D menus are only piloted by users of the 220 agency, then the pilot configuration of the C and D menus is:
[0048] resources.C=labelAgent
[0049] resources.D=labelAgent
[0050] resources.config.labelAgent.all=false
[0051] resources.config.labelAgent.appBeginVersion=1.20.1
[0052] resources.config.labelAgent.deptCode=220
[0053] Further, if it is necessary to adjust the pilot configuration of the menu, it can be divided into two adjustment methods, the first adjustment method is: if it is necessary to expand the pilot configuration of a certain menu or to pilot all within a certain time, the pilot configuration type of the resource group in which the menu is located is directly set to all open. The second adjustment method is: re-classify or merge the resource groups according to the pilot configuration type corresponding to the menu, that is, add or reduce the pilot dimension in the pilot configuration type, and split or merge the resource groups. For example, the C and D menus are controlled through the same resource group tag ID "labelAgent", when it is necessary to adjust the pilot configuration type of the C or D menu, first adjust the pilot configuration type corresponding to the C or D menu, and after adjusting the pilot configuration type, re-classify the C and D menus, and split the resource group tag ID "labelAgent" into: C:labelAgent1, D:labelAgent2.
[0054] In addition, the embodiment of the present application can also classify resource groups for the case of different institutions or different APP versions corresponding to the same menu for trial, for example, menu A needs to be tested on APP version (1.0-2.0) of institution 1 to collect the experience of institution 1 on APP version (1.0-2.0), and at the same time, menu A needs to be tested on APP version (2.0) or above of institution 2 to collect the experience of institution 2 on APP version (2.0) or above, then only the corresponding resource group tag ID of menu A needs to be added for trial adjustment according to the resource group tag ID.
[0055] S220: When the user accesses the database, the user attribute information of the user accessing the database is obtained;
[0056] In this step, when the user accesses the APP or PC database, there is a login state for recording the user attribute information of the user accessing the APP or PC, and the user attribute information includes but is not limited to user code, mobile phone number, network point, institution, APP version, channel, and network point type and the like.
[0057] S230: According to the user attribute information, the historical menu list saved in the database by the user is obtained, and the trial menu with the trial identification in the historical menu list is obtained;
[0058] In this step, the final menu list displayed by the user when accessing the APP or PC depends on the user attribute information, and the menu display permission corresponding to the user attribute information is also different, for example, the existing A, B, C, and D four menus are opened, and the C and D two menus are new online menus, which are only displayed for the users of the set institution and using the latest APP version, and the C and D two menus cannot be displayed for the users of other institutions and not updating the APP version. Therefore, after obtaining the historical menu list saved in the database by the user, the user attribute information is matched with the preset trial configuration type of each menu, and the historical menu list is filtered according to the matching result, and the filtered menu list is taken as the final displayable menu list and returned to the display interface of the user.
[0059] Further, it is assumed that there are 10 menus in the historical menu list of the user obtained from the database, and the 10 menus include 7 trial menus with trial identification and 3 non-trial menus without trial identification configured when the menu is initialized. For the 7 trial menus, the menu trial configuration center is used to filter them, and the filtered trial menus and the 3 non-trial menus are taken as the final displayable menu list and returned to the display interface of the user.
[0060] S240: traversing the pilot menu with the pilot identifier according to the divided resource group, judging whether the pilot menu exists in the resource group, if not, executing S250; if yes, executing S260;
[0061] In this step, the pilot menu traversal mode is specifically as follows: assuming that the pilot menu with the pilot identifier is 7, the 7 pilot menus are traversed according to the divided resource group, first, the menu code of each pilot menu is used to search in the resource group structure Map<menu code, resource group label ID> to judge whether the resource group label ID corresponding to the menu code is found, if not, the menu is filtered out from the 7 pilot menus; if yes, the matching of the pilot configuration type is further performed.
[0062] S250: filtering out the pilot menu from the historical menu list;
[0063] S260: obtaining the resource group label ID corresponding to the pilot menu in the resource group, finding the pilot configuration type corresponding to the pilot menu according to the resource group label ID, and matching the user attribute information with the pilot configuration type to judge whether the user attribute information is consistent with the pilot configuration type, if yes, executing S270; if not, executing S250;
[0064] In this step, the matching of the user attribute information with the pilot configuration type is specifically as follows: first, the corresponding resource group label ID is found based on the menu code of the pilot menu, then the corresponding pilot configuration type is found from the resource group structure Map<resource group label ID, pilot configuration type> based on the resource group label ID, and then the network point, the institution, the APP version, the channel and the network point type in the user attribute information are matched with the pilot configuration type to judge whether the network point, the institution, the APP version, the channel and the network point type are consistent with the pilot configuration type, if yes, it indicates that the user has the display permission of the menu, and the menu is returned to the display interface of the user, if not, it indicates that the user does not have the display permission of the menu, and the menu is deleted from the historical menu list. For example, the pilot configuration type of the C, D menu is that the user with the APP version less than 1.20.1 cannot display the C, D menu, and the C, D menu is only piloted in the user of the 220 institution, if the APP version of the current user is less than 1.20.1 and the current user does not belong to the 220 institution, it indicates that the user does not have the display permission of the C, D menu, and the C, D menu is deleted from the historical menu list.
[0065] S270: judging whether the pilot menu in the historical menu list is traversed, if yes, executing S280; otherwise, continuing to execute S240;
[0066] S280: taking the menu list after filtering the trial menu as the final displayable menu list, and returning the displayable menu list to the display interface of the user;
[0067] In this step, the final displayable menu list includes the trial menu after deleting the trial menu and the non-trial menu without the trial identifier.
[0068] Based on the above, the menu trial configuration method of the second embodiment of the present application proposes a dynamic trial configuration scheme based on resource groups. All menus that need to be trial configured are classified into resource groups according to menu functions or trial configuration types by the menu trial configuration center, menus with the same function or the same trial configuration type are divided into a resource group, and all menus in each resource group are uniformly trial configured. When a user accesses the database, the user's historical menu list is traversed using the divided resource groups, the user attribute information is matched with the trial configuration type in the resource group, the user's historical menu list is filtered according to the matching result, and the filtered menu list is returned to the user for display. The embodiment of the present application can control the display permission of all menus in the same resource group under different user attribute information by dynamically adjusting the trial configuration type corresponding to each resource group, reduce the single-dimensional menu trial configuration, and dynamically expand the trial configuration of the menu, greatly reduce the complexity of the menu trial configuration, and avoid the redundancy of the same configuration bundled menu.
[0069] In an optional embodiment, the result of the menu trial configuration method can also be uploaded to a blockchain.
[0070] Specifically, the corresponding summary information is obtained based on the result of the menu trial configuration method. Specifically, the summary information is obtained by hashing the result of the menu trial configuration method, for example, by using the sha256s algorithm. Uploading the summary information to the blockchain can ensure its security and fair transparency to users. Users can download the summary information from the blockchain to check whether the result of the menu trial configuration method has been tampered with. The blockchain referred to in this example is a new application mode of distributed data storage, peer-to-peer transmission, consensus mechanism, encryption algorithm, etc. computer technology. Blockchain, in essence, is a decentralized database, a series of data blocks associated using cryptographic methods, each data block containing information about a batch of network transactions, used to verify the validity (anti-fake) of the information and generate the next block. Blockchain can include blockchain underlying platform, platform product service layer, and application service layer, etc.
[0071] Please refer to Figure 3FIG. 1 is a structural schematic diagram of a menu pilot configuration device according to an embodiment of the present application. The menu pilot configuration device 40 according to the embodiment of the present application comprises:
[0072] The resource grouping module 41 is configured to collect the menus in the database that need to be pilot configured, divide the menus with the same menu function or pilot configuration type into the same resource group, and uniformly pilot configure all the menus in each resource group; wherein the pilot configuration type indicates whether the control condition of the menus in the same resource group is displayed, and the control condition is composed of different types of pilot dimensions such as APP version, network point, institution, and / or network point type. For example, four existing menus A, B, C, and D are open, wherein two new online menus C and D are pilot displayed only for the users of a set institution and using the latest APP version, and the two menus C and D cannot be displayed for the users of other institutions and not updating the APP version. Therefore, the pilot configuration type of the menu is: set network point and latest APP version. The resource group structure finally generated by the menu pilot configuration center is: Map<menu code, resource group label ID>, Map<resource group label ID, pilot configuration type>, wherein the resource group label ID indicates the set of all menu codes in the same resource group, the parent-child menus with the same function or the menus with the same pilot configuration type are uniformly managed through the resource group label ID, and then all the menus in the same resource group are uniformly pilot configured, so as to greatly reduce the calculation amount of single menu pilot configuration.
[0073] The menu collection module 42 is configured to acquire the user attribute information and the historical menu list of a user and acquire the pilot menu with the pilot identifier in the historical menu list when the user accesses the database; wherein the login state is used to record the user attribute information of the user when accessing the APP or PC when the user accesses the APP or PC database. The user attribute information includes but is not limited to user code, mobile phone number, network point, institution, APP version, channel, and network point type. The final menu list displayed by the user when accessing the APP or PC depends on the user attribute information, and the menu display permission corresponding to the user attribute information is also different. For example, four existing menus A, B, C, and D are open, wherein two new online menus C and D are pilot displayed only for the users of a set institution and using the latest APP version, and the two menus C and D cannot be displayed for the users of other institutions and not updating the APP version. Therefore, after acquiring the historical menu list saved by the user in the database, the user attribute information is matched with the pilot configuration type of each menu, the historical menu list is filtered according to the matching result, the filtered menu list is taken as the final displayable menu list, and the display interface of the user is returned.
[0074] Further, assuming that 10 menus are obtained from the database in the historical menu list of the user, the 10 menus respectively include 7 pilot menus with pilot identification and 3 non-pilot menus without pilot identification configured in the menu initialization configuration, for the 7 pilot menus, filtering is performed by the menu pilot configuration center, and the filtered pilot menus and the 3 non-pilot menus are taken as the final displayable menu list together and returned to the display interface of the user.
[0075] The menu filtering module 43 is configured to traverse the historical menu list by using the resource group, determine whether the menu in the historical menu list exists in any resource group, if so, match the user attribute information with the pilot configuration type of the resource group, filter the historical menu list according to the matching result, and return the filtered menu list to the user for display; wherein the menu traversal manner is specifically as follows: assuming that there are 7 pilot menus with pilot identification, the 7 pilot menus are traversed according to the divided resource groups, first, the menu code of each pilot menu is used to search in the resource group structure Map<menu code, resource group label ID> to determine whether the resource group label ID corresponding to the menu code is found, if not, the menu is filtered out from the 7 pilot menus; if the corresponding resource group label ID is found, the corresponding pilot configuration type is found from the resource group structure Map<resource group label ID, pilot configuration type> based on the resource group label ID, then the branch, institution, APP version, channel and branch type in the user attribute information are matched with the pilot configuration type to determine whether the branch, institution, APP version, channel and branch type are consistent with the pilot configuration type, if so, it indicates that the user has the display permission of the menu, and the menu is returned to the display interface of the user, if not, it indicates that the user does not have the display permission of the menu, and the menu is deleted from the historical menu list. Finally, the menu list after filtering the pilot menu is taken as the final displayable menu list, and the displayable menu list is returned to the display interface of the user.
[0076] The menu test point configuration device provided by the embodiment of the present application proposes a dynamic test point configuration scheme based on resource groups, resource groups are classified according to menu functions or test point configuration types by a menu test point configuration center, menus with the same function or the same test point configuration type are divided into one resource group, and all menus in each resource group are uniformly configured as test points, when a user accesses a database, the filtered menu list is returned to the user for display by using the divided resource groups to filter the historical menu list of the user. The embodiment of the present application can control the display permission of all menus in the same resource group under different user attribute information by dynamically adjusting the test point configuration type corresponding to each resource group, reduce the single-dimensional menu test point configuration, and dynamically expand the test point configuration of the menu, thereby greatly reducing the complexity of the menu test point configuration.
[0077] Please refer to Figure 4 , the computer device structure schematic diagram of the embodiment of the present application. The computer device 50 comprises:
[0078] The memory 51 storing executable program instructions;
[0079] The processor 52 connected with the memory 51;
[0080] The processor 52 is used to call the executable program instructions stored in the memory 51 and execute the following steps: collecting menus needing test point configuration in a database, dividing menus with the same menu function or test point configuration type into the same resource group, and uniformly configuring all menus in each resource group as test points; when a user accesses the database, obtaining user attribute information and a historical menu list of the user; traversing the historical menu list by using the resource group, judging whether the menus in the historical menu list exist in any resource group, if yes, matching the user attribute information with the test point configuration type of the resource group, filtering the historical menu list according to the matching result, and returning the filtered menu list to the user for display.
[0081] The processor 52 can also be called as CPU (Central Processing Unit, central processing unit). The processor 52 can be an integrated circuit chip with signal processing capability. The processor 52 can also be a general processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a ready programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component. The general processor can be a microprocessor or the processor can also be any conventional processor.
[0082] Terminal devices such as computers, servers, mobile phones, tablets and the like.
[0083] The storage medium of the embodiment of the present application proposes a dynamic trial configuration scheme based on resource groups, resource groups are classified according to menu functions or trial configuration types for all menus needing trial configuration through a menu trial configuration center, menus with the same function or the same trial configuration type are divided into one resource group, and all menus in each resource group are uniformly subjected to trial configuration, when a user accesses a database, the historical menu list of the user is filtered by using the divided resource groups, and the filtered menu list is returned to the user for display. The embodiment of the present application can control the display permission of all menus in the same resource group under different user attribute information by dynamically adjusting the trial configuration type corresponding to each resource group, reduces the single-dimensional menu trial configuration, and can dynamically expand the trial configuration of the menu, greatly reducing the complexity of the menu trial configuration.
[0084] In several embodiments provided by the present application, it should be understood that the disclosed system, device and method can be implemented by other manners. For example, the system embodiments described above are only illustrative, for example, the division of units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units or components shown or discussed can be indirect coupling or communication connection through some interfaces, units or components, and can be electrical, mechanical or other forms.
[0085] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit. The above is only an embodiment of the present application, and does not limit the patent scope of the present application, and any equivalent structure or equivalent process transformation using the content of the specification and drawings of the present application, or direct or indirect application in other related technical fields, are also included in the patent protection scope of the present application.
Claims
1. A menu pilot configuration method characterized by, The method comprises the following steps: Collecting menus in a database that need to be configured for a pilot, dividing menus with the same menu function or pilot configuration type into the same resource group, and uniformly configuring all menus in each resource group for a pilot; The pilot configuration of all menus in each resource group is specifically: The resource group structure after the pilot configuration is: Map<menu code, resource group label ID>, Map<resource group label ID, pilot configuration type>, wherein the resource group label ID represents a set of all menu codes in the same resource group, and the pilot configuration type represents a control condition for whether to display the menus in the same resource group; When a user accesses the database, the user attribute information and the historical menu list of the user are obtained, and the historical menu list includes pilot menus with a pilot identifier and non-pilot menus without a pilot identifier; The historical menu list is traversed using the resource group, it is judged whether the menus in the historical menu list exist in any resource group, if the menus exist, the user attribute information is matched with the pilot configuration type of the resource group, the historical menu list is filtered according to the matching result, and the filtered menu list is returned to the user for display; The historical menu list is traversed using the resource group, it is judged whether the menus in the historical menu list exist in any resource group, if the menus exist, the user attribute information is matched with the pilot configuration type of the resource group, the historical menu list is filtered according to the matching result, and the filtered menu list is returned to the user for display; The matching of the user attribute information and the pilot configuration type of the resource group is specifically: the pilot configuration type corresponding to the pilot menu is found from the resource group structure Map<resource group label ID, pilot configuration type> according to the resource group label ID, the user attribute information is matched with the pilot configuration type, it is judged whether the user attribute information is consistent with the pilot configuration type, if the user attribute information is not consistent with the pilot configuration type, the pilot menu is filtered out from the historical menu list; if the user attribute information is consistent with the pilot configuration type, the next pilot menu is continuously traversed, and after all the pilot menus are traversed, the menu list after the pilot menu filtering is returned to the display interface of the user.
2. The menu pilot arrangement method according to claim 1, characterized by, The control condition includes an APP version, a network point, an institution, or / and a network point type.
3. The menu pilot arrangement method according to claim 2, wherein The user attribute information includes a user code, a mobile phone number, a network point, an institution, an APP version, a channel, and a network point type.
4. The menu pilot arrangement method according to claim 3, wherein The historical menu list is traversed using the resource group, it is judged whether the menus in the historical menu list exist in any resource group, if the menus exist, the user attribute information is matched with the pilot configuration type of the resource group, the historical menu list is filtered according to the matching result, and the filtered menu list is returned to the user for display; The historical menu list is traversed using the resource group, it is judged whether the menus in the historical menu list exist in any resource group, if the menus exist, the user attribute information is matched with the pilot configuration type of the resource group, the historical menu list is filtered according to the matching result, and the filtered menu list is returned to the user for display; 5. A menu pilot configuration apparatus characterized by comprising: The control condition includes an APP version, a network point, an institution, or / and a network point type. The user attribute information includes a user code, a mobile phone number, a network point, an institution, an APP version, a channel, and a network point type. The historical menu list is traversed using the resource group, it is judged whether the menus in the historical menu list exist in any resource group, if the menus exist, the user attribute information is matched with the pilot configuration type of the resource group, the historical menu list is filtered according to the matching result, and the filtered menu list is returned to the user for display; The resource grouping module is configured to collect menus in the database that need to be configured for a pilot test, divide menus with the same function or pilot test configuration type into the same resource group, and uniformly configure all menus in each resource group for a pilot test; The pilot test configuration of all menus in each resource group is specifically configured as follows: The resource group structure after the pilot test configuration is Map<menu code, resource group label ID>, Map<resource group label ID, pilot test configuration type>, wherein the resource group label ID represents a set of all menu codes in the same resource group, and the pilot test configuration type represents a control condition for whether to display the menus in the same resource group; The menu collection module is configured to obtain user attribute information and a historical menu list of a user when the user accesses the database, and the historical menu list includes pilot test menus with a pilot test identifier and non-pilot test menus without the pilot test identifier; The menu filtering module is configured to traverse the historical menu list by using the resource group, determine whether the menus in the historical menu list exist in any resource group, match the user attribute information with the pilot test configuration type of the resource group if the menus exist in the resource group, filter the historical menu list according to a matching result, and return the filtered menu list to the user for display; The traversal of the historical menu list by using the resource group is specifically configured as follows: a menu code of each pilot test menu is used to search in the resource group structure Map<menu code, resource group label ID> to determine whether a resource group label ID corresponding to the menu code is found, the pilot test menu is filtered out of the historical menu list if the resource group label ID is not found, and the user attribute information is matched with the pilot test configuration type of the resource group if the resource group label ID is found. The matching of the user attribute information with the pilot test configuration type of the resource group is specifically configured as follows: the pilot test configuration type corresponding to the pilot test menu is found from the resource group structure Map<resource group label ID, pilot test configuration type> according to the resource group label ID, the user attribute information is matched with the pilot test configuration type, it is determined whether the user attribute information is consistent with the pilot test configuration type, the pilot test menu is filtered out of the historical menu list if the user attribute information is not consistent with the pilot test configuration type, and the next pilot test menu is continuously traversed if the user attribute information is consistent with the pilot test configuration type, and the menu list after the pilot test menu is filtered is returned to a display interface of the user after all pilot test menus are traversed.
6. The menu pilot configuration apparatus according to claim 5, wherein The control condition includes an APP version, a network point, an organization, or / and a network point type.
7. A computer device, characterized by The computer device includes: a memory storing executable program instructions; a processor connected with the memory; the processor invokes the executable program instructions stored in the memory to execute the menu pilot test configuration method in any one of claims 1-6.
8. A storage medium storing processor-executable program instructions, characterized in that, The program instructions are used to execute the menu pilot test configuration method in any one of claims 1-6.
Citation Information
Patent Citations
Menu display method and device, computer equipment and storage medium
CN109634698A
Page permission control method and device, electronic equipment and computer readable medium
CN114239033A