Cross-system function calling method and device, equipment and storage medium

Abstract

The invention discloses a cross-system function calling method and device, equipment and a storage medium, the cross-system function calling method and device are applied to a Web system platform comprising a plurality of service subsystems, the method comprises the steps that in response to starting operation on a system management subsystem, a system management page is displayed, and the system management page displays a plurality of function menus of the system management subsystem; in response to a starting operation on the menu management menu, displaying function menu directories of the plurality of service subsystems in a system management page; in response to a function menu adding operation on a function menu directory of the first service subsystem, adding a first function menu in the function menu directory corresponding to the first service subsystem; and in response to a link configuration operation on the first function menu, generating a URL access path of the first function menu based on a second function menu correspondingly linked with the first function menu and a second service subsystem to which the second function menu belongs, so that the first service subsystem calls the second function menu through the URL access path of the first function menu.

Description

Technical Field

[0001] The present application relates to the field of Web technology, and in particular to a cross-system function calling method, device, equipment and storage medium. Background Art

[0002] A web system platform is an online environment that integrates a variety of tools and services to help developers quickly build, deploy, and manage web applications. Web system platforms usually provide a range of functions such as code editing, version control, application deployment, database management, network security, analysis, and monitoring to support the entire web application life cycle. As the functions of the web system platform become more and more extensive, the loading speed of users accessing the web system platform through a browser is getting slower and slower, affecting the user experience.

[0003] In the prior art, in order to increase the speed at which users access the Web system platform through a browser, the Web system platform is divided into multiple business subsystems according to business types, and users can access the business subsystem corresponding to the Web system platform according to business needs. However, users or project teams cannot use different functions across business subsystems. When users or project teams need to use functions of other business subsystems, they need to customize the required functions in the business subsystems used by the users or project teams, which greatly increases the development and maintenance costs of the business subsystems, and the use flexibility of the Web system platform is low. Summary of the invention

[0004] The present application provides a cross-system function calling method, apparatus, device and storage medium to link a function menu of a first business subsystem to a function menu of a second business subsystem, so that the first business subsystem can call the function module of the second business subsystem across systems, without the need to customize and develop the function modules of other subsystems in the first business subsystem, thereby reducing the development cost and maintenance cost of the business subsystem and improving the use flexibility of the Web system platform.

[0005] In a first aspect, the present application provides a cross-system function calling method, which is applied to a Web system platform, wherein the Web system platform includes multiple business subsystems, and the method includes:

[0006] In response to a start-up operation of a system management subsystem among the multiple business subsystems, displaying a system management page of the system management subsystem, wherein the system management page displays multiple function menus of the system management subsystem, and the function menus of the system management subsystem include a menu management menu;

[0007] In response to a start operation on the menu management menu, displaying a function menu directory of the plurality of business subsystems in the system management page;

[0008] In response to a function menu adding operation on the function menu directory of the first business subsystem, adding a first function menu to the function menu directory corresponding to the first business subsystem;

[0009] In response to the link configuration operation on the first function menu, a URL access path of the first function menu is generated based on the second function menu corresponding to the link of the first function menu and the second business subsystem to which the second function menu belongs, so that the first business subsystem calls the second function menu of the second business subsystem through the URL access path of the first function menu.

[0010] In a second aspect, the present application provides a cross-system function calling device, which is applied to a Web system platform, wherein the Web system platform includes multiple business subsystems, and the device includes:

[0011] a system management startup module, configured to, in response to a startup operation on a system management subsystem among the multiple business subsystems, display a system management page of the system management subsystem, wherein the system management page displays multiple function menus of the system management subsystem, and the function menus of the system management subsystem include a menu management menu;

[0012] A menu management directory display module is configured to display the function menu directories of the plurality of business subsystems in the system management page in response to a start operation on the menu management menu;

[0013] A first function menu adding module is configured to add a first function menu to the function menu directory corresponding to the first business subsystem in response to a function menu adding operation on the function menu directory of the first business subsystem;

[0014] The first function menu configuration module is configured to respond to the link configuration operation of the first function menu, generate a URL access path for the first function menu based on the second function menu corresponding to the link of the first function menu and the second business subsystem to which the second function menu belongs, so that the first business subsystem calls the second function menu of the second business subsystem through the URL access path of the first function menu.

[0015] In a third aspect, the present application provides a cross-system function calling device, including:

[0016] One or more processors; a storage device storing one or more programs, when the one or more programs are executed by the one or more processors, the one or more processors implement the cross-system function calling method as described in the first aspect.

[0017] In a fourth aspect, the present application provides a storage medium comprising computer executable instructions, which, when executed by a computer processor, are used to execute the cross-system function calling method as described in the first aspect.

[0018] In the present application, in response to the startup operation of the system management subsystem in multiple business subsystems through the Web system platform, the system management page of the system management subsystem is displayed, and the system management page displays multiple function menus of the system management subsystem, and the function menu of the system management subsystem includes a menu management menu; in response to the startup operation of the menu management menu, the function menu directory of multiple business subsystems is displayed in the system management page; in response to the function menu adding operation of the function menu directory of the first business subsystem, the first function menu is added to the function menu directory corresponding to the first business subsystem; in response to the link configuration operation of the first function menu, the URL access path of the first function menu is generated based on the second function menu corresponding to the link of the first function menu and the second business subsystem to which the second function menu belongs, so that the first business subsystem calls the second function menu of the second business subsystem through the URL access path of the first function menu. By adopting the above technical means, the menu management menu can be opened in the system management page of the system management subsystem, and the function menu directories of multiple business subsystems can be displayed in the menu management menu, so that the user can intuitively understand the function menu corresponding to each business subsystem in the menu management menu, and add a new function menu in the business subsystem. After adding a new first function menu to the first business subsystem, if the first function menu is to implement the function of the second function menu of the second business subsystem, the first function menu is linked to the second function menu through a link configuration operation, thereby generating a URL access path for the first function menu according to the second function menu and the second business subsystem to which it belongs. The first business subsystem can call the second function menu of the second business subsystem in the first function menu through the URL access path, that is, realize cross-system calling of function modules of other business subsystems, without the need to customize the development of function modules of other subsystems in a certain business subsystem, thereby reducing the development cost and maintenance cost of the business subsystem and improving the flexibility of use of the Web system platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 is a flow chart of a cross-system function calling method provided by an embodiment of the present application;

[0020] Figure 2 It is a schematic diagram of the main interface of the Web system platform provided in the embodiment of the present application;

[0021] Figure 3 It is one of the schematic diagrams of the system management page provided in the embodiment of the present application;

[0022] Figure 4 This is the second schematic diagram of the system management page provided in the embodiment of the present application;

[0023] Figure 5 This is the third schematic diagram of the system management page provided in the embodiment of the present application;

[0024] Figure 6 This is the fourth schematic diagram of the system management page provided in the embodiment of the present application;

[0025] Figure 7 is a flowchart of generating a URL access path for a first function menu provided in an embodiment of the present application;

[0026] Figure 8 is a flowchart of using the first function menu provided in an embodiment of the present application;

[0027] Fig. 9 This is the fifth schematic diagram of the system management page provided in the embodiment of the present application;

[0028] Fig.10 This is the sixth schematic diagram of the system management page provided in the embodiment of the present application;

[0029] Fig.11 This is the seventh schematic diagram of the system management page provided in the embodiment of the present application;

[0030] Fig.12 This is the eighth schematic diagram of the system management page provided in the embodiment of the present application;

[0031] Fig.13 This is the ninth schematic diagram of the system management page provided in the embodiment of the present application;

[0032] Fig.14 This is the tenth schematic diagram of the system management page provided in the embodiment of the present application;

[0033] Fig.15 This is the eleventh schematic diagram of the system management page provided in the embodiment of the present application;

[0034] Fig.16 It is a structural diagram of a cross-system function calling device provided in an embodiment of the present application;

[0035] Fig.17 It is a structural diagram of a cross-system function calling device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0036] In order to make the purpose, technical scheme and advantages of the present application clearer, the specific embodiments of the present application are further described in detail below in conjunction with the accompanying drawings. It is understood that the specific embodiments described herein are only used to explain the present application, rather than to limit the present application. It should also be noted that, for the convenience of description, only the part related to the present application but not all the contents are shown in the accompanying drawings. Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flow charts. Although the flow chart describes each operation (or step) as a sequential process, many of the operations therein can be implemented in parallel, concurrently or simultaneously. In addition, the order of each operation can be rearranged. The process can be terminated when its operation is completed, but it can also have additional steps not included in the accompanying drawings. The process can correspond to a method, a function, a procedure, a subroutine, a subprogram, etc.

[0037] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0038] In the relevant implementation method, the Web system platform is divided into multiple business subsystems according to the business type, and users can access the business subsystem corresponding to the Web system platform according to business needs. However, users or project teams cannot use different functions across business subsystems. When users or project teams need to use the functions of other business subsystems, they need to customize the required functions in the business subsystems used by the users or project teams, which greatly increases the development and maintenance costs of the business subsystems. Moreover, with the continuous development of customized function modules, the code of the business subsystem is increasing, resulting in code redundancy, which affects the access speed and performance of the business subsystem.

[0039] To solve the above problems, this embodiment provides a cross-system function calling method to link the function menu of the first business subsystem to the function menu of the second business subsystem, so that the first business subsystem can call the function module of the second business subsystem across systems, without the need to customize the development of function modules of other subsystems in the first business subsystem, thereby reducing the development cost and maintenance cost of the business subsystem, avoiding code redundancy of the business subsystem, optimizing the access speed and performance of the business subsystem, and improving the flexibility of use of the Web system platform.

[0040] The cross-system function calling method provided in this embodiment can be executed by a cross-system function calling device, which can be implemented by software and / or hardware, and can be composed of two or more physical entities or one physical entity. The cross-system function calling device can be a Web system platform or an intelligent terminal running a Web system platform, such as a computer and a server.

[0041] The cross-system function calling device is installed with at least one type of operating system, and the cross-system function calling device can install at least one application based on the operating system, and the application can be an application that comes with the operating system, or an application downloaded from a third-party device or server. In this embodiment, the cross-system function calling device is installed with at least an application that can execute the cross-system function calling method.

[0042] For ease of understanding, this embodiment is described by taking a Web system platform as an example of a subject that executes a cross-system function calling method.

[0043] Figure 1 A flowchart of a cross-system function calling method provided by an embodiment of the present application is given. Figure 1 , the cross-system function calling method specifically includes:

[0044] S110. In response to a start-up operation on a system management subsystem in a plurality of business subsystems, a system management page of the system management subsystem is displayed. The system management page displays a plurality of function menus of the system management subsystem. The function menus of the system management subsystem include a menu management menu.

[0045] In this embodiment, the Web system platform includes multiple business subsystems, one business subsystem corresponds to a set of codes, and each business subsystem can be deployed and run independently without affecting each other. A business subsystem can be divided into multiple functional modules, one functional module corresponds to a set of module codes, and the business subsystem can deploy corresponding function menus through functional modules. It can be understood that, under normal circumstances, the business subsystem implements the functions of the corresponding function menu by running the module code of the corresponding configured function module. In this embodiment, in order for the business subsystem to use the services provided by the function modules of other business subsystems across systems, the function menus of different business subsystems are linked by link embedding, thereby calling the services provided by the function modules of other business subsystems across systems.

[0046] For example, Figure 2 Schematic diagram of the main interface of the Web system platform provided in the embodiment of the present application. Figure 2As shown, the multiple business subsystems of the Web system platform include a system management subsystem, a monitoring management subsystem, a report management subsystem, an equipment operation subsystem, and an operation management subsystem. Among them, the system management subsystem can configure the function menu of each business subsystem through the menu management corresponding function module, so that the business subsystem can call the services provided by the function modules of other business subsystems across the system. The main interface displays the start controls 18 of each business subsystem. When the user clicks the start control 18 of one of the business subsystems, the main interface jumps to the front-end page of the business subsystem. The front-end page of the system management subsystem is the system management page. When the user clicks the start control 18 of the system management subsystem in the main interface, the start operation of the system management subsystem is triggered. The Web system platform displays the system management page in the main interface in response to the start operation of the system management subsystem.

[0047] Furthermore, Figure 3 This is one of the schematic diagrams of the system management page provided in the embodiment of the present application. Figure 3 As shown, the system management page displays multiple function menus 11 configured by the system management subsystem, including a user management menu, a role management menu, a menu management menu, a page configuration menu, and a company management menu, etc. The function modules corresponding to these function menus 11 are all function modules included in the system management subsystem, that is, the system management subsystem runs the module code of the function module configured by itself to correspond to the services provided by the user management menu, the role management menu, the menu management menu, the page configuration menu, and the company management menu.

[0048] Among them, the service provided by the menu management menu is to configure the function menu of each business subsystem, and the function menu configured by the business subsystem can correspond to its own function module or the function module of other business subsystems. That is, the business subsystem can call the services provided by the function modules of other business subsystems across systems through the corresponding configured function menu.

[0049] It can be understood that a function menu corresponds to a function module, and the function module corresponding to the function menu can be a function module included in the corresponding business subsystem, or a function module included in other business subsystems. When a user uses a function menu, the module code of the corresponding function module is running to process the corresponding service request. In this regard, the function menu can be divided into two types based on the function module it corresponds to, one is the menu type, and the other is the link type. When the function menu is of the menu type, it is a function menu implemented by the business subsystem using its own function module, that is, the function module corresponding to the function menu is the function module included in the corresponding business subsystem; when the function menu is of the link type, it is a function menu implemented by the business subsystem calling the function modules of other business subsystems, that is, the function module corresponding to the function menu is the function module included in other business subsystems.

[0050] S120. In response to the start operation of the menu management menu, the function menu directories of multiple business subsystems are displayed in the system management page.

[0051] For example, when the user wants to configure the function menu of each business subsystem, he can click the menu management menu in the system management page to trigger the start operation of the menu management menu. The Web system platform responds to the start operation of the menu management menu and displays the function menu directory of multiple business subsystems in the system management page.

[0052] For example, Figure 4 This is the second schematic diagram of the system management page provided in the embodiment of the present application. Figure 4 As shown, the system management page displays multiple function menus 11 of the system management subsystem in the function menu bar. When the user clicks the menu management menu in the function menu bar 12, a business subsystem directory 13 pops up on the right side of the function menu bar 12. When the user clicks a business subsystem in the business subsystem directory 13, a function menu directory 14 of the business subsystem is displayed below the business subsystem and a function menu window 15 is displayed on the right side of the business subsystem directory 13. The function menu window 15 displays the function menus configured for the business subsystem and the detailed information of the function menus. At the same time, a menu adding control 16 is displayed above the function menu window 15. The menu adding control 16 can be used to trigger the operation of adding a new function menu in the corresponding business subsystem.

[0053] S130. In response to the function menu adding operation to the function menu directory of the first business subsystem, add a first function menu to the function menu directory corresponding to the first business subsystem.

[0054] The function menu adding operation is an operation for adding a new function menu in the function menu directory of the first business subsystem. The first business subsystem is any one of the multiple business subsystems included in the Web system platform. This embodiment is described by taking the system management subsystem as the first business subsystem as an example. Figure 4 When the user clicks on the system management subsystem in the business subsystem directory 13, the function menu directory 14 of the system management subsystem is expanded below the system management subsystem. The function menu directory 14 displays the user management menu, role management menu, menu management menu and company management menu contained in the system management subsystem, and the function menu window 15 displays the name, parent menu, type and access path and other detailed information of each function menu of the system management subsystem. After the function menu window 15 corresponding to the system management subsystem is displayed, the menu adding control 16 above it can be used to add a new function menu in the system management subsystem. When the user clicks on the menu adding control 16, the function menu adding operation to the function menu directory of the system management subsystem can be triggered. In response to the function menu adding operation, the Web system platform adds a new menu 17 to the head of the function menu directory 14 corresponding to the system management subsystem. Among them, the first function menu is the new menu 17 currently added by the first business subsystem. At this time, the first function menu has not been configured and named, so it is named as the new menu 17.

[0055] S140. In response to the link configuration operation on the first function menu, a URL access path of the first function menu is generated based on the second function menu corresponding to the link of the first function menu and the second business subsystem to which the second function menu belongs, so that the first business subsystem calls the second function menu of the second business subsystem through the URL access path of the first function menu.

[0056] Among them, the link configuration operation is an operation for configuring the first function menu of the first business subsystem to call the service provided by the function module of the second business subsystem. The second business subsystem is the remaining business subsystems except the first business subsystem. For example, when the user wants to use the service provided by the function module of the monitoring management subsystem in the system management subsystem, the link configuration operation can be used to link the new menu of the system management subsystem to the function menu of the monitoring management subsystem, thereby realizing the call of the service provided by the function module corresponding to the function menu of the monitoring management subsystem. The second function menu is the function menu of other business subsystems to which the first function menu is linked across systems.

[0057] It should be noted that the first function menu can only be linked to function menus of menu type in other business subsystems, that is, the function module corresponding to the second function menu is the function module of the corresponding business subsystem itself.

[0058] For example, Figure 5 This is the third schematic diagram of the system management page provided in the embodiment of the present application. Figure 5 As shown, when the user clicks or double-clicks Figure 4 When a new menu 17 is created in the system management page, a menu configuration window 19 of the new menu 17 is popped up on the system management page. The menu configuration window 19 shows a name input box 22, an identifier input box 23, a type selection control 24, an access path input box 26, a link menu control 20, and a first confirmation control 21. The user can enter the name of the first function menu in the name input box 22, enter the identifier of the first function menu in the identifier input box 23, select the type of the first function menu as a menu type or a link type through the type selection control 24, enter the access path of the first function menu through the access path input box 25, or select the second function menu corresponding to the link of the first function menu through the link menu control 20. After the user enters the name of the first function menu as test aggregation in the name input box 22, enters the identifier of the first function menu as systest1 in the identifier input box 23, selects the type of the first function menu as a link type through the type selection control 24, and clicks the link menu control 20, the link configuration window pops up on the system management page. Figure 6 This is the fourth schematic diagram of the system management page provided in the embodiment of the present application. Figure 6 As shown, click Figure 5 The link menu control 20 shows the system management page pop-up Figure 6 The link configuration window 26 is shown. The user can enter the name of the function menu to be linked in the search box 27 of the link configuration window 26, or click the business subsystem to which the function menu to be linked belongs in the menu list 28. Multiple function menus configured correspondingly are expanded under the business subsystem. After clicking a function menu, the function menu can be confirmed as the function menu to be linked. After selecting the function menu corresponding to the link, the system management page returns to Figure 5 In the menu configuration window 19 shown, the user clicks the first confirmation control 21 in the menu configuration window 19 to trigger the link configuration operation for the first function menu.

[0059] It should be noted that the link configuration window 26 only displays function menus of menu type configured by the business subsystem, so as to prevent the user from selecting a function menu of link type as the function menu to be linked.

[0060] In response to the link configuration operation on the first function menu, the Web system platform determines the name and identifier of the first function menu based on the name in the name input box 22 and the identifier in the identifier input box 23, and determines the second function menu corresponding to the first function menu and the second business subsystem to which the second function menu belongs based on the function menu corresponding to the selected function menu of the link menu control 20 and the business subsystem to which the function menu belongs. Afterwards, the Web system platform generates the URL access path of the first function menu according to the page route and menu identifier of the second function menu and the system identifier of the second business subsystem to which the second function menu belongs, so that the first business subsystem can subsequently call the service provided by the second function menu through the URL access path of the first function menu. For example, when the user names the first function menu newly added to the system management subsystem as test aggregation, and selects the key curve configuration function menu under the monitoring management subsystem as the second function menu corresponding to the link of the test aggregation, the Web system platform generates the URL access path of the test aggregation based on the menu identifier and page route of the key curve configuration and the system identifier of the monitoring management subsystem, and displays the URL access path in the access path input box 26.

[0061] For example, Figure 7 1 is a flowchart of generating a URL access path for a first function menu provided by an embodiment of the present application. Figure 7 As shown, the step of generating the URL access path of the first function menu specifically includes S1401-S1404:

[0062] S1401: Determine a preset page route as a page route of a first function menu.

[0063] Exemplarily, a page route of a fixed page is preset as asIframe. Before generating the URL access path of the first function menu, the page route of the first function menu is first set to asIframe, so that the function page of the first function menu is pointed to the preset fixed page through asIframe.

[0064] S1402: Acquire a page route and a menu identifier of a second function menu, and acquire a system identifier of a second business subsystem to which the second function menu belongs.

[0065] Among them, the page route of the second function menu points to the resource page of the corresponding function module, and the page route and menu identifier of the second function menu are obtained, as well as the system identifier of the second business subsystem, so as to subsequently obtain the page resources of the function module corresponding to the second function menu through the second business subsystem, and based on the obtained page resources, the function page of the second function menu is embeddedly displayed in the function page of the first function menu, thereby realizing the cross-system call of the first function menu to the second function menu.

[0066] S1403: Combine the page route and menu identifier of the second function menu and the system identifier of the second business subsystem to generate a URL access path of the first function menu.

[0067] Exemplarily, the page route and menu identifier of the second function menu and the system identifier of the second business subsystem to which the second function menu belongs are concatenated to obtain the URL access path of the first function menu. For example, the second function menu is key curve configuration, the page route of key curve configuration is urveConfig, the menu identifier of key curve configuration is subCurveConfig, the system identifier of the monitoring management subsystem to which it belongs is micro-monitor, and the corresponding URL access path of the test aggregation that can be combined is http: / / microServe:9000 / micro-monitor / curveConfig?asIfMenuSn=subCurveConfig, where microServe is an IP address placeholder.

[0068] S1404: associate the menu identifier of the first function menu with the corresponding URL access path and save it in a database.

[0069] Exemplarily, the menu identifier and URL access path of the first function menu are associated and saved in the database of the first business subsystem, so that when the first function menu is subsequently started, the page resource of the second function menu corresponding to the link can be loaded based on the URL access path of the menu identifier of the first function menu in the database of the first business subsystem, and the page content of the second function menu can be rendered in the function page of the first function menu based on the page resource, so as to realize the cross-system call of the first function menu to the second function menu. For example, after the URL access path of the test aggregation is generated, the URL access path of the test aggregation can be associated with its menu identifier and stored in the database corresponding to the system management subsystem.

[0070] After the URL access path of the first function menu is saved, the first function menu will be added to the function menu page corresponding to the first business subsystem. When the user wants to use the first function menu, the function menu page of the first business subsystem can be opened to use the first function menu through the function menu page of the first business subsystem. Figure 8 This is a flowchart of using the first function menu provided in an embodiment of the present application.

[0071] like Figure 8 As shown, the step of using the first function menu specifically includes S1501-S1504:

[0072] S1501. In response to a start-up operation on a first business subsystem, a function menu page of the first business subsystem is displayed.

[0073] refer to Figure 2 When the user clicks the start control of the business subsystem shown on the main interface, the start operation of the business subsystem is triggered. In response to the start operation of the business subsystem, the Web system platform jumps the main interface to the function menu page of the business subsystem, and the function menu page is the front page of the business subsystem, and the system management page of the system management subsystem is the function menu page of the system management subsystem. Figure 3 The function menu pages of other business subsystems are similar to the system management page of the system management subsystem. The function menu page of each business subsystem displays the corresponding configured function menu.

[0074] When displaying the function menu page of the first business subsystem, the various function menus configured corresponding to the first business subsystem can be matched according to the system identifier of the first business subsystem; a function menu directory is generated based on the tree structure between the various function menus of the first business subsystem, and the function menu directory is displayed in the function menu bar on the left side of the function menu page.

[0075] S1502: In response to a start operation on a first function menu in a function menu page, a corresponding URL access path is acquired in a database according to a menu identifier of the first function menu.

[0076] For example, Fig. 9 This is the fifth schematic diagram of the system management page provided in the embodiment of the present application. Fig. 9 As shown, after the system management subsystem adds the function menu of test aggregation, when the user opens the system management subsystem again, test aggregation is added to the function menu 11 of the system management page, and the user can click test aggregation to trigger the start operation of test aggregation. After the Web system platform receives the start operation of test aggregation, it obtains the URL access path of test aggregation in the database of the system management subsystem according to the menu identifier of test aggregation.

[0077] S1503: Jump to the first function page of the first function menu according to the page route of the first function menu, and embed the URL access path as the target address of the first function page.

[0078] Among them, the target address can be understood as the address of the web page corresponding to the first function page. Since the URL access path contains the page route of the second function menu, which points to the second function page of the second function menu, after the URL access path is embedded in the target address of the first function page, the first function page can be embedded in the second function page displaying the second function menu, thereby making a cross-system call from the first function menu to the second function menu. For example, the page route of the first function menu is asIframe, and the first function page displaying the first function menu can be embedded in the function menu page of the first business subsystem based on the page route of the first function menu. The first function page is the fixed page pointed to by asIframe. Afterwards, the URL access path of the first function menu is passed as the routing parameter (asIfUrl) of the fixed page to be embedded in the target address of the fixed page.

[0079] Optionally, when implementing embedding the first function page of the first function menu to display the second function page of the second function menu, the second function page of the second function menu can be embedded into the first function menu through an inline frame (iframe) tag of the first function menu. For example, the src attribute of the iframe tag of the first function menu is set to the URL access path of the first function menu, so that the second function page of the second function menu corresponding to the URL access path specified by the src attribute is to be embedded into the first function page of the first function menu.

[0080] Since the first function menu and the second function menu belong to two independent business subsystems, the two independent business subsystems will not share the user information and login token of the logged-in user when the user logs in. As a result, when the second function page of the second function menu is embedded from the first function page of the first function menu, the user needs to re-enter the login account and password, affecting the convenience and efficiency of cross-system calls. To this end, the user information and login token can be spliced ​​in the URL access path so that the second function menu can obtain the user information and login token from the URL access path, eliminating the user's login operation and directly providing the user with the corresponding functional services. The specific implementation process is: replace the IP address placeholder in the URL access path with the domain name of the Web system platform; splice the user information and login token of the logged-in user of the Web system platform with the URL access path, and splice the preset embedding identifier with the URL access path to obtain the link address; embed the link address into the target address of the first function page. Exemplarily, the domain name is replaced with the IP address placeholder (microServe) in the URL access path of the test aggregation, the user information and login token (token) of the logged-in user of the Web system platform are spliced ​​after the URL access path, and then an embedded identifier (asIfType=3) is spliced ​​on to inform the link target address through the embedded identifier that the URL access path is embedded as the target address of the fixed page. After the replacement and splicing processing, the URL access path forms a link address (sysUrl), and the link address is embedded in the target address of the first function page, so that the page resource corresponding to the link address can be loaded subsequently and the page content corresponding to the page resource can be embedded in the first function page for display. The page resource corresponding to the link address is the page resource of the second function menu linked to the first function menu. Therefore, it is possible to display the page content of the second function menu under the first function page of the first function menu, that is, to realize the first function menu calling the second function menu across systems.

[0081] S1504: Load the page resources of the second function menu of the second business subsystem according to the URL access path embedded in the target address of the first function page, and display the page content of the second function menu in the first function page according to the page resources.

[0082] Exemplarily, the URL access path embedded in the target address of the first function page points to the second function menu of the second business subsystem loaded therein. Therefore, the page resources of the second function menu can be loaded based on the URL access path embedded in the target address of the first function page, and the page content corresponding to the page resources can be embedded and displayed in the first function page, thereby realizing cross-system calling of the first function menu to the second function menu.

[0083] Optionally, the process of loading the page resources of the second function menu is as follows: the second business subsystem obtains the user information and login token in the link address, and caches the user information and login token; the second business subsystem obtains the page resources of the second function page of the second function menu according to the page route and menu identifier of the second function menu in the link address; the second business subsystem loads the main resources in the page resources of the second function page according to the embedded identifier in the link address, so as to render the main content of the second function page in the first function page. Exemplarily, after the link address is embedded in the target address of the first function page, the second business subsystem obtains the user information and login token in the link address and synchronizes them to the cache space to avoid the user from logging in again and can directly use the function module corresponding to the second function menu. The second business subsystem locates the page resources of the second function page of the second function menu according to the page route and menu identifier of the second function menu in the link address, and obtains the page resources of the second function page. Afterwards, the second business subsystem determines, based on the embedded identifier in the link address, that the second function page is embedded in the first function page for display. That is, there is no need to display the menu and the top navigation bar of the second function page in the first function page. Therefore, the main resources in the page resources of the second function page can be obtained to embed and display the main content of the second function page in the first function page through the main resources.

[0084] In one embodiment, when a user adds a function menu of a menu type in a business subsystem, it is also implemented through the menu management menu of the system management subsystem. Specifically, after starting the menu management menu in the system management page, the function menu directories of multiple business subsystems are displayed in the system management page. Afterwards, in response to the function menu adding operation on the function menu directory of the third business subsystem, a third function menu is added to the function menu directory corresponding to the third business subsystem; in response to the menu configuration operation on the third function menu, the page route of the third function menu is determined, and the resource page pointed to by the page route of the third function menu is determined as the third function page of the third function menu. Among them, the third business subsystem is any one of the multiple business subsystems of the Web system platform. The menu configuration operation is an operation for configuring the third function menu of the third business subsystem to call the service provided by its own function module. This embodiment is described by taking the third business subsystem as the monitoring subsystem as an example. For example, the functional modules included in the monitoring subsystem include process drawings, alarm events, area management, key curves and trend analysis. When the user wants to use the services provided by the functional modules corresponding to the alarm events in the monitoring subsystem, the user can configure the functional modules corresponding to the alarm events as the functional modules corresponding to the third functional menu through the menu configuration operation, thereby realizing the use of the services provided by the functional modules themselves.

[0085] For example, Fig.10This is the sixth schematic diagram of the system management page provided in the embodiment of the present application. Fig.10 As shown, when the user clicks on the monitoring subsystem in the business subsystem directory 13, the function menu directory 14 of the monitoring subsystem is expanded below the monitoring subsystem, and the function menu directory 14 displays the function menus of the process diagram, area management and key curve configuration contained in the monitoring subsystem, and the function menu window 15 displays the name, parent menu, type and access path and other detailed information of each function menu of the monitoring subsystem. After the function menu window 15 corresponding to the monitoring subsystem is displayed, the menu adding control 16 above it can be used to add a new function menu in the monitoring subsystem. When the user clicks on the menu adding control 16, the function menu adding operation of the function menu directory 14 of the monitoring subsystem can be triggered. In response to the function menu adding operation, the Web system platform adds a new menu 17 at the head of the function menu directory 14 corresponding to the monitoring subsystem. Among them, the third function menu is the new menu 17 currently added by the third business subsystem. At this time, the third function menu has not been configured and named, so it is named as the new menu 17.

[0086] Fig.11 This is the seventh schematic diagram of the system management page provided in the embodiment of the present application. Fig.11 As shown, when the user clicks or double-clicks Fig.10 When the new menu 17 is created in the system management page, the menu configuration window 19 of the new menu 17 pops up. The user enters the name of the third function menu as alarm event in the name input box 22, enters the identifier of the third function menu as alarm event in the identifier input box 23, selects the type of the third function menu as menu type through the type selection control 24, and enters the page route of the resource page of the function module corresponding to the alarm event in the access path input box 26. After that, the user clicks the first confirmation control 21 in the menu configuration window 19 to trigger the menu configuration operation for the third function menu.

[0087] The Web system platform responds to the menu configuration operation on the third function menu, determines the name and identifier of the third function menu based on the name in the name input box 22 and the identifier in the identifier input box 23, and determines the page route in the access path input box 26 as the page route of the third function page of the third function menu, so that the resource page of the function module pointed to by the page route serves as the third function page of the third function menu.

[0088] In one embodiment, reference Figure 3, the function menu of the system management subsystem also includes a role management menu and a user management menu. The business subsystem accessed by each role and the permissions of the corresponding function menu can be configured through the role management menu, and the role corresponding to each user can be configured through the user management menu, so as to quickly configure each user's access rights to the business subsystem and the corresponding function menu, thereby improving the configuration efficiency of the user's access rights. The specific implementation process is as follows: after displaying the system management page of the system management subsystem, in response to the start operation of the role management menu, multiple role types are displayed in the system management page; in response to the permission configuration operation of the role type, the access rights of the role type to multiple business subsystems and corresponding function menus are determined; in response to the start operation of the user management menu, multiple user accounts are displayed in the system management page; in response to the authorization operation of the user account, the target role type corresponding to the user account is determined, and the access rights corresponding to the target role type are determined as the access rights of the user account. Among them, the permission configuration operation is an operation for configuring the permission of the corresponding role type to access the business subsystem and the corresponding function menu; the authorization operation is an operation for granting the user the access rights configured for the corresponding role.

[0089] For example, Fig.12 This is the eighth schematic diagram of the system management page provided in the embodiment of the present application. Fig.12 As shown, after the user clicks on the role management menu in the system management page, the role management page 29 of the role management menu is displayed in the system management page. The role management page 29 displays the names and other information of each configured role type. A role adding control 30 is provided above the role management page 29, and the user can add a new role by clicking on the role adding control 30. Fig.13 This is the ninth schematic diagram of the system management page provided in the embodiment of the present application. Fig.13 As shown, when the user double-clicks the administrator in the role management page 29 or clicks the edit control of the administrator in the role management page 29 (not shown in the figure), the role management page 29 pops up the permission configuration window 31, and the permission configuration window 31 shows the selection controls 32 of each business subsystem and the corresponding function menus. The business subsystems and corresponding function menus that the administrator can access can be selected through the selection control 32. For example, when the user clicks the selection control 32 corresponding to the key curve configuration in the system management subsystem and the monitoring management subsystem, all the function menus in the system management subsystem and the key curves in the monitoring management subsystem are subsequently determined as function menus that the administrator can access. After the user selects the business subsystems and function menus that the administrator can access, click the second confirmation control 33 to trigger the permission configuration operation. According to the permission configuration operation, the business subsystems and function menus corresponding to the selected selection control 32 in the permission configuration window 31 are determined as the administrator's access rights.

[0090] After configuring the access rights for each role type, the user can click the User Management Menu to display the User Management page of the User Management Menu on the System Management page. Fig.14 This is a tenth schematic diagram of the system management page provided in the embodiment of the present application. Fig.14 As shown, the user management page 34 displays each user account that has been added and detailed information such as the user name, role type, and whether the user account is online. An account adding control 35 is displayed above the user management page 34, and a new user account can be added through the account adding control 35. Fig.15 This is the eleventh schematic diagram of the system management page provided in the embodiment of the present application. Fig.15 As shown, when the user double-clicks the user account xx1 in the user management page 34 or clicks the edit control of the user account xx1 in the user management page 34 (not shown in the figure), the user management page 34 pops up a user rights granting window 36, and the user rights granting window 36 shows a role selection box 37, through which the role type of the user account xx1 can be selected. For example, when the user clicks the role selection box 37, a corresponding role selection list 38 is expanded, and after clicking the administrator in the role selection list 38, the role type of the user account xx1 is selected as the administrator. Afterwards, the user clicks the third confirmation control 39 to trigger the authorization operation, and according to the authorization operation, the administrator selected in the user rights granting window 36 is determined as the role type of the user account xx1, and then the access rights of the user account xx1 are determined as the access rights of the administrator.

[0091] In one embodiment, the system management subsystem also includes a data dictionary management menu, which is used to configure the page layout of each business subsystem. Specifically, the display type of the function menu can be configured through the data dictionary management menu, and the display types include top-level display, left-side display, and separate display. When the display type of the function menu is top-level display, the business subsystem and the corresponding function menu are displayed at the top level of the page. When the display type of the function menu is left-side display, the business subsystem and the corresponding function menu are displayed on the left side of the page. When the display type of the function menu is separate display, the business subsystem is displayed at the top level and the function menu is displayed on the left. Based on this, this embodiment can achieve reasonable layout of pages through a low-code approach.

[0092] In addition, different companies have additional requirements for system names, login page backgrounds, etc., and the names and login page backgrounds of various business subsystems can be configured through the company management menu of the system management subsystem. For example, when configuring the login page background of the Web platform system, you can upload an image corresponding to the login page background in the company management page of the company management menu, and then set the corresponding uploaded image as the login page background. Based on this, this embodiment can quickly configure the names and login page backgrounds of various business subsystems in a low-code manner.

[0093] In summary, the cross-system function calling method provided by the embodiment of the present application, in response to the startup operation of the system management subsystem in multiple business subsystems through the Web system platform, displays the system management page of the system management subsystem, the system management page displays multiple function menus of the system management subsystem, and the function menu of the system management subsystem includes a menu management menu; in response to the startup operation of the menu management menu, the function menu directory of multiple business subsystems is displayed in the system management page; in response to the function menu adding operation of the function menu directory of the first business subsystem, the first function menu is added to the function menu directory corresponding to the first business subsystem; in response to the link configuration operation of the first function menu, the URL access path of the first function menu is generated based on the second function menu corresponding to the link of the first function menu and the second business subsystem to which the second function menu belongs, so that the first business subsystem calls the second function menu of the second business subsystem through the URL access path of the first function menu. By adopting the above technical means, the menu management menu can be opened in the system management page of the system management subsystem, and the function menu directories of multiple business subsystems can be displayed in the menu management menu, so that the user can intuitively understand the function menu corresponding to each business subsystem in the menu management menu, and add a new function menu in the business subsystem. After adding a new first function menu to the first business subsystem, if the first function menu is to implement the function of the second function menu of the second business subsystem, the first function menu is linked to the second function menu through a link configuration operation, thereby generating a URL access path for the first function menu according to the second function menu and the second business subsystem to which it belongs. The first business subsystem can call the second function menu of the second business subsystem in the first function menu through the URL access path, that is, realize cross-system calling of function modules of other business subsystems, without the need to customize the development of function modules of other subsystems in a certain business subsystem, thereby reducing the development cost and maintenance cost of the business subsystem and improving the flexibility of use of the Web system platform.

[0094] Based on the above embodiments, Fig.16 A schematic diagram of the structure of a cross-system function calling device provided in an embodiment of the present application. Fig.16The cross-system function calling device provided in this embodiment specifically includes: a system management startup module 41, a menu management directory display module 42, a first function menu adding module 43 and a first function menu configuration module 44.

[0095] The system management startup module 41 is configured to display a system management page of the system management subsystem in response to a startup operation of the system management subsystem in the plurality of business subsystems, wherein the system management page displays a plurality of function menus of the system management subsystem, and the function menus of the system management subsystem include a menu management menu;

[0096] The menu management directory display module 42 is configured to display the function menu directories of multiple business subsystems in the system management page in response to the start operation of the menu management menu;

[0097] The first function menu adding module 43 is configured to add the first function menu to the function menu directory corresponding to the first business subsystem in response to the function menu adding operation on the function menu directory of the first business subsystem;

[0098] The first function menu configuration module 44 is configured to respond to the link configuration operation of the first function menu, generate a URL access path for the first function menu based on the second function menu corresponding to the link of the first function menu and the second business subsystem to which the second function menu belongs, so that the first business subsystem calls the second function menu of the second business subsystem through the URL access path of the first function menu.

[0099] On the basis of the above embodiment, the first function menu configuration module 44 includes: a page routing configuration unit, configured to determine the preset page routing as the page routing of the first function menu; a link menu information acquisition unit, configured to obtain the page routing and menu identification of the second function menu, and obtain the system identification of the second business subsystem to which the second function menu belongs; an access path generation unit, configured to combine the page routing and menu identification of the second function menu and the system identification of the second business subsystem to generate a URL access path for the first function menu; an access path saving unit, configured to associate the menu identification of the first function menu with the corresponding URL access path and save it in a database.

[0100] On the basis of the above embodiments, the cross-system function calling device also includes: a function menu usage module, the function menu calling module includes: a function menu page display unit, configured to display the function menu page of the first business subsystem in response to the startup operation of the first business subsystem after generating the URL access path of the first function menu; an access path acquisition unit, configured to respond to the startup operation of the first function menu in the function menu page, and obtain the corresponding URL access path in the database according to the menu identifier of the first function menu; an access path embedding unit, configured to jump to the first function page of the first function menu according to the page routing of the first function menu, and embed the URL access path as the target address of the first function page; a function menu calling unit, configured to load the page resources of the second function menu of the second business subsystem according to the URL access path embedded in the target address of the first function page, and display the page content of the second function menu in the first function page according to the page resources.

[0101] Based on the above embodiment, the access path embedding unit includes: a domain name replacement subunit, configured to replace the IP address placeholder in the URL access path with the domain name of the Web system platform; a link address generation subunit, configured to splice the user information and login token of the login user of the Web system platform with the URL access path, and splice the preset embedding identifier with the URL access path to obtain a link address; an address embedding subunit, configured to embed the link address into the target address of the first function page.

[0102] Based on the above embodiment, the function menu calling unit includes: a user information caching subunit, which is configured for the second business subsystem to obtain user information and login token in the link address, and cache the user information and login token; a page resource acquisition subunit, which is configured for the second business subsystem to obtain the page resources of the second function page of the second function menu according to the page route and menu identifier of the second function menu in the link address; a body resource loading subunit, which is configured for the second business subsystem to load the body resources in the page resources of the second function page according to the embedded identifier in the link address, so as to render the body content of the second function page in the first function page.

[0103] On the basis of the above embodiments, the cross-system function calling device also includes: a second function menu adding module, which is configured to, after displaying the function menu directories of multiple business subsystems in the system management page, respond to the function menu adding operation on the function menu directory of the third business subsystem, and add a third function menu to the function menu directory corresponding to the third business subsystem; a second function menu configuration module, which is configured to determine the page route of the third function menu in response to the menu configuration operation on the third function menu, and determine the resource page pointed to by the page route of the third function menu as the third function page of the third function menu.

[0104] On the basis of the above embodiments, the function menu of the system management subsystem also includes a user management menu and a role management menu; accordingly, the cross-system function calling device also includes an access permission configuration module, and the access permission configuration module includes: a role type display unit, configured to display multiple role types in the system management page in response to a start operation of the role management menu; a role permission determination unit, configured to determine the role type's access permissions to multiple business subsystems and corresponding function menus in response to a permission configuration operation on the role type; a user account display unit, configured to display multiple user accounts in the system management page in response to a start operation of the user management menu; a user account permission determination unit, configured to determine the target role type corresponding to the user account in response to an authorization operation on the user account, and determine the access permissions corresponding to the target role type as the access permissions of the user account.

[0105] As described above, the cross-system function calling device provided by the embodiment of the present application, in response to the startup operation of the system management subsystem in multiple business subsystems through the Web system platform, displays the system management page of the system management subsystem, the system management page displays multiple function menus of the system management subsystem, and the function menu of the system management subsystem includes a menu management menu; in response to the startup operation of the menu management menu, the function menu directory of multiple business subsystems is displayed in the system management page; in response to the function menu adding operation of the function menu directory of the first business subsystem, the first function menu is added to the function menu directory corresponding to the first business subsystem; in response to the link configuration operation of the first function menu, the URL access path of the first function menu is generated based on the second function menu corresponding to the link of the first function menu and the second business subsystem to which the second function menu belongs, so that the first business subsystem calls the second function menu of the second business subsystem through the URL access path of the first function menu. By adopting the above technical means, the menu management menu can be opened in the system management page of the system management subsystem, and the function menu directories of multiple business subsystems can be displayed in the menu management menu, so that the user can intuitively understand the function menu corresponding to each business subsystem in the menu management menu, and add a new function menu in the business subsystem. After adding a new first function menu to the first business subsystem, if the first function menu is to implement the function of the second function menu of the second business subsystem, the first function menu is linked to the second function menu through a link configuration operation, thereby generating a URL access path for the first function menu according to the second function menu and the second business subsystem to which it belongs. The first business subsystem can call the second function menu of the second business subsystem in the first function menu through the URL access path, that is, realize cross-system calling of function modules of other business subsystems, without the need to customize the development of function modules of other subsystems in a certain business subsystem, thereby reducing the development cost and maintenance cost of the business subsystem and improving the flexibility of use of the Web system platform.

[0106] The cross-system function calling device provided in the embodiment of the present application can be used to execute the cross-system function calling method provided in the above embodiment, and has corresponding functions and beneficial effects.

[0107] Fig.17 This is a schematic diagram of a cross-system function calling device provided in an embodiment of the present application, with reference to Fig.17, the cross-system function calling device includes: a processor 51, a memory 52, a communication device 53, an input device 54 and an output device 55. The number of processors 51 in the cross-system function calling device can be one or more, and the number of memories 52 in the cross-system function calling device can be one or more. The processor 51, memory 52, communication device 55, input device 54 and output device 55 of the cross-system function calling device can be connected through a bus or other methods.

[0108] The memory 52, as a computer-readable storage medium, can be used to store software programs, computer executable programs and modules, such as program instructions / modules corresponding to the cross-system function call method of any embodiment of the present application (for example, the system management startup module 41, the menu management directory display module 42, the first function menu addition module 43 and the first function menu configuration module 44). The memory 52 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the device, etc. In addition, the memory 52 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network and a combination thereof.

[0109] The communication device 53 is used for data transmission.

[0110] The processor 51 executes various functional applications and data processing of the device by running the software programs, instructions and modules stored in the memory 52, that is, implements the above-mentioned cross-system function calling method.

[0111] The input device 54 may be used to receive input digital or character information and generate key signal input related to user settings and function control of the device. The output device 55 may include a display device such as a display screen.

[0112] The cross-system function calling device provided above can be used to execute the cross-system function calling method provided in the above embodiment, and has corresponding functions and beneficial effects.

[0113] An embodiment of the present application also provides a storage medium containing computer executable instructions, which are used to execute a cross-system function calling method when executed by a computer processor. The cross-system function calling method includes: in response to a startup operation of a system management subsystem in multiple business subsystems, a system management page of the system management subsystem is displayed, the system management page displays multiple function menus of the system management subsystem, and the function menu of the system management subsystem includes a menu management menu; in response to a startup operation of the menu management menu, a function menu directory of multiple business subsystems is displayed in the system management page; in response to a function menu adding operation to the function menu directory of the first business subsystem, a first function menu is added to the function menu directory corresponding to the first business subsystem; in response to a link configuration operation on the first function menu, a URL access path of the first function menu is generated based on a second function menu corresponding to the link of the first function menu and a second business subsystem to which the second function menu belongs, so that the first business subsystem calls the second function menu of the second business subsystem through the URL access path of the first function menu.

[0114] Storage medium - any of various types of memory devices or storage devices. The term "storage medium" is intended to include: installation media, such as CD-ROM, floppy disk or tape device; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory, such as flash memory, magnetic media (such as hard disk or optical storage); registers or other similar types of memory elements, etc. Storage media may also include other types of memory or combinations thereof. In addition, the storage medium may be located in the first computer system in which the program is executed, or may be located in a different second computer system, which is connected to the first computer system via a network (such as the Internet). The second computer system can provide program instructions to the first computer for execution. The term "storage medium" may include two or more storage media residing in different locations (for example, in different computer systems connected by a network). The storage medium may store program instructions (for example, embodied as a computer program) that can be executed by one or more processors.

[0115] Of course, the storage medium containing computer executable instructions provided in an embodiment of the present application is not limited to the above cross-system function calling method, and the computer executable instructions can also execute related operations in the cross-system function calling method provided in any embodiment of the present application.

[0116] The cross-system function calling apparatus, cross-system function calling system, storage medium and cross-system function calling device provided in the above embodiments can execute the cross-system function calling method provided in any embodiment of the present application. For technical details not described in detail in the above embodiments, please refer to the cross-system function calling method provided in any embodiment of the present application.

[0117] The above are only preferred embodiments of the present application and the technical principles used. The present application is not limited to the specific embodiments herein, and various obvious changes, readjustments and substitutions that can be made by those skilled in the art will not deviate from the protection scope of the present application. Therefore, although the present application is described in more detail through the above embodiments, the present application is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present application, and the scope of the present application is determined by the scope of the claims.

Claims

1. A cross-system function calling method, characterized in that: Applied to a Web system platform, the Web system platform includes multiple business subsystems, and the method includes: In response to a start-up operation of a system management subsystem among the multiple business subsystems, displaying a system management page of the system management subsystem, wherein the system management page displays multiple function menus of the system management subsystem, and the function menus of the system management subsystem include a menu management menu; In response to a start operation on the menu management menu, displaying a function menu directory of the plurality of business subsystems in the system management page; In response to a function menu adding operation on the function menu directory of the first business subsystem, adding a first function menu to the function menu directory corresponding to the first business subsystem; In response to the link configuration operation on the first function menu, a URL access path of the first function menu is generated based on the second function menu corresponding to the link of the first function menu and the second business subsystem to which the second function menu belongs, so that the first business subsystem calls the second function menu of the second business subsystem through the URL access path of the first function menu.

2. The cross-system function calling method according to claim 1, characterized in that: The generating a URL access path of the first function menu based on the second function menu linked to the first function menu and the second business subsystem to which the second function menu belongs includes: Determine the preset page route as the page route of the first function menu; Acquire the page route and menu identifier of the second function menu, and acquire the system identifier of the second business subsystem to which the second function menu belongs; Combining the page route and menu identifier of the second function menu and the system identifier of the second business subsystem to generate a URL access path of the first function menu; The menu identifier of the first function menu and the corresponding URL access path are associated and saved in a database.

3. The cross-system function calling method according to claim 2, characterized in that: After generating the URL access path of the first function menu, the method further includes: In response to a start-up operation on the first business subsystem, displaying a function menu page of the first business subsystem; In response to a start operation on a first function menu in the function menu page, acquiring a corresponding URL access path in the database according to a menu identifier of the first function menu; Jump to the first function page of the first function menu according to the page route of the first function menu, and embed the URL access path as the target address of the first function page; The page resources of the second function menu of the second business subsystem are loaded according to the URL access path embedded in the target address of the first function page, and the page content of the second function menu is displayed in the first function page according to the page resources.

4. The cross-system function calling method according to claim 3, characterized in that: The step of embedding the URL access path as the target address of the first function page includes: Replace the IP address placeholder in the URL access path with the domain name of the Web system platform; The user information and login token of the login user of the Web system platform are spliced ​​with the URL access path, and the preset embedded identifier is spliced ​​with the URL access path to obtain a link address; The link address is embedded into the target address of the first function page.

5. The cross-system function calling method according to claim 4, characterized in that: The step of loading the page resource of the second function menu of the second business subsystem according to the URL access path embedded in the target address of the first function page includes: The second business subsystem obtains user information and a login token from the link address, and caches the user information and the login token; The second business subsystem acquires the page resource of the second function page of the second function menu according to the page route and menu identifier of the second function menu in the link address; The second business subsystem loads the main resources in the page resources of the second function page according to the embedded identifier in the link address, so as to render the main content of the second function page in the first function page.

6. The cross-system function calling method according to claim 1, characterized in that: After displaying the function menu directories of the plurality of business subsystems on the system management page, the method further includes: In response to a function menu adding operation on the function menu directory of the third business subsystem, adding a third function menu to the function menu directory corresponding to the third business subsystem; In response to the menu configuration operation on the third function menu, a page route of the third function menu is determined, and a resource page pointed to by the page route of the third function menu is determined as a third function page of the third function menu.

7. The cross-system function calling method according to claim 1, characterized in that: The function menu of the system management subsystem also includes a user management menu and a role management menu; accordingly, after displaying the system management page of the system management subsystem, it also includes: In response to a start operation on the role management menu, displaying a plurality of role types in the system management page; In response to the permission configuration operation on the role type, determining the access rights of the role type to the multiple business subsystems and corresponding function menus; In response to a start operation on the user management menu, displaying a plurality of user accounts in the system management page; In response to the authorization operation on the user account, a target role type corresponding to the user account is determined, and the access permission corresponding to the target role type is determined as the access permission of the user account.

8. A cross-system function calling device, characterized in that: Applied to a Web system platform, the Web system platform includes multiple business subsystems, and the device includes: a system management startup module, configured to, in response to a startup operation on a system management subsystem among the multiple business subsystems, display a system management page of the system management subsystem, wherein the system management page displays multiple function menus of the system management subsystem, and the function menus of the system management subsystem include a menu management menu; A menu management directory display module is configured to display the function menu directories of the plurality of business subsystems in the system management page in response to a start operation on the menu management menu; A first function menu adding module is configured to add a first function menu to the function menu directory corresponding to the first business subsystem in response to a function menu adding operation on the function menu directory of the first business subsystem; The first function menu configuration module is configured to generate a URL access path for the first function menu in response to a link configuration operation on the first function menu, based on a second function menu corresponding to the link of the first function menu and a second business subsystem to which the second function menu belongs, so that the first business subsystem calls the second function menu of the second business subsystem through the URL access path of the first function menu.

9. A cross-system function calling device, characterized in that: include: one or more processors; A storage device stores one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors implement the cross-system function calling method as described in any one of claims 1-7.

10. A storage medium containing computer executable instructions, characterized in that: When the computer executable instructions are executed by a computer processor, they are used to execute the cross-system function calling method according to any one of claims 1 to 7.

Images