Menu display methods, devices, equipment, media and products
By obtaining user login information, finding role and permission information, determining menu identifiers, and calling the target menu from pre-configured menu information in a multi-tenant system, the problem of large code development volume and high maintenance cost is solved, achieving the effect of less code volume and lower maintenance cost.
Patent Information
- Application Number
- CN202411039625.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-31
- Publication Date
- 2025-11-14
- Estimated Expiration
- 2044-07-31
Smart Images

Figure CN119045693B_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of data processing technology, and in particular relates to a menu display method, apparatus, device, medium and product. Background Technology
[0002] With the development of random computing technology, many systems are no longer limited to use by a single tenant, but are instead shared by multiple tenants.
[0003] Currently, a separate set of code is typically developed and maintained for each tenant. However, this results in a large amount of code development, a lot of redundant code, and high maintenance costs, which increase exponentially with each new tenant added. Summary of the Invention
[0004] This application provides a menu display method, apparatus, device, medium, and product, which can at least solve the problems in the prior art of large code development volume, large amount of redundant code, high maintenance cost, and maintenance cost that increases exponentially with each additional tenant.
[0005] In a first aspect, embodiments of this application provide a menu display method applied to a target system, the method comprising:
[0006] Obtain the login information of the first user who logs into the target system. The login information includes the target identifier information corresponding to the first user. The target identifier information includes the target tenant identifier and the target role identifier. The first user is any user under any tenant among the multiple tenants using the target system.
[0007] Find the target role information corresponding to the target identifier information. The target role information includes the target permission identifier corresponding to the target role identifier.
[0008] Determine the target permission identifier corresponding to the first user based on the target role information;
[0009] Find the target permission information corresponding to the target permission identifier. The target permission information includes the target menu identifier corresponding to the target permission identifier.
[0010] Determine the target menu identifier corresponding to the target permission identifier based on the target permission information;
[0011] Retrieve the target menu information corresponding to the target menu identifier from multiple pre-configured menu information;
[0012] Display the target menu based on the target menu information.
[0013] Secondly, embodiments of this application provide a menu display device applied to a target system, the device comprising:
[0014] The acquisition module is used to acquire the login information of the first user logging into the target system. The login information includes the target identification information corresponding to the first user. The target identification information includes the target tenant identifier and the target role identifier. The first user is any user under any tenant among the multiple tenants using the target system.
[0015] The search module is used to find the target role information corresponding to the target identifier information. The target role information includes the target permission identifier corresponding to the target role identifier.
[0016] The determination module is used to determine the target permission identifier corresponding to the first user based on the target role information.
[0017] The search module is also used to find the target permission information corresponding to the target permission identifier, including the target menu identifier corresponding to the target permission identifier;
[0018] The determination module is also used to determine the target menu identifier corresponding to the target permission identifier based on the target permission information;
[0019] The calling module is used to call the target menu information corresponding to the target menu identifier from multiple pre-configured menu information;
[0020] The display module is used to display the target menu based on the target menu information.
[0021] Thirdly, embodiments of this application provide an electronic device, the device comprising: a processor and a memory storing computer program instructions;
[0022] When the processor executes the computer program instructions, it implements a menu display method as shown in any embodiment of the first aspect.
[0023] Fourthly, embodiments of this application provide a computer storage medium storing computer program instructions, which, when executed by a processor, implement the menu display method shown in any embodiment of the first aspect.
[0024] Fifthly, embodiments of this application provide a computer program product, wherein instructions in the computer program product, when executed by a processor of an electronic device, cause the electronic device to perform the menu display method shown in any embodiment of the first aspect.
[0025] In the menu display method, apparatus, device, medium, and product of this application embodiment, login information of a first user logging into a target system can be obtained. This login information includes target identifier information corresponding to the first user, which includes a target tenant identifier and a target role identifier. The first user is any user under any tenant among multiple tenants using the target system. Then, the target role information corresponding to the target identifier information can be searched. This target role information includes a target permission identifier corresponding to the target role identifier. Therefore, the target permission identifier corresponding to the first user can be determined based on the target role information. Then, the target permission information corresponding to the target permission identifier is searched. This target permission information includes a target menu identifier corresponding to the target permission identifier. Therefore, the target menu identifier corresponding to the target permission identifier can be determined based on the target permission information. Then, the target menu information corresponding to the target menu identifier is called from multiple pre-configured menu information, and the target menu is displayed based on the target menu information. Thus, by pre-configuring multiple menu information, it is not necessary to develop and maintain a separate set of code for each tenant. Any user under any tenant can index the menu information corresponding to that user from the multiple pre-configured menu information using the tenant identifier, role identifier, permission identifier, and menu identifier, thereby displaying the menu corresponding to that user. This results in less code development and less redundant code, reducing maintenance costs, and the maintenance costs will not increase much when adding tenants. Attached Figure Description
[0026] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0027] Figure 1 This is one of the flowcharts of a menu display method provided in one embodiment of this application;
[0028] Figure 2 This is a schematic diagram illustrating a configuration relationship provided in one embodiment of this application;
[0029] Figure 3 This is a second flowchart of a menu display method provided in one embodiment of this application;
[0030] Figure 4 This is a schematic diagram of a menu display provided in one embodiment of this application;
[0031] Figure 5 This is a schematic diagram of the structure of a menu display device provided in one embodiment of this application;
[0032] Figure 6 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this application. Detailed Implementation
[0033] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.
[0034] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, 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 limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.
[0035] It should be noted that the acquisition, storage, use, and processing of data in the technical solution of this application all comply with the relevant provisions of national laws and regulations.
[0036] Furthermore, it should be noted that in the embodiments of this application, certain software, components, models, and other existing solutions in the industry may be mentioned. These should be considered as exemplary, and their purpose is only to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.
[0037] As mentioned in the background technology, many systems are currently used by more than one tenant. With multiple tenants in the system application, menu configuration and permission control are cumbersome. If all the permissions of all tenants are controlled in the application code, it will result in a large amount of code development and a lot of redundant code. When a tenant is added, the maintenance cost will increase exponentially.
[0038] To address the aforementioned technical problems, embodiments of this application provide a menu display method, apparatus, device, medium, and product. This method can acquire login information of a first user logging into a target system. This login information includes target identifier information corresponding to the first user, which includes a target tenant identifier and a target role identifier. The first user is any user under any tenant among multiple tenants using the target system. Then, the method can search for target role information corresponding to the target identifier information. This target role information includes a target permission identifier corresponding to the target role identifier. Therefore, the target permission identifier corresponding to the first user can be determined based on the target role information. Then, the method can search for target permission information corresponding to the target permission identifier, which includes a target menu identifier corresponding to the target permission identifier. Therefore, the target menu identifier corresponding to the target permission identifier can be determined based on the target permission information. Then, the method can call the target menu information corresponding to the target menu identifier from multiple pre-configured menu information, and finally display the target menu based on the target menu information. Thus, by pre-configuring multiple menu information, it is unnecessary to develop and maintain a separate set of code for each tenant. Any user under any tenant can index the menu information corresponding to that user from the multiple pre-configured menu information using the tenant identifier, role identifier, permission identifier, and menu identifier, thereby displaying the menu corresponding to that user. This results in less code development and less redundant code, reducing maintenance costs, and the maintenance costs will not increase much when adding tenants.
[0039] The following is combined with Figure 1 The menu display method provided in the embodiments of this application will be described in detail.
[0040] Figure 1 The diagram illustrates a flowchart of a menu display method according to an embodiment of this application. It should be noted that this menu display method can be applied to a target system or a menu display device, such as... Figure 1 As shown, the menu display method may include the following steps:
[0041] S110, Obtain the login information of the first user logging into the target system;
[0042] S120, Locate the target role information corresponding to the target identifier information;
[0043] S130, determine the target permission identifier corresponding to the first user based on the target role information;
[0044] S140, Locate the target permission information corresponding to the target permission identifier;
[0045] S150, determine the target menu identifier corresponding to the target permission identifier based on the target permission information;
[0046] S160, retrieve the target menu information corresponding to the target menu identifier from multiple pre-configured menu information;
[0047] S170, displays the target menu based on the target menu information.
[0048] Therefore, the login information of the first user logging into the target system can be obtained. This login information includes the target identifier information corresponding to the first user, which includes the target tenant identifier and the target role identifier. The first user is any user under any tenant among multiple tenants using the target system. Then, the target role information corresponding to the target identifier information can be found. This target role information includes the target permission identifier corresponding to the target role identifier. Therefore, the target permission identifier corresponding to the first user can be determined based on the target role information. Then, the target permission information corresponding to the target permission identifier can be found. This target permission information includes the target menu identifier corresponding to the target permission identifier. Therefore, the target menu identifier corresponding to the target permission identifier can be determined based on the target permission information. Then, the target menu information corresponding to the target menu identifier is called from multiple pre-configured menu information, and the target menu is displayed based on the target menu information. In this way, by pre-configuring multiple menu information, it is not necessary to develop and maintain a separate set of code for each tenant. Any user under any tenant can use the tenant identifier, role identifier, permission identifier, and menu identifier to index the menu information corresponding to that user from multiple pre-configured menu information, and realize the display of the menu corresponding to that user. This results in less code development and less redundant code, reducing maintenance costs, and the maintenance costs will not increase much when adding tenants.
[0049] Involving S110, the target system can be configured with multiple tenants.
[0050] The first user can be any user under any tenant among multiple tenants using the target system. Login information may include target identification information corresponding to the first user. Target identification information may include a target tenant identifier and a target role identifier. The target tenant identifier can be a unique identifier of the tenant to which the first user belongs, and the target role identifier can be a unique identifier of the role corresponding to the first user. One first user can correspond to one or more roles.
[0051] For example, the target system can be a cloud customer service system. The tenant can be a company or organization, and the first user can be an employee of the company or organization.
[0052] The login information can be entered by the first user, or it can be the first user's username and password, which are associated with login information.
[0053] Regarding S120, the target role information can be determined from multiple role information based on the target tenant identifier and the target role identifier.
[0054] The target role information may include the target permission identifier corresponding to the target role identifier.
[0055] The target permission identifier can be a unique identifier of the permissions possessed by the role corresponding to the first user.
[0056] For example, role information can be as shown in Table 1. Role information role_info may include tenant identifier multinancy_id, role name role_name, role identifier role_id, permission identifier permission_id, component identifier pk_id, and update time update_time.
[0057] Table 1 - Character Information Table
[0058]
[0059] Regarding S130, the permission identifier included in the target role information can be determined as the target permission identifier corresponding to the first user.
[0060] Regarding S140, the target permission information can be determined from multiple permission information based on the target permission identifier.
[0061] The target permission information may include the target menu identifier corresponding to the target permission identifier.
[0062] For example, permission information can be as shown in Table 2. The permission information permission_info may include permission identifier permission_id, permission name permission_name, menu identifier menu_id, component identifier pk_id, update time update_time, role identifier role_id, and tenant identifier multinancy_id.
[0063] Table 2 - Permission Information Table
[0064]
[0065] Regarding S150, the menu identifier included in the target permission information can be identified as the target menu identifier.
[0066] Regarding S160, the target system can be pre-configured with multiple menu information.
[0067] Specifically, the target menu information corresponding to the target menu identifier can be retrieved from multiple pre-configured menu information based on the target menu identifier.
[0068] For example, the menu information can be as shown in Table 3. The menu information munu_info may include the menu name menu_name, route (not shown in the table), menu identifier menu_id, menu description menu_desc, menu icon menu_icon, menu order menu_order, creation time create_time, parent menu parent_menu, child menu child_menu, and role identifier role_id.
[0069] Table 3 - Menu Information Table
[0070]
[0071] Regarding S170, a target menu can be displayed based on the target menu information. This target menu is the menu that the role corresponding to the first user has permission to view and use.
[0072] In some examples, such as Figure 2 As shown, the target system is configured with multiple tenants: tenant 1, tenant 2, and tenant 3. Each tenant has roles: tenant 1 has roles 1 and 2, tenant 2 has roles 1 and 3, and tenant 3 has roles 3 and 4. Different roles within different tenants are assigned different permissions: role 1 under tenant 1 can be assigned permission 1, role 2 under tenant 1 can be assigned permission 2, role 1 under tenant 2 can be assigned permission 3, role 3 under tenant 2 can be assigned permission 4, role 3 under tenant 3 can be assigned permission 5, and role 4 under tenant 3 can be assigned permission 6. Different permissions have different menus: permission 1 has menu 1, permission 2 has menu 2, permission 3 has menu 3, permission 4 has menu 4, permission 5 has menu 5, and permission 6 has menu 6. Furthermore, a tenant can include multiple users, each of whom can be assigned one or more roles within that tenant.
[0073] In some implementations, to accurately determine the display position of the target menu, the target menu information may include the target display position of the target menu, and S170 may include:
[0074] Display the target menu at the target display location.
[0075] Here, you can pre-set the display position of the menu in the menu information.
[0076] For example, the target display location can be the coordinates of the target menu's display area on the page.
[0077] In this way, the display position of the target menu can be accurately determined based on the target menu information.
[0078] In some implementations, to avoid multiple menus from overlapping, the target menu information may include the target menu's priority and creation time, such as... Figure 3 As shown, S170 may include:
[0079] S171, determine the target display location of the target menu based on priority and creation time;
[0080] S172, Display the target menu at the target display location.
[0081] Here, when there are multiple menus, the menu with higher priority is displayed earlier, and the menu created later is displayed earlier.
[0082] The priority can be the menu order (menu_order) in Table 3 above, and the creation time can be the creation time (create_time) in Table 3 above.
[0083] Priorities can be preset, and different priorities can be set for the same role of different tenants and different roles of the same tenant.
[0084] The creation time can be recorded when the target menu information is created.
[0085] In this way, the display position of a menu can be determined based on its priority and creation time. The probability of multiple menus having the same priority and creation time is very small, so multiple menus can be avoided from being displayed in the same position, thus avoiding overlapping display of multiple menus.
[0086] In some implementations, to make the menu display position more in line with the user's habits, the method may further include the following before S170:
[0087] In response to the first input from the second user, the priority of the first menu in the first menu information corresponding to the first identification information is set to the first priority, and the priority of the second menu in the second menu information corresponding to the second identification information is set to the second priority.
[0088] Here, the second user can be the administrator of the target system.
[0089] The first menu can be the same as the second menu. The first priority can be different from the second priority. The first priority can be used to determine the display position of the first menu. The second priority can be used to determine the display position of the second menu. The first identification information can be different from the second identification information. Both the first and second identification information can include tenant identification and role identification.
[0090] The first input can be an input that sets the priority of the first menu in the first menu information corresponding to the first identifier information to the first priority and sets the priority of the second menu in the second menu information corresponding to the second identifier information to the second priority.
[0091] For example, two different roles can display the same menu items in different positions. For instance, role A uses menu 'a' more frequently and menu 'b' less frequently, so menu 'a' should be displayed earlier and menu 'b' later. Role B uses menu 'b' more frequently and menu 'a' less frequently, so menu 'b' should be displayed earlier and menu 'a' later. Therefore, different priorities can be set for menu 'a' and menu 'b' for the two roles, thus achieving a difference in menu display position. For example, as... Figure 4 As shown, on page 410 corresponding to character A, menu a is displayed above menu b, and on page 420 corresponding to character B, menu b is displayed above menu a. Here, the position above can be considered the position in front, and the position below can be considered the position in back.
[0092] Thus, different tenants with the same role or different roles within the same tenant may use the same menu at different frequencies. Therefore, setting the display position of the same menu differently for the same tenant with the same role or different roles within the same tenant can make the menu display position more in line with the usage habits of the respective users.
[0093] In some implementations, in order to quickly and accurately display the user's corresponding menu, the method may further include the following steps before S110:
[0094] In response to a second input of target information configured by a second user, target information is generated and stored.
[0095] Here, the second input can be the input of the configuration target information.
[0096] The target information may include at least one of the following: role information, permission information, and menu information.
[0097] The role information may include target role information, the permission information may include target permission information, and the menu information may include multiple pre-configured menu items.
[0098] In this way, multiple menu information, multiple role information, and multiple permission information can be pre-configured. Based on the above information, the menu information corresponding to any user under any tenant can be indexed so as to quickly and accurately display the menu corresponding to the user.
[0099] In this embodiment, tenant identifiers, role information, permission information, menu information, and user information are stored in a database. Different tenants are configured, and different roles are assigned to different tenants (role names can be the same across different tenants, but they must be attached to different tenants). Different menus are assigned to roles, and different roles are given to each logged-in user. Through layered configuration control, precise menu configuration is achieved, reducing the difficulty of permission control when multiple tenants use the same system, and further reducing repetitive development work.
[0100] In some implementations, to facilitate maintenance of the target system, after generating and storing the target information in response to the second input of the second user configuration target information, the method may further include:
[0101] In response to the third input from the second user to update the target information, the target information is updated.
[0102] Here, the update operation can include at least one of adding, deleting, or modifying.
[0103] Specifically, users can add, delete, and / or modify at least one of the menu information, role information, and permission information through input.
[0104] In this way, users can add, delete, and modify menu information, role information, and permission information through input, making the maintenance of the target system simpler and reducing maintenance costs.
[0105] There are various methods for configuring and controlling system menus. Front-end single-page applications are diverse and feature-rich. When multiple tenants use the same system simultaneously, precise control over page permissions is necessary to isolate page functions and separate operations for users with different permissions. It's not necessary for all pages to be open to all users; only users with the appropriate permissions should be granted access to the corresponding pages. This effectively reduces code development and allows for precise control over menu permissions.
[0106] In this embodiment, the target system can be configured with multiple tenants, and each tenant can have multiple roles attached. Each tenant maintains its own roles, and the roles used by different tenants are isolated from each other. Each role can maintain different menus. Users of the target system will be assigned different roles, which enables effective configuration and precise control of the display menus for different tenants and different users.
[0107] In this embodiment, by assigning roles to users, the menu information with the user's permissions can be indexed and displayed based on the user's login information through a layered configuration. This achieves precise control over the menu display for different roles and users across multiple tenants, and the configuration and maintenance ensure timely effectiveness.
[0108] In this embodiment, the cloud customer service system can meet the simultaneous use of multiple tenants, solve the access control of multiple organizations (i.e., tenants) in the cloud customer service system, reduce repetitive code development, and has strong reusability; roles are associated with organizations, forming different organizations that are both isolated from each other and compatible and parallel; roles are attached to different menus and roles are specific to users, achieving precise menu control through layer-by-layer association; information is maintained in the database, enabling timely addition, deletion, modification, and timely effect.
[0109] Based on the same inventive concept, embodiments of this application also provide a menu display device. The following, in conjunction with… Figure 5 The menu display device provided in the embodiments of this application will be described in detail.
[0110] Figure 5 A schematic diagram of the structure of a menu display device provided in one embodiment of this application is shown.
[0111] like Figure 5 As shown, the menu display device can be applied to the target system, and the menu display device may include:
[0112] The acquisition module 501 is used to acquire the login information of the first user logging into the target system. The login information includes the target identification information corresponding to the first user. The target identification information includes the target tenant identifier and the target role identifier. The first user is any user under any tenant among the multiple tenants using the target system.
[0113] The lookup module 502 is used to look up the target role information corresponding to the target identifier information. The target role information includes the target permission identifier corresponding to the target role identifier.
[0114] The determination module 503 is used to determine the target permission identifier corresponding to the first user based on the target role information;
[0115] The search module 502 is also used to search for the target permission information corresponding to the target permission identifier, and the target permission information includes the target menu identifier corresponding to the target permission identifier;
[0116] The determining module 503 is also used to determine the target menu identifier corresponding to the target permission identifier based on the target permission information;
[0117] Module 504 is invoked to retrieve the target menu information corresponding to the target menu identifier from multiple pre-configured menu information;
[0118] Display module 505 is used to display the target menu based on the target menu information.
[0119] Therefore, the login information of the first user logging into the target system can be obtained. This login information includes the target identifier information corresponding to the first user, which includes the target tenant identifier and the target role identifier. The first user is any user under any tenant among multiple tenants using the target system. Then, the target role information corresponding to the target identifier information can be found. This target role information includes the target permission identifier corresponding to the target role identifier. Therefore, the target permission identifier corresponding to the first user can be determined based on the target role information. Then, the target permission information corresponding to the target permission identifier can be found. This target permission information includes the target menu identifier corresponding to the target permission identifier. Therefore, the target menu identifier corresponding to the target permission identifier can be determined based on the target permission information. Then, the target menu information corresponding to the target menu identifier is called from multiple pre-configured menu information, and the target menu is displayed based on the target menu information. In this way, by pre-configuring multiple menu information, it is not necessary to develop and maintain a separate set of code for each tenant. Any user under any tenant can use the tenant identifier, role identifier, permission identifier, and menu identifier to index the menu information corresponding to that user from multiple pre-configured menu information, and realize the display of the menu corresponding to that user. This results in less code development and less redundant code, reducing maintenance costs, and the maintenance costs will not increase much when adding tenants.
[0120] In some implementations, to accurately determine the display position of the target menu, the target menu information may include the target display position of the target menu, and the display module 505 may include:
[0121] The display submodule is used to display the target menu at the target display location.
[0122] In some implementations, to avoid multiple menus from overlapping, the target menu information includes the priority and creation time of the target menu, and the display module 505 may include:
[0123] The display submodule is used to display the target menu at the target display location.
[0124] In some embodiments, to make the menu display position more in line with the user's habits, the device may further include:
[0125] The setting module is used to respond to the first input of the second user, set the priority of the first menu in the first menu information corresponding to the first identification information to the first priority, and set the priority of the second menu in the second menu information corresponding to the second identification information to the second priority.
[0126] The first menu is the same as the second menu, but the first priority is different from the second priority. The first priority is used to determine the display position of the first menu, and the second priority is used to determine the display position of the second menu. The first identification information is different from the second identification information. Both the first identification information and the second identification information include tenant identification and role identification.
[0127] In some embodiments, in order to quickly and accurately display the user's corresponding menu, the device may further include:
[0128] The processing module is used to generate and store target information in response to a second input of target information configured by a second user;
[0129] The target information includes at least one of the following: role information, permission information, and menu information. The role information includes the target role information, the permission information includes the target permission information, and the menu information includes multiple pre-configured menu information.
[0130] In some embodiments, the device may further include, for ease of maintenance of the target system:
[0131] The update module is used to update the target information in response to a third input from a second user, and the update operation includes at least one of adding, deleting, or modifying.
[0132] Figure 6 A schematic diagram of the structure of an electronic device provided in one embodiment of this application is shown.
[0133] like Figure 6 As shown, the electronic device 6 is a structural diagram of an exemplary hardware architecture of an electronic device capable of implementing the menu display method and menu display device according to the embodiments of this application. This electronic device may refer to the electronic device in the embodiments of this application.
[0134] The electronic device 6 may include a processor 601 and a memory 602 storing computer program instructions.
[0135] Specifically, the processor 601 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.
[0136] Memory 602 may include mass storage for data or instructions. For example, and not limitingly, memory 602 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 602 may include removable or non-removable (or fixed) media. Where appropriate, memory 602 may be internal or external to an integrated gateway disaster recovery device. In a particular embodiment, memory 602 is non-volatile solid-state memory. In a particular embodiment, memory 602 may include read-only memory (ROM), random access memory (RAM), disk storage media device, optical storage media device, flash memory device, electrical, optical, or other physical / tangible memory storage device. Thus, generally, memory 602 includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to one aspect of this application.
[0137] The processor 601 reads and executes computer program instructions stored in the memory 602 to implement any of the menu display methods in the above embodiments.
[0138] In one example, the electronic device may also include a communication interface 603 and a bus 604. Wherein, as... Figure 6 As shown, the processor 601, memory 602, and communication interface 603 are connected through bus 604 and complete communication with each other.
[0139] The communication interface 603 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.
[0140] Bus 604 includes hardware, software, or both, that couples components of an electronic device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 604 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, any suitable bus or interconnect is contemplated herein.
[0141] The electronic device can execute the menu display method in the embodiments of this application, thereby achieving a combination Figures 1 to 5 The menu display method and apparatus are described.
[0142] Furthermore, in conjunction with the menu display methods in the above embodiments, this application embodiment can provide a computer storage medium for implementation. This computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the menu display methods in the above embodiments.
[0143] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.
[0144] The functional blocks shown in the above-described structural diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.
[0145] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.
[0146] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block in 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, a special-purpose computer, or other programmable menu display device to create a machine such that these instructions, executed via the processor of the computer or other programmable menu display device, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.
[0147] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.
Claims
1. A menu display method, characterized in that, Applied to a target system, the method includes: Obtain login information of a first user logging into the target system. The login information includes target identification information corresponding to the first user. The target identification information includes a target tenant identifier and a target role identifier. The first user is any user under any tenant among multiple tenants using the target system. Find the target role information corresponding to the target identifier information, wherein the target role information includes the target permission identifier corresponding to the target role identifier; The target permission identifier corresponding to the first user is determined based on the target role information; Locate the target permission information corresponding to the target permission identifier, wherein the target permission information includes the target menu identifier corresponding to the target permission identifier; Determine the target menu identifier corresponding to the target permission identifier based on the target permission information; The target menu information corresponding to the target menu identifier is retrieved from a plurality of pre-configured menu information; Display the target menu based on the target menu information; The method further includes: In response to the first input of the second user, the priority of the first menu in the first menu information corresponding to the first identification information is set to the first priority, and the priority of the second menu in the second menu information corresponding to the second identification information is set to the second priority; The first menu is the same as the second menu, the first priority is different from the second priority, the first priority is used to determine the display position of the first menu, the second priority is used to determine the display position of the second menu, the first identification information is different from the second identification information, and both the first identification information and the second identification information include tenant identification and role identification.
2. The method according to claim 1, characterized in that, The target menu information includes the target display position of the target menu, and the step of displaying the target menu based on the target menu information includes: The target menu is displayed at the target display location.
3. The method according to claim 1, characterized in that, The target menu information includes the priority and creation time of the target menu, and the step of displaying the target menu based on the target menu information includes: The target display position of the target menu is determined based on the priority and the creation time. The target menu is displayed at the target display location.
4. The method according to claim 1, characterized in that, The method further includes: In response to a second input of target information configured by a second user, the target information is generated and stored; The target information includes at least one of role information, permission information, and menu information. The role information includes the target role information, the permission information includes the target permission information, and the menu information includes the pre-configured multiple menu information.
5. The method according to claim 4, characterized in that, The method further includes: In response to a third input from the second user to update the target information, an update operation is performed on the target information, the update operation including at least one of adding, deleting, and modifying.
6. A menu display device, characterized in that, Applied to a target system, the device includes: The acquisition module is used to acquire login information of a first user logging into the target system. The login information includes target identification information corresponding to the first user. The target identification information includes a target tenant identifier and a target role identifier. The first user is any user under any tenant among multiple tenants using the target system. The search module is used to search for target role information corresponding to the target identifier information, wherein the target role information includes the target permission identifier corresponding to the target role identifier; The determination module is used to determine the target permission identifier corresponding to the first user based on the target role information; The search module is also used to search for target permission information corresponding to the target permission identifier, the target permission information including the target menu identifier corresponding to the target permission identifier; The determining module is further configured to determine the target menu identifier corresponding to the target permission identifier based on the target permission information; The calling module is used to call the target menu information corresponding to the target menu identifier from multiple pre-configured menu information; The display module is used to display the target menu based on the target menu information; The device further includes: The setting module is used to respond to the first input of the second user, set the priority of the first menu in the first menu information corresponding to the first identification information to the first priority, and set the priority of the second menu in the second menu information corresponding to the second identification information to the second priority; The first menu is the same as the second menu, the first priority is different from the second priority, the first priority is used to determine the display position of the first menu, the second priority is used to determine the display position of the second menu, the first identification information is different from the second identification information, and both the first identification information and the second identification information include tenant identification and role identification.
7. An electronic device, characterized in that, The device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the menu display method as described in any one of claims 1-5.
8. A computer storage medium, characterized in that, The computer storage medium stores computer program instructions, which, when executed by a processor, implement the menu display method as described in any one of claims 1-5.
9. A computer program product, characterized in that, When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device performs the menu display method as described in any one of claims 1-5.
Citation Information
Patent Citations
Menu configuration and display method and device, electronic equipment and storage medium
CN117667094A
Menu Configuration System and Method for Display on an Electronic Device
US20100271312A1