Menu version configuration method and menu version data display method

By generating personalized route configuration files and implementing RBAC permission verification, the problems of code redundancy and inaccurate menu version matching in multi-region and multi-organization front-end software systems are solved, achieving efficient and secure menu version display and configuration.

CN122431743APending Publication Date: 2026-07-21BEIJING GUODIANTONG NETWORK TECH CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610312070.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-03-13
Publication Date
2026-07-21

AI Technical Summary

Technical Problem

Existing technologies suffer from problems such as high code redundancy, low operating efficiency, inaccurate menu version matching and display, and chaotic permissions in front-end software systems in multiple regions and organizations, making it difficult to meet differentiated customization needs.

Method used

By adopting a menu version configuration method, personalized routing configuration files are generated by receiving user login information and version requirement information. Combined with visual operation and RBAC permission verification, accurate matching and efficient display of menu versions are achieved.

Benefits of technology

It enables efficient menu version configuration and display in multi-region and multi-organization scenarios, reduces system storage and loading burden, improves operating efficiency and user experience, and ensures the security and consistency of permissions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122431743A_ABST
    Figure CN122431743A_ABST
Patent Text Reader

Abstract

The application provides a menu version configuration method and a menu version data display method. The configuration method comprises receiving user login information, version requirement information and a public routing configuration file; determining a personalized routing configuration file corresponding to the user login information according to the user login information, the version requirement information and the public routing configuration file; taking the public routing configuration file as a reference template, uniformly declaring the core component only once, and performing incremental correction on the reference template only, so that repeated coding of components in multiple independent routing files is avoided. In response to receiving modified menu information of the user, the personalized routing configuration file is modified according to the modified menu information to determine a target menu configuration routing file. The menu modification is realized through visual operation, and the intervention of a developer in coding is not required. When a new version requirement is added, the routing tree structure does not need to be redesigned.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of menu version configuration technology, and in particular to a menu version configuration method and a menu version data display method. Background Technology

[0002] With the accelerated pace of digital transformation, the application scenarios of front-end software systems are becoming increasingly complex, especially with the growing prevalence of differentiated customization needs across multiple regions and organizations. Currently, most mainstream front-end software systems are developed using frameworks such as Vue, implementing page navigation and menu management through front-end routing mechanisms. This model can run stably in basic application scenarios with unified functionality. However, in scenarios requiring differentiated customization of interface layout, interaction flow, and data display for multiple provincial companies and organizational levels, the original system architecture is gradually revealing its inability to adapt.

[0003] To address the diverse customization needs across different regions, existing technologies generally employ a solution of hard-coding multiple independent routing files to implement branching logic. Regarding menu version configuration, this hard-coding approach has significant drawbacks. Core business components must be repeatedly declared in multiple routing files, resulting in extremely high code redundancy. This not only increases the system's storage and loading burden but also reduces system efficiency. Furthermore, in terms of menu data display, the lack of a unified configuration and version management system makes it difficult for existing systems to achieve accurate matching and efficient display of menu versions. Summary of the Invention

[0004] In view of this, the purpose of this application is to propose a menu version configuration method and a menu version data display method to solve some or all of the technical problems existing in the background art.

[0005] To achieve the above objectives, this application provides a menu version configuration method, including:

[0006] Receive user login information, version requirement information, and public routing configuration files; Based on the user login information, the version requirement information, and the public routing configuration file, determine the personalized routing configuration file corresponding to the user login information; In response to receiving the user's modified menu information, the personalized routing configuration file is modified according to the modified menu information to determine the target menu configuration routing file.

[0007] Optionally, the user login information includes: organization information and permission information; Based on the user login information, the version requirement information, and the public routing configuration file, determine the personalized routing configuration file corresponding to the user login information, including: Generate a feature code based on the organizational information; Based on the organizational information, the target requirement information is determined by searching for the requirement information corresponding to the organizational information in the version requirement information. Based on the target requirement information and the permission information, the public routing configuration file is modified, and a mapping relationship is established between the signature code and the modified public routing file to obtain the personalized routing configuration file corresponding to the signature code.

[0008] Optionally, the modified menu information includes: information on newly added functional modules; In response to receiving user-modified menu information, the personalized routing configuration file is modified according to the modified menu information, and the target menu routing configuration file is determined, including: In response to receiving user-modified menu information indicating the addition of a new functional module, new route configuration information is generated based on the new functional module information. The newly added route configuration information is added to the personalized route configuration file corresponding to the user login information to obtain the target menu route configuration file.

[0009] Optionally, the modified menu information includes: deleting functional module information; In response to receiving user-modified menu information, the personalized routing configuration file is modified according to the modified menu information, and the target menu routing configuration file is determined, including: In response to receiving user's modified menu information as "delete function module information", the name of the function module to be deleted is determined based on the "delete function module information"; In the personalized routing configuration file corresponding to the user login information, delete the routing configuration information corresponding to the name to obtain the target menu routing configuration file.

[0010] Optionally, the modified menu information includes: modifying the location information of functional modules; In response to receiving user-modified menu information, the personalized routing configuration file is modified according to the modified menu information, and the target menu routing configuration file is determined, including: In response to receiving user's modified menu information as modifying the location information of a functional module, the target location of the functional module in the personalized routing configuration file is determined based on the modified functional module location information. The current functional module and the functional module to be modified in the target location are swapped to obtain the target menu routing configuration file.

[0011] Based on the same inventive concept, this application also provides a method for displaying menu version data, including: Received user login information; The user login information is parsed to determine the user's unique identifier; The initial menu version information is determined based on the user login information, the user feature code, and the central configuration library; the central configuration library is constructed from the target menu routing configuration file generated by applying the menu version configuration method described in any one of claims 1-5. Based on the initial menu version information, determine the target menu version information; The menu is rendered according to the target menu version information, generating menu data and displaying it.

[0012] Optionally, the user login information includes account information; The user login information is parsed to determine the user's unique identifier, including: Based on the account information, the organization information of the user login information is determined by searching in the preset organization structure dictionary. The key fields in the organization information are extracted according to the preset extraction rules to generate the user feature code.

[0013] Optionally, the user login information includes organizational information and permission information; Based on the user login information, the user signature, and the central configuration library, the initial menu version information is determined, including: Based on the user feature code, search the menu version information corresponding to the user feature code in the central configuration library; Based on the organization information and the permission information, the menu version information is subject to permission verification; In response to the permission verification result being passed, the menu version information is used as the initial menu version information.

[0014] Optionally, the target menu version information is determined based on the initial menu version information, including: Count the number of initial menu version information; In response to the fact that the number of initial menu version information is greater than one, the system receives the initial menu version selected by the user and uses the menu version information corresponding to the initial menu version selected by the user as the target menu version information. Since the number of initial menu version information is one, the initial menu version information is used as the target menu version information.

[0015] Optionally, the menu version information includes the menu version and the routing configuration file corresponding to the menu version. The routing configuration file includes: basic routing information, component association rules, data interface configuration, and display and jump rules. Render the menu according to the target menu version information to generate menu data, including: The menu data is generated by rendering based on the basic routing information, component association rules, data interface configuration, and display and navigation rules.

[0016] Based on the same inventive concept, this disclosure also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein the processor implements the method described above when executing the computer program.

[0017] Based on the same inventive concept, this disclosure also provides a non-transitory computer-readable storage medium that stores computer instructions for causing a computer to perform the method described above.

[0018] As described above, this application provides a menu version configuration method and a menu version data display method. The configuration method includes receiving user login information, version requirement information, and a common routing configuration file; determining a personalized routing configuration file corresponding to the user login information based on the user login information, version requirement information, and common routing configuration file; using the common routing configuration file as a base template, core components are declared only once, and personalized configurations are incrementally modified only on the base template, avoiding duplicate coding of components in multiple independent routing files. In response to receiving the user's modified menu information, the personalized routing configuration file is modified according to the modified menu information to determine the target menu configuration routing file. Menu modification is achieved through visual operations, requiring no developer intervention in coding; when adding organizations or new version requirements, there is no need to redesign the routing tree structure. The display method forms a complete closed loop of "login information reception - feature code generation - version matching - permission verification - rendering display," ultimately achieving the goal of "users seamlessly adapting to a dedicated menu version after login." By using feature codes to ensure that the menu version is accurately bound to the user's organization, by using three-level permission verification to ensure access security, and by using asynchronous loading and resource optimization to improve display efficiency, this approach ultimately solves problems such as poor menu display adaptation, slow loading, and chaotic permissions in multi-organizational scenarios, providing users with a personalized, efficient, and secure menu experience. Attached Figure Description

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

[0020] Figure 1This is a schematic flowchart of a menu version configuration method according to an embodiment of this application; Figure 2 This is a schematic flowchart of a menu version data display method according to an embodiment of this application; Figure 3 This is a schematic diagram of a menu version configuration device according to an embodiment of this application; Figure 4 This is a schematic diagram of a menu version data display device according to an embodiment of this application; Figure 5 This is a schematic diagram of the hardware structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0021] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with specific embodiments and the accompanying drawings.

[0022] It should be noted that, unless otherwise defined, the technical or scientific terms used in the embodiments of this application should have the ordinary meaning understood by one of ordinary skill in the art to which this application pertains. The terms "first," "second," and similar terms used in the embodiments of this application do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Terms such as "comprising" or "including" mean that the element or object preceding the word encompasses the elements or objects listed after the word and their equivalents, without excluding other elements or objects. Terms such as "connected" or "linked" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. Terms such as "upper," "lower," "left," and "right" are only used to indicate relative positional relationships; when the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0023] As described in the background section, existing technologies generally employ a scheme of hard-coding multiple independent routing files to implement branching logic. That is, each set of routing files corresponding to a region or organization fully defines the mapping relationship from the root path to the sub-components. By hard-coding, they match the customized needs of different regions and organizations, without establishing a unified routing configuration and version control system, and also lacking a corresponding efficient menu data display mechanism.

[0024] Regarding menu version configuration, the existing hard-coding solution has significant drawbacks. Core business components need to be repeatedly declared in multiple routing files, resulting in extremely high code redundancy. This not only increases the system's storage and loading burden but also reduces system efficiency. When basic functions need to be iterated and updated, developers need to modify the routing files for each region and organization one by one, adjusting component reference paths and parameter passing logic. This is not only cumbersome but also prone to human error, causing inconsistencies between different versions and drastically increasing system maintenance costs. Furthermore, when adding regional branches or organizational levels, the routing tree structure needs to be redesigned and dedicated jump rules configured. It is impossible to quickly generate standardized routing templates through parameterized configuration, resulting in severely insufficient dynamic expansion capabilities.

[0025] Regarding menu data display, the lack of a unified configuration and version management system makes it difficult for existing systems to achieve accurate matching and efficient display of menu versions. After a user logs in, the system cannot quickly locate the corresponding menu version based on the user's organization, permissions, and other information. It often requires complex branch judgment logic for matching, resulting in slow menu loading speed. At the same time, due to the independence of different version routing files, the consistency of menu data display is difficult to guarantee. Some users may experience problems such as incomplete menu display, missing functional modules, or duplicate display. In addition, when a user has multiple selectable menu versions, the existing system lacks a clear version selection and switching mechanism, which cannot meet the personalized usage needs of users and is not conducive to the unified management of menu versions by the system.

[0026] These problems are intertwined, resulting in front-end software systems built on existing technologies suffering from severe impacts on overall operational efficiency, ease of maintenance, and user experience when facing differentiated customization needs across multiple regions and organizations. They are no longer able to meet the requirements of the digital age for system flexibility, scalability, and efficiency.

[0027] To address the aforementioned technical problems, this application provides a menu version configuration system, comprising: The system comprises a configuration layer, a parsing layer, a validation layer, a loading and display layer, and a central configuration library. Each layer interacts with the other through standardized data interfaces, collaboratively configuring, adapting, validating, loading, and displaying menu versions. The core collaborative process of the system is as follows: (1) Configuration phase: The visual configuration platform of the configuration layer receives the menu version configuration information, organization-version mapping information and permission configuration information input by business personnel. After formatting the information, it is synchronously transmitted to the central configuration library for storage, and the association relationship between menu version, organization attribute, permission rules and routing configuration is established. (2) Adaptation stage: After the user logs in, the organization attribute parsing module of the parsing layer receives the user login information, extracts the organization level, organization type and permission identification information, generates a unique user feature code, and transmits the feature code to the routing mapping module of the loading display layer; the routing mapping module queries the central configuration library based on the feature code, matches the corresponding menu version identifier and routing configuration file path, and transmits the matched routing configuration file to the verification layer. (3) Verification phase: The permission verification module of the verification layer receives the routing configuration file transmitted by the routing mapping module, and performs three-level permission verifications of organization level, role level and function level in combination with the user permission identification information transmitted by the parsing layer. After the verification is passed, a loading instruction is sent to the asynchronous loading module of the loading display layer. If the verification fails, a permission interception signal is generated and fed back to the user interface. (4) Display stage: The asynchronous loading module receives the loading instruction transmitted by the verification layer, loads the corresponding component resources and data as needed based on the component reference path, data interface address and display rules in the routing configuration file, and after compressing and optimizing the resources, renders and generates a menu page that adapts to the user's organizational attributes and permissions and displays it.

[0028] In some embodiments, the configuration layer is a visual configuration platform, including a menu version maintenance module, an organization-version mapping configuration module, a version query module, and a permission allocation module; The menu version maintenance module is used to receive menu version addition, editing and deletion instructions from business personnel, generate basic menu version information including version name, menu list, component association information, data interface configuration and status identifier, and transmit the basic information to the menu version database in the central configuration library. The organization-version mapping configuration module is used to receive multi-type and multi-level organizational structure information and associated instructions, establish mapping relationship data of "organization level-organization type-menu version identifier", and transmit the mapping relationship data to the organization-version mapping database in the central configuration library; The version query module is used to receive query instructions from business personnel, retrieve basic information of menu versions, mapping relationship information and modification logs from the central configuration library, support filtering and version comparison by organization type, version status and configuration time, and feed the query results back to the visualization interface. The permission allocation module is used to receive permission allocation instructions from business personnel based on the RBAC permission model, generate three-level permission rule data of organization level, role level and function level, transmit the permission rule data to the central configuration library, and record the audit log of all configuration operations.

[0029] Specifically, the configuration layer, acting as the "configuration hub" of the entire system, provides a visual interface for business users, enabling them to complete menu version lifecycle management and organizational association configuration without coding. This configuration layer can serve as a visual configuration platform, and its core components and functions include: The menu version maintenance module is configured to: 1. Support adding, editing, and deleting menu versions: When adding a version, you can set the version name (e.g., "Hebei Provincial Company V2.0"), menu list (select display options, sorting rules), associated front-end components (data display components, interactive components, etc.), and bound data interface (customized query interface); 2. Support real-time updates of version parameters, and after modification, there is no need to restart the service; the changes are immediately synchronized to the central configuration library; 3. Provide version status management (enable / disable) to facilitate canary releases and version rollbacks.

[0030] The organization-version mapping configuration module: 1. Adapts to various organizational structures (Party organization tree, Youth League organization tree, administrative organization tree) and multi-level (provincial, municipal, county) configuration requirements; 2. Supports one-to-one and one-to-many associations between "organization level and menu version", for example, binding "Hebei Provincial Company Administrative Organization" with "Hebei Provincial Company V2.0" to generate a unique mapping relationship; 3. The mapping relationship is automatically synchronized to the organization-version mapping database in the central configuration library, providing a basis for subsequent user adaptation.

[0031] The version query module is configured to: 1. Provide a full query function for menu versions, displaying key attributes such as version name, associated organization, configuration time, status, and modification logs; 2. Support filtering queries by organization type, version status, configuration time, etc., making it easy for business personnel to quickly locate the target version; 3. Provide a version comparison function, intuitively displaying the differences in menu structure, component associations, and interface configurations between different versions.

[0032] The permission allocation module is configured as follows: 1. Based on the RBAC permission model, it assigns differentiated configuration permissions to business personnel, divided into "query permissions" (only view version information) and "edit permissions" (add, modify, and delete versions and mapping relationships); 2. It records the user, time, and content of all configuration operations to form an audit log, ensuring that configuration changes are traceable; 3. It supports dynamic adjustment of permissions to adapt to the needs of changes in business personnel roles.

[0033] In some embodiments, the parsing layer is an organization attribute parsing module, including an organization information extraction unit and a feature code generation unit; The organization information extraction unit is used to interface with the user login system, receive the login credentials after the user's identity verification is passed, extract the complete hierarchical chain information containing party organizations, youth league organizations and administrative organizations from the login credentials, verify the integrity and legality of the information, and transmit the formatted organization information to the feature code generation unit. The feature code generation unit is used to extract key fields from the formatted organization information according to preset rules and generate a unique user feature code. The key fields include at least the province abbreviation, city abbreviation, and organization type code. The feature code is associated with the core attribute information of the organization to which the user belongs. The generated user feature code is synchronously transmitted to the routing mapping module of the loading display layer and the permission verification module of the verification layer.

[0034] Specifically, the parsing layer (organization attribute parsing module) acts as a "bridge" between user login and menu adaptation. It is responsible for extracting key features from user login information and generating unique identifiers to match the corresponding menu version. Its core components and functions include: The organization information extraction unit is configured to: 1. Interface with the user login system to extract complete organization information from the login credentials (such as a token) after the user's identity verification is successful, including the hierarchical chain of the party organization, youth league organization, and administrative organization (such as "State Grid Corporation of China - Hebei Provincial Company - Shijiazhuang Municipality - a certain administrative organization"); 2. Verify the completeness and legality of the organization information. If the information is missing, return a prompt to complete it to ensure the accuracy of subsequent feature code generation; 3. Format the extracted organization information and store it in a "organization type - hierarchy - name" structure for easy extraction of key fields.

[0035] The feature code generation unit is configured to: 1. Extract key fields from the formatted organization information according to preset rules (such as "province abbreviation-city abbreviation-organization type code") and generate a unique regional feature code (example: "HEB-SJZ-XZ001", where HEB is the abbreviation for Hebei, SJZ is the abbreviation for Shijiazhuang, and XZ001 is the administrative organization code); 2. The feature code contains core dimension information such as organization type, regional level, and affiliated entity to ensure "one organization, one code" and avoid mapping conflicts; 3. Send the generated feature code to the routing mapping module as the core index for menu version matching.

[0036] In some embodiments, the verification layer is a permission verification module, including an RBAC permission model unit and a route guard unit; The RBAC permission model unit is used to store the organization-level, role-level, and function-level permission rule data synchronously transmitted from the central configuration library, establish the association between permission rules and menu version identifiers, receive user permission identifier information transmitted from the parsing layer, retrieve the corresponding permission rules, and transmit them to the routing guard unit. The routing guard unit is used to receive the routing configuration file transmitted by the display layer and the permission rules transmitted by the RBAC permission model unit, and perform three-level permission verification: the first level verifies whether the user's organization attributes match the organization permissions associated with the routing configuration file; the second level verifies whether the user's role matches the role permissions in the permission rules; and the third level verifies whether the user's operation permissions match the menu function permissions. If the verification passes, a loading instruction is generated and transmitted to the asynchronous loading module; if the verification fails, a permission interception signal is generated, and the interception signal and permission insufficient prompt information are transmitted to the user interface.

[0037] Specifically, the verification layer (permission verification module) acts as a "barrier" for system security and access control, integrating the RBAC permission model and routing guard mechanism to ensure that menu versions are only visible and accessible to authorized users. Its core components and functions include: The RBAC permission model unit is configured to: 1. Store three levels of permission data: "organizational level - role level - function level": organizational level permissions are associated with feature codes, role level permissions define user identities (such as administrators, ordinary users), and function level permissions specify the scope of menu operations (view, edit, delete); 2. Support dynamic maintenance of permission data, allowing the addition / deletion of permission roles and adjustment of permission scopes through a visual configuration platform; 3. Establish the association between permissions and menu versions, for example, configuring the "view basic function menu only" permission for the "ordinary user" role.

[0038] The route guard unit is configured to: 1. Intercept the menu version route configuration file retrieved by the route mapping module and initiate a three-level permission check: first, check if the user's organization attribute matches the organization-level permissions configured in the route; second, check if the user's role meets the role-level permission requirements; and finally, check if the user has the functional-level permissions for that menu version; 2. If the check passes, send a "load command" to the asynchronous loading module to allow the menu resource to load; if the check fails, intercept the request, send an "insufficient permissions" message to the user interface, and redirect to the permission explanation page; 3. Monitor permission changes in real time. If user permissions are adjusted, update the verification rules immediately to ensure that permission control takes effect in real time.

[0039] In some embodiments, the loading presentation layer includes a route mapping module and an asynchronous loading module; The routing mapping module includes a feature code matching unit and a routing configuration retrieval unit. The feature code matching unit receives user feature codes transmitted from the parsing layer, queries the organization-version mapping database of the central configuration library based on the feature codes, matches the corresponding menu version identifier, and transmits the menu version identifier to the routing configuration retrieval unit. The routing configuration retrieval unit queries the routing configuration database of the central configuration library based on the menu version identifier, retrieves the corresponding complete routing configuration file, which at least includes a basic routing path, component reference path, data interface address, and display and redirection rules, and transmits the routing configuration file to the permission verification module of the verification layer. The asynchronous loading module includes a Vue asynchronous component loading unit and a resource optimization unit. The Vue asynchronous component loading unit receives loading instructions transmitted from the validation layer, loads customized component resources on demand using the import() function based on the component reference path in the routing configuration file, retrieves corresponding business data based on the data interface address, and transmits the loaded component resources and business data to the resource optimization unit. The resource optimization unit compresses, obfuscates, and merges component resources, formats business data, renders a menu page adapted to the user terminal according to the display rules in the routing configuration file, and transmits the rendered menu page to the user interface for display.

[0040] Specifically, the presentation layer, acting as the "execution end" for menu data presentation, is responsible for retrieving route configurations, loading custom components on demand, and rendering the page. Its core components and functions include: The routing mapping module includes: a signature matching unit, configured to: 1. Receive signatures generated by the organization attribute parsing module and perform precise matching with the organization-version mapping database in the central configuration library; 2. Support multi-signature matching logic; if a user belongs to multiple organizations (e.g., simultaneously belonging to a party organization and an administrative organization), match all associated menu versions; 3. Return the matching result to the permission verification module, along with key information such as the menu version ID and the routing configuration file address. The routing configuration retrieval unit is configured to: 1. Retrieve the corresponding routing configuration file from the routing configuration database in the central configuration library based on the matched menu version ID; 2. The routing configuration file contains four core components: basic routing information (path mapping relationship), component association rules (binding logic between menus and front-end components), data interface configuration (customized data query address), and display and redirection rules (menu sorting, page redirection method); 3. Pass the complete routing configuration file to the permission verification module, providing a basis for subsequent loading and rendering.

[0041] The asynchronous loading module, including the Vue asynchronous component loading unit, is configured to: 1. Receive the "loading instruction" sent by the permission verification module, and load customized components on demand using Vue's import() function according to the component reference path in the route configuration file; 2. Load only the component resources required for the current menu version, and do not load redundant components from other provinces / organizations to reduce the system loading burden; 3. Support component loading status feedback. If a component fails to load, it will automatically retry. If the retry fails, a friendly prompt will be displayed to ensure user experience.

[0042] The resource optimization unit is configured to: 1. Compress loaded component resources (e.g., code obfuscation, resource merging) to reduce network bandwidth usage and improve page loading speed; 2. Establish a component resource caching mechanism, caching frequently used components locally after loading and reusing them on subsequent visits to shorten loading time; 3. Adapt to the display requirements of different terminals (PC, mobile), adjusting component rendering parameters according to terminal type to ensure menu display compatibility.

[0043] In some embodiments, the central configuration library includes a menu version database, an organization-version mapping database, and a routing configuration database, and the databases communicate with each other through a data synchronization interface; The menu version database is used to store basic menu version information transmitted by the configuration layer, establish a unique association between the version identifier and the basic version information, support real-time updates of version information and retention of historical logs, and provide data support for the version query module and the routing mapping module. The organization-version mapping database is used to store the mapping relationship data of "organization level-organization type-menu version identifier" transmitted by the configuration layer, establish an association index between the key fields of user feature code and menu version identifier, and provide a data source for feature code matching of the routing mapping module; The routing configuration database is used to store the complete routing configuration files corresponding to each menu version, associate menu version identifiers with routing configuration information, support the modification, synchronization and backup of routing configuration files, and provide configuration file retrieval services for the routing mapping module.

[0044] Specifically, the central configuration repository, serving as the system's data "storage hub," consists of three databases. It stores all configuration data related to menu versions, providing data support for collaboration among modules. Its specific components and functions include: The menu version database stores basic information for all menu versions, including version ID, version name, configuration time, status (enabled / disabled), modification logs, a list of associated components, and data interface addresses. Its core function is to provide the data source for version maintenance to the visual configuration platform, supporting operations such as version querying, editing, and rollback.

[0045] The organization-version mapping database stores mapping data for "organizational level - feature code - menu version ID," such as the associated record for "HEB-XZ-Hebei Provincial Company-Hebei Provincial Company V2.0." Its core function is to provide a data source for feature code matching for the routing mapping module, ensuring that users can quickly locate the corresponding menu version after logging in.

[0046] The route configuration database stores complete route configuration files for each menu version, including basic route information, component association rules, data interface configurations, and display and navigation rules. Its core function is to provide configuration file retrieval services for the route mapping module, serving as the core data support for menu rendering.

[0047] In some embodiments, the menu version maintenance module is also used to receive version status switching instructions from business personnel, generate version enable / disable signals, transmit the signals to the menu version database in the central configuration library, synchronously update the status identifier of the corresponding menu version, and automatically synchronize to the menu adaptation logic of all associated organizations after the status change, so that it can take effect without restarting the system.

[0048] In some embodiments, the asynchronous loading module is further configured to receive a user's menu version switching instruction, transmit the switching instruction to the routing mapping module, and the routing mapping module re-matches the corresponding menu version identifier and routing configuration file based on the switching instruction. After the permission verification by the verification layer is passed, the component loading and page rendering process is re-executed to achieve real-time switching of the menu version.

[0049] To solve the above technical problems, such as Figure 1 As shown, this application provides a menu version configuration method, applied to a menu version configuration system, including the following steps: Step 101: Receive user login information, version requirement information, and public routing configuration file.

[0050] In this step, user login information comprises three core dimensions: organizational information, permission information, and account information. The user login information is pre-configured; for example, based on requirements, an account is assigned organizational and permission information, which is then stored for configuration personnel to use. Furthermore, organizational information clarifies the user's complete hierarchical level (e.g., "State Grid Corporation - Hebei Provincial Company - Shijiazhuang City Level - [Administrative Organization]"), covering organizational types such as Party organizations, Youth League organizations, and administrative organizations. Permission information, based on the RBAC permission model, clarifies the user's role (e.g., administrator, ordinary user) and functional operation permissions (e.g., view, edit, delete menus). Account information serves as a correlation index used to verify the user's identity legitimacy in a pre-defined organizational structure dictionary. Version requirement information is a set of customized requirements categorized by region / organization, stored according to organizational level and type, including differentiated configuration requirements such as interface layout, functional module selection, data interface association, and menu display order for each organization. For example, the version requirements for the Hebei Provincial Company might include specific instructions such as "add a provincial data statistics module" or "hide the general report module." The common routing configuration file serves as a unified, system-wide routing template. It contains basic routing information for all common functional modules, component association rules, data interface configurations, and display and redirection rules. Core business components are declared uniformly in this file, eliminating the need for repetitive coding. This file serves as the basis for personalized configurations, avoiding code redundancy caused by multiple independent routing files.

[0051] Step 102: Determine the personalized routing configuration file corresponding to the user login information based on the user login information, the version requirement information, and the public routing configuration file.

[0052] In this step, based on the above embodiments, the configuration personnel automatically initiate a retrieval request to the routing configuration database in the central configuration library through the menu version maintenance module of the visualization platform, based on the configuration operation command (create / create menu version), to obtain the unified public routing configuration file maintained by the system. This public routing configuration file is the baseline template for menu version creation, containing core information such as basic routes, component references, and data interfaces for all common functional modules of the system (such as the nationwide user management module and basic query module), eliminating the need for configuration personnel to repeatedly build the basic framework. The visualization platform displays the retrieved public routing configuration file on the configuration interface (allowing a preview of all common modules), while also associating version requirement information and marking the modules that need to be added, retained, or hidden in the target province, providing visual support for the configuration personnel's personalized adjustments.

[0053] Step 103: In response to receiving the user's modified menu information, modify the personalized routing configuration file according to the modified menu information, and determine the target menu configuration routing file.

[0054] In this step, since users have editing permissions, when a user is in the administrator role, they can modify the menu information. When the system receives the user's modified menu information, that is, when it receives modification instructions such as adding, deleting, and adjusting functional modules, it will perform targeted operations to add, delete, or swap the positions of the route configuration, generate the final target route configuration file, and synchronize it to the central configuration library. For example, in this application, the visual configuration platform (menu version maintenance module) of the configuration layer serves as the core receiving module, receiving modification menu information input by users (business personnel / authorized users). This information includes the modification operation type (adding a functional module, deleting a functional module, adjusting the position of a functional module) and corresponding configuration parameters (component path / data interface of the added module, name of the module to be deleted, target location index, etc.). The menu version maintenance module parses the modification menu information and verifies the legality of the operation: first, it verifies whether the user has modification permissions (synchronously retrieving the permission rule data of the RBAC permission model unit in the verification layer to confirm whether the user role meets the editing permission requirements); second, it verifies whether the modification parameters are valid (such as whether the component path of the added module exists, and whether the module to be deleted belongs to the personalized configuration scope). After the verification is passed, the menu version maintenance module transmits the parsed modification instruction (including operation type, configuration parameters, and user feature code) to the routing mapping module (routing configuration retrieval unit) of the loading display layer. If the verification fails, an insufficient permission / invalid parameter signal is generated and fed back to the user interface to control the termination of the modification process.

[0055] By using steps 101-103, a common routing configuration file is used as a baseline template. Core components are declared only once, and personalized configurations are incrementally modified based on this baseline template. This avoids redundant coding of components in multiple independent routing files, reducing the front-end project size by 30%-50% and lowering system storage and loading burdens. During basic function iterations, only the unified common routing configuration file needs to be updated. All associated personalized routing configuration files automatically inherit the update results, eliminating the need to modify the routing files of each organization individually. Menu modifications are implemented through visual operations, requiring no developer intervention in coding, improving maintenance efficiency by 80% and completely avoiding version inconsistency issues. When adding organizations or new versions, there is no need to redesign the routing tree structure. Steps 101-102 are used to match requirements and generate personalized routing configurations, or step 103 is used to adjust existing configurations. The configuration cycle is shortened to 10-30 minutes, improving adaptation efficiency by over 90%, meeting the rapid expansion needs of multiple regions and organizations. By strongly associating user signatures with organizations and permissions, we ensure that personalized routing configurations are accurately matched with user identities; modification operations only affect the personalized files corresponding to the current user and do not affect other organizations or general configurations. Combined with RBAC permission verification, we avoid the risk of unauthorized modification.

[0056] In some embodiments, for step 102, the user login information includes: organization information and permission information; Based on the user login information, the version requirement information, and the public routing configuration file, the personalized routing configuration file corresponding to the user login information is determined, including the following steps: Step 1021: Generate a feature code based on the organizational information.

[0057] In this step, the core is to generate a unique feature code based on the "target organization information" (such as the organization identifier, level, and type corresponding to a provincial company or municipal branch) received by the visualization configuration platform. This unique feature code is generated through the organization attribute parsing module (feature code generation unit) of the system parsing layer, providing a core index for the accurate binding of the organization to the menu version. The specific process is as follows: The configuration personnel complete the selection of the target organization on the visualization platform (such as "State Grid Hebei Electric Power Co., Ltd. - Administrative Organization - Provincial Level"). The platform automatically extracts the core organization information of the organization, including the organization type code (administrative organization code "XZ", party organization code "DZ", etc.), regional level identifier (provincial "SJ", municipal "SJ", etc.), regional abbreviation (Hebei "HEB", Shandong "SD", etc.) and the organization's unique ID. The feature code generation unit of the organization attribute parsing module combines and encodes the key fields of the extracted organization information according to preset encoding rules (such as "regional abbreviation-organization type code-level identifier-organization unique ID") to generate a unique and traceable feature code (example: "HEB-XZ-SJ-001", corresponding to "Hebei Province administrative organization provincial level No. 001"). After the feature code is generated, it is synchronously fed back to the visualization configuration platform for display, and simultaneously transmitted to the organization-version mapping database in the central configuration library for temporary storage, establishing a reserved index for subsequent "feature code-routing configuration" mapping. This achieves a unique binding between organization information and feature code, ensuring that each target organization (province / city / county level organization) corresponds to a unique feature code, avoiding confusion between menu versions of different organizations, and laying the foundation for accurate matching of subsequent routing configurations. The feature code contains the organization's core attribute information, facilitating subsequent configuration queries and version traceability (such as quickly locating the menu version of the corresponding organization through the feature code), improving configuration management efficiency. The standardized encoding rules ensure that the feature code generation logic is unified when adding new organizations, eliminating the need to redefine rules and supporting configuration consistency after the organization scale expands.

[0058] Step 1022: Based on the organization information, search for the requirement information corresponding to the organization information in the version requirement information to determine the target requirement information.

[0059] In this step, the core is to accurately filter out the "province / level-specific module requirements" corresponding to the organization from the full version requirement information collected from the visualization platform based on the target organization information, and complete the requirement matching and confirmation through the collaboration between the configuration layer and the central configuration library. The specific process is as follows: Version requirement information has been pre-entered by configuration personnel through the visual configuration platform and stored in the organization-version mapping database of the central configuration library in the format of "organization information - module requirement list - configuration rules" (e.g., the requirement information for Hebei Province's administrative organizations is "add provincial data statistics module, retain user management module, hide general report module, module order: data statistics > user management > business application"). After receiving the organization information (e.g., "Hebei Province - administrative organization - provincial") from step 1021, the organization-version mapping configuration module of the visual platform performs precise matching in the version requirement information of the central configuration library using "organization type + region + level" as the search criteria. During the matching process, the completeness of the requirements is automatically verified: it is confirmed whether the organization's requirements include core configuration items such as module list, display order, and data interface association. If there are any missing items (e.g., data interface is not clearly defined), a pop-up window on the visual platform prompts the configuration personnel to supplement them. After the verification is passed, the matched requirement information is determined as the target requirement information and is synchronously displayed on the platform configuration interface for the configuration personnel to preview and confirm. After confirmation, the subsequent route correction stage begins. Achieve precise binding between organizations and specific version requirements, avoiding misconfiguration of module requirements from other organizations to the target organization, and ensuring that menu versions conform to the business scenario requirements of the organization (province / level); automating requirement matching reduces the operational cost of manual requirement screening by configuration personnel, while avoiding invalid configurations through integrity checks, thus improving configuration accuracy; visually displaying target requirement information facilitates verification and modification by configuration personnel, reducing the risk of configuration errors caused by misunderstandings of requirements.

[0060] Step 1023: Based on the target requirement information and the permission information, modify the public routing configuration file, and establish a mapping relationship between the feature code and the modified public routing file to obtain the personalized routing configuration file corresponding to the feature code.

[0061] This step is the core of generating personalized routing configuration files. Through collaboration between the visualization platform and the loading / display layer, and based on target requirements (province module requirements) and organizational permissions, the unified promotion public routing template is modified in a targeted manner, ultimately completing the binding and storage of the "feature code - personalized route". The specific process is as follows: The menu version maintenance module of the visualization platform first retrieves the unified promotion public routing configuration file from the central configuration library (containing core information such as basic routes, component references, and data interfaces for all common modules in the system, such as routing rules for common modules like user management, basic query, and business application); Combined with the target requirement information, targeted modification operations are performed: Adding a module: Based on the requirement of "adding a provincial data statistics module", the routing configuration template for this module (including route path, component reference address, and data interface binding rules) is retrieved from the system component library and added to the public routing configuration file; Deleting / hiding a module: Based on the requirement of "hiding the general report module", the routing mapping of this module is hidden in the public routing configuration file to ensure that it cannot be accessed after the organization logs in; Adjusting the order: Based on the module display order in the requirement, the routing configuration file is modified. The module sorting parameters in the configuration file ensure that the front-end display conforms to business priorities; permission adaptation: combined with the permission information in the user login information (e.g., the organization only has "view data" permission, not "edit data" permission), permission verification rules are added to the routing configuration to restrict operations that exceed permissions; after the correction is completed, a corrected public routing file containing the organization's exclusive module combination is generated, and the visualization platform automatically establishes a one-to-one mapping relationship between the feature code generated in step 1021 and the corrected routing file (e.g., "HEB-XZ-SJ-001" corresponds to "Hebei Provincial Administrative Organization Personalized Routing File"); the mapping relationship between "feature code-personalized routing configuration file" and the configuration file itself are synchronously stored in the routing configuration database and the organization-version mapping database of the central configuration library to complete the final generation of the personalized routing configuration file. The configuration logic of "common template + personalized modification" is implemented. Core general modules are declared uniformly only in the public route, avoiding duplicate coding and significantly reducing code redundancy. Modification operations accurately match target requirements and permissions, ensuring that personalized route configuration files not only meet the differentiated module requirements of organizations (provinces) but also comply with permission control requirements, avoiding the risk of unauthorized access. A strong association between feature codes and route files is established, providing a core basis for quick matching of menu versions when users log in (the corresponding personalized route can be retrieved through the feature code). Configuration files are stored in a central configuration library, which facilitates subsequent unified maintenance and version iteration, eliminating the need to manage multiple organizational route files separately and reducing maintenance costs.

[0062] Steps 1021-1023 form a closed loop of "organization identifier generation - precise requirement matching - route-oriented correction," with the core revolving around "organizational (province) differentiated needs" to achieve automated and standardized generation of personalized route configurations. It ensures a unique binding between organizations and routes through feature codes, ensures configurations fit business scenarios through requirement matching, and enables flexible module combinations and permission adaptation through route correction. Ultimately, it solves the problems of code redundancy, maintenance complexity, and expansion difficulties caused by hard-coding multiple independent route files in the past, providing core support for unified management and efficient adaptation of menu versions for multiple organizations and provinces.

[0063] In some embodiments, for step 103, the modified menu information includes: information on newly added functional modules; In response to receiving modified menu information from the user, the personalized routing configuration file is modified according to the modified menu information to determine the target menu routing configuration file, including the following steps: Step 103-11: In response to receiving the user's modified menu information as new function module information, generate new route configuration information based on the new function module information.

[0064] In this step, the core is to automatically generate standardized routing configuration items based on the menu version requirements of the target organization (such as a provincial / municipal organization) in the visual configuration platform, providing a compliant and reusable configuration basis for adding modules. The specific process is as follows: On the version modification interface of the visualization platform, the configuration personnel select the personalized routing configuration file for the target organization (e.g., "Hebei Provincial Administrative Organization V1.0"), and submit the information for the newly added functional module. This includes: the name of the new module (e.g., "Hebei Local Electricity Fee Settlement Module"), the module's category (business processing), the data interface address (e.g., / api / hebei / electricity-settlement), the component reference path (@ / components / hebei / settlement.vue), and the access permission scope (accessible only to provincial administrators). After receiving the new information, the menu version maintenance module of the visualization platform first verifies the module's legality: ① Verifies whether the new module name is duplicated (to avoid name conflicts with existing modules); ② Verifies whether the data interface address is valid (interface connectivity test); ③ Verifies whether the component reference path exists in the system component library. After successful verification, the platform loads the presentation layer's routing mapping module (routing configuration retrieval unit), automatically generating the exclusive routing configuration information for the newly added module according to the system's preset routing configuration template (including routing path, component binding, permission rules, display parameters, etc.). The generated new route configuration information is displayed in real time on the visualization platform interface. Configuration personnel can preview and fine-tune parameters (such as modifying the front-end display name or adjusting the permission scope). After confirming that everything is correct, they can submit a generation confirmation command. Standardized generation of route configurations for new modules avoids formatting errors and missing parameters caused by manually writing routes, ensuring configuration compliance. Pre-validation of module legitimacy prevents the addition of invalid modules (such as unavailable interfaces or missing components) from the source, improving configuration accuracy. Route configurations are automatically associated with province / organization identifiers to avoid route path conflicts between new modules from different organizations, ensuring a clear system routing architecture.

[0065] Step 103-12: Add the newly added route configuration information to the personalized route configuration file corresponding to the user login information to obtain the target menu route configuration file.

[0066] The core of this step is to accurately add the standardized newly generated routing configuration items to the personalized routing configuration file of the target organization, complete the module addition, and synchronize and store them to ensure that the changes take effect. The specific process is as follows: After receiving the newly added routing configuration information from steps 103-11, the menu version maintenance module of the visualization platform first locates the personalized routing configuration file corresponding to the target organization (retrieved from the central configuration library using the feature code "HEB-XZ-SJ-001" generated in step 1021). The platform inserts the newly added routing configuration information into the corresponding node of the personalized routing configuration file according to the module addition position specified by the configuration personnel (e.g., "under the business processing module, after the electricity bill query module"), and automatically updates the module sorting parameters in the file. After the addition is completed, the visualization platform displays the modified complete personalized routing configuration file (marking the position and configuration information of the newly added module), and the configuration personnel can preview the front-end menu display effect (e.g., whether the newly added module appears in the specified position). After verification, the platform designates the added route configuration file as the target menu route configuration file and synchronously transmits it to the route configuration database in the central configuration library, overwriting the original personalized route configuration file. Simultaneously, it updates the version log in the menu version database (recording "Added Hebei Province Local Electricity Fee Settlement Module," operation time, and user). The platform sends a "Module added successfully" notification to the configuration personnel and simultaneously informs the associated organization (Hebei Province provincial administrative organization) that the newly added module can be seen after logging in. This process ensures accurate addition of the new module route, guaranteeing the module is displayed in the designated location and aligns with the organization's business operation habits. The configuration file is synchronized to the central configuration library in real time, taking effect without a system restart, improving version iteration efficiency. Complete modification logs facilitate subsequent version traceability and rollback, ensuring auditable configuration.

[0067] In some embodiments, for step 103, modifying the menu information includes: deleting functional module information; In response to receiving user-modified menu information, the personalized routing configuration file is modified according to the modified menu information, and the target menu routing configuration file is determined, including: Step 103-21: In response to receiving the user's modified menu information as "delete function module information", determine the name of the function module to be deleted based on the "delete function module information".

[0068] The core of this step is to accurately locate the name of the module to be deleted in the target organization's personalized routing configuration file in the visual configuration platform, so as to avoid accidentally deleting valid modules. The specific process is as follows: On the version modification interface of the visualization platform, the configuration personnel select the personalized routing configuration file of the target organization (e.g., "Shandong Provincial and Municipal Administrative Organizations V1.0"), submit the information for deleting a functional module, and can specify the deletion target in two ways: ① Directly enter the module name (e.g., "General Report Module"); ② Select the module to be deleted from the module list displayed on the platform. After receiving the deletion information, the version maintenance module of the visualization platform first retrieves the personalized routing configuration file of the organization, parses out the list of all configured functional module names, and matches it with the name of the module to be deleted submitted by the configuration personnel. If the match is successful (e.g., "General Report Module" is found), the platform highlights the core information of the module (routing path, permission scope, associated interfaces) and provides a second confirmation: "Confirm deletion of [General Report Module]? After deletion, all accounts in this organization will be unable to access this module." If the match fails (e.g., the entered module name does not exist), the platform immediately prompts "Module not found, please check the name," and displays a list of all currently configured modules for the configuration personnel to check and select. After the configuration personnel confirm, the platform officially determines the name of the functional module to be deleted (e.g., "General Report Module") and proceeds to the subsequent deletion stage. The system double-checks the accuracy of the module names to be deleted, significantly reducing the risk of accidentally deleting valid modules; it visually displays the core information of the modules to be deleted, making it easier for configuration personnel to confirm the impact of deletion and avoiding errors caused by incomplete information; and it provides a module list selection method to simplify the deletion process and improve configuration efficiency.

[0069] Step 103-22: Delete the routing configuration information corresponding to the name in the personalized routing configuration file corresponding to the user login information to obtain the target menu routing configuration file.

[0070] The core of this step is to accurately delete the routing configuration items corresponding to the target module, while preserving the integrity of the configurations of other modules, and generating an updated target routing configuration file. The specific process is as follows: The menu version maintenance module of the visualization platform, based on the name of the module to be deleted (e.g., "General Report Module") determined in step 103-21, locates the corresponding routing configuration node in the personalized routing configuration file of the target organization (matching the "meta.title" or "name" field). The platform only deletes the routing configuration information corresponding to this module, keeping the routing configurations of other modules (e.g., user management, local business application) unchanged, while automatically adjusting the module sorting parameters in the file (e.g., subsequent modules after the deletion are automatically moved forward to maintain a consistent display order). After deletion, the platform displays the modified personalized routing configuration file (marking the deleted modules and the remaining module list), and the configuration personnel can preview the front-end menu effect (confirming that the deleted modules have disappeared). After confirmation, the platform determines the deleted routing configuration file as the target menu routing configuration file, synchronously updates the routing configuration database in the central configuration library, overwriting the original file; at the same time, it records a deletion log in the menu version database (e.g., "Deleted the General Report Module in Shandong Provincial Municipal Administrative Organization V1.0"). The platform sends a "Module deleted successfully" notification to the configuration personnel and simultaneously informs them that the module will no longer be displayed after logging into the organization's account. Precise deletion of the target module's routing configuration does not affect the normal operation of other modules, ensuring the integrity of the organization's menu version; it automatically adjusts the module sorting to avoid menu display gaps after module deletion, improving the user experience. Configuration files are updated in real time, and deletion operations take effect immediately, requiring no developer intervention and reducing maintenance costs.

[0071] In some embodiments, for step 103, modifying the menu information includes: modifying the location information of the functional modules; In response to receiving user-modified menu information, the personalized routing configuration file is modified according to the modified menu information, and the target menu routing configuration file is determined, including: Step 103-31: In response to receiving the user's modified menu information as modified function module location information, determine the target location of the function module in the personalized routing configuration file based on the modified function module location information.

[0072] In this step, the core is to accurately determine the target position of the module in the routing configuration file based on the location adjustment needs of the configuration personnel in the visual configuration platform, ensuring that the adjustment conforms to the business display logic. The specific process is as follows: The configuration personnel select the personalized routing configuration file of the target organization (such as "Henan Province County-level Administrative Organization V1.0") in the version modification interface of the visual platform, and submit the location information of the modified functional module. The operation method is as follows: ① Drag the module to be adjusted (such as "Local Payment Module") to the target position (such as "after the homepage module and before the query module") in the module list; ② Enter the module name and target position index (such as "Local Payment Module, target position index 2"); After receiving the location modification information, the menu version maintenance module of the visual platform first parses the module sorting logic in the personalized routing configuration file (the modules in the file are sorted by "sor... The platform sorts the location using the "t" field (e.g., sort=1 for the first position, sort=2 for the second position). It converts the user's visual drag-and-drop operations / location index input into the "sort" field value in the routing configuration file (e.g., dragging "Local Payment Module" to the second position corresponds to sort=2), clearly defining the module's target location and corresponding sorting parameters. The platform displays a preview of the adjusted location (e.g., "Adjusted menu order: Homepage Module (sort=1) → Local Payment Module (sort=2) → Query Module (sort=3)"). After confirmation by the user, the target location and corresponding sorting parameters for the functional module are officially determined. The visual drag-and-drop operation simplifies the location adjustment process, eliminating the need for users to understand the routing configuration file's sorting logic, thus lowering the operational threshold. Automatic conversion to routing configuration sorting parameters ensures that the location adjustment conforms to the system's front-end rendering rules, avoiding display anomalies. The preview visually displays the adjustment results, facilitating verification by users and improving the accuracy of location adjustments.

[0073] Steps 103-32: Swap the positions of the current functional module and the functional module to be modified in the target location to obtain the target menu routing configuration file.

[0074] In this step, the core is to adjust the module positions and generate an updated target route configuration file by swapping the module sorting parameters in the route configuration file. The specific process is as follows: Based on the target position determined in steps 103-31 (e.g., sort=2), the menu version maintenance module of the visualization platform first locates the module currently corresponding to that position (e.g., "Query Module", sort=2) and the module to be modified (e.g., "Local Payment Module", originally sort=3). The platform automatically swaps the "sort" field values ​​of the two modules: the sort value of "Local Payment Module" is changed to 2, and the sort value of "Query Module" is changed to 3, while keeping other route configuration information (component references, interface addresses, permission rules) of the two modules unchanged; if the target position is the first / last position (no corresponding swapped module), the sort value of the module to be adjusted is directly modified to the target index, and the sort values ​​of the other modules are automatically incremented (e.g., "Local Payment Module" is moved to the first position, sort=1, the original sort=1 "Homepage Module" is changed to sort=2, and the other modules are incremented by 1 in turn). After the position adjustment is completed, the platform displays the modified personalized routing configuration file (marking the adjusted module sorting parameters and front-end preview). Once the configuration personnel confirm that everything is correct, the adjusted file is designated as the target menu routing configuration file. The platform synchronously updates the target configuration file to the routing configuration database in the central configuration library, overwriting the original file, and records the position adjustment log in the menu version database (e.g., "Move the local payment module in Henan Province County-level Administrative Organization V1.0 to the second position"). The platform sends a "Module position adjustment successful" notification to the configuration personnel, who can then see the adjusted menu display order after logging into the organization's account. This process accurately swaps module positions, ensuring the menu display order aligns with the organization's business priorities (e.g., placing core business modules first), improving user efficiency; automatically handles the continuation / swap of sorting parameters, avoiding sorting chaos caused by manual parameter modifications, and ensuring configuration accuracy; the adjustment results take effect immediately without requiring a system restart, adapting to the rapid iteration needs following organizational business process adjustments.

[0075] Based on the same inventive concept, such as Figure 2 As shown, this application also provides a method for displaying menu version data, including the following steps: Step 201: Receive user login information.

[0076] In this step, the user initiates a login request by entering their account and password (or through single sign-on or token authentication) on the system login interface. The login system first verifies the user's identity (whether the account and password are correct, and whether the account is active). After successful identity verification, the login system automatically extracts the user's complete login information, including three core dimensions: ① Organizational information (organization type, such as administrative organization / party organization / youth league organization; organizational hierarchy chain, such as "State Grid Corporation - Shandong Provincial Company - Jinan Branch - a certain county-level organization"; unique organizational identifier); ② Permission information (user's role, such as administrator / ordinary business user; functional operation permissions, such as view / edit / approval permissions); ③ Basic account information (account ID, user name, login terminal type, such as PC / mobile). The login system transmits the extracted complete login information to the organization attribute parsing module of the parsing layer through a standardized interface, while retaining a backup for subsequent permission verification and comparison. If identity verification fails (such as incorrect password or disabled account), a login failure message is returned, terminating the subsequent process.

[0077] Step 202: Parse the user login information to determine the user's feature code.

[0078] In this step, the organization attribute parsing module of the parsing layer extracts key organization fields from the login information to generate a unique user feature code, which serves as the core index for the associated menu version. The specific process is as follows: After receiving the user login information transmitted by the login system, the organization attribute parsing module first extracts key fields from the organization information, including the province abbreviation (e.g., Shandong "SD"), city abbreviation (e.g., Jinan "JN"), organization type code (administrative organization "XZ" / party organization "DZ"), organization level identifier (county level "XJ"), and unique organization ID (e.g., "003"). Following a preset coding rule (e.g., "province abbreviation-city abbreviation-organization type code-level identifier-organization ID"), the key fields are combined and coded to generate a unique and traceable user feature code (example: "SD-JN-XZ-XJ-003", corresponding to "user of Shandong Province, Jinan City, administrative organization, county level, organization number 003"). After the feature code is generated, the organization attribute parsing module simultaneously performs verification: confirming whether the feature code format conforms to the specifications and whether the key fields are complete, to avoid subsequent menu matching failures due to coding errors. After successful verification, the user's signature code is bound to the original login information (organization information, permission information) and transmitted together to the routing mapping module that loads the presentation layer. At the same time, it is temporarily stored in the system cache for quick retrieval in subsequent steps.

[0079] Step 203: Determine the initial menu version information based on the user login information, the user feature code, and the central configuration library; the central configuration library is constructed by applying the menu version configuration method described in any one of claims 1-5 to generate the target menu routing configuration file.

[0080] In this step, the routing mapping module collaborates with the verification layer to query the central configuration library based on the user's feature code, match and verify the corresponding menu version, and determine the initial menu version information. The specific process is as follows: After receiving the user's feature code, the routing mapping module (feature code matching unit) of the display layer initiates a query request to the central configuration library. The central configuration library is constructed from the target menu routing configuration file generated by the menu version configuration method (claims 1-5), and includes a menu version database, an organization-version mapping database, and a routing configuration database. The feature code matching unit uses the user's feature code as the search condition to search for the associated menu version identifier (e.g., "Shandong Province Jinan City County-level Administrative Organization V2.0") in the organization-version mapping database. If the user's organization is associated with multiple menu versions (e.g., basic version, advanced version), all matching version identifiers are matched. The routing configuration retrieval unit retrieves the corresponding complete routing configuration file (including basic routing information, component association rules, data interface configuration, display and redirection rules) from the routing configuration database based on the matched menu version identifier. The permission verification module (RBAC permission model unit) of the verification layer receives the permission information from the retrieved routing configuration file and user login information, and performs three levels of permission verification: ① Organization-level verification (whether the user's organization is consistent with the organization associated with the menu version); ② Role-level verification (whether the user's role meets the access role requirements of the menu version); ③ Function-level verification (whether the user's operation permissions cover the functional modules included in the menu version). If the verification passes, the matched menu version identifier and the corresponding routing configuration file are determined as the initial menu version information; if the verification fails (e.g., the user role does not have permission to access this version), the version is filtered, and only the versions that pass the verification are retained as the initial menu version information; if all matched versions fail the verification, a "No available menu version" message is returned.

[0081] Step 204: Determine the target menu version information based on the initial menu version information.

[0082] In this step, the core is to determine the final target menu version information based on the number of initial menu version information, either through user selection or automatic system adaptation. The specific process is as follows: The routing mapping module of the display layer first counts the number of initial menu version information, handling two scenarios: Scenario 1: The number of initial menu version information is greater than one (e.g., the user can access two versions, "Basic Business Edition" and "Advanced Analysis Edition"). The system automatically pops up a version selection window in the user interface, displaying the core information of each version (version name, list of included functional modules, and description of applicable scenarios) for the user to choose from. After the user selects, the system determines the routing configuration file corresponding to that version as the target menu version information. If the user does not select within the timeout period, the associated basic version is loaded by default. Scenario 2: The number of initial menu version information is one (e.g., the user can only access "Dedicated Business Edition"). The system does not require user operation and directly determines this unique initial menu version information as the target menu version information, simplifying the user operation process. After the target menu version information is determined, the routing mapping module transmits it to the asynchronous loading module, while retaining the association record between the version identifier and the user's feature code for subsequent log traceability.

[0083] Step 205: Render according to the target menu version information, generate menu data and display it.

[0084] In this step, the core function is to use the asynchronous loading module to parse, load, and render the routing configuration file for the target menu version, ultimately displaying the adapted menu data to the user. The specific process is as follows: After receiving the target menu version information, the asynchronous loading module parses its corresponding routing configuration file, extracting four core configurations: ① Basic routing information (routing paths for each functional module); ② Component association rules (binding relationships between the menu and front-end components); ③ Data interface configuration (business data query interfaces for each module); ④ Display and navigation rules (menu sorting, page navigation methods, and style configurations). Based on the component association rules, Vue's asynchronous component loading technology (import() function) is used to load the necessary front-end components for the target menu version from the system component library on demand, avoiding the loading of redundant components (such as customized components for other provinces / organizations) and reducing loading time. Based on the data interface configuration, a data request is sent to the backend server to obtain real-time business data from each functional module (such as local business data and statistical report data for the user's organization), and the data is formatted (adapted to the front-end display format). According to the display and navigation rules, the above components and data are rendered into a visual menu page: ① Display functional modules according to the configured sorting rules (e.g., core business modules are placed first); ② Bind menu navigation events (clicking a module triggers the corresponding route path navigation); ③ Mark the user permission scope (e.g., display a "View Only" label for modules without editing permissions). After rendering, the menu data is displayed on the user interface, and the loading result is fed back to the user (e.g., "Menu loaded successfully"); if an exception occurs during the loading process (e.g., component loading failure, data interface unavailable), a user-friendly prompt is displayed (e.g., "Some modules failed to load, please refresh and try again"), and an exception log is recorded for troubleshooting.

[0085] Steps 201-205 form a complete closed loop of "login information reception - signature generation - version matching - permission verification - rendering and display," with the core goal of "seamlessly adapting to a personalized menu version after user login." The signature ensures precise binding between the menu version and the user's organization, three-level permission verification guarantees access security, and asynchronous loading and resource optimization improve display efficiency. Ultimately, this solves problems such as poor menu display adaptation, slow loading, and chaotic permissions in multi-organizational scenarios, providing users with a personalized, efficient, and secure menu experience.

[0086] In some embodiments, for step 202, the user login information includes account information; The process of parsing the user login information to determine the user's unique identifier includes the following steps: Step 2021: Based on the account information, search in the preset organizational structure dictionary to determine the organizational information of the user login information.

[0087] In this step, the organization attribute parsing module of the parsing layer receives account information from the user login information (such as account ID "SD-JN-XZ-001" or login name "hebei_xz_li"). The account information has embedded organization association identifiers according to system rules (such as prefixes and suffixes containing province / organization type abbreviations). The module calls the preset organization structure dictionary, which is a pre-configured structured database that stores all organization information, including the mapping relationship of "account association identifier - organization type - organization hierarchy chain - organization unique ID" (such as the account prefix "SD-JN-XZ" corresponding to "Shandong Province - Jinan City - administrative organization"). Using the account information as the search keyword, a precise match is performed in the dictionary: if the account ID contains an explicit organization identifier, the corresponding organization record is directly matched; if the account does not have an explicit identifier, indirect matching is performed through related fields such as the account's department and registration information. After a successful match, the complete organization information corresponding to the account is extracted, including core fields such as organization type (administrative / party / youth league organization), organization hierarchy chain (group-province-city-county), organization unique code, and regional abbreviation. The extracted organizational information undergoes integrity verification (e.g., checking for missing levels and coded fields). If verification passes, the information is considered valid; otherwise, a "organizational information not matched" message is returned, terminating the feature code generation process. This ensures precise binding between accounts and organizational information, preventing errors caused by users manually entering information and guaranteeing the authority and accuracy of the information. A pre-defined dictionary standardizes organizational data storage, automating and maximizing the matching process, significantly reducing the time required for organizational information extraction. Complete extraction of multi-dimensional organizational fields provides a comprehensive and standardized data source for subsequent feature code generation, ensuring the uniqueness and relevance of the feature codes.

[0088] Step 2022: Extract key fields from the organization information according to preset extraction rules to generate the user feature code.

[0089] In this step, the feature code generation unit of the organization attribute parsing module calls the system's preset extraction rules. These rules specify the extraction range of key fields (province abbreviation, city abbreviation, organization type code, hierarchical identifier, organization unique ID) and the encoding format (e.g., "province abbreviation-city abbreviation-organization type code-hierarchical identifier-organization ID"). Key fields are extracted from the organization information determined in step 2021: for example, if the organization information is "Shandong Province-Jinan City-Administrative Organization-County Level-003", then the province abbreviation "SD", city abbreviation "JN", organization type code "XZ", hierarchical identifier "XJ", and organization ID "003" are extracted. The key fields are combined and encoded according to the preset format to generate a user feature code (e.g., "SD-JN-XZ-XJ-003"). During the encoding process, special characters are automatically filtered, and missing abbreviations are filled in (e.g., "00" is filled in if there is no city-level information). The generated signature code undergoes uniqueness verification by querying the system's signature code database. If no duplicates are found, it is marked as valid. If duplicates exist, the organization ID suffix is ​​automatically adjusted (e.g., "003" is changed to "004"), and the code is regenerated and verified. Once a valid signature code is generated, it is bound and stored with organization and account information, and synchronously transmitted to the routing mapping module to provide an index for subsequent menu version matching. Standardized extraction rules ensure a consistent signature code format, avoiding format chaos caused by manual coding and supporting unified management across multiple organization scenarios. The signature code contains core organizational dimension information, achieving "one code per organization," ensuring accurate menu version matching and preventing confusion between menus from different organizations. The uniqueness verification mechanism eliminates signature code conflicts from the source, ensuring smooth execution of subsequent configuration library queries and permission verification processes.

[0090] In some embodiments, for step 203, the user login information includes organization information and permission information; Based on the user login information, the user signature, and the central configuration library, the initial menu version information is determined, including: Step 2031: Based on the user feature code, search for the menu version information corresponding to the user feature code in the central configuration library.

[0091] In this step, the route mapping module (signature code matching unit) of the presentation layer receives the user's signature code and initiates a query request to the central configuration database. The central configuration database is constructed from the target route configuration file generated by the menu version configuration method and includes an organization-version mapping database, a menu version database, and a route configuration database. The signature code matching unit breaks down the user's signature code into key fields (province, organization type, level, etc.) and performs multi-dimensional matching in the organization-version mapping database to find all menu version identifiers associated with the signature code (e.g., "Shandong Province Jinan City County-level Administrative Organization Basic Version V1.0" and "Shandong Province Jinan City County-level Administrative Organization Advanced Version V2.0"). If the signature code does not have a directly associated menu version, it matches the general version of the superior organization (e.g., if there is no specific version for the county level, it matches the general version for the city level) to ensure that the user has a usable menu version. Based on the matched menu version identifier, it retrieves the basic information of each version (version name, applicable scenarios, configuration time) from the menu version database and the corresponding complete route configuration file (including basic routes, component rules, interface configurations, etc.) from the route configuration database. Menu version identifiers, basic information, and routing configuration files are integrated into a candidate menu version information set and transmitted to the permission verification module. A multi-dimensional matching mechanism improves the accuracy of menu version lookup, ensuring that the matching results align with the customized needs of the user's organization. A fallback strategy with higher-level versions avoids situations where "no usable menus" occur, guaranteeing system availability. Integrating basic version information and routing configuration files provides complete data support for subsequent permission verification and rendering / display.

[0092] Step 2032: Perform permission verification on the menu version information based on the organization information and the permission information.

[0093] In this step, the permission verification module (RBAC permission model unit) of the verification layer receives the candidate menu version information set and the organization and permission information from the user login information. It performs organization-level verification: comparing the organizational scope associated with the candidate version with the user's organization information, filtering out versions unrelated to the user's organization (e.g., filtering out Shandong users from the "Henan Province organization version"). It performs role-level verification: based on the RBAC permission model, comparing the user's role (e.g., administrator, ordinary user) with the access role requirements of the candidate version (e.g., advanced version only allows administrator access), filtering out versions with mismatched roles. It performs function-level verification: checking whether the user's specific operation permissions (e.g., view, edit, approve) cover the function module permission requirements of the candidate version (e.g., a certain version's "data approval" module only allows users with approval permissions), filtering out versions with insufficient function permissions. It records the verification process log (e.g., filtering reasons, verification passed items of retained versions), and transmits the verified candidate version information set to the next step. Through the three-tiered verification mechanism described above, the system ensures that users can only access menu versions that match their organizational affiliation, role level, and functional permissions, preventing unauthorized access and sensitive data leakage. The verification process is traceable, facilitating subsequent troubleshooting and permission adjustments. Precisely selecting valid versions reduces unnecessary load on subsequent version selection and rendering, improving system efficiency.

[0094] Step 2033: In response to the permission verification result being passed, the menu version information is used as the initial menu version information.

[0095] In this step, the permission verification module receives the verified version information set it outputs. It first determines if a valid version exists: if one or more verified versions exist, the version information set (including version identifier, basic information, and routing configuration file) is determined as the initial menu version information. If no verified version exists, an "No usable menu version" error signal is generated and fed back to the user interface, while simultaneously prompting the administrator to configure the corresponding permissions or menu version. The initial menu version information is formatted, sorted by version update time (latest version first), and the core differences between each version are marked (e.g., the advanced version has an additional "Data Statistics" module compared to the basic version). The formatted initial menu version information is transmitted to the routing mapping module loading the presentation layer and stored in the system cache for quick retrieval in subsequent steps. The scope and priority of the initial menu version information are clearly defined, providing a clear basis for user selection or automatic system adaptation. Timely feedback of anomalies facilitates quick location of missing permissions or configuration problems, ensuring a good user experience. Formatting and caching improve the execution efficiency of subsequent processes and shorten menu display time.

[0096] In some embodiments, for step 204, determining the target menu version information based on the initial menu version information includes the following steps: Step 2041: Count the number of initial menu version information.

[0097] In this step, after receiving the initial menu version information, the routing mapping module of the presentation layer calls the counting unit to count the number of versions. The counting range is the menu versions that have passed verification and are in the "enabled" state. If the version information contains a "default version" identifier (such as the system's default basic version), this default version is marked while counting the number of versions. After the count is completed, the count results are generated (such as "quantity=2" or "quantity=1"), and the core information of each version (version name, applicable scenario) is associated with it and transmitted to the version selection processing unit. Accurately counting the number of valid versions provides clear triggering conditions for subsequent "user selection" or "automatic adaptation" logic. Marking the default version is a fallback option in multi-version scenarios to avoid process stagnation caused by user timeout. Associating the core version information makes it easier to display to the user for selection later, improving decision-making efficiency.

[0098] Step 2042: In response to the fact that the number of initial menu version information is greater than one, receive the initial menu version selected by the user, and use the menu version information corresponding to the initial menu version selected by the user as the target menu version information.

[0099] In this step, the routing mapping module detects that the number of initial menu versions is greater than one (e.g., two or more) and immediately sends a version selection command to the user interface. The user interface then pops up a version selection window, displaying key information for each initial menu version: version name, list of included functional modules, applicable scenarios, and update time, while also indicating the default version (e.g., "Recommended: Basic Version V1.0"). Users can select the target version by clicking or searching, and the selection window has a timeout mechanism (e.g., if no selection is made within 30 seconds, the default version will automatically be used). After receiving the user's selection command, the routing mapping module extracts the complete information corresponding to the selected version (version identifier, routing configuration file, etc.) from the initial menu version information. This extracted complete information is then used as the target menu version information and transmitted to the asynchronous loading module, while simultaneously recording the user selection log (selected version, selection time). This grants users version selection rights to meet the personalized business needs of different users (e.g., ordinary users select the basic version, administrators select the advanced version).

[0100] Step 2043: In response to the fact that the number of initial menu version information is one, the initial menu version information is used as the target menu version information.

[0101] In this step, the route mapping module detects that there is only one initial menu version. Without any user intervention, it directly determines this initial menu version information (including version identifier, route configuration file, and basic information) as the target menu version. A version confirmation signal is generated and briefly displayed on the user interface (e.g., "Currently compatible version: Shandong Province, Jinan City, County-level Administrative Organization V1.0") to inform the user of the currently used menu version. The target menu version information is quickly transmitted to the asynchronous loading module to start the subsequent rendering process, shortening the menu loading wait time. No additional user intervention is required, achieving "seamless adaptation" of the menu version and improving user convenience.

[0102] In some embodiments, for step 205, the menu version information includes the menu version and the routing configuration file corresponding to the menu version. The routing configuration file includes: basic routing information, component association rules, data interface configuration, and display and jump rules. Render the menu according to the target menu version information to generate menu data, including: Step 2051: Render the menu data according to the basic routing information, component association rules, data interface configuration, and display and navigation rules.

[0103] After receiving the target menu version information, the asynchronous loading module first parses the four core rules in the routing configuration file: basic routing information, component association rules, data interface configuration, and display and navigation rules. Based on the component association rules, it uses Vue's asynchronous component loading technology (import() function) to load the front-end components required by the target version on demand, avoiding the loading of redundant components (such as customized components for other provinces), while compressing and optimizing component resources (code obfuscation, resource merging). Based on the data interface configuration, it initiates batch data requests to the backend server to obtain real-time business data from each module (such as local business statistics and to-do items), formats the returned data (adapting it to the component display format), and caches frequently used data locally. Based on the basic routing information and display rules, it constructs a menu hierarchy structure: modules are arranged in sorting order, route paths and navigation events are bound, menu icons and display names are set, and the layout is adjusted according to the terminal type (a complete hierarchical menu is displayed on PCs, and collapsed into a dropdown menu on mobile devices). Finally, it integrates the loaded components, formatted data, and menu structure to render and generate complete menu data, including a visual interface layout, module interaction logic, and data display content. On-demand loading and resource optimization reduce network transmission pressure, improve menu loading speed, and shorten user waiting time. Strict adherence to routing configuration rules ensures accurate menu module associations, real-time data, and adaptive display. Generated menu data is tailored to the customized needs and usage scenarios of the user's organization, guaranteeing ease of operation and data accuracy.

[0104] It should be noted that the method in this embodiment can be executed by a single device, such as a computer or server. The method can also be applied in a distributed scenario, where multiple devices cooperate to complete the task. In such a distributed scenario, one of these devices may execute only one or more steps of the method in this embodiment, and the multiple devices will interact with each other to complete the method described.

[0105] It should be noted that the above description describes some embodiments of this application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in a different order than that shown in the above embodiments and still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0106] Based on the same inventive concept, corresponding to any of the above embodiments, this application also provides a menu version configuration device.

[0107] refer to Figure 3 The menu version configuration device includes: The first receiving module 301 is configured to receive user login information, version requirement information, and public routing configuration files. The first determining module 302 is configured to determine the personalized routing configuration file corresponding to the user login information based on the user login information, the version requirement information, and the public routing configuration file; The second determining module 303 is configured to, in response to receiving modified menu information from a user, modify the personalized routing configuration file according to the modified menu information, and determine the target menu configuration routing file.

[0108] In some embodiments, the first determining module 302 is further configured such that the user login information includes: organization information and permission information; Based on the user login information, the version requirement information, and the public routing configuration file, determine the personalized routing configuration file corresponding to the user login information, including: Generate a feature code based on the organizational information; Based on the organizational information, the target requirement information is determined by searching for the requirement information corresponding to the organizational information in the version requirement information. Based on the target requirement information and the permission information, the public routing configuration file is modified, and a mapping relationship is established between the signature code and the modified public routing file to obtain the personalized routing configuration file corresponding to the signature code.

[0109] In some embodiments, the second determining module 303 is further configured such that the modified menu information includes: information on newly added functional modules; In response to receiving user-modified menu information, the personalized routing configuration file is modified according to the modified menu information, and the target menu routing configuration file is determined, including: In response to receiving user-modified menu information indicating the addition of a new functional module, new route configuration information is generated based on the new functional module information. The newly added route configuration information is added to the personalized route configuration file corresponding to the user login information to obtain the target menu route configuration file.

[0110] In some embodiments, the second determining module 303 is further configured to include: deleting function module information in the modified menu information; In response to receiving user-modified menu information, the personalized routing configuration file is modified according to the modified menu information, and the target menu routing configuration file is determined, including: In response to receiving user's modified menu information as "delete function module information", the name of the function module to be deleted is determined based on the "delete function module information"; In the personalized routing configuration file corresponding to the user login information, delete the routing configuration information corresponding to the name to obtain the target menu routing configuration file.

[0111] In some embodiments, the second determining module 303 is further configured to modify the menu information by including: modifying the position information of the function module; In response to receiving user-modified menu information, the personalized routing configuration file is modified according to the modified menu information, and the target menu routing configuration file is determined, including: In response to receiving user's modified menu information as modifying the location information of a functional module, the target location of the functional module in the personalized routing configuration file is determined based on the modified functional module location information. The current functional module and the functional module to be modified in the target location are swapped to obtain the target menu routing configuration file.

[0112] For ease of description, the above devices are described in terms of function, divided into various modules. Of course, in implementing this application, the functions of each module can be implemented in one or more software and / or hardware.

[0113] The apparatus described above is used to implement a menu version configuration method in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0114] Based on the same inventive concept, corresponding to any of the above embodiments, this application also provides a menu version data display device.

[0115] refer to Figure 4 The menu version data display device includes: The second receiving module 401 is configured to receive user login information; The third determining module 402 is configured to parse the user login information and determine the user feature code; The fourth determining module 403 is configured to determine the initial menu version information based on the user login information, the user feature code, and the central configuration library; the central configuration library is constructed from the target menu routing configuration file generated by applying any of the menu version configuration methods described above. The fifth determining module 404 is configured to determine the target menu version information based on the initial menu version information; The generation module 405 is configured to render according to the target menu version information, generate menu data, and display it.

[0116] In some embodiments, the third determining module 402 is further configured such that the user login information includes account information; The user login information is parsed to determine the user's unique identifier, including: Based on the account information, the organization information of the user login information is determined by searching in the preset organization structure dictionary. The key fields in the organization information are extracted according to the preset extraction rules to generate the user feature code.

[0117] In some embodiments, the fourth determining module 403 is further configured such that the user login information includes organization information and permission information; Based on the user login information, the user signature, and the central configuration library, the initial menu version information is determined, including: Based on the user feature code, search the menu version information corresponding to the user feature code in the central configuration library; Based on the organization information and the permission information, the menu version information is subject to permission verification; In response to the permission verification result being passed, the menu version information is used as the initial menu version information.

[0118] In some embodiments, the fifth determining module 404 is further configured to determine target menu version information based on the initial menu version information, including: Count the number of initial menu version information; In response to the fact that the number of initial menu version information is greater than one, the system receives the initial menu version selected by the user and uses the menu version information corresponding to the initial menu version selected by the user as the target menu version information. Since the number of initial menu version information is one, the initial menu version information is used as the target menu version information.

[0119] In some embodiments, the generation module 405 is further configured such that the menu version information includes the menu version and the routing configuration file corresponding to the menu version, the routing configuration file including: basic routing information, component association rules, data interface configuration and display and jump rules; Render the menu according to the target menu version information to generate menu data, including: The menu data is generated by rendering based on the basic routing information, component association rules, data interface configuration, and display and navigation rules.

[0120] For ease of description, the above devices are described in terms of function, divided into various modules. Of course, in implementing this application, the functions of each module can be implemented in one or more software and / or hardware.

[0121] The apparatus described above is used to implement a menu version data display method in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0122] Based on the same inventive concept, corresponding to any of the above embodiments, this application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements a menu version configuration method or a menu version data display method as described in any of the above embodiments.

[0123] Figure 5This embodiment illustrates a more specific hardware structure of an electronic device. The device may include a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, memory 1020, input / output interface 1030, and communication interface 1040 are interconnected internally via the bus 1050.

[0124] The processor 1010 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0125] The memory 1020 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program code is stored in the memory 1020 and is called and executed by the processor 1010.

[0126] The input / output interface 1030 is used to connect input / output modules to realize information input and output. Input / output modules can be configured as components within the device (not shown in the figure) or externally connected to the device to provide corresponding functions. Input devices may include keyboards, mice, touchscreens, microphones, various sensors, etc., while output devices may include displays, speakers, vibrators, indicator lights, etc.

[0127] The communication interface 1040 is used to connect a communication module (not shown in the figure) to enable communication between this device and other devices. The communication module can communicate via wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0128] Bus 1050 includes a pathway for transmitting information between various components of the device, such as processor 1010, memory 1020, input / output interface 1030, and communication interface 1040.

[0129] It should be noted that although the above-described device only shows the processor 1010, memory 1020, input / output interface 1030, communication interface 1040, and bus 1050, in specific implementations, the device may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the above-described device may only include the components necessary for implementing the embodiments of this specification, and not necessarily all the components shown in the figures.

[0130] The electronic devices described above are used to implement a menu version configuration method or a menu version data display method in any of the foregoing embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be elaborated here.

[0131] Based on the same inventive concept, corresponding to any of the above embodiments, this application also provides a non-transitory computer-readable storage medium that stores computer instructions for causing the computer to execute a menu version configuration method or a menu version data display method as described in any of the above embodiments.

[0132] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device.

[0133] The computer instructions stored in the storage medium of the above embodiments are used to cause the computer to execute a menu version configuration method or a menu version data display method as described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0134] It is understood that before using the technical solutions of the various embodiments in this disclosure, users will be informed of the type, scope of use, and usage scenarios of the personal information involved in an appropriate manner, and user authorization will be obtained.

[0135] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose, based on the prompt message, whether to provide personal information to the software or hardware such as electronic devices, applications, servers, or storage media performing the operations of this disclosed technical solution.

[0136] As an optional but not limited implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0137] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0138] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of this application is limited to these examples; under the concept of this application, the technical features of the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations of different aspects of the embodiments of this application as described above, which are not provided in detail for the sake of brevity.

[0139] Additionally, to simplify the description and discussion, and to avoid obscuring the embodiments of this application, the well-known power / ground connections to integrated circuit (IC) chips and other components may or may not be shown in the provided drawings. Furthermore, the apparatus may be shown in block diagram form to avoid obscuring the embodiments of this application, and this also takes into account the fact that the details of the implementation of these block diagram apparatuses are highly dependent on the platform on which the embodiments of this application will be implemented (i.e., these details should be fully understood by those skilled in the art). While specific details (e.g., circuits) have been set forth to describe exemplary embodiments of this application, it will be apparent to those skilled in the art that the embodiments of this application can be implemented without these specific details or with variations thereof. Therefore, these descriptions should be considered illustrative rather than restrictive.

[0140] Although this application has been described in conjunction with specific embodiments thereof, many substitutions, modifications, and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may be used with the embodiments discussed.

[0141] Any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the embodiments of this application shall be included within the protection scope of this application.

Claims

1. A menu version configuration method, characterized in that, include: Receive user login information, version requirement information, and public routing configuration files; Based on the user login information, the version requirement information, and the public routing configuration file, determine the personalized routing configuration file corresponding to the user login information; In response to receiving the user's modified menu information, the personalized routing configuration file is modified according to the modified menu information to determine the target menu configuration routing file.

2. The method according to claim 1, characterized in that, The user login information includes: organization information and permission information; Based on the user login information, the version requirement information, and the public routing configuration file, determine the personalized routing configuration file corresponding to the user login information, including: Generate a feature code based on the organizational information; Based on the organizational information, the target requirement information is determined by searching for the requirement information corresponding to the organizational information in the version requirement information. Based on the target requirement information and the permission information, the public routing configuration file is modified, and a mapping relationship is established between the signature code and the modified public routing file to obtain the personalized routing configuration file corresponding to the signature code.

3. The method according to claim 1, characterized in that, The modified menu information includes: information on newly added functional modules; In response to receiving user-modified menu information, the personalized routing configuration file is modified according to the modified menu information, and the target menu routing configuration file is determined, including: In response to receiving user-modified menu information as new function module information, new route configuration information is generated based on the new function module information; The newly added route configuration information is added to the personalized route configuration file corresponding to the user login information to obtain the target menu route configuration file.

4. The method according to claim 1, characterized in that, The modified menu information includes: deleting function module information; In response to receiving user-modified menu information, the personalized routing configuration file is modified according to the modified menu information, and the target menu routing configuration file is determined, including: In response to receiving user's modified menu information as "delete function module information", the name of the function module to be deleted is determined based on the "delete function module information"; In the personalized routing configuration file corresponding to the user login information, delete the routing configuration information corresponding to the name to obtain the target menu routing configuration file.

5. The method according to claim 1, characterized in that, The modified menu information includes: modifying the location information of functional modules; In response to receiving user-modified menu information, the personalized routing configuration file is modified according to the modified menu information, and the target menu routing configuration file is determined, including: In response to receiving user's modified menu information as modifying the location information of a functional module, the target location of the functional module in the personalized routing configuration file is determined based on the modified functional module location information. The current functional module and the functional module to be modified in the target location are swapped to obtain the target menu routing configuration file.

6. A method for displaying menu version data, characterized in that, include: Received user login information; The user login information is parsed to determine the user's unique identifier; The initial menu version information is determined based on the user login information, the user feature code, and the central configuration library; the central configuration library is constructed from the target menu routing configuration file generated by applying the menu version configuration method described in any one of claims 1-5. Based on the initial menu version information, determine the target menu version information; The menu is rendered according to the target menu version information, generating menu data and displaying it.

7. The method according to claim 6, characterized in that, The user login information includes account information; The user login information is parsed to determine the user's unique identifier, including: Based on the account information, the organization information of the user login information is determined by searching in the preset organization structure dictionary. The key fields in the organization information are extracted according to the preset extraction rules to generate the user feature code.

8. The method according to claim 6, characterized in that, The user login information includes organization information and permission information; Based on the user login information, the user signature, and the central configuration library, the initial menu version information is determined, including: Based on the user feature code, search the menu version information corresponding to the user feature code in the central configuration library; Based on the organization information and the permission information, the menu version information is subject to permission verification; In response to the permission verification result being passed, the menu version information is used as the initial menu version information.

9. The method according to claim 6, characterized in that, Based on the initial menu version information, the target menu version information is determined, including: Count the number of initial menu version information; In response to the fact that the number of initial menu version information is greater than one, the system receives the initial menu version selected by the user and uses the menu version information corresponding to the initial menu version selected by the user as the target menu version information. Since the number of initial menu version information is one, the initial menu version information is used as the target menu version information.

10. The method according to claim 6, characterized in that, The menu version information includes the menu version and the corresponding routing configuration file. The routing configuration file includes: basic routing information, component association rules, data interface configuration, and display and jump rules. Render the menu according to the target menu version information to generate menu data, including: The menu data is generated by rendering based on the basic routing information, component association rules, data interface configuration, and display and navigation rules.