CN102609271A - Metadata-driven visual SaaS (Software as a Service) application customizing method and metadata-driven visual SaaS application customizing system - Google Patents

Abstract

The present invention relates to a metadata-driven visual customization method and system for SaaS applications, which can flexibly support SaaS application customization types and expansion within customization types. The steps are: A. tenants lease applications to build business systems; Business system customization, select the customization type and customization object; C. According to the customization type, initialize the SaaS application visualization customization system; D. The SaaS application visual customization system reads the content of the tenant's customized metadata, and displays the customized metadata as visual elements on the tenant's customized operation interface through translation and analysis; E. Tenants customize in the visual customization interface according to their own needs; F. The SaaS application visual customization system judges whether the tenant's operation on the custom elements is allowed, and modifies the visual customization data. When the tenant customization is completed and saved, the customized metadata is written back; G. At the same time as the metadata is written back, the SaaS application visualization customization system executes the publishing operation, and the customization takes effect. H． When a user logs in to the business system, what he sees is the business system customized by the tenant.

Description

A metadata-driven visual customization method and system for SaaS applications

the

technical field

The invention relates to the field of software development, in particular to a method and system for visual customization of SaaS applications driven by metadata.

Background technique

In the traditional mode, developers need to develop and deploy applications according to the needs of different customers, and the cost is high. The SaaS model has changed the traditional software business model, providing services to different tenants based on the same software instance, that is, "single instance with multiple leases", which is cheap and quickly deployed. As a standard application, the application submitted by the developer is not suitable for the needs of each tenant, and the needs of the tenants will change over time. Therefore, in order to meet the personalized business needs of different tenants, SaaS applications must support "tenant Customize". The application involves multiple levels such as interface, service, and data, forming customization requirements in various aspects. After the tenant leasing application builds the business system, customize the function points of the system, the style used, the navigation method, the security authentication method, and also customize the pages, data, workflow, rules, parameters, etc.

Analyzing the flexible customization requirements of SaaS applications has the following characteristics: First, SaaS applications have many aspects that can be customized, such as page customization, function customization, data customization, etc. Although these customization types have different requirements, they are more complicated to implement individually. New requirements need to be re-implemented again, which limits the customization type and the internal scalability of the customization type; secondly, the complexity of customization implementation affects the customization efficiency and promotion difficulty of tenants. Hiding the underlying implementation details is the key to solving the problem; thirdly, to meet the isolation requirements of tenants, tenants can only see their own data during customization and runtime; finally, to ensure that tenants do not violate the requirements of the business system when customizing on demand The internal logic needs to limit the customization operations of tenants on customized content. Therefore, it is necessary to establish a method and system for SaaS application customization that supports extension of customization types, extension within customization types, visual customization, and limited customization operations.

Contents of the invention

The object of the present invention is to solve the above problems, and provide a method and system for visual customization of SaaS applications driven by metadata, so as to solve the problem of customization of applications.

To achieve the above object, the present invention adopts the following technical solutions:

A metadata-driven visual customization method for SaaS applications, comprising the following steps:

A. According to business needs, tenants lease applications that include function points that meet business needs, and combine the function points of each application to build a new usable application system, which is called a business system;

B. The tenant customizes the business system, selects the customization type, and the optional customization types include page customization, data customization, workflow customization, rule customization, parameter customization, function customization, security customization, system style customization, and then selects the object to be customized , customized objects include pages, database tables, workflows, rule files, system table parameters, etc.;

C. According to the customization type, initialize the SaaS application visualization customization system. The layout of the interface for customizing operations includes an operation tray, an attribute editing area, and a customizing operation area;

D． The SaaS application visualization customization system reads the tenant's custom metadata according to the lease number, custom object type, and custom object number. The metadata includes custom operation content and custom operation constraint information. Through translation, parsing, and conversion, the custom operation content is visualized in the tenant. Customized operation area display on the customized operation interface;

E． Tenants can add controls by dragging and dropping the interface elements of the operation tray to the custom operation area, edit the ID, length, width, display content, etc. Delete the mouse click event and bind the data model;

F． The SaaS application visual customization system judges whether the tenant's operation on the customized elements is allowed according to the customized operation constraint information, and makes corresponding modifications to the visualized customized data according to the tenant's addition, deletion, modification and configuration operations of the elements on the customized interface; when the tenant When saving after customization is completed, the SaaS application visual customization system removes the data used for visual display, and writes back the customized metadata according to the lease number, customized object type, and customized object number;

G． At the same time when the metadata is written back, the SaaS application visualization customization system executes the publishing operation, and republishes according to the customized content to make the customization take effect. If the page is customized, re-translate and compile the page.

H． When a user logs in to the business system, what he sees is the business system customized by the tenant.

  Before the first customization of the business system in step A, the application metadata is the standard application metadata uploaded by the developer; including:

Standard application metadata is the initial detailed information of the application. This information includes various customized subject description information, that is, the specific objects to be operated in various aspects of customization. Standard application metadata includes page metadata, data metadata, and workflow metadata. data, rule metadata, parameter metadata, functional metadata, security metadata, system style metadata;

Tenant customization metadata refers to information customized in various aspects and tenant leasing information. This type of information is metadata generated by tenants after performing customization operations on the customization aspects of specific applications leased by tenants. Contains the lease information of the tenant; after the tenant customizes the page/data/workflow/rule/parameter/function/security/system style, the corresponding tenant page/data/workflow/rule/parameter/function/security/system style customization is generated metadata.

In the step C, the operation tray accommodates tenants to drag and display interface elements. The interface elements are controls, such as various controls in page customization, and can also be customized, such as custom nodes in workflow customization; To allow tenants to edit the ID, length, width, display content, whether to activate, and whether to display the interface elements. The editable attributes of different interface elements are different; the custom operation area is used to display the customized content in a visual form, and right-click the interface. Elements perform deletion, add/modify/delete events, custom data model operations.

In the step D, the customized metadata is obtained according to the tenant's business system number, lease number, customized object type, and customized object number, so as to ensure strict isolation of the metadata of each tenant and avoid confusion in metadata management; the application metadata describes the application data, Pages, processes, rules, and style information; application metadata is divided into standard application metadata and tenant-customized metadata; when obtaining custom metadata, first search for tenant-customized metadata; if tenant-customized metadata does not exist, obtain standard application metadata The data is obtained according to the application number, custom object type, and custom object number; considering the convenience of metadata translation and analysis, standard application metadata and tenant custom metadata bodies are designed in XML format.

Translating the customized metadata in the step D is: according to the customization type, add visual display data for the tenant’s customized metadata, including the type and size of the visual elements displayed by the metadata; The displayed control is the data table, the length and width of the data table. Analyzing the translated data is to convert the translated data into visual elements according to the type, size, and content of the visual elements in the translated data, and display them on the tenant's customized operation interface. For example, when customizing data, parse the translated data and convert it into a data table with data.

In the step F, the tenant performs a custom operation, and adds controls by dragging and dropping the interface elements of the operation tray to the custom operation area, and edits attribute information such as ID, length, width, display content, whether to activate, or whether to display, etc. in the attribute editing area. Customize the operation area to delete controls, add/modify/delete events for controls, and bind data models through right-click operations. For example, when customizing a page, after the tenant selects the page to be customized, drag the control from the control area to the custom operation area, describe the ID attribute of the control and the rear control according to the prompt information, and after adding the control, right click to add events and customize the control. The data model can also delete controls. Another example is style customization. The tenant selects the system payment method, authentication method, and navigation method through the radio button, and modifies the LOGO image by uploading the image.

Through the constraint information of tenants on elements on the visual interface, judge whether tenants’ operations on customized elements are allowed, and make corresponding visual customization data according to tenants’ various operations such as adding, deleting, modifying and configuring elements on the customized interface Modifications.

When the tenant customization is completed and saved, the SaaS application visual customization system removes the data used for visual display and reverse-translates the visual customization data. Reverse translation is the reverse process of adding visual display data to metadata in step D. The existing The metadata is extracted, that is, the visual information and auxiliary information modified or added during forward translation are removed; the metadata is written back according to the lease number, custom object type, and custom object number, and the isolation of the tenant's custom metadata is guaranteed when writing back. Perform republishing operations at the same time, that is, perform dynamic changes to the application based on the results of tenant customizations. For example, page customization may require re-translation and compilation of pages, workflow customization redeploys processes, and parameter customization modifies parameter information in the corresponding database.

A metadata-driven SaaS application visualization customization system, the system includes:

The metadata management unit is responsible for the interaction between all applications and metadata, involving the operation of the database. By providing a unified interface for obtaining and writing back application metadata, it avoids the confusion of metadata operations and ensures the consistency of metadata; The convenience of data translation and analysis, etc., the main body of various metadata adopts XML format;

The metadata translation unit is responsible for forward and reverse translation of metadata; forward translation is mainly to add visual display information and auxiliary information to metadata, including the type, size, content, and number of leases of visual elements to form visualization Customized data; reverse translation is the reverse process of forward translation, which extracts existing metadata from visualized customized data, and removes the visual information and auxiliary information modified or added by forward translation and metadata generation unit;

The metadata parsing unit is responsible for parsing the translated metadata, implementing different metadata parsing strategies for the metadata in different aspects of customization, and converting them into visual elements according to the description information of the translated metadata to the visual elements, Displayed on the tenant customization interface;

The metadata display unit is responsible for the display of visual elements. The visual element set is a collection of various controls on the visual custom operation interface for tenants to perform customized operations;

The metadata generating unit is responsible for modifying the visualized customized data according to the various customized operations of the tenant on the visualized customized operation interface; the metadata generating unit must accurately control the consistency between the tenant’s operation and the metadata to ensure the tenant’s operation Can be completely reflected in the metadata;

The custom constraint unit restricts the custom operation behavior of the tenant; according to the custom operation constraint information in the metadata, it judges whether the operation of the tenant is allowed and controls the custom operation of the tenant;

The customization release unit, after the customization operation is completed, judges whether the corresponding application part needs to be republished according to the customization type; if necessary, executes the dynamic release of the application according to the customization result. If the page is customized, re-translate and compile the page.

The metadata display unit includes:

Page customization visual element set, page customization includes almost all controls, including general element controls such as label control (Label), container components such as canvas (Cavas), data display components such as data grid (DataGrid), non-visual elements such as services (WebService ), where in order to provide non-visual element customization, it needs to be designed with visual elements;

Data customization visualization element set, controls required for data customization, including data grid (DataGrid);

Workflow customization visual element set, workflow customization required controls, including Task node, Decision node, Java node, Start node, End node, Join node, Fork node, connection, selection button;

Rule customization visual element set, rule file display control, text area (TextArea), button;

Parameter customization visual element set, parameter customization required controls, data table (DataGrid), button

Function customization visual element set, function customization required controls, tree controls, buttons;

Security customization visual element set, security customization required controls, tree control with check box, button;

System style custom set of visual elements, labels, text boxes, radio buttons, buttons.

The application metadata includes:

Page metadata, which describes the data of the page, including page customization operation content and page customization operation constraints. The page customization operation content describes the controls on the page, the data model that provides data for the controls, the services called on the page, and the definition of the services; the page customization operation constraints are divided into three categories according to the control types, one is the constraints on the data display controls, and the description The necessary properties of the control, whether the control can be deleted and modified, whether the column can be deleted and modified; the second is the constraints on the label and input control, describing the necessary properties of the control, whether the control can be deleted and modified; The third is the constraints on the operation definition control, describing the necessary attributes of the control, whether the control can be deleted or modified.

Data metadata, data describing business data, including data customization operation content and data customization operation constraints. Data customization operation content describes all tables of the user, the application of the table, the user of the table, all columns of the table, the primary key of the table, the name of each column, data type, length, whether it is empty, whether it is available, whether it can be customized, Data that describes information and the location of the corresponding physical table. The data customization operation constraint describes whether the column can be customized.

Workflow metadata, describing workflow data, including workflow custom operation content and workflow custom operation constraints. The workflow customization operation content describes a series of interconnected and automatic business activities or tasks, as well as the business processing method and sequence. The workflow customization operation constraints describe the list of nodes that can be customized, the list of nodes that can be added, the list of nodes that can change the direction of branches, and the list of nodes that can be deleted.

Rule metadata, data describing the rule, including rule customization operation content and rule customization operation constraints. The rule customization operation content describes the name, function and business logic of the rule. Rule customizing operation constraints describe customizing constraints between rules.

Parameter metadata, data describing parameters, including parameter customization operation content. The parameter customization operation content describes the name, description, type, and initial value of the system parameter.

Function metadata, data describing function points, including function customization operation content. The function customization operation content describes the organizational structure, name, description, and corresponding page of the function point.

Security metadata, which describes the data of function points that require security authentication, including security customization operation content. The security customization operation content describes the function points to be security certified.

System style metadata, data describing system parameters, including system style operation content and system style operation constraints, system style operation content description system style includes payment method, authentication method, navigation method, display name, and LOGO image data. A system style operation constraint describes the mandatory items of a system style.

The beneficial effects of the present invention are:

1. A metadata-driven SaaS application visualization customization method and system are provided, enabling tenants to conveniently perform various customizations by dragging, selecting, and right-clicking to operate interface elements on a visualization customization interface, improving the usability of SaaS application customization.

2. By using the metadata-driven method, the tenants can be customized to isolate metadata to avoid confusion of tenant data and ensure that each tenant sees the tenant's own data.

3. Define constraints on tenants' customization operations in the metadata, limit tenants' customization operations, and ensure that industry customers will not violate the internal logic of the business system when performing on-demand customization.

4. Reasonable design of metadata can simply and effectively support custom types and internal extensions of custom types. By adding metadata of related types, the addition of customized types can be realized simply and effectively. By adding or modifying the attributes describing the custom operation content and custom operation constraints in the metadata, the modification of the existing custom type can be realized.

Description of drawings

Fig. 1 is a detailed flowchart of a metadata-driven visual customization method for SaaS applications.

Fig. 2 is a schematic diagram of a metadata-driven visual customization system for SaaS applications.

Detailed ways

The present invention will be further described below by referring back to the accompanying drawings and the embodiments.

In Fig. 1, it is a flowchart of a metadata-driven SaaS application visualization customization method of the present invention, including the following steps:

Step 101. According to the business needs, the tenant leases applications that include function points that meet the business needs, and combines the function points of each application to build a new usable application system, which is called a business system;

Step 102, the tenant customizes the business system, selects the customization type, and the optional customization types include page customization, data customization, workflow customization, rule customization, parameter customization, function customization, security customization, and system style customization, and then selects the one to be customized Objects, customized objects include pages, database tables, workflows, rule files, system table parameters, etc.;

Step 103. According to the customization type, initialize the SaaS application visualization customization system. The layout of the interface for customizing operations includes an operation tray, an attribute editing area, and a customizing operation area;

Step 104, the SaaS application visualization customization system reads the tenant's custom metadata according to the lease number, custom object type, and custom object number. The metadata includes custom operation content and custom operation constraint information, and visualizes the custom operation content through translation, parsing, and conversion. Elements are displayed in the customized operation area on the tenant's customized operation interface;

Step 105, the tenant adds controls by dragging and dropping the interface elements of the operation tray to the custom operation area, edits the ID, length, width, display content, etc. /Modify/delete mouse click event, bind data model;

Step 106: The SaaS application visual customization system judges whether the tenant's operation on the customized element is allowed according to the customized operation constraint information, and makes corresponding modifications to the visualized customized data according to the tenant's addition, deletion, modification and configuration operations of the elements on the customized interface ; When the tenant customization is completed and saved, the SaaS application visualization customization system removes the visualization data, and writes back the customized metadata according to the lease number, customized object type, and customized object number;

In step 107, while the metadata is written back, the SaaS application visualization customization system executes the publishing operation, and republishes according to the customized content to make the customization take effect. If the page is customized, re-translate and compile the page.

Step 108, the user logs in to the business system, and what he sees is the business system customized by the tenant.

In Figure 2, a metadata-driven SaaS application visualization customization system, the system includes:

The metadata management unit 201 is responsible for the interaction between all applications and metadata, involving the operation of the database. By providing a unified interface for obtaining and writing back application metadata, it avoids the confusion of metadata operations and ensures the consistency of metadata. Considering the convenience of metadata translation and analysis, various metadata bodies are designed in XML format.

The metadata translation unit 202 is responsible for forward and reverse translation of metadata. Forward translation is mainly to add visual display information and auxiliary information to metadata, including the type, size, content, rental times, etc. of visual elements, to form visual customized data. Reverse translation is the reverse process of forward translation, which extracts the existing metadata from the visual customization data, and removes the visual information and auxiliary information modified or added by the forward translation and metadata generation unit.

The metadata parsing unit 203 is responsible for parsing the translated metadata. In view of the standardization of the metadata XML format, different metadata parsing strategies are implemented for the metadata in the customization of different aspects, and the description of the visual elements according to the translated metadata The information is converted into visual elements and displayed on the tenant's customized interface.

The metadata display unit 204 is responsible for the display of visual elements. The visual element set is a collection of various controls on the visual customization operation interface for tenants to perform customization operations. The requirements for each customization are different, and some may be complicated.

The metadata generation unit 205 is responsible for modifying the visualization customization data according to various customization operations performed by the tenant on the visualization customization operation interface. For tenant operations, such as adding elements, modifying element attributes, and deleting elements, etc., the metadata generation unit must precisely control the consistency between tenant operations and metadata to ensure that tenant operations can be fully reflected in metadata.

The customization restriction unit 206 restricts the customization operation behavior of the tenant. According to the custom operation constraint information in the metadata, judge whether the tenant's operation is allowed, and control the tenant's custom operation.

The customization release unit 207, after the customization operation is completed, judges whether the corresponding application part needs to be republished according to the customization type. Perform dynamic publishing of the application based on customization results if required. If the page is customized, re-translate and compile the page.

The metadata display unit 204 includes a page customization visualization element set 2041, a data customization visualization element set 2042, a workflow customization visualization element set 2043, a rule customization visualization element set 2044, a parameter customization visualization element set 2045, a function customization visualization element set 2046, a security Customized visualization element set 2047 and system style visualization element set 2048 .

Page customization visual element set 2041, page customization includes almost all controls, including general element controls such as label control (Label), container components such as canvas (Cavas), data display components such as data grid (DataGrid), non-visual elements such as services ( WebService), where in order to provide customization of non-visual elements, it needs to be designed with visual elements

Data customization visualization element set 2042, controls required for data customization, including data grid (DataGrid).

Workflow customization visualization element set 2043, controls required for workflow customization, including Task node, Decision node, Java node, Start node, End node, Join node, Fork node, connection, selection button.

Rule customization visualization element set 2044, rule file display control, text area (TextArea), button.

Parameter customization visual element set 2045, controls required for parameter customization, data grid (DataGrid), button.

Function customization visual element set 2046, controls required for function customization, tree controls, buttons.

Security customization visual element set 2047, controls required for security customization, tree control and buttons with check boxes.

System style visual element set 2048, space required for system style customization, labels, text boxes, radio buttons, buttons. the

The applications and metadata include:

Page metadata, which describes the data of the page, including page customization operation content and page customization operation constraints. The page customization operation content describes the controls on the page, the data model that provides data for the controls, the services called on the page, and the definition of the services; the page customization operation constraints are divided into three categories according to the control types, one is the constraints on the data display controls, and the description The necessary properties of the control, whether the control can be deleted and modified, whether the column can be deleted and modified; the second is the constraints on the label and input control, describing the necessary properties of the control, whether the control can be deleted and modified; The third is the constraints on the operation definition control, describing the necessary attributes of the control, whether the control can be deleted or modified.

Data metadata, data describing business data, including data customization operation content and data customization operation constraints. Data customization operation content describes all tables of the user, the application of the table, the user of the table, all columns of the table, the primary key of the table, the name of each column, data type, length, whether it is empty, whether it is available, whether it can be customized, Data that describes information and the location of the corresponding physical table. The data customization operation constraint describes whether the column can be customized.

Workflow metadata, describing workflow data, including workflow custom operation content and workflow custom operation constraints. The workflow customization operation content describes a series of interconnected and automatic business activities or tasks, as well as the business processing method and sequence. The workflow customization operation constraints describe the list of nodes that can be customized, the list of nodes that can be added, the list of nodes that can change the direction of branches, and the list of nodes that can be deleted.

Rule metadata, data describing the rule, including rule customization operation content and rule customization operation constraints. The rule customization operation content describes the name, function and business logic of the rule. Rule customizing operation constraints describe customizing constraints between rules.

Parameter metadata, data describing parameters, including parameter customization operation content. The parameter customization operation content describes the name, description, type, and initial value of the system parameter.

Function metadata, data describing function points, including function customization operation content. The function customization operation content describes the organizational structure, name, description, and corresponding page of the function point.

Security metadata, which describes the data of function points that require security authentication, including security customization operation content. The security customization operation content describes the function points to be security certified.

System style metadata, data describing system parameters, including system style operation content and system style operation constraints, system style operation content description system style includes payment method, authentication method, navigation method, display name, and LOGO image data. A system style operation constraint describes the mandatory items of a system style.

Claims (9)

1. A method for visual customization of metadata-driven SaaS applications, comprising the following steps: A. According to business needs, tenants lease applications that include function points that meet business needs, and combine the function points of each application to build a new application system, which is called a business system; B. The tenant customizes the business system, selects the customization type, and the optional customization types include page customization, data customization, workflow customization, rule customization, parameter customization, function customization, security customization, system style customization, and then selects the object to be customized , customized objects include pages, database tables, workflows, rule files, and system table parameters; C. According to the type of customization, initialize the SaaS application visual customization system, and the layout of the interface for customizing operations includes an operation tray, an attribute editing area, and a customizing operation area; D． Read the tenant's custom metadata according to the lease number, custom object type, and custom object number. The metadata includes custom operation content and custom operation constraint information. Through translation, parsing, and conversion, the custom operation content is visualized on the tenant's custom operation interface. Customize the display of the operating area; E． Tenants add controls by dragging and dropping the interface elements of the operation tray to the custom operation area, edit the ID, length, width, and display content of the control in the attribute editing area, delete controls, and add/modify/delete controls in the custom operation area by right-clicking Mouse click event, binding data model; F． According to the custom operation constraint information, it is judged whether the tenant’s operation on the custom element is allowed, and the visual customization data is modified accordingly according to the tenant’s addition, deletion, modification and configuration operations on the elements on the customization interface; when the tenant’s customization is completed and saved , the SaaS application visual customization system removes the data used for visual display, and writes back the customized metadata according to the lease number, customized object type, and customized object number; G． At the same time when the metadata is written back, the SaaS application visualization customization system executes the publishing operation, and republishes according to the customized content to make the customization take effect; H． When a user logs in to the business system, what he sees is the business system customized by the tenant. 2. The visual customization method for metadata-driven SaaS applications according to claim 1, wherein, before the first customization of the business system in the step A, the application metadata is the standard application metadata uploaded by the developer; including: Standard application metadata is the initial detailed information of the application. This information includes various customized subject description information, that is, the specific objects to be operated in various aspects of customization. Standard application metadata includes page metadata, data metadata, and workflow metadata. data, rule metadata, parameter metadata, functional metadata, security metadata, system style metadata; Tenant customization metadata refers to information customized in various aspects and tenant leasing information. This type of information is metadata generated by tenants after performing customization operations on the customization aspects of specific applications leased by tenants. Contains the lease information of the tenant; after the tenant customizes the page/data/workflow/rule/parameter/function/security/system style, the corresponding tenant page/data/workflow/rule/parameter/function/security/system style customization is generated metadata. 3. The visual customization method for metadata-driven SaaS applications as claimed in claim 1, wherein in said step C, the operation tray accommodates tenants to drag and display interface elements, and the interface elements are controls; To allow tenants to edit the ID, length, width, display content, whether to activate, and whether to display the interface elements. The editable attributes of different interface elements are different; the custom operation area is used to display the customized content in a visual form, and right-click the interface. Elements perform deletes, events, and custom data model operations. 4. The visual customization method of the metadata-driven SaaS application according to claim 1, wherein in the step D, the custom metadata is obtained according to the tenant's business system number, lease number, custom object type, and custom object number , to ensure strict isolation of tenant metadata; application metadata describe application data, pages, processes, rules, and style information; application metadata is divided into standard application metadata and tenant custom metadata; when obtaining custom metadata, first search Tenant-customized metadata; if the tenant-customized metadata does not exist, obtain the standard application metadata, and obtain it according to the application number, custom object type, and custom object number; both the standard application metadata and the tenant-customized metadata body are designed in XML format. 5. The method for visually customizing metadata-driven SaaS applications according to claim 1, wherein translating the custom metadata in the step D is: according to the customization type, adding visual display data to the tenant custom metadata, including The type and size of the visual element displayed by the metadata; the analysis of the translated data is based on the type, size, and content of the visual element in the translated data, and the translated data is converted into a visual element, which is displayed on the tenant's customized operation interface. 6. The method for visual customization of metadata-driven SaaS applications as claimed in claim 1, wherein in said step F, when the tenant customization is completed and saved, the SaaS application visual customization system removes the data used for visual display, Reverse translation of the visualized customized data, the reverse translation is the reverse process of the forward translation in step C, which extracts the existing metadata, that is, removes the visual information and auxiliary information modified or added during the forward translation; according to the lease number, customization The object type and custom object number are written back to the metadata, ensuring the isolation of the tenant's custom metadata when writing back, and executing the publish operation at the same time as writing back, that is, performing dynamic changes to the application according to the result of the tenant's customization. 7. A metadata-driven SaaS application visualization customization system, characterized in that the system includes: The metadata management unit is responsible for the interaction between all applications and metadata, involving the operation of the database. By providing a unified interface for obtaining and writing back application metadata, it avoids the confusion of metadata operations and ensures the consistency of metadata; The data subject is in XML format; The metadata translation unit is responsible for forward and reverse translation of metadata; forward translation is mainly to add visual display information and auxiliary information to metadata, including the type, size, content, and number of leases of visual elements to form visualization Customized data; reverse translation is the reverse process of forward translation, which extracts existing metadata from visualized customized data, and removes the visual information and auxiliary information modified or added by forward translation and metadata generation unit; The metadata parsing unit is responsible for parsing the translated metadata, implementing different metadata parsing strategies for the metadata in different aspects of customization, and converting them into visual elements according to the description information of the translated metadata to the visual elements, Displayed on the tenant customization interface; The metadata display unit is responsible for the display of visual elements. The visual element set is a collection of various controls on the visual custom operation interface for tenants to perform customized operations; The metadata generating unit is responsible for modifying the visualized customized data according to the various customized operations of the tenant on the visualized customized operation interface; the metadata generating unit must accurately control the consistency between the tenant’s operation and the metadata to ensure the tenant’s operation Can be completely reflected in the metadata; The custom constraint unit constrains the customized operation behavior of the tenant; not all the elements on the visual interface are authorized by the tenant to operate, the metadata contains the tenant's custom permission information on the metadata, and the custom constraint unit is based on the corresponding metadata information Maintain the tenant's authority to operate metadata on various parts, and control the tenant's customized operations; Custom release unit, after the customization operation is completed, judges whether the corresponding application part needs to be republished according to the customization type; if necessary, executes dynamic release of the application according to the customization result; If the page is customized, re-translate and compile the page. 8. The metadata-driven SaaS application visualization customization system according to claim 7, wherein the metadata display unit comprises: A set of visual elements for page customization. Page customization includes general element controls, container components, data display components, and non-visual elements. In order to provide non-visual element customization, it needs to be designed as visual elements; Data customization visualization element set, controls required for data customization, including data tables; Workflow customization visual element set, workflow customization required controls, including Task node, Decision node, Java node, Start node, End node, Join node, Fork node, connection, selection button; Rule customization visual element set, rule file display control, text area, button; Parameter customization visual element set, parameter customization required controls, data tables, buttons Function customization visual element set, function customization required controls, tree controls, buttons; Security customization visual element set, security customization required controls, tree control with check box, button; System style custom set of visual elements, labels, text boxes, radio buttons, buttons. 9. The metadata-driven SaaS application visualization customization system according to claim 7, wherein the application and metadata include: Page metadata, describing the data of the page, including page customization operation content and page customization operation constraints; page customization operation content describes the controls on the page, the data model that provides data for the control, the service called on the page, and the definition of the service; page customization Operational constraints are divided into three categories according to the type of control. One is the constraint on the data display control, which describes the necessary attributes of the control, whether the control can be deleted and modified, whether the column can be deleted and modified; the second is the constraint on the label and input. Constraints of the control, describing the necessary attributes of the control, whether the control can be deleted, and whether it can be modified; the third is the constraint on the operation definition control, describing the necessary attributes of the control, whether the control can be deleted, or whether it can be modified; Data metadata, which describes the data of business data, including data customization operation content and data customization operation constraints; data customization operation content describes all tables of the user, the application to which the table belongs, the user to which the table belongs, all columns of the table, the primary key of the table, The name of each column, data type, length, whether it is empty, whether it is available, whether it can be customized, description information, and the location data of the corresponding physical table; Whether the data customization operation constraint description column can be customized; Workflow metadata, describing workflow data, including workflow custom operation content and workflow custom operation constraints; workflow custom operation content describes a series of interconnected and automatic business activities or tasks, as well as business processing methods and sequences ;Workflow customization operation constraints describe the list of nodes that can be customized, the list of nodes that can be added, the list of nodes that can change the direction of branches, and the list of nodes that can be deleted; Rule metadata, data describing rules, including rule customization operation content and rule customization operation constraints; rule customization operation content describes the name, function and implemented business logic of the rule; rule customization operation constraints describe the customization constraints between rules; Parameter metadata, data describing parameters, including parameter customization operation content; parameter customization operation content describes the name, description, type, and initial value of system parameters; Function metadata, data describing function points, including function customization operation content; function customization operation content describes the organizational structure, name, description, and corresponding pages of function points; Security metadata, which describes the data of function points that require security authentication, including the content of security customization operations; the content of security customization operations describes the function points that need security authentication; System style metadata, data describing system parameters, including system style operation content and system style operation constraints, system style operation content description system style includes payment method, authentication method, navigation method, display name, LOGO picture data; system style operation Constraints describe mandatory items for system styles.

Images