Method for realizing extensibility, integration and exploration of SaaS (Software as Service) system based on low code

Abstract

The invention discloses a method for realizing extensibility, integration and exploration of a SaaS (Software as a Service) system based on a low code, which comprises the following steps of: S1, configuring an access application based on the SaaS system, and importing a corresponding physical table structure through the access application; s2, for a universal service scene of the SaaS system, creating different service domain models according to a physical table structure corresponding to the service scene; s3, customizing service scenes for tenants of the SaaS system, and saving the corresponding service domain models as different tenant models based on the service scenes or creating custom models of different service scenes based on a universal service physical table structure; s4, importing the business domain model in the step S2, and developing business logics of different business scenes; s5, importing the business domain model in the step S2 to carry out page development of different business scenes; and S6, saving the page of the SaaS system as a tenant page by the tenant in an inheritance form, thereby realizing customized expansion based on the page of the SaaS system.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and particularly relates to a method for realizing the extensibility, integration and exploration of a SaaS system based on low-code. Background Art

[0002] SaaS is short for Software-as-a-Service, which is a new software delivery model. Under this model, software service providers will centrally deploy application software on their own servers. Customers can negotiate with software service providers through the network according to their actual business needs to purchase the required software services. Customers pay fees to suppliers according to the purchased service volume and the length of use time. This method allows customers to obtain services provided by software service providers through the Internet without having to purchase and maintain software by themselves.

[0003] SaaS adopts the methods of hosting and multi-tenancy, and customers can subscribe to services and pay according to their needs. Compared with the traditional way of software that requires cumbersome deployment and operation and maintenance locally, SaaS greatly simplifies this process and saves the costs and time of enterprises.

[0004] At present, each SaaS system on the market mainly solves the basic needs of enterprises in different fields, that is, general needs. However, each enterprise has its own special needs, that is, personalized needs, and the solution costs of these needs are extremely high, such as private cloud deployment, which leads to higher implementation, operation and maintenance, and upgrade costs of SaaS systems. Summary of the Invention

[0005] The purpose of the present invention is to provide a method for realizing the extensibility, integration and exploration of a SaaS system based on low-code to solve the above problems.

[0006] To achieve the above purpose, the present invention adopts the following technical solutions:

[0007] A method for realizing the extensibility, integration and exploration of a SaaS system based on low-code, comprising the following steps:

[0008] S1. Configure an access application based on the SaaS system, import the corresponding physical table structure through the access application, and configure and mark the corresponding reserved index fields and JSON fields;

[0009] S2. For the general business scenarios of the SaaS system, create different business domain models according to the physical table structure corresponding to the business scenario, and perform physical table field binding and model attribute mapping;

[0010] S3. For the tenant customization business scenarios of the SaaS system, save the corresponding business domain model as different tenant models based on this business scenario or create custom models for different business scenarios based on the general business physical table structure, and perform model attribute extension and model attribute mapping respectively;

[0011] S4. Import the business domain model in step S2, and develop the business logics for different business scenarios. Tenants import the tenant model or custom model in step S3 through the tenant extension nodes of the business logics of the SaaS system, achieve customized extension based on the business logics of the SaaS system, and the code executor is responsible for dynamically loading the business logic extension code of the tenant;

[0012] S5. Import the business domain model in step S2 for page development of different business scenarios;

[0013] S6. Tenants save the pages of the SaaS system as tenant pages in an inheritance form, import the tenant model or custom model in step S3, achieve customized extension based on the pages of the SaaS system, and the page rendering parser is responsible for dynamically loading and parsing the tenant-customized pages and binding the tenant model or custom model.

[0014] Preferably, the physical table structure is imported through the database link corresponding to the access application.

[0015] Preferably, the reserved index fields and JSON fields are used to support the tenant's customization requirements based on the enterprise by adopting the characteristics of the database JSON fields, and achieve the tenant's extensible demands for business fields.

[0016] Preferably, the business domain model in step S2 is the system domain operation object under the corresponding business scenario. Define the business domain object in a visual way, map the physical table structure to the system operation object, and support the business logic orchestration of visual development and the data binding and database operations of the page.

[0017] Preferably, the tenant model in step S3 is an extended object of the tenant based on the SaaS system domain model, used to support the tenant to extend the attributes of the SaaS system domain model by itself. The custom model is a custom system operation object for different business scenarios created based on the physical table structure built in the SaaS system, used to support the tenant's custom new function development.

[0018] Preferably, the model attribute extension and model attribute mapping of the tenant model or custom model in step S3 are implemented through the JSON fields of the physical table structure corresponding to the current model or the physical table structure associated with the current model.

[0019] Preferably, the business domain model in step S4 is imported through a visual business logic editor, and the tenant extension node of the visual business logic editor is used for the tenant's requirements for the integration and exploration of the SaaS system based on the general capabilities of the SaaS system.

[0020] Preferably, the business logic includes business logic control, HTTP service call, atomic service call, SQL service call, business rule call, custom function call, and tenant extension node.

[0021] Preferably, the business domain model in step S5 is imported through a visual page editor, and the tenant page of the visual page editor is used for the tenant's requirements for the extensibility and exploration of the SaaS system page.

[0022] After adopting the above technical solution, compared with the background technology, the present invention has the following beneficial effects:

[0023] The present invention provides a method for realizing the extensibility, integration, and exploration of a SaaS system based on low-code, which can not only meet the general needs of enterprises, but also customize according to the unique needs of enterprises, with low cost and small difficulty, and improve the extensibility, integration, and exploration capabilities of the SaaS system. Description of the Drawings

[0024] Figure 1 It is a flowchart of the method of the present invention. Detailed Embodiments

[0025] In order to make the purpose, technical solution, and advantages of the present invention clearer, the following further describes the present invention in detail with reference to the embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not used to limit the present invention.

[0026] Embodiment

[0027] Cooperate with Figure 1 As shown, the present invention discloses a method for realizing the extensibility, integration, and exploration of a SaaS system based on low-code, including the following steps:

[0028] S1. Based on the SaaS system, configure the access application, import the corresponding physical table structure through the access application, and configure and mark the corresponding reserved index fields and JSON fields;

[0029] The physical table structure is imported through the database link corresponding to the access application. The reserved index fields and JSON fields are used to support the tenant's customized requirements based on the enterprise by using the database JSON field feature, and realize the tenant's extensibility requirements for business fields.

[0030] S2. For the general business scenarios of the SaaS system, different business domain models are created according to the physical table structures corresponding to the business scenarios, and physical table field binding and model attribute mapping are performed;

[0031] S3. For the tenant customization business scenarios of the SaaS system, the corresponding business domain models are saved as different tenant models based on the business scenarios or custom models for different business scenarios are created based on the general business physical table structure, and model attribute extension and model attribute mapping are performed respectively;

[0032] S4. Import the business domain models in step S2, and develop the business logics for different business scenarios. The tenants of the SaaS system import the tenant models or custom models in step S3 through the tenant extension nodes of the business logics of the SaaS system, realize the customized extension based on the business logics of the SaaS system, and the built-in code executor of the system is responsible for dynamically loading the business logic extension codes of the tenants;

[0033] S5. Import the business domain models in step S2 for page development of different business scenarios;

[0034] S6. The tenants of the SaaS system save the pages of the SaaS system as tenant pages in an inheritance form, import the tenant models or custom models in step S3, realize the customized extension based on the pages of the SaaS system, and the page rendering parser is responsible for dynamically loading and parsing the tenant customized pages and binding the tenant models or custom models.

[0035] In step S2, the business domain model is the system domain operation object under the corresponding business scenario. The business domain object is defined visually, so that the physical table structure is mapped to the system operation object, and it supports the visual development of business logic orchestration and page data binding and database operations.

[0036] In step S3, the tenant model is the extended object of the tenant based on the SaaS system domain model, which is used to support the tenant to expand the attributes of the SaaS system domain model by itself. The custom model is a custom system operation object for different business scenarios created based on the built-in physical table structure of the SaaS system, which is used to support the tenant to develop custom new functions.

[0037] In step S3, the model attribute extension and model attribute mapping of the tenant model or custom model are realized through the physical table structure corresponding to the current model or the JSON fields of the physical table structure associated with the current model.

[0038] In step S4, the business domain model is imported through the visual business logic editor. The tenant extension node of the visual business logic editor is used for the tenant's requirements for integration and exploration of the SaaS system based on the general capabilities of the SaaS system.

[0039] The business logic includes business logic control, HTTP service call, atomic service call, SQL service call, business rule call, custom function call, and tenant extension node.

[0040] In step S5, the business domain model is imported through a visual page editor, and the tenant page of the visual page editor is used for the tenant's extensible and explorative requirements based on the SaaS system page.

[0041] As mentioned above, only the specific preferred embodiments of the present invention are described, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by those skilled in the art within the technical scope disclosed by the present invention should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims

1. A method for implementing the extensibility, integration, and exploration of a SaaS system based on low-code, characterized in that: It includes the following steps: S1. Based on the SaaS system configuration, access the application, import the corresponding physical table structure through the access application, and configure and mark the corresponding reserved index fields and JSON fields; S2. For the general business scenarios of the SaaS system, create different business domain models according to the physical table structure corresponding to the business scenario, and perform physical table field binding and model attribute mapping; S3. For the tenant-customized business scenarios of the SaaS system, save the corresponding business domain model as different tenant models based on the business scenario or create custom models for different business scenarios based on the general business physical table structure, and perform model attribute extension and model attribute mapping respectively; S4. Import the business domain model in step S2, and develop the business logic for different business scenarios. The tenant imports the tenant model or custom model in step S3 through the tenant extension node of the business logic of the SaaS system, realizes the customized extension of the business logic based on the SaaS system, and the code executor is responsible for dynamically loading the business logic extension code of the tenant; S5. Import the business domain model in step S2 for page development of different business scenarios; S6. The tenant saves the page of the SaaS system as a tenant page in an inheritance form, imports the tenant model or custom model in step S3, realizes the customized extension of the page based on the SaaS system, and the page rendering parser is responsible for dynamically loading and parsing the tenant-customized page and binding the tenant model or custom model.

2. A method for implementing the extensibility, integration, and exploration of a SaaS system based on low-code as described in claim 1, characterized in that: The physical table structure is imported through the database link corresponding to the access application.

3. A method for implementing the extensibility, integration, and exploration of a SaaS system based on low-code as described in claim 1, characterized in that: The reserved index fields and JSON fields are used to support the tenant's customization requirements based on the enterprise by using the characteristics of the database JSON fields, and to realize the tenant's extensible appeal for business fields.

4. A method for implementing the extensibility, integration, and exploration of a SaaS system based on low-code as described in claim 1, characterized in that: In step S2, the business domain model is the system domain operation object in the corresponding business scenario. The business domain object is defined in a visual way, so that the physical table structure is mapped to the system operation object, and it supports the visual development of business logic orchestration and page data binding and database operations.

5. A method for implementing the extensibility, integration, and exploration of a SaaS system based on low-code as described in claim 1, characterized in that: In step S3, the tenant model is an extended object of the tenant based on the SaaS system domain model, which is used to support the tenant to extend the attributes of the SaaS system domain model by itself. The custom model is a custom system operation object for different business scenarios created based on the built-in physical table structure of the SaaS system, which is used to support the tenant's custom new function development.

6. A method for realizing the scalability, integration and exploration of a SaaS system based on low-code as claimed in claim 1, characterized in that: The model attribute extension and model attribute mapping of the tenant model or custom model described in step S3 are implemented through the JSON fields of the physical table structure corresponding to the current model or the physical table structure associated with the current model.

7. A method for realizing the scalability, integration and exploration of a SaaS system based on low-code as claimed in claim 1, characterized in that: The business domain model described in step S4 is imported through a visual business logic editor, and the tenant extension node of the visual business logic editor is used for the tenant's requirements for the integration and exploration of the SaaS system based on the general capabilities of the SaaS system.

8. A method for realizing the scalability, integration and exploration of a SaaS system based on low-code as claimed in claim 1, characterized in that: The business logic includes business logic control, HTTP service call, atomic service call, SQL service call, business rule call, custom function call and tenant extension node.

9. A method for realizing the scalability, integration and exploration of a SaaS system based on low-code as claimed in claim 1, characterized in that: The business domain model described in step S5 is imported through a visual page editor, and the tenant page of the visual page editor is used for the tenant's requirements for the scalability and exploration of the SaaS system page.

Images