Business menu index display method and device, equipment, medium and product

Abstract

This application relates to a business menu index display method, apparatus, device, medium, and product thereof. The method includes: responding to a user-triggered page access request for obtaining a target page; determining the user's role tag and the target page's type tag; searching a menu database for all menu items matching the role tag and the type tag, constructing a Kanban menu list, linking each menu item to a corresponding function page, and storing the access address of the function page associated with the corresponding menu item in the menu database; embedding the Kanban menu list into the source code of the target page, generating a corresponding result page, and pushing it to the user for display. This application improves the menu item indexing method while taking into account the focus and flexibility of operational functions in complex functional scenarios, making the functional organization of computer program products more reasonable, improving operating efficiency, and enhancing the related user experience.

Description

Technical Field

[0001] This application relates to the field of software engineering technology, and in particular to a method, apparatus, device, medium, or product for displaying a business menu index. Background Technology

[0002] Enterprise Resource Planning (ERP) related software products require functional planning and development for multiple business departments and various operational roles. As enterprises grow and their needs increase, according to the law of entropy increase, the originally relatively simple system will become more and more bloated, making the development and management of the system increasingly difficult.

[0003] The organizational relationships between the functional menus of a software product are one of the key reasons for this difficulty. To illustrate, when planning the functional modules of software, there's a tendency towards a horizontally and vertically ordered organizational structure. For example, a system might be divided into subsystems such as sales, customer service, warehousing, advertising, logistics, and product management. Within each subsystem, corresponding sub-functions are planned and managed vertically as much as possible. On the surface, each functional page performs its own function. However, in actual application, because some functions are cross-functional and cross-role, it's sometimes necessary to break the ordered structure, leading to organizational disorder. As similar situations increase, the challenges faced by developers become increasingly complex, ultimately affecting development efficiency and the orderly nature of system functions.

[0004] The above situation also presents confusion for terminal users. If the system fails to provide various functions to users in a more flexible way, users will be overwhelmed during operation and will not be able to take advantage of the system's organizational efficiency.

[0005] Therefore, the traditional approach of simply dividing system menus by function cannot meet the service needs of complex and overlapping scenarios, leading to inefficient system operation and requiring improvement. Summary of the Invention

[0006] The purpose of this application is to solve the above-mentioned problems by providing a business menu index display method and corresponding apparatus, devices, non-volatile readable storage media, and computer program products.

[0007] According to one aspect of this application, a method for displaying a business menu index is provided, comprising the following steps:

[0008] In response to a user-triggered page access request to obtain a target page, determine the user's role tag and the target page's type tag;

[0009] Search the menu database to find all menu items that match the character tag and the type tag, construct a Kanban menu list, link each menu item to the corresponding function page, and store the access address of the function page associated with the corresponding menu item in the menu database;

[0010] After embedding the Kanban menu list into the source code of the target page, a corresponding result page is generated and pushed to the user for display.

[0011] Optionally, determining the user's role tag and the target page's type tag includes:

[0012] Obtain the role tag from the user's personal account information;

[0013] The target page is determined from the request address of the page access request, and the type tag that maps to the target page is read from the page function mapping table.

[0014] Optionally, all menu items matching the character tag and the type tag are searched from the menu database and constructed as a Kanban menu list. Each menu item is linked to a corresponding function page, including:

[0015] Construct a query vector from the character tags and the type tags;

[0016] Calculate the semantic similarity between the query vector and the tag vector consisting of all the tags carried by each menu item in the menu database, so that each menu item obtains a corresponding semantic similarity.

[0017] Multiple menu items are selected based on semantic similarity, and these multiple menu items are used to construct the Kanban menu list.

[0018] Optionally, multiple menu items are selected based on semantic similarity, and the multiple menu items are constructed into the Kanban menu list, including:

[0019] The menu items in the menu database are sorted in reverse order based on semantic similarity.

[0020] A candidate menu list is created by selecting a number of top-ranked menu items according to a preset quantity.

[0021] Detect whether each menu item in the candidate menu list lists the user's role tag as a prohibited item. If it is listed as a prohibited item, delete the corresponding menu item from the candidate menu list.

[0022] The candidate menu list is converted into the Kanban menu list, so that when the Kanban menu list is displayed, the menu title of the corresponding menu item is shown and linked to the corresponding function page of the menu item.

[0023] Optionally, in response to a user-triggered page access request to obtain a target page, before determining the user's role tag and the target page's type tag, the following steps are included:

[0024] In response to the page publishing request of the function page, obtain the menu title of the corresponding function page, the authorized role tags and type tags, and the role tags listed as prohibited items;

[0025] The access address of the function page is associated with its corresponding menu title, authorized role label and type label, and role label listed as prohibited items and stored in the menu database to be set as the corresponding menu item.

[0026] Optionally, after embedding the Kanban menu list into the source code of the target page, generating the corresponding result page and pushing it to the user for display, the process includes:

[0027] The user's terminal device receives and parses the results page, thereby loading the dashboard menu list embedded in the results page;

[0028] The terminal device generates an index item corresponding to the result page, and stores the index item in a local navigation map in association with the dashboard menu list;

[0029] The terminal device displays the navigation map in a floating window, in which the icons of each index item are displayed in order of the user's access time.

[0030] Optionally, the terminal device displays the navigation map in a floating window, after which the icons of each of the index items are displayed in chronological order of the user's access time, including:

[0031] In response to a touch command applied to the icon of any of the index items, the corresponding Kanban menu list is invoked and displayed.

[0032] In response to a touch command applied to any menu item in the Kanban menu list displayed by the corresponding index item, load and display the corresponding function page.

[0033] According to another aspect of this application, a business menu index display device is provided, comprising:

[0034] The request and response module is configured to respond to a user's page access request for obtaining a target page, and to determine the user's role tag and the target page's type tag.

[0035] The menu construction module is configured to search the menu database for all menu items that match the role tag and the type tag, construct a Kanban menu list, link each menu item to the corresponding function page, and store the access address of the function page associated with the corresponding menu item in the menu database.

[0036] The results push module is configured to embed the dashboard menu list into the source code of the target page, generate a corresponding results page, and push it to the user for display.

[0037] According to another aspect of this application, a business menu index display device is provided, including a central processing unit and a memory, wherein the central processing unit is used to call and run a computer program stored in the memory to execute the steps of the business menu index display method described in this application.

[0038] According to another aspect of this application, a non-volatile readable storage medium is provided, which stores a computer program implemented according to the business menu index display method in the form of computer-readable instructions, wherein the computer program, when invoked by a computer, executes the steps included in the method.

[0039] According to another aspect of this application, a computer program product is provided, including a computer program / instructions that, when executed by a processor, implement the steps of the method described in any embodiment of this application.

[0040] Compared to existing technologies, this application uses a menu database to store the type and role tags of the functional pages to which menu items belong. It matches the type and role tags provided in the user's page retrieval request for the target page with the corresponding information of each menu item in the menu database to achieve menu item search. The searched menu items are then constructed into a Kanban menu list, decoupling the Kanban menu list from the pages while still associating them through type and role tags. This makes the combination of the Kanban menu list and the pages more flexible. For example, it allows developers to create corresponding functional pages for specific menu items and define the corresponding type and role tags, without being constrained by horizontal functional divisions, thus making development more flexible. Furthermore, it allows for adaptive generation of the Kanban menu list for each target page through fuzzy matching, enabling the Kanban menu list to flexibly change according to changes in the tags of the menu items in the menu database. Therefore, this application, by improving the indexing method of menu items, fundamentally changes the menu hierarchy architecture of enterprise resource planning (ERP) related software products, while also considering the focus and flexibility of operational functions in complex functional scenarios. This makes the functional organization more rational, improves the operating efficiency of related computer program products, and enhances the user experience. Attached Figure Description

[0041] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0042] Figure 1 This is a schematic diagram of the architecture of an exemplary network environment for this application;

[0043] Figure 2 This is a flowchart illustrating one embodiment of the business menu index display method of this application;

[0044] Figure 3 This is a flowchart illustrating the process of determining the Kanban menu list based on semantic similarity in an embodiment of this application.

[0045] Figure 4 This is a flowchart illustrating the process of constructing a Kanban menu list in an embodiment of this application;

[0046] Figure 5 This is a schematic diagram illustrating the process of displaying a navigation map on a terminal device in an embodiment of this application;

[0047] Figure 6 This is an exemplary graphical user interface of the present application, which displays page controls corresponding to the Kanban board and a Kanban board menu list;

[0048] Figure 7 The graphical user interface exemplified in this application displays a navigation map, in which page controls for displaying dashboards corresponding to multiple pages are shown;

[0049] Figure 8 The graphical user interface provided is an example of this application, which demonstrates the effect of bringing up a list of Kanban menus from a navigation map;

[0050] Figure 9 This is a schematic block diagram of the business menu index display device of this application;

[0051] Figure 10 This is a schematic diagram of the structure of a business menu index display device used in this application. Detailed Implementation

[0052] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting this application.

[0053] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the term “comprising” as used in this application means the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. It should be understood that when we say an element is “connected” or “coupled” to another element, it can be directly connected or coupled to the other element, or there may be intermediate elements. Furthermore, “connected” or “coupled” as used herein can include wireless connections or wireless coupling. The term “and / or” as used herein includes all or any units and all combinations of one or more associated listed items.

[0054] It will be understood by those skilled in the art that, unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. It should also be understood that terms such as those defined in general dictionaries should be understood to have the same meaning as in the context of the prior art, and should not be interpreted in an idealized or overly formal sense unless specifically defined as herein.

[0055] Those skilled in the art will understand that the terms "client," "terminal," and "terminal device" as used herein include both devices that receive wireless signals, devices that only possess wireless signal receiver capabilities without transmission capabilities, and devices with receiving and transmitting hardware, devices that have receiving and transmitting hardware capable of bidirectional communication over a bidirectional communication link. Such devices may include: cellular or other communication devices such as personal computers or tablets, having single-line displays, multi-line displays, or cellular or other communication devices without multi-line displays; PCS (Personal Communications Service) that can combine voice, data processing, fax, and / or data communication capabilities; PDA (Personal Digital Assistant) that may include radio frequency receivers, pagers, internet / intranet access, web browsers, notepads, calendars, and / or GPS (Global Positioning System) receivers; and conventional laptops and / or handheld computers or other devices that have and / or include radio frequency receivers. As used herein, "client," "terminal," and "terminal device" can be portable, transportable, installed in a means of transportation (air, sea, and / or land), or suitable and / or configured to operate locally and / or in a distributed manner, operating in any other location on Earth and / or in space. "Client," "terminal," and "terminal device" as used herein can also be a communication terminal, an internet access terminal, or a music / video playback terminal, such as a PDA, a MID (Mobile Internet Device), and / or a mobile phone with music / video playback capabilities, or a smart TV, set-top box, etc.

[0056] The hardware referred to by the names "server," "client," and "service node" in this application is essentially an electronic device with the equivalent capabilities of a personal computer. It is a hardware device with the necessary components revealed by the von Neumann architecture, such as a central processing unit (including an arithmetic logic unit and a control unit), memory, input devices, and output devices. The computer program is stored in its memory, and the central processing unit loads the program stored in the secondary storage into the main memory to run it, execute the instructions in the program, and interact with the input and output devices to complete specific functions.

[0057] It should be noted that the concept of "server" used in this application can also be extended to the case of server clusters. Based on the network deployment principles understood by those skilled in the art, the servers should be logically divided. Physically, these servers can be independent of each other but accessible through interfaces, or they can be integrated into a single physical computer or a computer cluster. Those skilled in the art should understand this flexibility and should not use it to constrain the implementation of the network deployment method in this application.

[0058] One or more of the technical features of this application, unless explicitly specified herein, can be deployed on a server and accessed by a client remotely calling the online service interface provided by the server, or can be directly deployed and run on a client for access.

[0059] Unless otherwise specified, the neural network models referenced or potentially referenced in this application may be deployed on a remote server and invoked remotely on the client, or deployed on a client with the capability to invoke directly. In some embodiments, when running on the client, the corresponding intelligence may be acquired through transfer learning in order to reduce the requirements on the client's hardware resources and avoid excessive consumption of the client's hardware resources.

[0060] Unless otherwise specified, all data involved in this application may be stored remotely on a server or on a local terminal device, as long as it is suitable for use by the technical solution of this application.

[0061] Those skilled in the art will understand that although the various methods in this application are described based on the same concept and thus present commonality among them, they can be performed independently unless otherwise specified. Similarly, the various embodiments disclosed in this application are all based on the same inventive concept; therefore, concepts expressed in the same way, as well as concepts that are appropriately changed for convenience but are expressed differently, should be understood equivalently.

[0062] Unless otherwise expressly stated, the various embodiments disclosed in this application can be combined in a cross-cutting manner to flexibly construct new embodiments, as long as such combination does not depart from the inventive spirit of this application and can meet the needs of the prior art or solve a certain deficiency in the prior art. Those skilled in the art should be aware of such modifications.

[0063] The business menu index display method of this application can be programmed into a computer program product and deployed on a client or server to run. For example, in an exemplary application scenario of this application, it can be deployed on the server of an e-commerce platform. In this way, the method can be executed by human-computer interaction with the process of the computer program product through a graphical user interface by accessing the interface opened after the computer program product is run.

[0064] Please see Figure 1 The network architecture adopted in an exemplary application scenario of this application includes a terminal device 80 and a business server 81. The business server 81 can be used to deploy software systems related to enterprise resource planning. For example, the software system can be a dedicated software system used by cross-border e-commerce enterprises, which can realize centralized management of the operational data of multiple online stores distributed across multiple e-commerce platforms. Each online store can have multiple language versions to serve different language regions. Cross-border e-commerce enterprise users can realize centralized control and management of different aspects such as sales, logistics, warehousing, customer service, and advertising through the software system.

[0065] The business menu index display method of this application can be implemented as a computer program product, constructing one of the functional plug-ins of the software system, and deployed together on the business server 81. The terminal device 80 can provide developers with various software resources for publishing the software system, including source code, material resources, style resources, etc., thereby providing various functional pages of the software system. The terminal device 80 can also be accessed by any user operating the software system to access the various pages provided by the business server 81 and use the software system.

[0066] Based on the above explanation of principles, please refer to Figure 2 According to a business menu index display method provided in this application, in one embodiment, the method includes the following steps:

[0067] Step S1100: Respond to the page access request triggered by the user to obtain the target page, and determine the user's role tag and the target page's type tag;

[0068] When any user in the software system needs to access a target page of the software system, they usually log in first to become the corresponding user. Then, by entering an access address in the browser or by clicking a link to another target page on a page in the software system, a page access request corresponding to the target page can be triggered, and the page access request is submitted to the business server.

[0069] The users are typically assigned different roles beforehand, thus obtaining corresponding role tags, such as "operations," "customer service," and "advertising." These role tags indicate that the users have access to the corresponding functions or function pages. Furthermore, they can be further refined to specific job roles such as "sales plan" and "system administrator." As can be seen, based on the flexibility of the technical solution of this application, the setting of role tags can be flexibly divided into multiple levels and positions, and the permissions corresponding to different role tags are allowed to overlap to a certain extent.

[0070] The target page that the user needs to access is a functional page of the software system. In this application, the functional pages of the software system are also assigned corresponding role tags, and in addition, type tags are assigned for multi-level and multi-faceted labeling. For example, a functional page can be labeled with two type tags: "Customer Service" and "General." "Customer Service" is categorized according to functional modules, indicating that it belongs to the customer service subsystem, while "General" is categorized according to operation permissions, indicating that it is applicable to any user. Figuratively speaking, a functional page defined by the above two type tags is a list of customer service questions. The two type tags it carries can be used to indicate that any user can use the target page in the customer service functional module to view the list of customer service questions.

[0071] As can be seen, both role tags and type tags can have relatively complex classification systems. They can be designed as multi-level vertical architectures, and the same level can be designed as a multi-faceted horizontal architecture. Furthermore, the same functional page can be labeled as being available for use by multiple levels and / or multiple aspects.

[0072] To this end, the business server will pre-store the mapping relationship data between each functional page of each software system and its corresponding type tags and role tags. This mapping relationship data is stored in the menu database, and the title information of the functional page is used as its menu title, which is associated with the access address of the functional page. Thus, each functional page actually forms a corresponding menu item in the menu database. The corresponding type tags and type labels of each functional page can be retrieved through the menu database, and these tags can also be used to realize functions such as search and matching.

[0073] When a user triggers a page access request, the business server responds by parsing the user's role tag and the type tag of the target page to be obtained. Based on these tags, it determines the Kanban menu list within the target page. The target page can also be a functional page within the software system, and the Kanban menu list can be implemented as a cross-page functional menu for each page in the software system. This menu can be generated and embedded when the user accesses the target page, allowing the user's terminal device to access the embedded Kanban menu list when displaying the target page, and thus access the functional pages corresponding to the menu items in the Kanban menu list.

[0074] Step S1200: Search the menu database for all menu items that match the role tag and the type tag, construct a Kanban menu list, link each menu item to the corresponding function page, and store the access address of the function page associated with the corresponding menu item in the menu database.

[0075] As mentioned earlier, the menu database already contains role tags, type tags, menu titles, and access addresses for each functional page. The page access request provides the user's role tag and the type tag of the target page to be obtained. Therefore, the correspondence between role tags and type tags can be used to search for multiple matching functional pages from the menu database for the page access request to construct menu items and generate a Kanban menu list for the target page.

[0076] In a more efficient embodiment, a rule-based matching method is used to match the role tags and type tags of the page access request as query terms, and to match the role tags and type tags carried by the menu items corresponding to the function pages in the menu database, thereby matching each menu item carrying the query terms.

[0077] In a more intelligent embodiment, semantic features can be extracted using the role and type tags of the page access request as query terms based on semantic matching. Then, semantic similarity matching is performed with the semantic features extracted from the role and type tags of each menu item in the menu database to match each menu item carrying the query terms.

[0078] Once all menu items are matched from the menu database according to the role tags and type tags corresponding to the page access request and constructed into a corresponding Kanban menu list, each menu item in the Kanban menu list essentially points to a functional page. Therefore, a link to the access address of the corresponding functional page can be created for it, so that the Kanban menu list becomes an interactive object.

[0079] Step S1300: After embedding the Kanban menu list into the source code of the target page, generate the corresponding result page and push it to the user for display.

[0080] After determining the corresponding Kanban menu list for the page access request, the entire Kanban menu list can be embedded into the source code of the target page, and then the corresponding result page is rendered and pushed to the user who sent the page access request. Upon receiving the result page, the user's terminal device parses and displays it, thus showing not only the content of the result page but also the Kanban menu list. Within this list, users can see menu items corresponding to various functional pages associated with the current result page, and touching any menu item will take them to the corresponding functional page.

[0081] As can be seen from the above embodiments, this application uses a menu database to store the type tags and role tags of the functional pages of menu items. It matches the type tags and role tags provided in the user's page retrieval request for the target page with the corresponding information of each menu item in the menu database to achieve menu item search. The searched menu items are then constructed into a Kanban menu list, decoupling the Kanban menu list from the page while still associating it through type tags and role tags. This makes the combination of the Kanban menu list and the page more flexible. For example, it allows developers to develop corresponding functional pages for specific function menu items and define the corresponding type tags and role tags, without being restricted by horizontal functional divisions, making development more flexible. Furthermore, it allows for adaptive generation of the Kanban menu list for each target page through fuzzy matching, enabling the Kanban menu list to flexibly change according to changes in the tags of the menu items in the menu database. Therefore, this application, by improving the indexing method of menu items, fundamentally changes the menu hierarchy architecture of enterprise resource planning related software products, while also considering the focus and flexibility of operational functions in complex functional scenarios. This makes the functional organization more reasonable, improves the operating efficiency of related computer program products, and enhances the user experience.

[0082] Based on any embodiment of this application, determining the user's role tag and the target page's type tag includes:

[0083] Step S1110: Obtain the role tag from the user's personal account information;

[0084] After a user submits a page access request, the user's pre-configured role tags can be obtained from their personal account information. A user may hold one or more role tags, typically pre-selected by the system administrator or their authorized users. If multiple role tags exist, they can be obtained simultaneously.

[0085] Step S1120: Determine the target page from the request address of the page access request, and read the type tag that maps to the target page from the page function mapping table.

[0086] User-submitted page access requests are generally represented by Uniform Resource Locators (URLs), which are addresses. The address usually ends with the filename of the target page to be retrieved. Even if the filename of the target page is missing, it can be determined according to the default settings of the business server. Based on this, the unique feature information of the menu item whose filename is the function page can be used to query all the corresponding type tags in a function mapping table that has a pre-set mapping relationship between filenames and function pages. Of course, in some embodiments, the function mapping table can also be integrated into the menu database so that all the type tags of the target page can also be queried through the menu database. Using a function mapping table to represent the mapping relationship between filenames and function pages independently of the menu database has unique advantages. Mainly, it allows the software system's function pages to be divided into two categories: those recorded in the function mapping table but not in the menu database, and those appearing in the menu database but not in the function mapping table. Thus, the two types of function pages can each perform their respective functions. The target page actively triggered by the user is a function page from the function mapping table, while the menu items in the Kanban menu list on the target page are function pages from the menu database. This facilitates developers in performing corresponding development based on different types of function pages.

[0087] As can be seen from the above embodiments, after a page access request is initiated, the business server can obtain the corresponding type tag and role tag based solely on the page access request. This does not require modification of the existing web page protocol, but it can lay the foundation for the implementation of this application and facilitate the efficient implementation of software engineering.

[0088] Based on any embodiment of this application, please refer to Figure 3 The system retrieves all menu items that match the character tag and type tag from the menu database, constructs a Kanban menu list, and links each menu item to a corresponding function page, including:

[0089] Step S1210: Construct a query vector from the role tags and the type tags;

[0090] When it is necessary to match menu items for a page access request, all role tags of the user corresponding to the page access request and all type tags of the target page to be obtained can be constructed as a query vector. The query vector can be constructed using a corresponding text feature representation model, which can be a deep learning-based neural network model. It is prepared by pre-training and using the text feature representation model to extract and determine each role tag and type tag in advance. In fact, it is a kind of word vector. That is to say, the word vectors corresponding to all role tags and all type tags of the page access request can be organized together to construct the same query vector.

[0091] In some embodiments, a text feature extraction model can be further applied to the query vector to extract deep semantic information and obtain a corresponding query vector to replace the query vector.

[0092] Step S1220: Calculate the semantic similarity between the query vector and the tag vector consisting of all the tags carried by each menu item in the menu database, so that each menu item obtains a corresponding semantic similarity.

[0093] Similarly, for all role tags and all type tags of the function page corresponding to each menu item in the menu database, the corresponding tag vector can be constructed in the same way as the query vector determined in the previous step, so that the function page pointed to by each menu item in the menu database has its corresponding tag vector.

[0094] Based on the query vector and the tag vectors corresponding to each menu item in the menu database, the data distance between the query vector and each tag vector can be calculated to determine the corresponding semantic similarity. The higher the semantic similarity, the more semantically similar the query vector and the tag vector are.

[0095] The data distance algorithm used for data distance calculation can be any algorithm suitable for calculating the distance between vectors, such as the cosine similarity algorithm, Euclidean distance algorithm, Pearson correlation coefficient algorithm, Jaccard coefficient algorithm, etc., as long as the final result is normalized to the representation of the semantic similarity.

[0096] Through similarity calculation, each menu item in the menu database obtains a corresponding semantic similarity, which is used to represent the degree of semantic similarity between it and the query vector.

[0097] Step S1230: Filter out multiple menu items based on semantic similarity, and construct the multiple menu items into the Kanban menu list.

[0098] To construct the Kanban menu list, all menu items in the menu database are filtered based on semantic similarity, and a subset of menu items with high semantic similarity are selected. These menu items are then used to construct the Kanban menu list for the target page.

[0099] As illustrated in the above embodiments, based on semantic similarity, a list of functional pages similar to the target page is matched for each page access request. This constructs a Kanban menu list that allows access to these functional pages, establishing a semantic connection between the target page and these functional pages without relying on strong constraints. This makes the composition of the menu items in the Kanban menu list unrestricted. In other words, for each target page accessed by a user, the functional pages pointed to by each menu item in its Kanban menu list are generated based on the semantics between tags. This language considers both the user's role tag and the target page's type tag. Utilizing these two aspects, when a specific user accesses a target page, a Kanban menu list matching that user and the target page is provided. The Kanban menu list provides functional pages adapted to that specific user and the target page through menu items. This changes the strong constraint between the target page and its referenced functional pages to a semantic constraint. Therefore, whether the developer is developing a page or the user is using it, they do not need to overly focus on the reference relationships between pages; they only need to follow the correspondence between tags to achieve the associated access between pages.

[0100] Based on any embodiment of this application, please refer to Figure 4 Multiple menu items are selected based on semantic similarity, and these multiple menu items are used to construct the Kanban menu list, including:

[0101] Step S1231: Sort the menu items in the menu database in reverse order based on semantic similarity;

[0102] In order to select the target menu items from the menu database, based on obtaining the semantic similarity of each menu item to the query vector, all menu items can be sorted in reverse order according to the semantic similarity, so that the semantic similarity is arranged from largest to smallest.

[0103] Step S1232: Select a number of menu items ranked first according to a preset quantity to form a candidate menu list;

[0104] Considering the limited display space on a page, a maximum number of menu items is typically set for the Kanban menu list. This maximum number is used to truncate the inverted sorting results, thus obtaining several top-ranked menu items corresponding to the maximum number of menu items. These are the target menu items adapted to the page access request. These target menu items are then extracted to form a candidate menu list.

[0105] Step S1233: Detect whether each menu item in the candidate menu list lists the user's role tag as a prohibited item. If it is listed as a prohibited item, delete the corresponding menu item from the candidate menu list.

[0106] Considering the characteristic of this application in determining the menu items of the target page based on tag matching, for some functional pages with relatively independent functions, it is not necessary to rely on other pages to pass parameters to each other. Therefore, it is more convenient for developers to develop various functional pages more freely. However, for some functional pages that may need to rely on the passing of parameters between pages, or have an exclusion relationship with different role tags, it is allowed to set corresponding prohibited items for each functional page in the menu database. The prohibited items can record the role tags that need to be prohibited. When such role tags exist, the corresponding functional page should not be matched to users who hold the role tags.

[0107] Therefore, after determining the candidate menu list, further checks can be performed on prohibited items. The checks can be conducted to see if each menu item in the candidate menu list lists the user's character tag as a prohibited item. If a character tag is listed as a prohibited item, the corresponding menu item is removed from the candidate menu list.

[0108] Step S1234: Convert the candidate menu list into the Kanban menu list, so that when the Kanban menu list is displayed, the menu title of the corresponding menu item is displayed and linked to the corresponding function page of the menu item.

[0109] The candidate menu list obtained through the above process is a satisfactory list. Therefore, based on the final candidate menu list, each menu item can be formatted and encapsulated to convert it into the Kanban menu list. Specifically, based on each menu item in the candidate menu list, the corresponding access address and menu title can be obtained, a hyperlink relationship can be established between the menu title and its access address, and then stored in the Kanban menu list. In the Kanban menu list, the menu items can be sorted in reverse order according to semantic similarity. In this way, when the Kanban menu list is parsed and displayed, the more relevant the function page is to the current page, the more prominently it will be displayed to the user, resulting in higher page access efficiency.

[0110] As can be seen from the above embodiments, this application selects each menu item in the Kanban menu list corresponding to the target page by means of reverse sorting and exclusion of prohibited items. These menu items are usually highly related to the target page and have higher interaction efficiency. This can further reduce the interaction depth when users visit the page and make the interaction efficiency of the software system higher.

[0111] Based on any embodiment of this application, before determining the user's role tag and the target page's type tag in response to a user-triggered page access request for obtaining a target page, the process includes:

[0112] Step S2100: Respond to the page publishing request of the function page, and obtain the menu title, authorized role tags and type tags of the corresponding function page, as well as the role tags listed as prohibited items;

[0113] After developing a functional page, the developer of the software system can publish it, triggering a corresponding page publication request. When triggering this request, the developer is generally required to provide the menu title of the functional page to be published, the authorized role tags, and the corresponding type tags for the functional page. Additionally, they may also be required to submit role tags listed as prohibited. The business server responds to the page publication request, parses it, and obtains the above data.

[0114] Step S2200: Associate the access address of the function page with its corresponding menu title, authorized role label and type label, and role label listed as prohibited items and store them in the menu database, so as to set them as the corresponding menu items.

[0115] Furthermore, the business server stores the source code of the function page, obtains the corresponding access address, and then constructs a mapping relationship data for its menu title, authorized role title and type label, as well as the role label listed as prohibited items, and stores it in the menu database, thereby adding a corresponding menu item to the menu database.

[0116] As can be seen from the above embodiments, according to the idea of ​​this application, developers no longer need to pay excessive attention to the strong reference relationships between pages in the software system. They only need to publish the corresponding functional pages by setting role tags and type tags for the functional pages they develop. Subsequently, according to the tag matching logic of this application, the functional pages they develop can be called in a certain way, so that the functional pages are decoupled from the Kanban menu list but still maintain the association through tags, making the connection between different pages more flexible and greatly improving the development efficiency of the software system.

[0117] Based on any embodiment of this application, please refer to Figure 5After embedding the Kanban menu list into the source code of the target page, generating the corresponding result page and pushing it to the user for display, the process includes:

[0118] Step S3100: The user's terminal device receives the result page and parses and displays it, thereby loading the dashboard menu list embedded in the result page;

[0119] On the terminal device side, when the user receives the result page corresponding to the target page they want, the browser parses it and displays it in the graphical user interface. Since the result page embeds a corresponding dashboard menu list, the page loads the dashboard menu list through parsing. In one embodiment, the entry point of the dashboard menu list can be implemented as a page control such as... Figure 6 As shown, it could be a menu item, a floating window, or something else; those skilled in the art can implement it flexibly.

[0120] Step S3200: The terminal device generates an index item corresponding to the result page, and stores the index item in the local navigation map in association with the dashboard menu list;

[0121] Considering the complexity of the software system's functions and the intelligent customization of the Kanban menu list in this application to adapt to each different page, in this embodiment, a local navigation map corresponding to the user's access process can be created during the user's use of the software system. The Kanban menu list of each page used by the user during the access process can be displayed through the navigation map.

[0122] Therefore, for each result page, a corresponding index item is first generated. This index item can be a unique feature value generated using a hash algorithm based on the access address of the result page. Based on the determined index item for the result page, a mapping relationship is constructed between this index item and its dashboard menu list, and stored in the system's navigation map. This navigation map will also be displayed in the user's graphical user interface as a floating window. When the dashboard menu list is associated with its index item, its source code data is primarily stored so that it can be parsed and displayed accordingly.

[0123] Step S3300: The terminal device displays the navigation map in a floating window, in which the icons of each index item are displayed in order of the user's access time.

[0124] In the graphical user interface of the terminal device, such as Figure 7As shown, a floating window is displayed to represent the path formed by the various pages accessed by the user during the use of the software system. For each result page, that is, for each result page's index, an icon can be displayed in the floating window to represent the corresponding result page. Of course, the corresponding page title can also be displayed below the icon. Different icons can be arranged in order according to the time sequence of the user's access to the corresponding result pages.

[0125] In one embodiment, each illustration may create a hyperlink to the address of its corresponding results page, so that the illustration can be used to return to the corresponding results page.

[0126] As can be seen from the above embodiments, in a complex software system, displaying the various result pages visited by the user through a navigation map can facilitate the user to quickly switch between history pages and improve the efficiency of human-computer interaction.

[0127] Based on any embodiment of this application, the terminal device displays the navigation map in a floating window, and after displaying the illustrations of each index item in the order of the user's access time, the following is included:

[0128] Step S3400: In response to a touch command applied to the illustration of any of the index items, call up and display its corresponding Kanban menu list;

[0129] like Figure 8 As shown, the icons in the navigation map can be linked to their dashboard menu lists. When a user touches any icon in the navigation map, the corresponding touch command is triggered, and the source code data of the dashboard menu list corresponding to the icon's index item can be obtained, parsed, and loaded. This results in the display of each menu item in the corresponding dashboard menu list in a floating window, with each menu item linked to the access address of its corresponding function page.

[0130] Step S3500: Respond to a touch command applied to any menu item in the Kanban menu list displayed by the corresponding index item, and load and display the corresponding function page.

[0131] When a user needs to access a menu item in the Kanban menu list corresponding to a certain icon, they can perform a touch operation on it to trigger the corresponding touch command. In response to the command, the browser retrieves the corresponding function page from the business server based on the access address of the menu item, thereby enabling quick access to the corresponding function page.

[0132] As can be seen from the above embodiments, the flexibility provided by the menu items in the Kanban menu list corresponding to pages rather than by mandatory constraints in this application allows users to quickly search for related Kanban menu lists obtained in the past, making it convenient for users to quickly obtain the corresponding function pages, thereby improving the efficiency of human-computer interaction.

[0133] Please see Figure 9 According to one aspect of this application, a business menu index display device includes a request response module 1100, a menu construction module 1200, and a result push module 1300. The request response module 1100 is configured to respond to a user-triggered page access request for obtaining a target page, and determine the user's role tag and the target page's type tag. The menu construction module 1200 is configured to search a menu database for all menu items matching the role tag and the type tag, construct a Kanban menu list, and link each menu item to a corresponding function page. The access address of the function page is associated with the corresponding menu item and stored in the menu database. The result push module 1300 is configured to embed the Kanban menu list into the source code of the target page, generate a corresponding result page, and push it to the user for display.

[0134] Based on any embodiment of this application, the request response module 1100 includes: a role determination unit, configured to obtain role tags from the user's personal account information; and a type determination unit, configured to determine the target page from the request address of the page access request and read the type tag mapped to the target page from the page function mapping table.

[0135] Based on any embodiment of this application, the menu construction module 1200 includes: a query construction unit configured to construct a query vector from the role tags and the type tags; a similarity calculation unit configured to calculate the semantic similarity between the query vector and the tag vector composed of all tags carried by each menu item in the menu database, so that each menu item obtains a corresponding semantic similarity; and a menu filtering unit configured to filter out multiple menu items based on semantic similarity, and construct the multiple menu items into the dashboard menu list.

[0136] Based on any embodiment of this application, the menu filtering unit includes: a sorting processing subunit, configured to sort each menu item in the menu database in reverse order according to semantic similarity; a filtering subunit, configured to filter a number of the top-ranked menu items to form a candidate menu list; an exception exclusion subunit, configured to detect whether each menu item in the candidate menu list lists the user's role tag as a prohibited item, and when it is listed as a prohibited item, delete the corresponding menu item from the candidate menu list; and a conversion construction subunit, configured to convert the candidate menu list into the dashboard menu list, so that when the dashboard menu list is displayed, the menu title of the corresponding menu item is displayed and linked to the corresponding function page of the menu item.

[0137] Based on any embodiment of this application, the business menu index display device of this application includes: a publishing response module, configured to respond to the page publishing request of the function page, obtain the menu title, authorized role tags and type tags of the corresponding function page, and role tags listed as prohibited items; and a storage processing module, configured to associate the access address of the function page with its corresponding menu title, authorized role tags and type tags, and role tags listed as prohibited items and store them in the menu database, so as to set them as corresponding menu items.

[0138] Based on any embodiment of this application, the business menu index display device of this application includes: a parsing and display module, configured to receive and parse the result page from the user's terminal device, thereby loading the dashboard menu list embedded in the result page; a local index module, configured to generate an index item corresponding to the result page from the terminal device, and store the index item and the dashboard menu list in a local navigation map; and a map presentation module, configured to display the navigation map in a floating window from the terminal device, in which the icons of each index item are displayed in order of the user's access time.

[0139] Based on any embodiment of this application, the business menu index display device of this application includes: an illustration response module, configured to respond to a touch command applied to the illustration of any one of the index items and call up and display its corresponding dashboard menu list; and a menu response module, configured to respond to a touch command applied to any menu item in the dashboard menu list displayed for the corresponding index item and load and display the corresponding function page.

[0140] Another embodiment of this application also provides a business menu index display device. For example... Figure 10The diagram shows the internal structure of a business menu index display device. This device includes a processor, a computer-readable storage medium, a memory, and a network interface connected via a system bus. The computer-readable, non-volatile storage medium stores an operating system, a database, and computer-readable instructions. The database stores information sequences, and when executed by the processor, these computer-readable instructions enable the processor to implement a business menu index display method.

[0141] The processor of the service menu index display device provides computing and control capabilities to support the operation of the entire device. The memory of the device can store computer-readable instructions, which, when executed by the processor, cause the processor to perform the service menu index display method of this application. The network interface of the device is used for communication with a terminal.

[0142] Those skilled in the art will understand that Figure 10 The structure shown is merely a block diagram of a portion of the structure related to the solution of this application, and does not constitute a limitation on the business menu index display device to which the solution of this application is applied. The specific business menu index display device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0143] In this embodiment, the processor is used to execute... Figure 9 The specific functions of each module, submodule, and unit are described, and the memory stores the program code and various data required to execute the aforementioned modules or submodules. The network interface is used to enable data transmission between user terminals or the server. In this embodiment, the non-volatile readable storage medium stores the program code and data required to execute all modules in the business menu index display device of this application, and the server can call the server's program code and data to execute the functions of all modules.

[0144] This application also provides a non-volatile readable storage medium storing computer-readable instructions, which, when executed by one or more processors, cause the one or more processors to perform the steps of the business menu index display method of any embodiment of this application.

[0145] This application also provides a computer program product, including a computer program / instructions that, when executed by one or more processors, implement the steps of the method described in any embodiment of this application.

[0146] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. This computer program can be stored in a non-volatile readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The aforementioned storage medium can be a computer-readable storage medium such as a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM).

[0147] In summary, this application improves the menu item indexing method, fundamentally changing the menu hierarchy of enterprise resource planning (ERP) related software products. It also balances the focus on and flexibility of operational functions in complex scenarios, resulting in a more rational functional organization. This can improve the operating efficiency of related computer program products and enhance the user experience.

Claims

1. A method for displaying a business menu index, characterized in that, include: In response to a user-triggered page access request to obtain a target page, determine the user's role tag and the target page's type tag; The process involves: retrieving all menu items from the menu database that match the character tag and the type tag, constructing a Kanban menu list, and linking each menu item to a corresponding function page. The access address of the function page is associated with the corresponding menu item and stored in the menu database. This includes: constructing a query vector from the character tag and the type tag; calculating the semantic similarity between the query vector and the tag vector formed by all tags carried by each menu item in the menu database, so that each menu item obtains a corresponding semantic similarity; filtering multiple menu items based on semantic similarity, constructing the Kanban menu list from the multiple menu items, and linking each menu item to a corresponding function page. After embedding the Kanban menu list into the source code of the target page, a corresponding result page is generated and pushed to the user for display.

2. The business menu index display method according to claim 1, characterized in that, Determining the user's role tag and the target page's type tag includes: Obtain the role tag from the user's personal account information; The target page is determined from the request address of the page access request, and the type tag that maps to the target page is read from the page function mapping table.

3. The business menu index display method according to claim 1, characterized in that, Multiple menu items are selected based on semantic similarity, and these multiple menu items are constructed into the Kanban menu list. Each menu item is then linked to a corresponding function page, including: The menu items in the menu database are sorted in reverse order based on semantic similarity. A candidate menu list is created by selecting a number of top-ranked menu items according to a preset quantity. Detect whether each menu item in the candidate menu list lists the user's role tag as a prohibited item. If it is listed as a prohibited item, delete the corresponding menu item from the candidate menu list. The candidate menu list is converted into the Kanban menu list, so that when the Kanban menu list is displayed, the menu title of the corresponding menu item is shown and linked to the corresponding function page of the menu item.

4. The business menu index display method according to claim 1, characterized in that, Before responding to a user-triggered page access request to obtain a target page, and before determining the user's role tag and the target page's type tag, the process includes: In response to the page publishing request of the function page, obtain the menu title of the corresponding function page, the authorized role tags and type tags, and the role tags listed as prohibited items; The access address of the function page is associated with its corresponding menu title, authorized role label and type label, and role label listed as prohibited items and stored in the menu database to be set as the corresponding menu item.

5. The business menu index display method according to any one of claims 1 to 4, characterized in that, After embedding the Kanban menu list into the source code of the target page, generating the corresponding result page and pushing it to the user for display, the process includes: The user's terminal device receives and parses the results page, thereby loading the dashboard menu list embedded in the results page; The terminal device generates an index item corresponding to the result page, and stores the index item in a local navigation map in association with the dashboard menu list; The terminal device displays the navigation map in a floating window, in which the icons of each index item are displayed in order of the user's access time.

6. The business menu index display method according to claim 5, characterized in that, The navigation map is displayed in a floating window by the terminal device, and after the icons of each index item are displayed in chronological order of the user's access time, the following steps are included: In response to a touch command applied to the icon of any of the index items, the corresponding Kanban menu list is invoked and displayed. In response to a touch command applied to any menu item in the Kanban menu list displayed by the corresponding index item, load and display the corresponding function page.

7. A business menu index display device, characterized in that, include: The request and response module is configured to respond to a user's page access request for obtaining a target page, and to determine the user's role tag and the target page's type tag. The menu construction module is configured to search the menu database for all menu items that match the role tag and the type tag, construct a Kanban menu list, and link each menu item to a corresponding function page. The access address of the function page is associated with the corresponding menu item and stored in the menu database. This includes: constructing a query vector from the role tag and the type tag; calculating the semantic similarity between the query vector and the tag vector formed by all tags carried by each menu item in the menu database, so that each menu item obtains a corresponding semantic similarity; filtering multiple menu items based on the semantic similarity, constructing the Kanban menu list from the multiple menu items, and linking each menu item to a corresponding function page. The results push module is configured to embed the dashboard menu list into the source code of the target page, generate a corresponding results page, and push it to the user for display.

8. The business menu index display device according to claim 7, characterized in that, The request-response module includes: The role determination unit is configured to obtain role tags from the user's personal account information; The type determination unit is configured to determine the target page from the request address of the page access request and read the type label that maps to the target page from the page function mapping table.

9. A business menu index display device, comprising a central processing unit and a memory, characterized in that, The central processing unit is used to invoke and run a computer program stored in the memory to perform the steps included in the method as described in any one of claims 1 to 6.

10. A non-volatile readable storage medium, characterized in that, It stores a computer program in the form of computer-readable instructions, which, when invoked by a computer, performs the steps included in the method as described in any one of claims 1 to 6.

Images