A system menu generation method, device, equipment and storage medium

Abstract

The present application relates to artificial intelligence, and discloses a system menu generation method, device, equipment and storage medium, the method comprising: generating a menu script file and a file identifier of the menu script file based on the configuration information input by the first user on the menu configuration interface contained in the script file generation tool, and storing the menu script file and the file identifier in association; determining whether the test menu page generated based on the menu script file meets the preset test conditions; if it is determined that the test menu page meets the preset test conditions, storing the menu script file in the background storage of the corresponding designated system; when the second user logs in to the designated system, generating a menu page matching the second user on the front-end page of the designated system based on the menu script file in the background storage. The generation efficiency and accuracy of the generated menu script file can be improved. The application involves blockchain technology, such as writing the above data into the blockchain for use in scenarios such as menu generation.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a system menu generation method, device, equipment and storage medium. Background Art

[0002] With the rapid development of computer technology, various backend management systems are being used more and more frequently, and the menus corresponding to the backend management systems also require a lot of development. At present, it is usually created in the test environment through functions, and then the corresponding menus are created in the production environment. It can be seen that creating menus in the test environment and creating menus in the production environment are two separate operations, and it is easy to have inconsistent operations when creating the same menu for different operations. Therefore, how to unify the menus corresponding to the backend management system in different environments to ensure the accuracy of system menu generation has become an urgent problem to be solved. Summary of the invention

[0003] The embodiments of the present application provide a system menu generation method, apparatus, device and storage medium, which can improve the generation efficiency and accuracy of menu script files, so that the menu script file can ensure the menu generated by the unified background management system in different environments, and ensure the accuracy of system menu generation, and can generate menus matching the user's role based on the menu script file and the user's different roles, thereby improving the adaptability of the menu script file.

[0004] In a first aspect, an embodiment of the present application discloses a system menu generation method, the method comprising:

[0005] Generate a menu script file and a file identifier of the menu script file based on configuration information input by the first user on a menu configuration interface included in a script file generation tool, and store the menu script file and the file identifier in association, wherein the file identifier is used to uniquely indicate the menu script file;

[0006] Determine whether a test condition is preset on the test menu page generated based on the menu script file;

[0007] If it is determined that the test menu page meets the preset test condition, the menu script file is stored in the background storage of the corresponding designated system;

[0008] When the second user logs in to the designated system, a menu page matching the second user is generated on the front-end page of the designated system based on the menu script file in the background storage.

[0009] In a second aspect, an embodiment of the present application discloses a system menu generating device, the device comprising:

[0010] A first generating unit, configured to generate a menu script file and a file identifier of the menu script file based on configuration information input by a first user on a menu configuration interface included in a script file generating tool, and to store the menu script file and the file identifier in association, wherein the file identifier is used to uniquely indicate the menu script file;

[0011] A testing unit, used to determine whether a test menu page generated based on the menu script file has preset test conditions;

[0012] A storage unit, for storing the menu script file in a background storage of a corresponding designated system if it is determined that the test menu page meets the preset test condition;

[0013] The second generating unit is configured to generate a menu page matching the second user on the front-end page of the designated system based on the menu script file in the background storage when the second user logs into the designated system.

[0014] In a third aspect, an embodiment of the present application discloses a system menu generating device, comprising a processor and a memory, wherein the memory is used to store a computer program, the computer program comprises program instructions, and the processor is configured to call the program instructions to execute the method of the first aspect mentioned above.

[0015] In a fourth aspect, an embodiment of the present application discloses a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a processor, the processor executes the method of the first aspect.

[0016] In an embodiment of the present application, a menu script file and a file identifier of the menu script file can be generated based on the configuration information input by the first user on the menu configuration interface contained in the script file generation tool, and the menu script file and the file identifier are stored in association, and the file identifier is used to uniquely indicate the menu script file. Then, it can be determined whether the test menu page generated based on the menu script file presets the test conditions. If it is determined that the test menu page meets the preset test conditions, the menu script file can be stored in the background storage of the corresponding designated system. When the second user logs in to the designated system, a menu page matching the second user can be generated on the front-end page of the designated system based on the menu script file in the background storage. By implementing the above method, the generation efficiency and accuracy of the generated menu script file can be improved, so that the menu script file can ensure the menu generated by the unified background management system in different environments, and ensure the accuracy of the system menu generation, and can generate menus matching their roles based on the menu script file and the different roles of the user, thereby improving the adaptability of the menu script file. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0018] Figure 1 It is a flowchart of a method for generating a system menu provided in an embodiment of the present application;

[0019] Figure 2 It is a schematic diagram of an interface of a script file tool provided in an embodiment of the present application;

[0020] Figure 3 This is a schematic diagram of a task management interface provided in an embodiment of the present application;

[0021] Figure 4 It is a schematic diagram of an interface of a system management interface provided in an embodiment of the present application;

[0022] Figure 5a It is a schematic diagram of a menu management interface provided in an embodiment of the present application;

[0023] Figure 5b This is a schematic diagram of a menu list management configuration interface provided in an embodiment of the present application;

[0024] Figure 5c This is a schematic diagram of a menu modification interface provided in an embodiment of the present application;

[0025] Figure 5d This is a schematic diagram of a menu role management configuration interface provided in an embodiment of the present application;

[0026] Figure 6 This is a schematic diagram of an operation permission management configuration interface provided in an embodiment of the present application;

[0027] Figure 7 It is a schematic diagram of an interface of a role management interface provided in an embodiment of the present application;

[0028] Figure 8 is a schematic diagram of another task management interface provided in an embodiment of the present application;

[0029] Fig. 9 It is a structural schematic diagram of a system menu generating device provided in an embodiment of the present application;

[0030] Fig.10 It is a structural diagram of a system menu generating device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0031] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0032] See also Figure 1 , Figure 1 1 is a flow chart of a system menu generation method provided in an embodiment of the present application. The system menu generation method described in this embodiment is applied to a system menu generation device and can be executed by the system menu generation device. Figure 1 As shown, the system menu generation method includes the following steps:

[0033] S101: Generate a menu script file and a file identifier of the menu script file based on configuration information input by a first user on a menu configuration interface included in a script file generation tool, and store the menu script file and the file identifier in association with each other.

[0034] In one implementation, the script file generation tool can be a unified menu script file generation tool, when the first user (the first user can be any user, such as a tester or developer in an enterprise) needs to generate a menu script file corresponding to a background management system, the script file generation tool can be used to automatically generate a menu script file. Specifically, the first user can perform relevant operations in the script file generation tool to generate a menu script file according to the operation of the first user. For example, the script file generation tool can include a menu configuration interface, and the first user can input relevant configuration information in the menu configuration interface, and after the operation of the first user in the script file generation tool is completed, the system menu generation device can generate a menu script file based on the configuration information input by the first user on the menu configuration interface included in the script file generation tool. Generate a menu script file through the script file generation tool, the user does not need to understand the structural information of various information (such as the binding of role types, the setting of menu operation authority, etc.) in the generated menu script file, and the user only needs to input corresponding information on the relevant menu configuration interface in the script file generation tool, which can reduce the generation time of the menu script file, and the generation complexity, thereby improving the generation efficiency of the menu script file.

[0035] In one implementation, when the system menu generating device generates a menu script file using a script file generating tool, it can also generate a file identifier corresponding to the menu script file, and the file identifier can be used to uniquely indicate the menu script file, wherein the file identifier can be a digital number, a bit value (bit), or other information, which is not limited in this application. After generating the menu script file and the file identifier corresponding to the menu script file, the menu script file and the file identifier can be stored in association, so that the corresponding menu script file can be queried according to the file identifier later, so as to improve the query speed.

[0036] Among them, optionally, the system menu generating device can be a server, which can be an independent server or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (Content Delivery Network, CDN), and big data and artificial intelligence platforms. Optionally, the system menu generating device can also be a terminal device, which can include but is not limited to: smart phones, tablet computers, laptop computers, wearable devices, desktop computers, etc.

[0037] In one implementation, the menu configuration interface included in the script file generation tool may include a task management interface, a system management interface, a menu management interface, an operation authority management configuration interface, and a role management interface. Figure 2 As shown, the terminal used by the first user may be equipped with the script file generation tool, and various menu configuration interfaces in the script file generation tool may be displayed on the terminal screen. For example, when the first user needs to use the script file generation tool to generate a menu script file, the first user may click on various interface controls in the area marked by 21 so that the current interface may jump to the corresponding menu configuration interface. For example, when the first user clicks "Task Management", the interface in the script file generation tool may jump to the task management interface.

[0038] In one implementation, when the first user needs to use the script file generation tool to generate a menu script file, a task for the current menu script file can be created in the task management interface of the script file generation tool. For example, the first user can click Figure 2 New task controls in Figure 2 When the first user clicks the new task control, a task management interface may be displayed in the script file generation tool. The task management interface may be as follows: Figure 3As shown in the page marked by 31 in FIG. 1 , the task management interface can be used to input task information required for configuring the menu script file, and the task information can include task name, task description information, and task tenant information. Figure 3 Enter the corresponding task name, task description information and task tenant information in the task name setting item, task description setting item and tenant setting item on the page marked by 31. Among them, the task description information can usually be a relevant description of the current task, so that subsequent users can understand the current task based on the task description information. The task tenant information can refer to the enterprise to which the specified system (such as a business system) corresponding to the menu script file created by the first user is applied. For example, if the first user creates a corresponding menu script file for a business system in enterprise A, the task tenant information can be "Enterprise A". When the first user is in Figure 3 After entering the above task information in the page marked by 31, a trigger operation (such as a click operation, a press operation, etc.) can be performed on the create immediately control in the page, so that the system menu generating device can obtain the task information input by the first user and add the task information to the menu script file.

[0039] In one implementation, the first user can also input system information related to the specified system settings corresponding to the menu script file in the system management interface of the script file generation tool. The system can be understood as a business system for the specific menu functions provided by the menu script file. For example, the menu script file of the present application can be for the menu to be generated on the agent management system, or for the menu to be generated on the campus education system, etc. The system information may include system identification, system name, etc. For example, see Figure 4 As shown, when the first user clicks on the "system management" marked by 41, the interface in the script file generation tool can jump to the following Figure 4 When the first user needs to set the system information of the system, he can click "Add a new business system" marked by 42. After clicking the "Add a new business system", he can Figure 4 An interface pops up in the interface shown, which can be a specific system management configuration interface. The system management configuration interface allows the first user to input the system identifier, system name, etc. of the system corresponding to the menu script file. After entering the corresponding system information in the system management configuration interface, the system can be configured in the following manner: Figure 4 The input system information is displayed in the existing system list in the system management interface shown. For example, the area marked by 43 can be the system information input in the system management configuration interface, such as the system ID is 420069 and the system name is product factory.

[0040] In one implementation, the menu configuration interface in the script file generation tool may include a menu list management configuration interface. For example, the menu list management configuration interface may be displayed in the script file generation tool, and the menu list management configuration interface may include a menu name setting item, and the menu name setting item may be used by the user to input the menu names corresponding to each menu in the menu list. It is understandable that the menu list includes multiple levels of menus, for example, a first-level menu, a second-level menu, a third-level menu, and the like, wherein the menu names corresponding to each menu described above may include the menu names corresponding to each level of menus. After the first user inputs relevant configuration information in the menu list management configuration interface, the system menu generation device may receive the configuration information of the first user in the menu list management configuration interface, and add the configuration information to the menu script file, and the configuration information may include the menu name input by the first user in the menu list setting item, and the menu name is the menu name of each menu included in the menu list.

[0041] For example, when the first user clicks Figure 5a When the menu management control is in the script file generation tool, the following can be displayed Figure 5a In the menu management interface, when configuring the menu list corresponding to the menu script file, the following can be displayed: Figure 5a The area marked by 51 in the menu management interface is the current menu list generated in the menu list creation process. The menu management interface can be used by the first user to input basic menu information for the menu list. For example, the menu management interface may include a menu adding control marked by 52, a menu modifying control marked by 53, and a menu role control marked by 54. The first user can click on the above-mentioned various controls to configure the corresponding information.

[0042] Optionally, if the first user needs to add a menu, he can click the menu adding control marked by 52. ​​After the first user clicks the menu adding control, the following may be displayed: Figure 5b The interface shown, where Figure 5bThe area marked by 55 is the menu list management configuration interface, which is used for the first user to input menu information corresponding to the menu. It can be seen that in this interface, in addition to configuring the menu name of the menu, you can also configure the menu URL, menu sort number and system to which the menu belongs corresponding to the menu, and you can also configure other menu-related information, which is not limited in this application. When the first user clicks the Create Now control, the system menu generation device can receive the input configuration information and add the configuration information to the menu script file. It can be understood that when creating a complete menu list, the menu list can be created in order from high to low menu levels. For example, a menu list includes multiple levels, such as a first-level menu, a second-level menu, a third-level menu, etc., and each level of menu can also include multiple submenus. Each level of menu or submenu needs to configure its corresponding basic menu information. The first user can click the menu add control multiple times to configure the menu information corresponding to each menu in the menu list. As shown in the figure below: Figure 5a The "existing system menu list" shown in the figure may indicate a menu list being configured, and the first-level menu of the menu list is the "redemption tracking management system".

[0043] Optionally, when configuring the menu information of the menu list, an incorrect configuration may occur. In this case, the first user can click Figure 5a The menu modification control marked by 53 is used to modify the relevant information. When it is detected that the menu modification control is triggered, the following information can be displayed: Figure 5c The interface shown in the figure, wherein the area marked by 56 in the interface is a menu modification interface, and the menu modification interface can be used for the first user to modify the menu information of the configured menu. After the first user enters the modification information in the menu modification interface, he can click the confirm modification control, then, the system menu generation device can receive the input modification information, and can adjust the original information in the menu script file according to the modification information to obtain the adjusted menu script file.

[0044] In one implementation, the menu configuration interface in the script file generation tool may include a menu role management configuration interface. For example, the menu role management configuration interface may be displayed in the script file generation tool, and the menu role management configuration interface may be used by the first user to set the role type corresponding to each menu in the menu list. The menu role management configuration interface may include menu selection items and role setting items. After the first user enters the role type of each menu in the menu list in the menu role management configuration interface, the system menu generation device may receive the configuration information of the first user in the menu role management configuration interface, and add the configuration information to the menu script file. The configuration information may include the menu name entered by the first user in the menu selection item and the role type entered in the role setting item.

[0045] It is understandable that whether the system menu is visible to a certain user can be controlled by role. For example, for a related enterprise system in an enterprise, when users with different roles log in to the system, the menu pages displayed in the system may be different, that is, different users have different permissions for the target menus in the system. In a specific implementation, the menu can be bound to a role. If the user needs to use this menu, he can apply for binding this role through related operations. Then, subsequent users can see the menu corresponding to the role and use the functions of the menu. For example, when the binding role control marked by 54 in 5a is triggered, it can be displayed as follows Figure 5d The interface shown, where Figure 5d The area marked by 57 is a menu role management configuration interface, which can be used for the first user to set the role type corresponding to each menu in the menu list. For example, a menu can set the role corresponding to the review post, or the role of the application post. Among them, a menu can set multiple role types, and the role types that have been set can also be modified on the menu role management configuration interface, for example, the role types that have been set can be deleted.

[0046] In one implementation, the menu configuration interface in the script file generation tool may include an operation authority management configuration interface. For example, the operation authority management configuration interface may be displayed in the script file generation tool, and the operation authority management configuration interface includes a menu selection item, a role setting item, and an operation authority setting item. After the first user enters relevant information in the setting item corresponding to the operation authority management configuration interface, the system menu generation device may receive the configuration information of the first user in the operation authority management configuration interface, and add the configuration information to the menu script file. The configuration information may include the menu name entered by the first user in the menu selection item, the role type entered in the role setting item, and the operation authority entered in the operation authority setting item.

[0047] For example, when a user clicks Figure 6 After operating the permission management control in Figure 6 The operation permission management configuration interface shown in the figure can be used to implement the operation permission settings corresponding to the menu or bind the operation permission to the role type by using the relevant operations of the interface. It can be understood that for a menu in a menu list, after opening the page corresponding to the menu, there may be multiple functions for a certain event in the page, such as a view button, a new button, and a modify button. Different functions correspond to different operations, and these different operations can also set corresponding permissions, that is, the operation permission settings corresponding to the menu can be performed to perform operation permission management. For example, in Figure 6In the area marked by 61 in the menu list, set the relevant information to set the operation permission. In addition to setting the operation permission directly for the menu, you can also bind the operation permission to the role type, that is, instead of setting the operation permission for a menu in the menu list, you can directly bind the operation permission to the above role type. For example, you can Figure 6 Bind the operation permissions to the role type in the area marked by 62.

[0048] Optional, in addition to being able to use Figure 5d The interface shown in the figure can be used to bind the menu to the role type. Figure 7 The interface shown in FIG. 1 binds the menu to the role type. For example, when the first user clicks Figure 2 After the role management controls in Figure 7 In the interface shown, the first user can perform relevant operations on the interface to achieve binding of the role type for the menu.

[0049] In one implementation, after the configuration information of each of the above management interfaces is configured, a menu script file can be generated according to the corresponding configuration information. When the menu script file is generated, a unique identifier of the menu script file can be automatically generated, for example, Figure 8 The following is the task management interface displayed in the script file generation tool after the configuration information of each management interface is configured. Figure 8 The data marked by 81 in the table is the file identifier corresponding to the menu script file generated by the system menu generating device after the menu script file is generated. Moreover, after the menu script file is generated, the corresponding task status displayed in the task management interface can also be changed from the script status to be generated to the following: Figure 8 The script marked by 82 has been generated. When the system menu generating device generates a menu script file and a file identifier of the menu script file, the menu script file and the file identifier can be associated and stored in a specified location, which is not limited in this application.

[0050] In one implementation, before using a script file generation tool to generate a menu script file, it can also be determined whether the script file generation tool can be used to generate a menu script file. For example, it can be determined according to the reuse probability of the menu script file, the storage space corresponding to the script file generation tool, etc. Among them, the reuse probability of the menu script file can be determined according to the user population of the designated system corresponding to the menu script file. If the user population of the designated system is more, it can be understood that, in the case of more user populations, based on the user's role type and the menu script file, various menu pages matching the user are generated on the front-end page of the designated system. There are also more, that is, the reuse probability of the menu script file is also higher. For example, taking the reuse probability of the menu script file as an example for explanation, the preset reuse probability and the reuse probability of the menu script file can be obtained, and the reuse probability of the menu script file is detected to be higher than the preset reuse probability. If the detection result is that the reuse probability of the menu script file is higher than the preset reuse probability, the script file generation tool can be used to generate the menu script file. If the detection result is that the reuse probability of the menu script file is not higher than the preset reuse probability, it can be considered not to use the script file generation tool to generate the menu script file. Thus, it can be ensured that menu script files with a high probability of reuse can be quickly generated using the script file generation tool. For another example, relevant generation rules can be set based on the reuse probability and storage space. For example, when the storage space is insufficient but the reuse probability is low, it can be determined not to generate a menu script file. For another example, when the storage space is insufficient but the reuse probability is high, it can be determined to generate a menu script file.

[0051] In one implementation, when multiple first users use a script file generation tool to perform a task of generating a menu script file in the same time period, the file generation order of the corresponding files can be determined according to the file priority of the menu script file. Among them, the file priority can be positively correlated with the file generation order, that is, the higher the file priority of the menu script file, the faster the corresponding file generation order is, thereby ensuring that more important menu script files can be quickly generated. For example, the file priority can be determined according to the reuse probability of the menu script file. If the reuse probability of a menu script file is higher, the corresponding file priority is also higher.

[0052] S102: Determine whether the test menu page generated based on the menu script file meets a preset test condition.

[0053] In one implementation, the menu script file generated by the script file generation tool can be applied to a variety of scenarios, such as a test environment and an actual production environment. It is understandable that before the menu script file is put into actual production, the menu script file can be tested in a test environment to ensure the validity of the menu script file. For example, a corresponding test menu page can be generated based on the menu script file, and the test menu page is detected to determine whether it meets the preset test conditions. If the test result is that the test menu page meets the preset test conditions, it can be determined that the menu script file is a valid file, and after determining that the menu script file is a valid file, the menu script file can be published in an actual production environment to be put into actual production. If the test result is that the test menu page does not meet the preset test conditions, the menu script file can be adjusted to ensure the validity of the menu script file. Wherein, in the case of determining that the menu script file is invalid, the invalid reason of the invalid menu script file can also be determined, so that the relevant information can be reconfigured in the script file generation tool according to the invalid reason to obtain a valid menu script file. Optionally, the above-mentioned preset test conditions may include: whether the menu list in the test menu page corresponding to different user types is consistent with the configuration in the menu script file, whether the operation permissions corresponding to each menu in the menu list in the test menu page are consistent with the configuration in the menu script file, whether each menu in the menu list in the test menu page can be operated normally, etc.

[0054] In one implementation, before determining whether the test menu page generated based on the menu script file meets the preset test conditions, a script file request sent by a third user may also be obtained, and the script file request carries a file identifier. Then, after receiving the script file request, the menu script file corresponding to the file identifier may be obtained from the storage according to the file identifier. The menu script file obtained may be used to perform subsequent test tasks. Optionally, after obtaining the script file request sent by the third user, it may also be determined whether the third user has the request authority. If it is determined that the third user has the corresponding request authority, the menu script file corresponding to the file identifier may be obtained from the storage according to the file identifier. If the third user does not have the corresponding request authority, the corresponding menu script file may not be obtained according to the file identifier. For example, user request authorities corresponding to each menu script file may be pre-set in the storage.

[0055] S103: If it is determined that the test menu page meets the preset test conditions, the menu script file is stored in the background storage of the corresponding designated system.

[0056] In one implementation, if it is determined that the test menu page meets the preset test conditions, it can be determined that the menu script file is valid. Then, the menu script file can be applied in an actual production environment. For example, the menu script file can be stored in the background storage of the corresponding specified system, so that the menu script file can be used to generate the corresponding menu page on the front-end page of the specified system later.

[0057] S104: When the second user logs in to the designated system, a menu page matching the second user is generated on the front-end page of the designated system based on the menu script file in the background storage.

[0058] In one implementation, whether the menu of the backend management system is visible to a certain user is controlled by the user's role type. As can be seen from the above, each submenu in the menu list can be bound to a certain role type. Then, if a user needs to log in to a certain system, he can apply to bind to this certain role type. For example, in an enterprise, the role types of employees may include ordinary employees, important employees, leaders, and administrators. Then, when employees of different role types log in to the system, the displayed menu pages may be different. As can be seen from the above, each menu in the menu list can also be bound to the corresponding operation permissions, or different role types can also be bound to different operation permissions. Then, the operation permissions of each menu in the menu page displayed by Sohu later are also different.

[0059] In one implementation, the target role type of the second user can be obtained to determine the target menu list and menu operation authority associated with the target role type from the menu script file based on the target role type. After the target menu list and menu operation authority for the second user are determined, a menu page matching the second user can be generated on the front-end page of the designated system according to the target menu list and menu operation authority. For example, taking an enterprise as an example, assuming that the second user is an employee in the enterprise, and the employees in the enterprise can generally include ordinary employees, important employees, leaders, administrators, etc., that is, the target role type of the second user can include ordinary employees, important employees, leaders, administrators, etc. Then, it can be understood that different types of employees may display different menu pages when logging into the designated system. For example, when an administrator logs into the designated system, a menu page of the management type is displayed on the front-end page of the designated system. For example, when a leader logs into the designated system, a menu page of the leader type is displayed on the front-end page of the designated system.

[0060] In one implementation, after the menu script file is generated for the first time, it is also possible to detect whether the menu script file has been updated. For example, if the menu name of a submenu in the menu list changes, or the role type bound to a submenu changes, or other changes occur in other menu script files, it can be understood that the menu script file has been updated. If it is detected that the menu script file has been updated, an update task can be triggered to update the menu page according to the updated menu script file to obtain the replaced menu page, so that when the user logs in to the specified system, the menu page displayed on the front-end page of the specified system can also be updated in real time, thereby improving the user experience.

[0061] In an embodiment of the present application, a menu script file and a file identifier of the menu script file can be generated based on the configuration information input by the first user on the menu configuration interface contained in the script file generation tool, and the menu script file and the file identifier are stored in association, and the file identifier is used to uniquely indicate the menu script file. Then, it can be determined whether the test menu page generated based on the menu script file presets the test conditions. If it is determined that the test menu page meets the preset test conditions, the menu script file can be stored in the background storage of the corresponding designated system. When the second user logs in to the designated system, a menu page matching the second user can be generated on the front-end page of the designated system based on the menu script file in the background storage. The generation efficiency and accuracy of the generated menu script file can be improved, so that the menu script file can ensure the menu generated by the unified background management system in different environments, and ensure the accuracy of the system menu generation, and can generate menus matching their roles based on the menu script file and the different roles of the user, thereby improving the adaptability of the menu script file.

[0062] See also Fig. 9 , Fig. 9 : is a structural diagram of a system menu generating device provided in an embodiment of the present application, wherein the system menu generating device comprises:

[0063] A first generating unit 901 is used to generate a menu script file and a file identifier of the menu script file based on configuration information input by a first user on a menu configuration interface included in a script file generating tool, and store the menu script file and the file identifier in association with each other, wherein the file identifier is used to uniquely indicate the menu script file;

[0064] A testing unit 902, used to determine whether a test menu page generated based on the menu script file has preset test conditions;

[0065] The storage unit 903 is used to store the menu script file in the background storage of the corresponding designated system if it is determined that the test menu page meets the preset test condition;

[0066] The second generating unit 904 is configured to generate a menu page matching the second user on the front-end page of the designated system based on the menu script file in the background storage when the second user logs into the designated system.

[0067] In one implementation, the second generating unit 904 is specifically configured to:

[0068] Obtaining the target role type of the second user;

[0069] Determine a target menu list and menu operation authority associated with the target role type from the menu script file based on the target role type;

[0070] A menu page matching the second user is generated on the front-end page of the designated system according to the target menu list and the menu operation authority.

[0071] In one implementation, the menu configuration interface includes a menu list management configuration interface; the first generating unit 901 is specifically configured to:

[0072] Displaying the menu list management configuration interface in the script file generation tool, wherein the menu list management configuration interface includes a menu name setting item;

[0073] Receive the configuration information of the first user in the menu list management configuration interface, and add the configuration information to the menu script file, wherein the configuration information includes the menu name input by the first user in the menu list setting item, and the menu name is the menu name of each submenu included in the menu list.

[0074] In one implementation, the menu configuration interface includes a menu role management configuration interface; the first generating unit 901 is specifically used to:

[0075] Displaying the menu role management configuration interface in a script file generation tool, wherein the menu role management configuration interface includes menu selection items and role setting items;

[0076] The configuration information of the first user in the menu role management configuration interface is received, and the configuration information is added to the menu script file, wherein the configuration information includes the menu name input by the first user in the menu selection item and the role type input in the role setting item.

[0077] In one implementation, the menu configuration interface includes an operation authority management configuration interface; the first generating unit 901 is specifically used to:

[0078] Displaying the operation authority management configuration interface in the script file generation tool, the operation authority management configuration interface including menu selection items, role setting items and operation authority setting items;

[0079] Receive the configuration information of the first user in the operation authority management configuration interface, and add the configuration information to the menu script file, wherein the configuration information includes the menu name entered by the first user in the menu selection item, the role type entered in the role setting item, and the operation authority entered in the operation authority setting item.

[0080] In one implementation, the testing unit 902 is further configured to:

[0081] Obtaining a script file request sent by a third user, wherein the script file request carries the file identifier;

[0082] The menu script file corresponding to the file identifier is obtained from storage according to the file identifier.

[0083] In one implementation, the second generating unit 904 is further configured to:

[0084] Detect whether the menu script file is updated;

[0085] If it is detected that the menu script file is updated, an update task is triggered to update the menu page according to the updated menu script file to obtain a replaced menu page.

[0086] It is understandable that the functions of the various functional units of the system menu generating device described in the embodiment of the present application can be based on Figure 1 The specific implementation process of the method in the method embodiment can be referred to Figure 1 The relevant description of the method embodiment will not be repeated here.

[0087] In the embodiment of the present application, the first generation unit 901 generates a menu script file and a file identifier of the menu script file based on the configuration information input by the first user on the menu configuration interface contained in the script file generation tool, and stores the menu script file and the file identifier in association, and the file identifier is used to uniquely indicate the menu script file; the test unit 902 determines whether the test menu page generated based on the menu script file presets the test condition; if the storage unit 903 determines that the test menu page meets the preset test condition, the menu script file is stored in the background storage of the corresponding designated system; the second generation unit 904 generates a menu page matching the second user on the front-end page of the designated system based on the menu script file in the background storage when the second user logs in to the designated system. The generation efficiency and accuracy of the generated menu script file can be improved.

[0088] See also Fig.10 , Fig.10 1 is a schematic diagram of the structure of a system menu generating device provided in an embodiment of the present application. The system menu generating device includes: a processor 1001, a memory 1002 and a network interface 1003. The processor 1001, the memory 1002 and the network interface 1003 can exchange data.

[0089] The processor 1001 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0090] The memory 1002 may include a read-only memory and a random access memory, and provide program instructions and data to the processor 1001. A portion of the memory 1002 may also include a random access memory. When the processor 1001 calls the program instructions, it is used to execute:

[0091] Generate a menu script file and a file identifier of the menu script file based on configuration information input by the first user on a menu configuration interface included in a script file generation tool, and store the menu script file and the file identifier in association, wherein the file identifier is used to uniquely indicate the menu script file;

[0092] Determine whether a test condition is preset on the test menu page generated based on the menu script file;

[0093] If it is determined that the test menu page meets the preset test condition, the menu script file is stored in the background storage of the corresponding designated system;

[0094] When the second user logs in to the designated system, a menu page matching the second user is generated on the front-end page of the designated system based on the menu script file in the background storage.

[0095] In one implementation, the processor 1001 is specifically configured to:

[0096] Obtaining the target role type of the second user;

[0097] Determine a target menu list and menu operation authority associated with the target role type from the menu script file based on the target role type;

[0098] A menu page matching the second user is generated on the front-end page of the designated system according to the target menu list and the menu operation authority.

[0099] In one implementation, the menu configuration interface includes a menu list management configuration interface; the processor 1001 is specifically configured to:

[0100] Displaying the menu list management configuration interface in the script file generation tool, wherein the menu list management configuration interface includes a menu name setting item;

[0101] Receive the configuration information of the first user in the menu list management configuration interface, and add the configuration information to the menu script file, wherein the configuration information includes the menu name input by the first user in the menu list setting item, and the menu name is the menu name of each submenu included in the menu list.

[0102] In one implementation, the menu configuration interface includes a menu role management configuration interface; the processor 1001 is specifically configured to:

[0103] Displaying the menu role management configuration interface in a script file generation tool, wherein the menu role management configuration interface includes menu selection items and role setting items;

[0104] The configuration information of the first user in the menu role management configuration interface is received, and the configuration information is added to the menu script file, wherein the configuration information includes the menu name input by the first user in the menu selection item and the role type input in the role setting item.

[0105] In one implementation, the menu configuration interface includes an operation authority management configuration interface; the processor 1001 is specifically configured to:

[0106] Displaying the operation authority management configuration interface in the script file generation tool, the operation authority management configuration interface including menu selection items, role setting items and operation authority setting items;

[0107] Receive the configuration information of the first user in the operation authority management configuration interface, and add the configuration information to the menu script file, wherein the configuration information includes the menu name entered by the first user in the menu selection item, the role type entered in the role setting item, and the operation authority entered in the operation authority setting item.

[0108] In one implementation, the processor 1001 is further configured to:

[0109] Obtaining a script file request sent by a third user, wherein the script file request carries the file identifier;

[0110] The menu script file corresponding to the file identifier is obtained from storage according to the file identifier.

[0111] In one implementation, the processor 1001 is further configured to:

[0112] Detect whether the menu script file is updated;

[0113] If it is detected that the menu script file is updated, an update task is triggered to update the menu page according to the updated menu script file to obtain a replaced menu page.

[0114] In a specific implementation, the processor 1001 and the memory 1002 described in the embodiments of the present application can execute the embodiments of the present application. Figure 1 The implementation method described in the system menu generation method provided can also be used to implement the embodiments of this application. Fig. 9 The implementation method of the described system menu generating device will not be described in detail here.

[0115] In the embodiment of the present application, the processor 1001 can generate a menu script file and a file identifier of the menu script file based on the configuration information input by the first user on the menu configuration interface contained in the script file generation tool, and store the menu script file and the file identifier in association, wherein the file identifier is used to uniquely indicate the menu script file; determine whether a test menu page generated based on the menu script file has preset test conditions; if it is determined that the test menu page meets the preset test conditions, store the menu script file in the background storage of the corresponding designated system; when the second user logs in to the designated system, generate a menu page matching the second user on the front-end page of the designated system based on the menu script file in the background storage. The generation efficiency and accuracy of the generated menu script file can be improved.

[0116] The present application also provides a computer-readable storage medium in which program instructions are stored. When the program is executed, it may include: Figure 1 Part or all of the steps of the system menu generating method in the corresponding embodiment.

[0117] It should be noted that, for the above-mentioned various method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0118] A person skilled in the art may understand that all or part of the steps in the various methods of the above embodiments may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0119] It should be emphasized that in order to further ensure the privacy and security of the above data, the above data can also be stored in a node of a blockchain. Among them, the blockchain referred to in this application is a new application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm, etc. Blockchain is essentially a decentralized database, a string of data blocks generated by cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify the validity of its information (anti-counterfeiting) and generate the next block. The blockchain can include the blockchain underlying platform, the platform product service layer, and the application service layer.

[0120] The above is a detailed introduction to a system menu generation method, device, equipment and storage medium provided in an embodiment of the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for general technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A system menu generation method, characterized in that: include: Generate a menu script file and a file identifier of the menu script file based on configuration information input by the first user on a menu configuration interface included in a script file generation tool, and store the menu script file and the file identifier in association, wherein the file identifier is used to uniquely indicate the menu script file; Determine whether the test menu page generated based on the menu script file meets the preset test conditions; If it is determined that the test menu page meets the preset test condition, the menu script file is stored in the background storage of the corresponding designated system; When the second user logs in to the designated system, a menu page matching the second user is generated on the front-end page of the designated system based on the menu script file in the background storage.

2. The method according to claim 1, characterized in that The step of generating a menu page matching the second user on the front-end page of the designated system based on the menu script file in the background storage includes: Obtaining the target role type of the second user; Determine a target menu list and menu operation authority associated with the target role type from the menu script file based on the target role type; A menu page matching the second user is generated on the front-end page of the designated system according to the target menu list and the menu operation authority.

3. The method according to claim 1, characterized in that The menu configuration interface includes a menu list management configuration interface; the menu script file is generated based on the configuration information input by the first user on the menu configuration interface contained in the script file generation tool, including: Displaying the menu list management configuration interface in the script file generation tool, wherein the menu list management configuration interface includes a menu name setting item; Receive the configuration information of the first user in the menu list management configuration interface, and add the configuration information to the menu script file, wherein the configuration information includes the menu name input by the first user in the menu list setting item, and the menu name is the menu name of each menu included in the menu list.

4. The method according to claim 3, characterized in that The menu configuration interface includes a menu role management configuration interface; the menu script file is generated based on the configuration information input by the first user on the menu configuration interface contained in the script file generation tool, including: Displaying the menu role management configuration interface in a script file generation tool, wherein the menu role management configuration interface includes menu selection items and role setting items; The configuration information of the first user in the menu role management configuration interface is received, and the configuration information is added to the menu script file, wherein the configuration information includes the menu name input by the first user in the menu selection item and the role type input in the role setting item.

5. The method according to claim 3, characterized in that: The menu configuration interface includes an operation authority management configuration interface; the menu script file is generated based on the configuration information input by the first user on the menu configuration interface included in the script file generation tool, including: Displaying the operation authority management configuration interface in the script file generation tool, the operation authority management configuration interface including menu selection items, role setting items and operation authority setting items; Receive the configuration information of the first user in the operation authority management configuration interface, and add the configuration information to the menu script file, wherein the configuration information includes the menu name entered by the first user in the menu selection item, the role type entered in the role setting item, and the operation authority entered in the operation authority setting item.

6. The method according to claim 1, characterized in that Before determining whether the test menu page generated based on the menu script file meets the preset test condition, the method further includes: Obtaining a script file request sent by a third user, wherein the script file request carries the file identifier; The menu script file corresponding to the file identifier is obtained from storage according to the file identifier.

7. The method according to any one of claims 1 to 6, characterized in that: After generating a menu page matching the second user on the front-end page of the designated system based on the role type of the second user and the menu script file, the method further includes: Detect whether the menu script file is updated; If it is detected that the menu script file is updated, an update task is triggered to update the menu page according to the updated menu script file to obtain a replaced menu page.

8. A system menu generating device, characterized in that: include: A first generating unit, configured to generate a menu script file and a file identifier of the menu script file based on configuration information input by a first user on a menu configuration interface included in a script file generating tool, and to store the menu script file and the file identifier in association, wherein the file identifier is used to uniquely indicate the menu script file; A testing unit, used to determine whether a test menu page generated based on the menu script file has preset test conditions; A storage unit, for storing the menu script file in a background storage of a corresponding designated system if it is determined that the test menu page meets the preset test condition; The second generating unit is configured to generate a menu page matching the second user on the front-end page of the designated system based on the menu script file in the background storage when the second user logs into the designated system.

9. A system menu generating device, characterized in that: The method comprises a processor and a memory, wherein the memory is used to store a computer program, the computer program comprises program instructions, and the processor is configured to call the program instructions to execute the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a processor, the processor is caused to perform the method according to any one of claims 1 to 7.

Images