Application assembling method and device, equipment and storage medium

Abstract

The invention discloses an application assembling method and device, equipment and a storage medium, and relates to the technical field of computers, and the method comprises the steps: constructing a main application architecture based on layout position information and explicit and implicit information corresponding to a to-be-laid functional component; obtaining menu configuration data, and binding the menu configuration data with the main application architecture; when binding is completed, receiving an application assembly request triggered based on the application assembly page, and determining function menu configuration information of the to-be-assembled application based on the application assembly request; and performing information configuration on the to-be-assembled application based on the function menu configuration information to generate an assembled application. According to the invention, when the menu configuration data and the main application architecture are bound, information configuration can be performed on the to-be-assembled application based on the function menu configuration information of the to-be-assembled application to generate the assembled application, so that the problem that an application assembling method in the prior art lacks in-depth design of a service architecture is solved; and the flexibility and the efficiency of application assembly are not high.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, in particular to an application assembly method and device, equipment and storage medium. BACKGROUND

[0002] With the rapid development of financial technology, the business model of financial institutions is becoming increasingly complex and diversified. Among them, large financial institutions usually need to manage their business processes, customer service and risk control through complex software systems, which need to have high flexibility and scalability to adapt to the needs of different business departments, personalized services for different customer groups and changing financial regulatory requirements.

[0003] In traditional financial software development, micro-frontend technology can be used to build large financial web applications. Micro-frontend technology splits large applications into multiple independent sub-applications, each of which can be developed, deployed and maintained independently, thereby improving development efficiency and system scalability. However, since the micro-frontend technology framework usually focuses more on the generality of technology, it lacks in-depth design of financial business architecture, resulting in low flexibility and efficiency of application assembly. SUMMARY

[0004] The main purpose of the present application is to provide an application assembly method, device, equipment and storage medium, which aims to solve the technical problem that the existing application assembly method lacks in-depth design of business architecture, resulting in low flexibility and efficiency of application assembly.

[0005] To achieve the above-mentioned purpose, the present application provides an application assembly method, which comprises:

[0006] Constructing a main application architecture based on layout position information and visibility information corresponding to the functional components to be laid out, the visibility information being used to represent whether the functional components to be laid out are displayed;

[0007] Obtaining menu configuration data and binding the menu configuration data with the main application architecture;

[0008] When the binding is completed, receiving an application assembly request triggered based on an application assembly page, and determining functional menu configuration information of an application to be assembled based on the application assembly request;

[0009] Configuring information for the application to be assembled based on the functional menu configuration information, and generating an assembled application.

[0010] In an embodiment, the step of constructing a main application architecture based on layout position information and visibility information corresponding to the functional components to be laid out comprises:

[0011] Determine a component replacement mode and a component control mode corresponding to a to-be-laid-out functional component according to a business requirement, the to-be-laid-out functional component including a navigation bar, a left menu, and a tab page;

[0012] Determine layout position information and visibility information corresponding to the to-be-laid-out functional component;

[0013] Construct a main application architecture based on the layout position information, the visibility information, the component replacement mode, and the component control mode.

[0014] In an embodiment, the step of receiving, upon completion of binding, an application assembly request triggered based on an application assembly page includes:

[0015] Upon completion of binding, determine identification information corresponding to a menu object in the main application architecture according to the menu configuration data;

[0016] Obtain resource function attribution identification and resource path identification corresponding to the menu object according to the identification information;

[0017] Generate an application assembly page based on the menu object, the resource function attribution identification, and the resource path identification;

[0018] Receive an application assembly request triggered based on the application assembly page.

[0019] In an embodiment, after the step of configuring information of the to-be-assembled application based on the functional menu configuration information to generate an assembled application, the method further includes:

[0020] Generate an application industry version based on the assembled application and a target functional component in the main application architecture, the application industry version performing hierarchical linkage with a top navigation and a left menu in the main application architecture;

[0021] Upon receiving an application control request triggered by a user based on the application industry version, determine a target control application according to the application control request;

[0022] Determine whether the target control application has a top menu;

[0023] If so, perform hierarchical adjustment on a target left menu corresponding to the target control application.

[0024] In an embodiment, after the step of generating an application industry version based on the assembled application and a target functional component in the main application architecture, the method further includes:

[0025] Upon receiving a to-be-identified URL, parse the to-be-identified URL;

[0026] determine a to-be-recognized classification identifier and a to-be-recognized resource path identifier corresponding to the to-be-recognized URL according to the analysis result;

[0027] determine a to-be-rendered menu object in the application assembly page based on the to-be-recognized classification identifier and the to-be-recognized resource path identifier;

[0028] perform page rendering on the application assembly page based on the to-be-rendered menu object.

[0029] In an embodiment, the step of performing page rendering on the application assembly page based on the to-be-rendered menu object comprises:

[0030] determine a navigation mode and target visibility information corresponding to the to-be-rendered menu object;

[0031] if the navigation mode is a left-side navigation mode, display the to-be-rendered menu object in a left-side menu of the application assembly page based on the target visibility information;

[0032] if the navigation mode is a double navigation mode, display the to-be-rendered menu object in a left-side menu and a top navigation bar of the application assembly page based on the target visibility information.

[0033] In an embodiment, the step of performing page rendering on the application assembly page based on the to-be-rendered menu object comprises:

[0034] determine a rendering mode corresponding to the to-be-rendered menu object;

[0035] perform page rendering on the application assembly page based on the rendering mode and the to-be-rendered menu object.

[0036] In addition, to achieve the above object, the present application further provides an application assembly device, which comprises:

[0037] an application architecture construction module, configured to construct a main application architecture based on layout position information and visibility information of a to-be-laid-out functional component, the visibility information being used to represent whether the to-be-laid-out functional component is displayed;

[0038] an information binding module, configured to acquire menu configuration data and bind the menu configuration data with the main application architecture;

[0039] an information determination module, configured to, when the binding is completed, receive an application assembly request triggered based on an application assembly page, and determine functional menu configuration information of a to-be-assembled application based on the application assembly request;

[0040] an application assembly module, configured to perform information configuration on the to-be-assembled application based on the functional menu configuration information, and generate an assembled application.

[0041] In addition, to achieve the above object, the application further provides an application assembly device, which comprises a memory, a processor and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the application assembly method as described above.

[0042] In addition, to achieve the above object, the application further provides a storage medium, which is a computer readable storage medium, and the storage medium stores a computer program, and the computer program is executed by a processor to implement the steps of the application assembly method as described above.

[0043] The application provides an application assembly method, and discloses constructing a main application architecture based on layout position information and display / hidden information of a to-be-laid-out functional component, the display / hidden information being used to represent whether the to-be-laid-out functional component is displayed; obtaining menu configuration data, and binding the menu configuration data with the main application architecture; when the binding is completed, receiving an application assembly request triggered based on an application assembly page, and determining functional menu configuration information of a to-be-assembled application based on the application assembly request; performing information configuration on the to-be-assembled application based on the functional menu configuration information, and generating an assembled application. Compared with the micro-frontend technology used in the prior art to build a large financial Web application, the prior art usually pays more attention to the generality of the technology, and lacks in-depth design of the financial business architecture, resulting in low flexibility and efficiency of application assembly. Since the application can perform information configuration on the to-be-assembled application based on the functional menu configuration information of the to-be-assembled application when the binding of the menu configuration data and the main application architecture is completed, and generate an assembled application, the technical problem that the prior art lacks in-depth design of the business architecture, resulting in low flexibility and efficiency of application assembly, is solved. BRIEF DESCRIPTION OF DRAWINGS

[0044] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and serve to explain the principles of the application, together with the description.

[0045] In order to more clearly illustrate the technical solutions in the embodiments of the application or the prior art, the accompanying drawings needed to be used in the embodiments or prior art description will be briefly introduced as follows. Obviously, for those skilled in the field, the other drawings can also be obtained based on these drawings without any creative work.

[0046] Figure 1 A flowchart is provided for the application assembly method embodiment one of the application;

[0047] Figure 2 A flowchart is provided for the application assembly method embodiment two of the application;

[0048] Figure 3 A flowchart provided for application of assembly method embodiment three of the present application;

[0049] Figure 4 An example diagram of the application of the assembly method of the present application;

[0050] Figure 5 A display diagram of the completed function menu in the assembly method of the present application;

[0051] Figure 6 A module structure diagram of the assembly device applied in the embodiment of the present application;

[0052] Figure 7 A device structure diagram of the hardware running environment involved in the assembly method applied in the embodiment of the present application.

[0053] The object implementation, functional features and advantages of the present application will be further described with reference to the embodiments and the accompanying drawings. DETAILED DESCRIPTION

[0054] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application, and are not used to limit the present application.

[0055] In order to better understand the technical solutions of the present application, the specific embodiments will be described in detail below with reference to the drawings and the specific embodiments.

[0056] The main solution of the embodiment of the present application is: constructing a main application architecture based on the layout position information and the display information of the function component to be laid out, the display information being used to represent whether the function component to be laid out is displayed; obtaining menu configuration data, and binding the menu configuration data with the main application architecture; when the binding is completed, receiving an application assembly request triggered based on an application assembly page, and determining function menu configuration information of the application to be assembled based on the application assembly request; configuring the application to be assembled based on the function menu configuration information, and generating an assembled application.

[0057] In the prior art, micro-frontend technology is usually used to build large financial Web applications, which usually pays more attention to the generality of technology, and lacks in-depth design of financial business architecture, resulting in low flexibility and efficiency of application assembly.

[0058] The present application provides a solution, which can configure the application to be assembled based on the function menu configuration information of the application to be assembled when the menu configuration data is bound with the main application architecture, and generate an assembled application, thereby solving the technical problem that the application assembly method in the prior art lacks in-depth design of business architecture, resulting in low flexibility and efficiency of application assembly.

[0059] It should be noted that the execution subject of the embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, or an electronic device capable of realizing the above functions, an application assembly device, or an application assembly system containing the application assembly device. The following takes the application assembly system as an example (hereinafter referred to as the system) to describe the embodiment and the following embodiments.

[0060] Based on this, the application embodiment provides an application assembly method, which refers to Figure 1 , Figure 1 The flowchart of the first embodiment of the application assembly method is shown in the figure.

[0061] In the embodiment, the application assembly method includes steps S10-S40:

[0062] Step S10: Constructing a main application architecture based on layout position information and visibility information corresponding to a to-be-laid-out functional component, the visibility information being used to represent whether the to-be-laid-out functional component is displayed.

[0063] It should be understood that the to-be-laid-out functional component can be each functional module in the main application that can be dynamically configured and replaced. In the embodiment, the to-be-laid-out functional component can include but is not limited to a navigation bar, a left menu, a Tab tab, a content area, etc. These components are constituent parts of the main application, and can be flexibly configured and replaced according to different business requirements.

[0064] It can be understood that the layout position information can be the specific position of the to-be-laid-out functional component in the main application. In actual application, the layout position information defines the placement position of the component on the page, for example, the top navigation bar is located at the top of the page, the left menu is located at the left side of the page, the Tab tab is located above the content area, and the content area is located at the center of the page, etc. The embodiment does not limit the specific position of the to-be-laid-out functional component. In the embodiment, the layout position information corresponding to the to-be-laid-out functional component can be defined by a configuration file or a database table, so as to be dynamically loaded and configured at runtime.

[0065] It should be noted that the visibility information can be information used to represent the display state of the to-be-laid-out functional component on the page. The display state can include a display state and a hidden state, wherein the display state means that the component is visible in the page, and the hidden state means that the component is invisible in the page. In actual application, the system can define the visibility information by a configuration file or a database table, so as to dynamically control the display state of the component at runtime in the future. In addition, in order to improve the flexibility of application assembly, the embodiment can configure a visibility control switch for the functional component of each layout position in the main application architecture, and the visibility control switch can be used to individually control the visibility information of the functional component.

[0066] It should be noted that the above main application architecture can be a top-level application structure for managing and coordinating various sub-applications (or functional modules) under the micro-frontend technology framework. In actual application, the main application architecture is the core framework of the entire large application, responsible for providing unified layout, navigation, permission management, and page rendering functions. The main application architecture is the base part in the micro-frontend technology, which can provide a running environment and an interaction interface for the sub-application, and the application assembly can be implemented in the main application architecture in the embodiment.

[0067] In a specific implementation, the system can first define the layout position information of each to-be-laid-out functional component in the configuration file or database of the main application. Subsequently, in the initialization stage of the main application, the layout position information and the display / hidden information in the configuration file or database can be used to dynamically load and configure each to-be-laid-out functional component, so as to construct the main application architecture.

[0068] Further, the step S10 includes: determining a component replacement mode and a component control mode corresponding to the to-be-laid-out functional component according to a business requirement, the to-be-laid-out functional component including a navigation bar, a left menu, and a tab page; determining layout position information and display / hidden information corresponding to the to-be-laid-out functional component; and constructing the main application architecture based on the layout position information, the display / hidden information, the component replacement mode, and the component control mode.

[0069] It should be noted that the above component replacement mode can be a mode used for dynamically replacing a functional component at a layout position in the main application architecture. In the embodiment, the system can internally build some common layout effects in the main application architecture, and define that only a placeholder of a component is performed at a layout position of the main application architecture, so that the position of the component can be flexibly replaced subsequently, that is, the main application architecture can be replaced by using a flexible replacement mode. In actual application, it is assumed that there are two layout positions of a top navigation bar and a left menu in the main application architecture, for example: in a financial business scenario A, the top navigation bar can need to display three menu items of “account overview”, “transaction record”, and “settings”; in a financial business scenario B, the top navigation bar can need to display three menu items of “market situation”, “investment portfolio”, and “message center”, if the components at these positions need to be replaced in different business scenarios, then the component replacement mode can be used to dynamically load different navigation bar components at runtime, without the need to modify the code of the main application.

[0070] In a specific implementation, the system can determine the functions that the functional components at different layout positions in the main application architecture need to implement according to business requirements in different business scenarios, for example, the top navigation bar can need to display different menu items, the left menu can need to dynamically adjust the menu items according to user permissions, the content area can need to dynamically load different page contents according to the user's operation history, etc. Then, the system can define the component replacement mode and the component control mode corresponding to the functional components to be laid out, and finally construct the main application architecture based on the layout position information, the display / hidden information, the component replacement mode and the component control mode corresponding to the functional components to be laid out, so that the subsequent main application can dynamically load and replace the functional components according to the layout position information, the display / hidden information, the component replacement mode and the component control mode corresponding to the functional components when initializing or running, thereby improving the flexibility and scalability of the main application architecture, and further meeting the complex application requirements of large enterprises such as financial institutions.

[0071] It should be noted that the above component control mode can be a mode adopted to dynamically control the display, hiding, interaction behavior, etc. of the functional components at a certain layout position in the main application architecture. In this embodiment, this mechanism allows the behavior of the functional components to be dynamically adjusted according to the user's permissions, operation behavior or business logic in different business scenarios.

[0072] Step S20: Obtain menu configuration data and bind the menu configuration data with the main application architecture.

[0073] It should be understood that the above menu configuration data can be a collection of data for describing the application navigation structure and page path, for example, the identification of the menu item (such as applicationPath), the path of the menu item (such as webUrl), the navigation mode, the permission information, etc. The present embodiment does not limit this, wherein the identification of the menu item can be identification information for identifying the functional module or application to which the menu item belongs; the path of the menu item can be information for positioning to a specific page or function; the navigation mode can be information defining the navigation mode of the menu item in the page (such as top navigation, left menu, etc.); the permission information can be information representing whether the user has the permission to access the menu item. In actual application, the menu configuration data is usually stored in a configuration file or a database, and the main application can load and parse these menu configuration data when starting, and then dynamically generate and control the user interface according to the data content parsed.

[0074] In the embodiment, the binding of the menu configuration data and the main application architecture can be a process of associating the defined menu data structure with the running logic and layout of the main application, which can enable the main application to dynamically generate navigation menus, control page layout, and perform permission verification according to the menu configuration data, and implement corresponding functions, thereby improving the flexibility and scalability of the application, facilitating management and maintenance.

[0075] Step S30: When the binding is completed, an application assembly request triggered based on an application assembly page is received, and function menu configuration information of an application to be assembled is determined based on the application assembly request.

[0076] It should be noted that the application assembly page described above can be a user interface for application assembly and configuration. In the embodiment, the application assembly page can provide functions such as selecting a function menu, configuring a function menu, and publishing an application.

[0077] It can be understood that the application assembly request described above can be a request of assembling an application initiated by a user through an application assembly page. In actual application, the application assembly request can include information such as a menu selected by the user, function menu configuration information, and an application to be assembled. The menu selected by the user can be a function menu item selected by the user on the application assembly page and needed to be assembled. The function menu configuration information can be detailed configuration information of the selected menu item, such as an identifier of the menu item, a path of the menu item, a navigation mode, a display state, a permission, and the like, which can be dynamically configured and generated according to the application assembly request. The application to be assembled can be a new application or an industry version that the user hopes to assemble, which can be composed of menu items selected and configured by the user through the application assembly page.

[0078] In actual application, the user selects a function menu item needed to be assembled and configures it through the application assembly page. For example, the user selects three menu items of “account management”, “fund transfer”, and “report query”, and configures “account management” as a top navigation, “fund transfer” and “report query” as a left menu, and sets “account management” and “fund transfer” to be visible to all users, and “report query” to be visible only to administrators. After the configuration is completed, the user can click a “publish” button. At this time, the system can generate an application assembly request in the application assembly page, which can include the menu items and configuration information selected by the user.

[0079] Further, the step S30 comprises: determining the identification information corresponding to the menu object in the main application architecture according to the menu configuration data when the binding is completed; obtaining the resource function attribution identifier and the resource path identifier corresponding to the menu object according to the identification information; generating an application assembly page based on the menu object, the resource function attribution identifier and the resource path identifier; and receiving an application assembly request triggered based on the application assembly page.

[0080] It should be understood that the menu object described above can be a data structure used to describe menu items in the main application architecture; correspondingly, the identification information described above can be an attribute or field used to uniquely identify each menu item. In this embodiment, the system can parse the menu configuration data to determine the identification information of each menu object in the main application architecture.

[0081] It should be noted that the resource function attribution identifier described above can be a unique identifier used to identify the function module or application to which the menu item belongs. In this embodiment, the resource function attribution identifier belongs to the function attribution of the resource, is used by the business, and meets the custom demand. It can be used to distinguish different function modules or sub-applications, and ensure that each menu object in the main application architecture can be correctly mapped to the function module to which it belongs.

[0082] It can be understood that the resource path identifier described above can be a path used to locate a specific page or function. In actual application, the resource path identifier is usually a URL used to navigate to a specific page or function. It belongs to a specific resource path and is defined by the developer. By combining the resource function attribution identifier and the resource path identifier, differential page display can be achieved.

[0083] In this embodiment, the system can determine the resource function attribution identifier and the resource path identifier corresponding to all menu objects in the main application architecture according to the menu configuration data, and dynamically generate an application assembly page based on these menu objects and their respective resource function attribution identifiers and resource path identifiers.

[0084] Step S40: information configuration is performed on the application to be assembled based on the function menu configuration information, and an assembled application is generated.

[0085] In specific implementation, after receiving the application assembly request, the system can parse the application assembly request, obtain all applications to be assembled and the function menu configuration information corresponding to these applications to be assembled, and then configure the menu items in the application to be assembled according to the function menu configuration information, such as setting the navigation mode, the display state, the permission, etc., and generate the assembled application when the configuration is completed.

[0086] The embodiment provides an application assembly method. The method discloses constructing a main application framework based on layout position information and display / hidden information of a functional component to be laid out, the display / hidden information is used to represent whether the functional component to be laid out is displayed; menu configuration data is acquired, and the menu configuration data is bound with the main application framework; when the binding is completed, an application assembly request triggered based on an application assembly page is received, and functional menu configuration information of an application to be assembled is determined based on the application assembly request; information configuration is performed on the application to be assembled based on the functional menu configuration information, and an assembled application is generated. Compared with the micro-frontend technology used to build a large financial Web application in the prior art, the prior art usually pays more attention to the generality of the technology, and lacks in-depth design of a financial business framework, so that flexibility and efficiency of application assembly are not high. Since the embodiment can perform information configuration on the application to be assembled based on functional menu configuration information of the application to be assembled when the menu configuration data is bound with the main application framework, and generate the assembled application, the technical problem that the application assembly method in the prior art lacks in-depth design of a business framework, so that flexibility and efficiency of application assembly are not high, is solved.

[0087] Based on the first embodiment of the application, in the second embodiment of the application, the same or similar contents as the above-mentioned first embodiment can be referred to the above introduction, and will not be described in detail. On this basis, please refer to Figure 2 , Figure 2 The flowchart provided by the second embodiment of the application assembly method.

[0088] In the embodiment, after step S40, the method further includes steps S501-S504:

[0089] Step S501: generating an application industry version based on the assembled application and a target functional component in the main application framework, and performing hierarchical linkage of the application industry version through association of a top navigation and a left menu in the main application framework.

[0090] It should be noted that the above-mentioned application industry version can be an application version customized according to specific industry or business demand. In the embodiment, the application industry version can meet the individualized demand of a specific industry or business scenario by selecting and configuring specific functional menu items. The above-mentioned target functional component can be a functional component selected and configured according to business demand in the process of assembling the application, and these components will be integrated into the final application industry version. In actual application, the system can determine the components in the default application or the assembled application as the target functional component, and realize the assembly of the industry version through the target functional component and the top navigation.

[0091] Step S502: when an application control request triggered by a user based on the application industry version is received, determining a target control application according to the application control request.

[0092] It should be understood that the above application control request can be a request for dynamically adjusting or controlling the behavior of an application, such as display, hiding, permission adjustment, or other runtime configuration changes of a functional component in the application; accordingly, the above target control application can be an application that needs to be adjusted in behavior.

[0093] Step S503: Determine whether the target control application has a top menu.

[0094] Step S504: If so, adjust the level of the target left menu corresponding to the target control application.

[0095] In this embodiment, the industry version defaults to top navigation, and the application is on the navigation bar. When an application is selected, the left menu is the function menu under it. For the assembled application, this embodiment supports level linkage of the top navigation and the left menu, that is, dual-mode switching of the left navigation and the top navigation and the left navigation. For example, if the target control application has a top menu, the left menu will be downgraded to the second-level menu of the next-level menu (at the top) of the application (at the left).

[0096] In this embodiment, the application industry version based on the target functional component in the assembled application and the main application architecture is disclosed. The application industry version performs level linkage by associating the top navigation and the left menu in the main application architecture. When an application control request triggered by a user based on the application industry version is received, the target control application is determined according to the application control request. It is determined whether the target control application has a top menu. If so, the level of the target left menu corresponding to the target control application is adjusted. Since the application industry version in this embodiment can perform level linkage by associating the top navigation and the left menu in the main application architecture, flexible control of the application can be achieved, personalized needs of different users and business scenarios can be met, and the flexibility and scalability of the application are improved.

[0097] Based on the first and / or second embodiments of the present application, in the third embodiment of the present application, the same or similar contents as the above embodiments can be referred to the above introduction, and will not be described hereinafter. On this basis, please refer to Figure 3 , Figure 3 The flowchart provided for the third embodiment of the application assembly method is shown.

[0098] In this embodiment, after step S40, the method further includes steps S601-S604:

[0099] Step S601: When the to-be-identified URL is received, the to-be-identified URL is parsed.

[0100] It can be understood that the above-mentioned to-be-identified URL can be a complete URL address input by a user in a browser or accessed through a link, which can include a protocol, a domain name, a path, and the like. Referring to Figure 4 , Figure 4 is an example diagram of applying the assembly method to a URL. As shown in Figure 4 , the to-be-identified URL can be https: / / xft.cmbchina.com / psn / # / hrmapp / staff-roster, and the like, which is not described one by one here.

[0101] Step S602: determining a to-be-identified classification identifier and a to-be-identified resource path identifier corresponding to the to-be-identified URL according to the analysis result.

[0102] It should be understood that the above-mentioned to-be-identified classification identifier can be information used for identifying a function module or an application to which a request belongs and parsed from the to-be-identified URL; and the above-mentioned to-be-identified resource path identifier can be information used for locating to a specific page or function and parsed from the to-be-identified URL.

[0103] In actual application, a same URL resource position can belong to an application and an industry version, and therefore, the embodiment can perform normalized definition on a complete URL, as shown in Figure 4 , the classification identifier of the URL corresponds to the applicationPath on the menu (the application is also a special menu), and the resource path identifier is divided into two parts, in which xxxapp is a sub-application identifier, and the path (such as staff-roster) behind is a sub-application internal route, and the two parts combine to form a complete page path identifier.

[0104] Step S603: determining a to-be-rendered menu object in the application assembly page based on the to-be-identified classification identifier and the to-be-identified resource path identifier.

[0105] It can be understood that the above-mentioned to-be-rendered menu object can be a menu object that needs to be rendered in the application assembly page. In the embodiment, the system can extract the to-be-identified classification identifier (applicationPath) and the to-be-identified resource path identifier (webUrl) after analyzing the URL of the request, then can find a matched menu object in the menu configuration data according to the extracted applicationPath and webUrl, and determine the menu object matched successfully as the to-be-rendered menu object.

[0106] Step S604: performing page rendering on the application assembly page based on the to-be-rendered menu object.

[0107] Further, the step S604 comprises: determining the navigation mode corresponding to the to-be-rendered menu object and target visibility information; if the navigation mode is a left navigation mode, displaying the to-be-rendered menu object in the left menu of the application assembly page based on the target visibility information; if the navigation mode is a double navigation mode, displaying the to-be-rendered menu object in the left menu and the top navigation bar of the application assembly page based on the target visibility information.

[0108] It should be noted that the navigation mode described above can be the display position and manner of the menu item in the user interface. In the embodiment, the navigation mode can include a top navigation mode, a left navigation mode and a double navigation mode. The top navigation mode can be a mode in which the menu item is displayed at the top of the page. The left navigation mode can be a mode in which the menu item is displayed at the left of the page. The double navigation mode can be a mode in which the menu item is displayed at the top and the left of the page.

[0109] It should be understood that the target visibility information described above can be information for representing whether the menu item is displayed in the user interface, which can be used to control the visibility of the menu item.

[0110] In the embodiment, if the navigation mode corresponding to the to-be-rendered menu object is a left navigation mode, the to-be-rendered menu object can be controlled to be displayed at the left of the user page. If the navigation mode corresponding to the to-be-rendered menu object is a double navigation mode, the to-be-rendered menu object can be controlled to be displayed at the left and the top of the user page according to business requirements.

[0111] Further, the step S604 comprises: determining the rendering mode corresponding to the to-be-rendered menu object; and performing page rendering on the application assembly page based on the rendering mode and the to-be-rendered menu object.

[0112] It should be noted that the rendering mode described above can be a strategy adopted for generating and displaying a page. In the embodiment, the rendering mode can include a pre-rendering mode and a multi-instance mode. The pre-rendering mode can be a rendering mode in which the content of a sub-application or a page is rendered in advance before global data loading is completed. The pre-rendering mode can quickly display the basic structure of the page, improve user experience and reduce waiting time. The multi-instance mode can be a rendering mode in which multiple sub-applications or page instances exist simultaneously and quickly respond when the user switches. The multi-instance mode can improve user experience and reduce page loading time.

[0113] In this embodiment, if the rendering mode corresponding to the menu object to be rendered is the pre-rendering mode, the system can render the basic structure of the page in advance according to the menu object to be rendered, and then refresh the page status after the global data loading is completed; if the rendering mode corresponding to the menu object to be rendered is the multi-instance mode, the system can initialize multiple sub-applications or page instances according to the menu object to be rendered, and quickly load and display them when the user switches.

[0114] In practical applications, refer to Figure 5 , Figure 5 This is a diagram showing the function menu assembled in the assembly method of this application. Figure 5 As shown, the main application architecture can include multiple applications, such as the existing individual tax management, employee management, intelligent expense control, corporate welfare and other applications of Xinfutong. In this embodiment, after generating the assembled application, by selecting the default application or the assembled application, combined with the top navigation, the industry version assembly can be completed, such as assembling Figure 5 The employee management applications (including rosters, archives, points management, financial processing, etc.) and expense control applications (including financial management, archives, accounting, data management, etc.) are finally generated into exclusive versions that meet the personalized characteristics of different customers, such as the human resources industry version or the XX industry version, so as to meet the precise marketing of operations and the personalized needs of customers, thereby improving the customer experience.

[0115] In this embodiment, it is disclosed that when a URL to be identified is received, the URL to be identified is parsed; the category identifier to be identified and the resource path identifier to be identified corresponding to the URL to be identified are determined based on the parsing result; the menu object to be rendered in the application assembly page is determined based on the category identifier to be identified and the resource path identifier to be identified; and the application assembly page is rendered based on the menu object to be rendered; since this embodiment can determine the menu object to be rendered in the application assembly page based on the category identifier to be identified and the resource path identifier to be identified corresponding to the URL to be identified, and perform page rendering based on the menu object to be rendered, the menu object to be rendered can be accurately determined by identifying the complete URL, thereby achieving accurate page rendering.

[0116] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the assembly method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0117] This application also provides an application assembly device, please refer to Figure 6 , the application assembly device includes:

[0118] The application architecture construction module 10 is configured to construct a main application architecture based on layout position information of the functional components to be laid out and display / hidden information, the display / hidden information being used to represent whether the functional components to be laid out are displayed.

[0119] The information binding module 20 is configured to acquire menu configuration data and bind the menu configuration data with the main application architecture.

[0120] The information determination module 30 is configured to, when the binding is completed, receive an application assembly request triggered based on an application assembly page, and determine functional menu configuration information of an application to be assembled based on the application assembly request.

[0121] The application assembly module 40 is configured to perform information configuration on the application to be assembled based on the functional menu configuration information, and generate an assembled application.

[0122] The application assembly apparatus provided in the present application adopts the application assembly method in the above embodiments, and can solve the technical problem that the application assembly method in the prior art lacks in-depth design of a service architecture, resulting in low flexibility and efficiency of application assembly. Compared with the prior art, the application assembly apparatus provided in the present application has the same beneficial effects as the application assembly method provided in the above embodiments, and other technical features in the application assembly apparatus are the same as the features disclosed in the above embodiments, which will not be repeated here.

[0123] The present application provides an application assembly device, the application assembly device comprising: at least one processor; and a memory in communication connection with the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the application assembly method in the above embodiment one.

[0124] Reference will now be made to the following description Figure 7 which shows a structural schematic diagram of an application assembly device suitable for implementing the embodiments of the present application. The application assembly device in the embodiments of the present application can include, but is not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (Personal Digital Assistant), PADs (Portable Application Description), PMPs (Portable Media Player), vehicle-mounted terminals (for example, vehicle-mounted navigation terminals), and the like, and fixed terminals such as digital TVs, desktop computers, and the like. Figure 7 The application assembly device shown is merely an example, and should not bring any limitation to the functions and use range of the embodiments of the present application.

[0125] AsFigure 7 As shown, the application assembly device can include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.) that can perform various appropriate actions and processes according to programs stored in a read-only memory 1002 or loaded from a storage device 1003 into a random access memory 1004. Various programs and data required for the operation of the application assembly device are also stored in the random access memory 1004. The processing device 1001, the read-only memory 1002, and the random access memory 1004 are connected to each other by a bus 1005. An input / output interface 1006 is also connected to the bus. Generally, the following systems can be connected to the input / output interface 1006: input devices 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; the storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the application assembly device to communicate with other devices wirelessly or by wire to exchange data. Although the application assembly device with various systems is shown in the figure, it should be understood that all the shown systems are not required to be implemented or possessed. More or fewer systems can be alternatively implemented or possessed.

[0126] In particular, according to the embodiments disclosed in the present application, the processes described above with reference to the flowcharts can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product comprising a computer program carried on a computer readable medium, the computer program containing program codes for executing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network through the communication device, or installed from the storage device 1003, or installed from the read-only memory 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the methods of the embodiments disclosed in the present application are performed.

[0127] The application assembly device provided by the present application adopts the application assembly method in the above-mentioned embodiments, and can solve the technical problems of application assembly. Compared with the prior art, the application assembly device provided by the present application has the same beneficial effects as the application assembly method provided by the above-mentioned embodiments, and other technical features in the application assembly device are the same as the features disclosed in the previous embodiment method, which will not be described here.

[0128] It should be understood that parts of the present application can be realized by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0129] The above merely provides the specific implementation of the present application, but the protection scope of the present application is not limited to this. Any person skilled in the art can easily think of the changes or replacements within the technical range disclosed by the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

[0130] The present application provides a computer readable storage medium having computer readable program instructions (i.e. computer programs) stored thereon, which are used to execute the application assembly method in the above embodiments.

[0131] The computer readable storage medium provided by the present application may, for example, be a U disk, but is not limited to an electric, magnetic, optical, electromagnetic, infrared, or semiconductor system or device, or any combination of the above. More specific examples of the computer readable storage medium can include, but are not limited to, an electric connection with one or more conductive wires, a portable computer disk, a hard disk, a random access memory (RAM), a read only memory (ROM), an erasable programmable read only memory (EPROM or flash memory), an optical fiber, a portable compact disk read only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present embodiment, the computer readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system or device. The program code contained on the computer readable storage medium can be transmitted by any suitable medium, including but not limited to an electric wire, an optical cable, an RF (Radio Frequency), etc., or any suitable combination of the above.

[0132] The above computer readable storage medium can be contained in the application assembly device; or can exist separately without being assembled into the application assembly device.

[0133] The computer readable storage medium described above carries one or more programs, when the one or more programs are executed by the application assembly device, cause the application assembly device to: construct a main application architecture based on layout position information corresponding to the functional component to be laid out and display information, the display information being used to represent whether the functional component to be laid out is displayed; obtain menu configuration data, and bind the menu configuration data with the main application architecture; when the binding is completed, receive an application assembly request triggered based on the application assembly page, and determine functional menu configuration information of the application to be assembled based on the application assembly request; perform information configuration on the application to be assembled based on the functional menu configuration information, and generate an assembled application.

[0134] Computer program code for carrying out operations of the present application can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0135] The computer program code can also be loaded onto a computer or other programmable information processing apparatus to cause a series of operations to be performed on the computer or other programmable information processing apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable information processing apparatus implement the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0136] The modules described in the embodiments of the present application can be implemented in the form of software or in the form of hardware. In some cases, the name of the module does not constitute a limitation on the module itself.

[0137] The computer readable storage medium provided by the present application is a computer readable storage medium, which stores computer readable program instructions (i.e. computer programs) for executing the application assembly method described above, and can solve the technical problem that the application assembly method in the prior art lacks in-depth design of the business architecture, resulting in low flexibility and efficiency of application assembly. Compared with the prior art, the beneficial effects of the computer readable storage medium provided by the present application are the same as those of the application assembly method provided by the above-mentioned embodiments, and will not be repeated here.

[0138] The above only describes some embodiments of the present application, and does not limit the patent scope of the present application. Any equivalent structural transformation, direct / indirect application in other related technical fields based on the technical concept of the present application, and the contents of the present application specification and drawings are included in the patent protection scope of the present application.

Claims

1. An application assembly method, characterized in that: The method includes: Building a main application architecture based on the layout position information and visibility information corresponding to the functional components to be laid out, wherein the visibility information is used to indicate whether the functional components to be laid out are displayed; Obtaining menu configuration data, and binding the menu configuration data to the main application architecture; When the binding is completed, receiving an application assembly request triggered based on the application assembly page, and determining function menu configuration information of the application to be assembled based on the application assembly request; The application to be assembled is configured with information based on the function menu configuration information to generate an assembled application.

2. The method according to claim 1, wherein The step of constructing the main application architecture based on the layout position information and explicit and implicit information corresponding to the functional components to be laid out includes: Determine component replacement methods and component control methods corresponding to the functional components to be laid out according to business needs, wherein the functional components to be laid out include a navigation bar, a left menu, and a tab page; Determine the layout position information and visibility information corresponding to the functional components to be laid out; A main application architecture is constructed based on the layout position information, the visibility information, the component replacement method and the component control method.

3. The method according to claim 1, wherein The step of receiving an application assembly request triggered by the application assembly page when the binding is completed includes: When the binding is completed, determining the identification information corresponding to the menu object in the main application architecture according to the menu configuration data; Acquire the resource function attribution identifier and resource path identifier corresponding to the menu object according to the identifier information; Generate an application assembly page based on the menu object, the resource function attribution identifier and the resource path identifier; An application assembly request triggered based on the application assembly page is received.

4. The method according to any one of claims 1 to 3, characterized in that After the step of configuring information of the application to be assembled based on the function menu configuration information to generate an assembled application, the method further includes: Generate an application industry version based on the assembled application and the target functional components in the main application architecture, wherein the application industry version is hierarchically linked by associating the top navigation and the left menu in the main application architecture; Upon receiving an application control request triggered by a user based on the application industry version, determining a target control application according to the application control request; Determine whether a top menu exists for the target control application; If so, the target left menu corresponding to the target control application is hierarchically adjusted.

5. The method according to claim 4, wherein After the step of generating an application industry version based on the assembled application and the target functional components in the main application architecture, the method further includes: When receiving a URL to be identified, parsing the URL to be identified; Determine the category identifier to be identified and the resource path identifier to be identified corresponding to the URL to be identified according to the analysis result; Determine the menu object to be rendered in the application assembly page based on the category identifier to be identified and the resource path identifier to be identified; The application assembly page is rendered based on the menu object to be rendered.

6. The method according to claim 5, wherein The step of rendering the application assembly page based on the menu object to be rendered includes: Determine the navigation mode and target visibility information corresponding to the menu object to be rendered; If the navigation mode is a left navigation mode, displaying the menu object to be rendered in the left menu of the application assembly page based on the target visibility information; If the navigation mode is a dual navigation mode, the menu object to be rendered is displayed in the left menu and the top navigation bar of the application assembly page based on the target display and hiding information.

7. The method according to claim 5, wherein The step of rendering the application assembly page based on the menu object to be rendered includes: Determine the rendering mode corresponding to the menu object to be rendered; The application assembly page is rendered based on the rendering mode and the menu object to be rendered.

8. An application assembly device, characterized in that: The device comprises: An application architecture construction module, configured to construct a main application architecture based on layout position information and visibility information corresponding to the functional components to be laid out, wherein the visibility information is used to indicate whether the functional components to be laid out are displayed; An information binding module, configured to obtain menu configuration data and bind the menu configuration data to the main application architecture; An information determination module is configured to receive an application assembly request triggered based on an application assembly page when binding is completed, and determine function menu configuration information of the application to be assembled based on the application assembly request; The application assembly module is used to configure information of the application to be assembled based on the function menu configuration information to generate an assembled application.

9. An application assembly device, characterized in that: The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the application assembly method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the application assembly method according to any one of claims 1 to 7 are implemented.

Images