CN106201506A - Function assembly and customization method based on multi-tenant mode - Google Patents

Abstract

The invention discloses a kind of functional assembly based on many tenants pattern and method for customizing, comprise the following steps: S1: the allomeric function of intended application is split as atomic function by metadata configurations end, and atomic function is configured to functional packet and includes the sale bag of one or more functional packet；The data being uploaded to application management platform in S1 are resolved by S2: application management platform；S3: tenant's end is sold bag by application management platform building, is distributed one or more functional packet to user；S4: user side obtains the menu metadata of the current request page and page elements metadata from application management platform, and shows menu and the page elements of functional packet Atom function association that user side is distributed to be obtained.It is an object of the invention to provide a kind of general functional assembly method, also disclose a kind of functional assembly based on many tenants pattern and custom-built system simultaneously.

Description

Function assembly and customization method based on multi-tenant mode

technical field

The present invention relates to the field of SaaS application, in particular to a function assembly and customization method and system based on a multi-tenant model.

Background technique

The SaaS model is a completely innovative software application model currently emerging. Usually, the real SaaS application architecture should meet the requirements of configurable and high-performance multi-tenant architecture to effectively reduce the hardware cost and maintenance cost of SaaS applications. Configurability makes SaaS applications more versatile, and customers can meet their individual needs through simple configuration. In an enterprise SaaS environment, a tenant can correspond to a specific organization, and the organization uses the service through a customized application, and is not the owner of the application; the organization is associated with a group of employee users, and the employee user is the user of the SaaS application. Tenants order on-demand according to the configurable features of the SaaS application to obtain the software services provided by the SaaS application; and SaaS provides each tenant with a copy of the application to isolate the tenant's data. SaaS applications are more broadly defined as instrumental SaaS, such as video conference rental, corporate mailboxes and other major SaaS applications.

Contents of the invention

The problem to be solved by the present invention is to propose a function assembly and customization method based on a multi-tenant model, which is suitable for products expected to be transformed into SaaS multi-tenant applications. The invention proposes an XML-based functional assembly specification, decomposes system functions of target applications according to the specification, combines atomic functions into function packages, and packages the function packages into sales packages that are convenient for tenants to customize. After the tenant customizes the functions according to their needs, they can reassign the functions to employee users with specific roles according to their own needs. The invention also discloses a multi-tenant mode-based function assembly and customization system.

The specific technical solution of the present invention is: a function assembly and customization method based on a multi-tenant mode, the method includes a metadata configuration terminal, an application management platform, a tenant terminal and a user terminal, which includes the following steps:

S1: The metadata configuration end splits the overall function of the target application into atomic functions, and configures the atomic functions as a function package and a sales package including one or more function packages; Functions, associations between atomic functions and menu metadata and page element metadata, function packages and sales packages are uploaded to the application management platform;

S2: The application management platform analyzes the data uploaded to the application management platform in S1;

S3: The tenant customizes the sales package through the application management platform, and assigns one or more function packages to the user;

S4: The user terminal obtains the menu metadata and page element metadata of the currently requested page from the application management platform, and displays the menu and page elements associated with the atomic functions in the function package allocated by the user terminal.

In the above-mentioned function assembly and customization method based on the multi-tenant mode, the S1 specifically includes:

S11: Split the overall function of the target application into atomic functions at the metadata configuration end, and identify menu metadata and page element metadata;

S12: Define the correlation between atomic functions, atomic functions and menu metadata, atomic functions and page element metadata at the metadata configuration side;

S13: At the metadata configuration end, configure the atomic function as a function package and a sales package including one or more function packages; combine the atomic function, menu metadata and page element metadata in S11, the association in S12, and S13 Upload the function package and sales package in the application management platform.

In the above-mentioned function assembly and customization method based on the multi-tenant mode, the S4 specifically includes:

S41: After the client logs in to the target application, it sends an identity verification connection request to the application management platform, and verifies from the application management platform;

S42: Obtain an access token from the application management platform after the verification is passed;

S43: Obtain menu metadata and page element metadata of the currently requested page from the application management platform according to the access token;

S44: When each page is displayed by the target application, display menus and page elements associated with atomic functions assigned by the tenant, and hide menus and page elements that are not associated.

In the above multi-tenant-based function assembly and customization method, the menu metadata, page element metadata, function package, and sales package are all defined in a metadata specification file.

In the above method of function assembly and customization based on the multi-tenant model, the atomic functions contained in the function package allocated by the client and the metadata of the menu and page elements associated with the atomic functions are marked as customized, and include Keyword for the associated atomic function.

In the above-mentioned function assembly and customization method based on multi-tenant mode, the menu metadata includes menu id, menu name, menu path, menu identifier, menu identifier value, parent menu id;

The page element metadata includes: page element id, page element name, page element path, page element identifier, page element identifier value, built-in menu name, built-in menu path, built-in menu identifier, built-in menu marker value ;

The correlation between atomic functions refers to the dependency relationship between atomic functions.

At the same time, the present invention also discloses a system for realizing the above-mentioned function assembly and customization method based on the multi-tenant mode, including a metadata configuration terminal, an application management platform, a tenant terminal and a user terminal;

The metadata configuration end is used for the configurator to split the overall function of the target application into atomic functions, and configure the atomic functions into function packages and sales packages including one or more function packages; Data, atomic functions, associations between atomic functions and menu metadata and page element metadata, function packages and sales packages are uploaded to the application management platform;

The application management platform is used to analyze the data uploaded by the metadata configuration terminal;

The tenant terminal is used to customize the sales package through the application management platform, and distribute one or more function packages to the user;

The client is used to obtain the menu metadata and page element metadata of the currently requested page from the application management platform, and display the menu and page elements associated with the atomic functions in the function package allocated by the client.

In the above-mentioned functional assembly and customization system based on multi-tenant mode, the application management platform includes:

The metadata analysis sub-module is used to analyze the data uploaded to the application management platform;

The function customization and distribution sub-module is used for the tenant to customize the sales package, and for the tenant to distribute one or more function packages to the user;

The metadata service sub-module is used to send the corresponding menu metadata and page element metadata to the client according to the access token of the client.

In the above-mentioned functional assembly and customization system based on multi-tenant mode, the client includes the following submodules:

The verification sub-module is used to send an identity verification connection request to the application management platform after logging in to the target application, and perform verification from the application management platform. After the identity verification connection request is verified, the returned data is obtained, which is the access token;

The metadata acquisition sub-module is used to acquire the menu metadata and page element metadata of the currently requested page from the application management platform according to the access token;

The display sub-module is used to display the menu and page elements associated with the atomic functions assigned by the tenant when the target application displays each page, and hide the menu and page elements that are not associated.

In the above-mentioned functional assembly and customization system based on the multi-tenant mode, the application management platform further includes:

The data isolation sub-module is used to isolate the data customized by the tenant;

Application management sub-module: used to register tenants and register applications.

Compared with prior art, the beneficial effect of the present invention is:

Versatility; functional assembly specifications and application management platform are suitable for applications developed in different languages.

Reduce the complexity of the target application transformation, thereby reducing the transformation cost and the transformation time period.

Data isolation is mainly the isolation of application data and tenant data of each application.

Loose coupling: Mainly, the target application and metadata analysis, function customization and distribution, tenant customization data isolation, tenant management, metadata service and other modules exist independently. If the target application is bound with the extension module, it can be restored to a non-SaaS application.

Description of drawings

Fig. 1 is the flowchart of embodiment 1 and 2 of the present invention;

Fig. 2 is the flowchart of embodiment 2 of the present invention;

Fig. 3 is the flowchart of embodiment 2 of the present invention;

Fig. 4 is the structural block diagram of embodiment 3 of the present invention;

Fig. 5 is a structural block diagram of Embodiment 4 of the present invention;

Fig. 6 is the flowchart of embodiment 4 of the present invention;

Fig. 7 is the flowchart of embodiment 4 of the present invention;

Fig. 8 is a schematic diagram of Embodiment 4 of the present invention.

detailed description

The technical solutions of the present invention will be further described in detail below in conjunction with specific embodiments, but this does not constitute any limitation to the present invention.

Example 1

As shown in Figure 1, a function assembly and customization method based on multi-tenant mode, the method includes a metadata configuration terminal, an application management platform, a tenant terminal and a user terminal, which includes the following steps:

S1: The metadata configuration end splits the overall function of the target application into atomic functions, and configures the atomic functions as a function package and a sales package including one or more function packages; Functions, associations between atomic functions and menu metadata and page element metadata, function packages and sales packages are uploaded to the application management platform;

S2: The application management platform analyzes the data uploaded to the application management platform in S1;

S3: The tenant customizes the sales package through the application management platform, and assigns one or more function packages to the user;

S4: The user terminal obtains the menu metadata and page element metadata of the currently requested page from the application management platform, and displays the menu and page elements associated with the atomic functions in the function package allocated by the user terminal.

Through the above steps, tenants can freely customize functions, reduce the difficulty of users' transformation of target applications, and the functional assembly specifications and application management platform are suitable for applications developed in different languages.

Example 2:

As shown in Figures 1 to 3, a function assembly and customization method based on a multi-tenant mode, the method includes a metadata configuration terminal, an application management platform, a tenant terminal and a user terminal, which includes the following steps:

S1: The configurator splits the overall function of the target application into atomic functions at the metadata configuration end, and configures the atomic functions into function packages and sales packages including one or more function packages; Data, atomic functions, associations between atomic functions and menu metadata and page element metadata, function packages and sales packages are uploaded to the application management platform;

Specifically, as shown in Figure 2, the step S1 includes the following sub-steps:

S11: Split the overall function of the target application into atomic functions at the metadata configuration end, and identify menu metadata and page element metadata; the metadata configuration end can be a complete set of automatic configuration system, or manual The target application is split.

The menu metadata includes menu id, menu name, menu path, menu identifier, menu identifier value, parent menu id. The goal of the design of the menu metadata assembly specification is to uniquely identify the corresponding menu object through the metadata during the running of the target application.

The page element metadata includes: page element id, page element name, page element path, page element identifier, page element identifier value, built-in menu name, built-in menu path, built-in menu identifier, built-in menu marker value . The goal of the page element metadata assembly specification design is to uniquely identify the corresponding page element object through the metadata during the running of the target application.

There are two purposes for defining menu and page elements through the metadata specification file. One is to identify the menu and page of the target application according to the metadata of the menu and page elements, and the other is to associate the definition of menu and page element metadata with atoms. Features. The metadata referred to in this article refers to the data defined by the metadata specification file.

S12: Define the correlation between atomic functions, atomic functions and menu metadata, atomic functions and page element metadata at the metadata configuration side;

Specifically, before each new page of the target application is displayed, the menu and page element metadata corresponding to the page will be accessed, and the menu and page element metadata associated with the atomic function assigned to the logged-in user will be marked as "already custom made". The main contents of the page element metadata assembly specification are: page id, page path, menu id associated with the page, and page element id associated with the page.

The design concept of atomic functions is "user value driven", and only encapsulates functions that are meaningful to users. Atomic functions are independent of each other, and the collection of atomic functions is the entire function of the target application. The main contents of the atomic function metadata assembly specification are: function id, function name, function description, function keyword, associated menu id, associated page id, and dependent function id. A feature may depend on one feature or set of features, or may not depend on other features.

S13: At the metadata configuration end, configure the atomic function as a function package and a sales package including one or more function packages; combine the atomic function, menu metadata and page element metadata in S11, the association in S12, and S13 Upload the function package and sales package in the application management platform.

The design idea of the function package mainly considers three aspects: user business, atomic functions with dependencies, and atomic functions with dependencies. The sales package is a further encapsulation of the function package, and object-oriented is the tenant. The main contents of the function package/sales package metadata assembly specification are: function package id, function package name, function package description, atomic function id contained in the function package, and function package id contained in the function package. After the tenant customizes the sales package, he can assign the function package contained in the sales package to a certain role, and perform atomic function dependency check on the assignment result.

S2: The application management platform analyzes the data uploaded to the application management platform in S1;

Specifically, the application management platform provides a special parsing class for each type of metadata to parse the data of the specification file.

S3: The tenant customizes the sales package through the application management platform, and assigns one or more function packages to the user;

Specifically, tenants can customize user roles, and assign a certain role to the set of function packages included in the customized sales package as needed. When a role is assigned some or all of the function package permissions, a function check can be performed on the role. The function check will disassemble the assigned function package into a collection of atomic functions and analyze the dependencies between atomic functions. For example, A depends on B; If it is found that some atomic functions with dependencies are not assigned, inform the inspector. The tenant specifies the role for the user through user management, and the user has the function package permissions assigned to the role. The application management platform uses a database to store the id and type of atomic functions or function packages.

S4: The user terminal obtains the menu metadata and page element metadata of the currently requested page from the application management platform, and displays the menu and page elements associated with the atomic functions in the function package allocated by the user terminal.

Specifically, as shown in Figure 3, the S4 includes the following sub-steps:

S41: After the client logs in to the target application, it sends an identity verification connection request to the application management platform, and verifies from the application management platform;

S42: Obtain an access token from the application management platform after the verification is passed;

S43: Obtain menu metadata and page element metadata of the currently requested page from the application management platform according to the access token;

S44: When each page is displayed by the target application, display menus and page elements associated with atomic functions assigned by the tenant, and hide menus and page elements that are not associated.

In practical application, the application management platform encapsulates the data access of the metadata service into an http request, and provides a restful access format. When a user logs in to the target application, the target application sends an http request to connect to the metadata service module of the application management platform for identity verification, and obtains an access token after successful verification. Afterwards, the target application uses the token to obtain the atomic function collection data available to the logged-in user to check the availability of the atomic functions corresponding to the menus in the page and the built-in menus on the page. Before each page is displayed, the target application sends an http request according to the token and page path to request page data access, and the metadata service module parses out the information associated with the target page based on the atomic function or function package information stored in the database and the analysis result of the metadata file Menu and page elements, and parse out the menu and page elements associated with the atomic function set that the user can use, mark the intersection data of the two as "customized" and return all menu and page element data. The target application hides unavailable (uncustomized) menus and page elements, and binds click events and corresponding atomic function keywords to menus. When the menu is clicked, check whether the atomic function can be used according to the keyword, and if it is not available, it will prompt the user that there is no operation permission.

Through the above operations, menus, page elements, pages, atomic functions, and function packages (sales packages) are defined in a unified format; at the same time, an application management platform is developed: the application management platform is responsible for the metadata analysis module, function customization and Allocation module, tenant customized data isolation module, tenant management module and metadata service module, etc. Among them, the metadata service module is responsible for encapsulating http requests for metadata access for target applications. The target application extension part is the running data isolation module, page parsing module, event listening module, function verification module, and request proxy module. These modules can be packaged into application-related library files, and applications developed in the same type of language can be directly imported into the library The file is expanded, and the transformation work is more lightweight.

It solves the problem that in traditional technology, in order to transform an application into a SaaS multi-tenant application, it is necessary to remodel the original application on a large scale, and develops a metadata analysis module, a function customization and distribution module, a tenant customization data isolation module, Tenant management module, metadata service module, operation data isolation module, page parsing module, event listening module, function verification module, request proxy module, etc., generate a lot of workload problems.

Example 3

This embodiment shows the system corresponding to Embodiments 1 and 2. Specifically, as shown in FIG. 4 , it includes a metadata configuration terminal 1, an application management platform 2, a tenant terminal 3 and a user terminal 4;

The metadata configuration terminal 1 is used for the configurator to split the overall function of the target application into atomic functions, and configure the atomic functions into function packages and sales packages including one or more function packages; Metadata, atomic functions, associations between atomic functions and menu metadata and page element metadata, function packages and sales packages are uploaded to the application management platform 2;

The application management platform 2 is used to analyze the data uploaded by the metadata configuration terminal 1;

Described application management platform 2 comprises:

The metadata parsing sub-module 21 is used for parsing the data uploaded to the application management platform 2; it has designed a corresponding parsing class for each configuration element, and designed class objects according to the configuration element specification format to save the parsing results, and provide Access interface for calling by other modules to obtain file parsing results. The metadata parsing module caches the parsing results.

The function customization and distribution sub-module 22 is used for the tenant terminal 3 to customize the sales package, and for the tenant terminal 3 to distribute one or more function packages to the user terminal 4; it mainly performs function customization, role management, User management, role function assignment and function check, etc. Wherein, the functions owned by the user are the functions assigned to the role to which the user belongs.

The metadata service sub-module 23 is used to send the corresponding menu metadata and page element metadata to the client 4 according to the access token of the client 4; it is responsible for user login verification, atomic function data access, page request data access, etc. Encapsulated as a restful http request for the target application to call. When a user of the target application logs in, an http request is sent with the registrant information, and the metadata service module verifies the user's identity. If the verification is successful, the access token is returned to the target application, and the token is written into the database, and the user information is cached at the same time. When the target application sends subsequent requests, it uses the token for data access. If the token fails, the metadata service module first reads user information from the database based on the token.

The data isolation sub-module 24 is used to isolate tenant-customized data; it is mainly responsible for application data isolation and tenant-customized data isolation, and each registered application can use the module service of the application management platform 2, so each application needs to be The data involved is isolated to ensure that the data of each application does not interfere with each other, and the tenant data under an application also needs to be independent of each other. The data scheme adopted by the application management platform 2 is "shared database, shared data structure".

Application management sub-module 25: for registering tenants and registering applications. After successfully registering the application, you will get a unique appid. Each registered application can use the module services of the application management platform 2 . The application configurator uploads the configuration metadata file after registering the application, and the application management module decompresses the packaged and uploaded metadata specification file. The content of the metadata file under the application can be obtained according to the appid. Each application will design a tenant manager to manage the application's tenants.

The tenant management module 26 is mainly a tenant manager responsible for managing all tenants of a specific application, mainly including the work of registering tenants and deleting tenants.

The tenant terminal 3 is used to customize the sales package through the application management platform 2, and distribute one or more function packages to the user;

The client 4 is used to obtain the menu metadata and page element metadata of the currently requested page from the application management platform 2, and display the menu and pages associated with the atomic functions in the function package allocated by the client 4.

Described user end 4 comprises following submodule:

The verification sub-module 41 is used to send an identity verification connection request to the application management platform 2 after logging in to the target application, and perform verification from the application management platform 2. After the identity verification connection request is verified, the returned data is obtained, which is the access token;

The metadata obtaining sub-module 42 is used to obtain menu metadata and page element metadata of the currently requested page from the application management platform 2 according to the access token;

The display sub-module 43 is configured to display menus and page elements associated with atomic functions assigned by the tenant terminal 3 and hide unrelated menus and page elements when the target application presents a page.

This system has the following advantages:

Versatility; function assembly specification, application management platform 2 is suitable for applications developed in different languages.

Reduce the complexity of the target application transformation, thereby reducing the transformation cost and the transformation time period.

Data isolation is mainly the isolation of application data and tenant data of each application.

Loose coupling: Mainly, the target application and metadata analysis, function customization and distribution, tenant customization data isolation, tenant management, metadata service and other modules exist independently. If the target application is bound with the extension module, it can be restored to a non-SaaS application.

Example 4

As shown in Figure 5-8, a video conferencing system developed based on flex, taking it as an example, describes the cooperative working relationship between various modules as follows, as shown in Figure 5: 1. The video conferencing system configurator bases on the overall function of the video conferencing system , Write menu, page, page, atomic function, function package metadata specification files. 2. The video conferencing system configurator registers the application in the application management module and obtains the application appid. 3. The video conferencing system configurator enters the management interface of the above application, packages and uploads the metadata specification file, and registers a tenant manager to manage the tenants of the application. 4. The tenant manager logs in to the tenant management module and registers the tenant information of the application. 5. Registered tenants log in to the function customization and allocation module to perform functions such as function customization, role management, user management, and role function allocation. Among them, the function customization and role function allocation will be obtained through the metadata analysis module to obtain metadata analysis results. 6. The data of each application and the tenant data under each application are isolated and stored through the data isolation module. 7. The metadata service module encapsulates the http request for metadata access to the target application, and obtains the metadata analysis result through the metadata analysis module.

The functional assembly process is shown in Figure 6. The configuration element specification is described in an xml file, and different assembly objects are consistent in the specification format, so that a consistent data structure can be designed for parsing and maintenance, and it is easy to read. The specific analysis is as follows:

Assembling menus: Menus and page elements are essentially elements of the page. In order to distinguish, elements that trigger click events are classified as menus here, while elements such as panels and lists are classified as page elements. Maybe you want to have an edit button in the list too, so: page elements can also have elements that trigger click events, we call them built-in menus. The main contents of the menu metadata assembly specification are: menu id, menu name, menu path, menu identifier, menu identifier value, and parent menu id; the goal of the menu metadata assembly specification design is that the target application can pass metadata Uniquely identifies the corresponding menu object.

Assembling page elements: The main contents of the page element metadata assembly specification are: page element id, page element name, page element path, page element identifier, page element identifier value, built-in menu name, built-in menu path, built-in menu identifier , the built-in menu marker value. The goal of the page element metadata assembly specification design is to uniquely identify the corresponding page element object through the metadata during the running of the target application.

Assembly page: Before each new page of the target application is displayed, the menu and page element metadata corresponding to the page will be accessed, and the menu and page element metadata associated with the atomic function assigned to the logged-in user will be marked as "customized ". The main contents of the page element metadata assembly specification are: page id, page path, menu id associated with the page, and page element id associated with the page.

Assembling atomic functions: The design concept of atomic functions is "user value driven", and only encapsulates functions that are meaningful to users. Atomic functions are independent of each other, and the collection of atomic functions is the entire function of the target application. The main contents of the atomic function metadata assembly specification are: function id, function name, function description, function keyword, associated menu id, associated page element id, and dependent function id. A feature may depend on one feature or set of features, or may not depend on other features.

Assembling function packages and sales packages: The design idea of function packages mainly considers three aspects: user business, atomic functions with dependencies, and atomic functions with dependencies. The sales package is a further encapsulation of the function package, and object-oriented is the tenant. The main contents of the function package/sales package metadata assembly specification are: function package id, function package name, function package description, atomic function id contained in the function package, and function package id contained in the function package. After the tenant customizes the sales package, he can assign the function package contained in the sales package to a certain role, and perform atomic function dependency check on the assignment result.

The tenant function customization and function allocation process is shown in Figure 7. After the application configurator uploads the assembly file, the application tenant logs in to the function customization and allocation module, which obtains the relevant content of the sales package through the metadata analysis module, and the tenant can customize the sales package. The data isolation module ensures that the data of each tenant is physically isolated so that they do not interfere with each other.

After the target application is transformed into a SaaS multi-tenant application, the operation process is shown in Figure 8. The target application adopted by the present invention is a video conferencing system developed based on flex, which extends the request agent module, page analysis module, event listening module, function verification module and tenant Run the data isolation module. When a user logs in to the video conferencing system based on tenant information and user personal information, the request agent module sends an http request to access the metadata service module of the application management platform for identity verification, and returns the access token. Before each page is displayed, the page parsing module relies on the request proxy module to send a page request, and the request proxy module calls the rest api to request access to page data according to the token and page path, and returns the menu and page element data of the requested page; among them, the user is assigned to The leaf menu and page elements corresponding to the atomic functions have been bound with atomic function keywords, which can be used for function checking. The page parsing module hides unavailable menus and page elements, and transfers all leaf menus to the event listening module for event binding and atomic function keyword binding corresponding to the menu. When the menu is clicked, the function verification module is inquired whether the function is available according to the keyword, and the function verification module is inquired whether the function is available according to the keyword and the expiration date. The target application will perform data isolation on user data from the perspective of the tenant during the running of the program.

The above are only preferred embodiments of the present invention, and any modifications, equivalent replacements and improvements made within the spirit and scope of the present invention shall be included within the protection scope of the present invention.

Claims (10)

1. A function assembly and customization method based on multi-tenant pattern, it is characterized in that, described method comprises metadata configuration end, application management platform, tenant end and user end, and it comprises the following steps: S1: The metadata configuration end splits the overall function of the target application into atomic functions, and configures the atomic functions as a function package and a sales package including one or more function packages; Functions, associations between atomic functions and menu metadata and page element metadata, function packages and sales packages are uploaded to the application management platform; S2: The application management platform analyzes the data uploaded to the application management platform in S1; S3: The tenant customizes the sales package through the application management platform, and assigns one or more function packages to the user; S4: The user terminal obtains the menu metadata and page element metadata of the currently requested page from the application management platform, and displays the menu and page elements associated with the atomic functions in the function package allocated by the user terminal. 2. The function assembly and customization method based on multi-tenant mode according to claim 1, wherein said S1 specifically includes: S11: Split the overall function of the target application into atomic functions at the metadata configuration end, and identify menu metadata and page element metadata; S12: Define the correlation between atomic functions, atomic functions and menu metadata, atomic functions and page element metadata at the metadata configuration side; S13: At the metadata configuration end, configure the atomic function as a function package and a sales package including one or more function packages; combine the atomic function, menu metadata and page element metadata in S11, the association in S12, and S13 Upload the function package and sales package in the application management platform. 3. The function assembly and customization method based on multi-tenant mode according to claim 1, characterized in that, said S4 specifically includes: S41: After the client logs in to the target application, it sends an identity verification connection request to the application management platform, and verifies from the application management platform; S42: Obtain an access token from the application management platform after the verification is passed; S43: Obtain menu metadata and page element metadata of the currently requested page from the application management platform according to the access token; S44: When each page is displayed by the target application, display menus and page elements associated with atomic functions assigned by the tenant, and hide menus and page elements that are not associated. 4. The function assembly and customization method based on the multi-tenant mode according to any one of claims 1 to 3, characterized in that, the described menu metadata, page element metadata, function packages, and sales packages are all standardized by metadata file definition. 5. The function assembly and customization method based on the multi-tenant mode according to any one of claims 1 to 3, characterized in that, the atomic functions included in the function package allocated by the client and the menus and pages associated with the atomic functions The element's metadata is marked as customized and contains the key of the associated atomic function. 6. The function assembly and customization method based on multi-tenant mode according to any one of claims 1 to 3, wherein the menu metadata includes menu id, menu name, menu path, menu identifier, menu identification Symbol value, parent menu id; The page element metadata includes: page element id, page element name, page element path, page element identifier, page element identifier value, built-in menu name, built-in menu path, built-in menu identifier, built-in menu marker value ; The correlation between atomic functions refers to the dependency relationship between atomic functions. 7. A system for implementing the multi-tenant mode-based function assembly and customization method according to any one of claims 1 to 6, characterized in that it includes a metadata configuration terminal, an application management platform, a tenant terminal and a user terminal ; The metadata configuration end is used for the configurator to split the overall function of the target application into atomic functions, and configure the atomic functions into function packages and sales packages including one or more function packages; Data, atomic functions, associations between atomic functions and menu metadata and page element metadata, function packages and sales packages are uploaded to the application management platform; The application management platform is used to analyze the data uploaded by the metadata configuration terminal; The tenant terminal is used to customize the sales package through the application management platform, and distribute one or more function packages to the user; The client is used to obtain the menu metadata and page element metadata of the currently requested page from the application management platform, and display the menu and page elements associated with the atomic functions in the function package allocated by the client. 8. The function assembly and customization system based on multi-tenant mode according to claim 7, wherein the application management platform includes: The metadata analysis sub-module is used to analyze the data uploaded to the application management platform; The function customization and distribution sub-module is used for the tenant to customize the sales package, and for the tenant to distribute one or more function packages to the user; The metadata service sub-module is used to send the corresponding menu metadata and page element metadata to the client according to the access token of the client. 9. The functional assembly and customization system based on multi-tenant mode according to claim 7, wherein the client terminal includes the following submodules: The verification sub-module is used to send an identity verification connection request to the application management platform after logging in to the target application, and perform verification from the application management platform. After the identity verification connection request is verified, the returned data is obtained, which is the access token; The metadata acquisition sub-module is used to acquire the menu metadata and page element metadata of the currently requested page from the application management platform according to the access token; The display sub-module is used to display the menu and page elements associated with the atomic functions assigned by the tenant when the target application displays each page, and hide the menu and page elements that are not associated. 10. The function assembly and customization system based on multi-tenant mode according to claim 7, wherein the application management platform further comprises: The data isolation sub-module is used to isolate the data customized by the tenant; Application management sub-module: used to register tenants and register applications.