Menu management device and menu management method

Abstract

The invention provides a menu management device and a menu management method, wherein the menu management device comprises a data loading unit used for loading menu data used for generating a menu; a data filtering unit used for carrying out filtering for the menu data according to a presupposed strategy; and a menu generating unit used for generating menu options and displaying the menu options according to the filtered menu data. Through the menu management device and the menu management method, different strategies can be formulated to carry out filtering for data for generating the menu, therefore, the generated menu can be ensured to accord with an application scenario of the menu and customization demands for clients.

Description

technical field [0001] The invention relates to the technical field of computers, in particular to a menu management device and a menu management method. Background technique [0002] In a large-scale ERP system, the function menu includes the function list of each subsystem (module). The display effect, ease of use and loading efficiency of the function menu have a great impact on users, and occupy an important position in the functions of the ERP system. . The function menu generally has the following characteristics and requirements: [0003] 1. The menu item belongs to a certain subsystem, and whether the menu item is loaded needs to be judged according to whether the subsystem is installed or enabled. [0004] 2. The name and display rules of the content function menu are dynamically changed according to the needs of different contexts. For example, it will filter according to whether the user has certain function permissions, and the menu items without permissions w...

AI Technical Summary

Problems solved by technology

[0005] 3. Maintainability, users may modify the name according to actual needs, or adjust the display order and other logic

If the definition of the menu item is saved in a file, such as an XML file, it will cause deployment problems when supporting the secondary development of the plug-in. For example, plug-in A adds a menu item A1, and the configuration definition file of the menu needs to be added. For example, "menu definition.xml", in the installation package of the plug-in, plug-in B adds a menu item B1, and also needs to put the changed menu definition file "menu definition.xml" into the installation package of plug-in B, If the user installs plug-in A and plug-in B separately, there will be a problem that the menu definition file "menu definition. This increases the difficulty for secondary developers, and a slight negligence will lead to system menu definition file confusion, and eventually cause the system to be unavailable

[0010] 2. Loading strategy problem

Whether the menu item is displayed or the name is changed may be determined according to the enabling and installation of the subsystem, or the setting of the system parameters, or whether the operator has the corresponding authority. The current existing implementations either do not have this function, Either through hard-coding, both of which are not flexible enough to adapt to customer needs. Hard-coding leads to a high degree of coupling between menus and components, and cannot achieve complete decoupling, which is not conducive to later maintenance.

[0011] 3. Menu data maintenance issues

Since the amount of data in the menu is generally more than several thousand, no matter whether the menu data is in the database or in the file, if there is no visual tool to modify it, it will be cumbersome and error-prone. Once there is a mistake, the system will be unavailable

Images