Extensible low-code platform cross-system business integration method

Abstract

The embodiment of the disclosure discloses an extensible low-code platform cross-system business integration method, a target terminal defines a unified and standardized data model and API interface of a low-code platform integration system and a data model and API interface of an external system according to a specification of the low-code platform; the low-code platform integration system calls an API interface of the external system to obtain basic configuration data of the external system; the external system calls an API interface of the low-code platform integration system according to a synchronization rule to execute a business data synchronization task; and the target terminal integrates the basic configuration data and the business data according to a data correspondence relationship between the basic configuration data and the business data to form a complete business. The target terminal defines the unified and standardized data model and API interface, reduces the complexity and maintenance difficulty of the low-code platform integration system itself, and improves the development efficiency of using the low-code platform to perform business integration across external systems.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of computer, in particular to an extensible low-code platform cross-system business integration method. BACKGROUND

[0002] Currently, the internal business of an enterprise is complex and cannot be managed by a single system. In this case, a low-code platform is used to integrate business across external systems. In related technologies for integrating business across external systems using a low-code platform, the low-code platform needs to perform API interface adaptation processing for different external systems according to different external systems. As more and more external systems are accessed, the low-code platform needs to continuously expand the integration module to adapt to the API interfaces of different external systems, which will greatly increase the complexity and maintenance difficulty of the integration module itself. SUMMARY

[0003] The following is a summary of the subject matter of the detailed description of the present disclosure. This summary is not intended to limit the scope of protection of the claims.

[0004] The present disclosure provides an extensible low-code platform cross-system business integration method, which can reduce the workload of the low-code platform integration system in adapting to the API interfaces of different external systems, reduce the complexity and maintenance difficulty of the low-code platform integration system itself, improve the development efficiency of business integration across external systems using a low-code platform, and simplify the docking method of multiple external systems in an enterprise with a low-code platform, facilitating target object maintenance and operation of low-code platform cross-system business integration.

[0005] In an embodiment of the first aspect of the present disclosure, an extensible low-code platform cross-system business integration method is applied to a three-party synchronization system, the three-party synchronization system including a low-code platform, a low-code platform integration system, and an external system.

[0006] The extensible low-code platform cross-system business integration method includes:

[0007] The target terminal defines a unified specification of the data model and API interface of the low-code platform integration system according to the specification of the low-code platform, and defines a unified specification of the data model and API interface of the external system according to the specification of the low-code platform;

[0008] The target terminal enters the API calling address and authentication information of the external system into the low-code platform integration system, and the low-code platform integration system stores the API calling address and authentication information of the external system;

[0009] The target terminal verifies the API call address and the authentication information of the external system, and if the verification is passed, the low-code platform integration system calls the API interface of the external system to obtain the basic configuration data of the external system;

[0010] The target terminal configures the synchronization rule of the low-code platform and the business data of the external system;

[0011] The target terminal sets the format and structure of the basic configuration data of the external system, the business data of the low-code platform, and the business data of the external system transmitted by the API interface according to the unified standard data model;

[0012] The external system calls the API interface of the low-code platform integration system according to the synchronization rule to perform a business data synchronization task;

[0013] The target terminal integrates the basic configuration data of the external system and the business data of the low-code platform according to the data correspondence relationship between the basic configuration data of the external system and the business data of the low-code platform, or integrates the basic configuration data of the external system and the business data of the external system according to the data correspondence relationship between the basic configuration data of the external system and the business data of the external system, to form a complete business.

[0014] According to certain embodiments of the first aspect of the present disclosure, the low-code platform integration system calling the API interface of the external system to obtain the basic configuration data of the external system comprises:

[0015] The target terminal sets the correspondence relationship between the data form of the low-code platform and the data form of the external system, and the field mapping relationship in the data forms of the low-code platform and the external system, and the low-code platform integration system calls the API interface of the external system to obtain the basic configuration data of the external system according to the correspondence relationship between the data form of the low-code platform and the data form of the external system, and the field mapping relationship in the data forms of the low-code platform and the external system.

[0016] According to certain embodiments of the first aspect of the present disclosure, the synchronization rule includes the correspondence relationship between the data forms, the field mapping relationship in the data forms, the data flow relationship, and the execution period of the timing synchronization, and the target terminal configuring the synchronization rule of the low-code platform and the business data of the external system comprises:

[0017] The target terminal sets the correspondence between the data forms of the low-code platform and the data forms of the external system, and the field mapping relationship between the data forms of the low-code platform and the external system;

[0018] The target terminal sets the data flow relationship of the business data, and the data flow relationship of the business data specifies that the business data is synchronized from the low-code platform to the external system or from the external system to the low-code platform;

[0019] The target terminal sets the execution cycle for the timed synchronization of business data between the low-code platform and the external system.

[0020] According to certain embodiments of the first aspect of this disclosure, the external system, based on the synchronization rules, invokes the API interface of the low-code platform integration system to perform a business data synchronization task, including:

[0021] If the data flow relationship of the business data specifies that the business data is synchronized from the low-code platform to the external system, the target terminal responds to the target object's operation of triggering the business data synchronization task on the low-code platform. The low-code platform integration system then notifies the external system that the business data synchronization task needs to be executed. The external system, based on the correspondence between the data forms of the low-code platform and the data forms of the external system, and the field mapping relationship in the data forms of the low-code platform and the external system, calls the API interface of the low-code platform integration system to initiate a request to the low-code platform integration system to obtain the business data of the low-code platform. The low-code platform integration system responds to the external system's request to obtain the business data of the low-code platform by calling its internal API interface to obtain the business data of the low-code platform. Finally, the low-code platform integration system returns the business data of the low-code platform to the external system.

[0022] If the data flow relationship of the business data specifies that the business data is synchronized from the external system to the low-code platform, the target terminal responds to the operation of the target object triggering the business data synchronization task on the low-code platform. The low-code platform integration system then notifies the external system that the business data synchronization task needs to be executed. The external system, based on the correspondence between the data forms of the low-code platform and the data forms of the external system, and the field mapping relationship in the data forms of the low-code platform and the external system, calls the API interface of the low-code platform integration system to send the business data of the external system to the low-code platform integration system. The low-code platform integration system then calls its internal API interface to send the business data of the external system to the low-code platform.

[0023] According to certain embodiments of the first aspect of this disclosure, the external system, based on the synchronization rules, calls the API interface of the low-code platform integration system to perform a business data synchronization task, further comprising:

[0024] If the data flow relationship of the business data specifies that the business data is synchronized from the low-code platform to the external system, the external system monitors whether the execution cycle of the scheduled synchronization of the business data has arrived. If the execution cycle of the scheduled synchronization of the business data has arrived, the external system calls the API interface of the low-code platform integration system according to the correspondence between the data forms of the low-code platform and the data forms of the external system, and the field mapping relationship in the data forms of the low-code platform and the external system, to initiate a request to the low-code platform integration system to obtain the business data of the low-code platform. The low-code platform integration system responds to the request from the external system to obtain the business data of the low-code platform by calling the internal API interface to obtain the business data of the low-code platform. The low-code platform integration system then returns the business data of the low-code platform to the external system.

[0025] If the data flow relationship of the business data specifies that the business data is synchronized from the external system to the low-code platform, the external system monitors whether the execution cycle of the scheduled synchronization of the business data has arrived. If the execution cycle of the scheduled synchronization of the business data has arrived, the external system calls the API interface of the low-code platform integration system according to the correspondence between the data form of the low-code platform and the data form of the external system, and the field mapping relationship in the data forms of the low-code platform and the external system, to send the business data of the external system to the low-code platform integration system. The low-code platform integration system then calls the internal API interface to send the business data of the external system to the low-code platform.

[0026] According to certain embodiments of the first aspect of this disclosure, the authentication information is an account and password, or the authentication information is a key and a secret, or the authentication information is a token.

[0027] According to certain embodiments of the first aspect of this disclosure, the API interface defining the uniform specification includes:

[0028] The API interface is configured using the RESTful specification, wherein the HTTP request method of the API interface is GET, POST, PUT, or DELETE, the request parameters of the API interface are in JSON format, and the response parameters of the API interface are in either JSON or XML format.

[0029] According to certain embodiments of the first aspect of this disclosure, the low-code platform integration system includes an integration configuration module and an integration data module. The integration configuration module is used to adapt and manage the basic configuration data of the external system, and the integration data module is used to adapt the business data of the low-code platform and the external system.

[0030] According to a second aspect of this disclosure, an electronic device includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement a scalable low-code platform cross-system business integration method as described above.

[0031] According to a third aspect of this disclosure, a storage medium stores a computer program that, when executed by a processor, implements a scalable low-code platform cross-system business integration method as described above.

[0032] The embodiments disclosed herein include at least the following beneficial effects: The target terminal defines a unified and standardized data model and API interface for the low-code platform integration system according to the low-code platform specifications; the target terminal also defines a unified and standardized data model and API interface for the external system according to the low-code platform specifications; the target terminal inputs the API call address and authentication information of the external system into the low-code platform integration system, and the low-code platform integration system stores the API call address and authentication information of the external system; the target terminal verifies the API call address and authentication information of the external system; if the verification is successful, the low-code platform integration system calls the API interface of the external system to obtain the basic configuration data of the external system; the target terminal configures the business logic of the low-code platform and the external system. The system establishes data synchronization rules; the target terminal uses a unified and standardized data model to set the format and structure of the basic configuration data of the external system, the business data of the low-code platform, and the business data of the external system transmitted via API interfaces; the external system calls the API interface of the low-code platform integration system according to the synchronization rules to execute the business data synchronization task; the target terminal integrates the basic configuration data of the external system and the business data of the low-code platform one-to-one according to the data correspondence between the basic configuration data of the external system and the business data of the low-code platform, or integrates the basic configuration data of the external system and the business data of the external system one-to-one according to the data correspondence between the basic configuration data of the external system and the business data of the external system, to form a complete business. The target terminal defines a unified and standardized data model and API interface for the low-code platform integration system and the data model and API interface for the external system according to the low-code platform specifications, standardizing and normalizing the business integration work. The target object does not need to constantly modify the code to expand the low-code platform integration system to adapt to the API interfaces of different external systems, reducing the workload of adapting the low-code platform integration system to the API interfaces of different external systems, reducing the complexity and maintenance difficulty of the low-code platform integration system itself, and improving the development efficiency of using the low-code platform for cross-external system business integration. Furthermore, it simplifies the integration of multiple external systems within an enterprise with the low-code platform, making it easier for target users to maintain and operate the low-code platform for cross-external system business integration. Additionally, the target terminal uses a unified and standardized data model to configure the format and structure of basic configuration data from external systems transmitted via API interfaces, as well as business data from the low-code platform. This enables seamless integration and interaction of basic configuration data and business data between different external systems within the low-code platform, improving its data processing efficiency.

[0033] Other features and advantages of this disclosure will be set forth in the following description and will be apparent in part from the description or may be learned by practicing this disclosure. Attached Figure Description

[0034] The accompanying drawings are provided to further understand the technical solutions of this disclosure and constitute a part of the specification. They are used together with the embodiments of this disclosure to explain the technical solutions of this disclosure and do not constitute a limitation on the technical solutions of this disclosure.

[0035] Figure 1 An optional flowchart for a scalable low-code platform cross-system business integration method provided in this disclosure embodiment;

[0036] Figure 2 An optional flowchart for a scalable low-code platform cross-system business integration method provided in this disclosure embodiment;

[0037] Figure 3 This is a schematic diagram of a three-party synchronization system provided in an embodiment of this disclosure. Detailed Implementation

[0038] To make the objectives, technical solutions, and advantages of this disclosure clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and are not intended to limit the scope of this disclosure.

[0039] It should be noted that in the various specific embodiments of this disclosure, when processing is required based on data related to the characteristics of the target object, such as target object attribute information or a set of attribute information, the permission or consent of the target object will be obtained first. Furthermore, the collection, use, and processing of this data will comply with relevant laws, regulations, and standards. The target object can be a user. In addition, when embodiments of this disclosure require obtaining target object attribute information, separate permission or consent from the target object will be obtained through pop-ups or redirection to a confirmation page. Only after obtaining the target object's separate permission or consent will the necessary target object-related data for the normal operation of the embodiments of this disclosure be obtained.

[0040] In this disclosure, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0041] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. The terminology used herein is for the purpose of describing embodiments of this disclosure only and is not intended to be limiting of this disclosure.

[0042] To facilitate understanding of the technical solutions provided in the embodiments of this disclosure, some key terms used in the embodiments of this disclosure will be explained below:

[0043] An Application Programming Interface (API) is a set of predefined functions designed to provide applications and developers with the ability to access a set of routines based on certain software or hardware, without needing to access the source code or understand the details of the internal workings.

[0044] Representational State Transfer (REST) ​​is a new architectural style for web services. RESTful is a common application of REST, and it refers to web services that follow the REST style.

[0045] The Hypertext Transfer Protocol (HTTP) is a simple request-response protocol and an application layer protocol. Like other application layer protocols, it is a protocol designed to implement a specific type of application, and its functionality is implemented by an application running in user space.

[0046] JavaScript Object Notation (JSON) is an open standard file and data exchange format that is easy for humans to read and write, and also easy for machines to parse and generate.

[0047] Extensible Markup Language (XML) is a subset of Standard Generalized Markup Language (SGML). It can be used to mark up data and define data types. It is a source language that allows users to define their own markup language.

[0048] The embodiments of this disclosure will be further described below with reference to the accompanying drawings.

[0049] This disclosure provides a scalable low-code platform cross-system business integration method, applied to a three-party synchronization system, which includes a low-code platform, a low-code platform integration system, and an external system. (Refer to...) Figure 3 As shown, Figure 3This diagram illustrates a three-way synchronization system provided in an embodiment of this disclosure. Specifically, enterprise internal business processes are complex, involving services from multiple external systems. Each external system can only provide a portion of the enterprise's services, necessitating the integration of these external systems with a low-code platform. Low-code is a software development methodology that minimizes manual coding, enabling faster application building and deployment. A low-code platform provides a set of visual tools and components, allowing users to create applications through drag-and-drop, configuration, and property settings. It is a development platform that allows for rapid application generation with little or no coding. The low-code platform integration system can be used to adapt and manage configuration data, as well as to adapt business data from the low-code platform and external systems. This configuration data can be directly obtained basic configuration data from external systems or custom configuration data defined by the target user. The target user can be an IT expert or a general business user.

[0050] Reference Figure 1 As shown, Figure 1 This is an optional flowchart of a scalable low-code platform cross-system business integration method provided in this disclosure embodiment. The scalable low-code platform cross-system business integration method includes, but is not limited to, steps 101 to 107, which are described in turn below.

[0051] Step 101: The target terminal defines a unified and standardized data model and API interface for the low-code platform integration system, and defines a unified and standardized data model and API interface for the external system, in accordance with the low-code platform specifications.

[0052] Specifically, the low-code platform establishes a set of specifications. The target terminal defines the data models and API interfaces of the low-code platform integrated system and external systems according to these specifications, resulting in a unified and standardized data model and API interface for both the low-code platform integrated system and external systems. In essence, the target terminal defines the data models and API interfaces of multiple external systems as a unified standard.

[0053] In some embodiments, defining a unified API interface includes: setting up the API interface using the RESTful specification, wherein the HTTP request method of the API interface uses GET, POST, PUT, and DELETE, the request parameters of the API interface use JSON format, and the response parameters of the API interface use JSON or XML format.

[0054] Specifically, GET indicates retrieving resources, POST indicates creating resources, PUT indicates updating resources on the server and providing all changed resources to the client, and DELETE indicates deleting resources. Using the RESTful specification to design API interfaces, the HTTP request methods of the API interfaces use GET, POST, PUT, and DELETE to represent operations on resources, providing clear semantics and making the API interface design more intuitive and easier to understand. API request parameters use JSON format, and API response parameters use either JSON or XML format. Using the same format allows for seamless interaction between the API interface and the basic configuration data of external systems, business data of low-code platforms, and business data of external systems, improving data processing efficiency.

[0055] Step 102: The target terminal enters the API call address and authentication information of the external system into the low-code platform integration system, and the low-code platform integration system stores the API call address and authentication information of the external system.

[0056] Specifically, the target terminal inputs the API call addresses and authentication information of multiple external systems into the low-code platform integration system. The low-code platform integration system stores these API call addresses and authentication information. Each external system's API interface has a corresponding API call address and authentication information. The low-code platform integration system stores these API call addresses and authentication information so that the target terminal can directly read and verify the stored API call addresses and authentication information of the corresponding external system's API interface, thereby enabling it to call the external system's API interface.

[0057] Step 103: The target terminal verifies the API call address and authentication information of the external system. If the verification is successful, the low-code platform integration system calls the API interface of the external system to obtain the basic configuration data of the external system.

[0058] Specifically, after the low-code platform integration system stores the API call address and authentication information of the external system's API interface, when the low-code platform integration system needs to call the external system's API interface, the target terminal verifies the stored API call address and authentication information of the external system's API interface. If the verification is successful, the low-code platform integration system has the permission to call the external system's API interface. Then, the low-code platform integration system calls the external system's API interface to obtain the external system's basic configuration data.

[0059] Understandably, the target terminal verifies the API call addresses and authentication information of multiple external systems' API interfaces. If the verification is successful, the low-code platform integration system calls the API interfaces of multiple external systems to obtain the basic configuration data of multiple external systems.

[0060] In some embodiments, the authentication information is an account and password, or the authentication information is a key and a secret, or the authentication information is a token.

[0061] Specifically, if the API call address of the external system's API interface is verified and the authentication information of the external system's API interface is also verified, then the low-code platform integration system has the authority to call the external system's API interface and can call the external system's API interface to obtain the external system's basic configuration data.

[0062] If the authentication information for the external system's API interface is username and password, this is the most commonly used authentication method in the daily lives of the target audience, especially when the target audience consists of ordinary business personnel. They have a high degree of familiarity and acceptance with it, and can quickly understand how to use the API interface, thus improving the development efficiency of integrating multiple external systems using a low-code platform. For external systems, using usernames and passwords facilitates user management and permission allocation in the backend management system.

[0063] If the authentication information for an external system's API interface is a key and a secret, and these keys and secrets are relatively long and complex, they are more difficult for hackers to brute-force, thus improving the security of the external system's API interface authentication. Furthermore, combining the key and secret for API interface authentication further enhances the security of the external system's API interface authentication.

[0064] If the authentication information of the external system's API interface is a token, the token is an effective means of preventing cross-site request forgery (CSRF) attacks. It is difficult for hackers to forge a valid token, and using a token for the authentication information of the external system's API interface can improve the security of the external system's API interface authentication.

[0065] In some embodiments, the low-code platform integration system calls the API interface of an external system to obtain basic configuration data of the external system, including: the target terminal sets the correspondence between the data form of the low-code platform and the data form of the external system, and the field mapping relationship in the data forms of the low-code platform and the external system; the low-code platform integration system calls the API interface of the external system to obtain basic configuration data of the external system based on the correspondence between the data forms of the low-code platform and the data forms of the external system, and the field mapping relationship in the data forms of the low-code platform and the external system.

[0066] Specifically, the low-code platform integration system uses the mapping relationship between the data forms of the low-code platform and the data forms of the external system, as well as the field mapping relationship in the data forms of the low-code platform and the external system, to call the API interface of the external system to obtain the basic configuration data of the external system. The target terminal can obtain the entire dataset of basic configuration data from the external system, or it can select the required data forms and data fields from the basic configuration data of the external system according to the needs of the enterprise's business, without having to obtain the entire dataset, thus improving data flexibility. Furthermore, by setting the mapping relationship between the data forms and the field mapping relationship in the data forms to obtain the basic configuration data from the external system, the target terminal can improve the accuracy and consistency of obtaining the basic configuration data from the external system.

[0067] Step 104: Configure synchronization rules for business data between the low-code platform and external systems on the target terminal.

[0068] Specifically, the target terminal is configured with synchronization rules for business data between the low-code platform and external systems to perform business data synchronization tasks.

[0069] In some embodiments, the synchronization rules include the correspondence of data forms, the field mapping relationship in the data forms, the data flow relationship, and the execution cycle of timed synchronization. The synchronization rules for business data between the target terminal's low-code platform and external systems include:

[0070] The target terminal sets up the correspondence between the data forms of the low-code platform and the data forms of the external system, as well as the field mapping relationship between the data forms of the low-code platform and the external system;

[0071] The target terminal sets the data flow relationship of business data, which specifies whether business data is synchronized from the low-code platform to the external system or from the external system to the low-code platform.

[0072] The target terminal is configured to schedule the synchronization of business data between the low-code platform and external systems.

[0073] Understandably, by setting up the mapping relationships between data forms on the low-code platform and data forms in external systems, as well as the field mapping relationships within these data forms, the target terminal can obtain the entire dataset of business data from either the low-code platform or the external system. Alternatively, it can select the necessary data forms and fields from the business data of the low-code platform or the external system based on the enterprise's business needs, without having to obtain the entire dataset, thus improving data flexibility. Furthermore, setting up the mapping relationships between data forms and their fields to obtain business data from the low-code platform or external system improves the accuracy and consistency of the obtained business data.

[0074] Understandably, the target terminal sets the data flow relationship of business data, specifying whether business data is synchronized from the low-code platform to an external system or from an external system to the low-code platform. Business data on the low-code platform can be synchronized from the low-code platform to the external system, and vice versa. This allows business data on both the low-code platform and the external system to be synchronized, improving data accuracy and consistency. Furthermore, the synchronization of business data between the low-code platform and the external system can also be understood as backing up business data on both the low-code platform and the external system. Even if one of the low-code platform or the external system fails, data can be restored from the other backup, reducing the risk of data loss.

[0075] It is understood that the execution cycle for the scheduled synchronization of business data between the low-code platform and external systems can be one day or one week. This can be set according to actual needs, and this embodiment does not impose specific limitations. Specifically, the business data synchronization task is executed according to the scheduled synchronization cycle between the low-code platform and external systems. The target object can flexibly set different times to synchronize business data according to the enterprise's business needs, improving the flexibility of business data synchronization. Furthermore, after the target terminal sets the scheduled synchronization cycle for business data between the low-code platform and external systems, the external system automatically synchronizes the business data between the low-code platform and external systems, reducing the time spent on manual operations by the target object and improving the efficiency of business data synchronization.

[0076] Step 105: The target terminal uses a unified and standardized data model to set the format and structure of the basic configuration data of the external system, the business data of the low-code platform, and the business data of the external system transmitted through the API interface.

[0077] Specifically, the target terminal uses a unified and standardized data model to set the format and structure of the basic configuration data of the external system, the business data of the low-code platform, and the business data of the external system transmitted through the API interface. This enables seamless connection and interaction of basic configuration data and business data between different external systems within the low-code platform, thereby improving the data processing efficiency of the low-code platform.

[0078] Step 106: The external system calls the API interface of the low-code platform integration system according to the synchronization rules to execute the business data synchronization task.

[0079] Specifically, business data synchronization tasks can be executed periodically by the target terminal, or they can be manually triggered by the target object to be executed by the target terminal.

[0080] In some embodiments, the external system, according to synchronization rules, calls the API interface of the low-code platform integration system to perform business data synchronization tasks, including:

[0081] If the data flow relationship of the business data specifies that the business data is synchronized from the low-code platform to the external system, the target terminal responds to the operation of triggering a business data synchronization task on the low-code platform. When the business data synchronization task is triggered on the low-code platform, the low-code platform integration system notifies the external system that the business data synchronization task needs to be executed. The external system, based on the correspondence between the data forms of the low-code platform and the data forms of the external system, and the field mapping relationship in the data forms of the low-code platform and the external system, calls the API interface of the low-code platform integration system to initiate a request to obtain the business data from the low-code platform. The low-code platform integration system responds to the external system's request to obtain the business data from the low-code platform by calling its internal API interface to retrieve the business data from the low-code platform. Finally, the low-code platform integration system returns the business data from the low-code platform to the external system.

[0082] If the data flow relationship of the business data specifies that the business data is synchronized from the external system to the low-code platform, the target terminal responds to the operation of triggering the business data synchronization task on the low-code platform. When the business data synchronization task is triggered on the low-code platform, the low-code platform integration system notifies the external system that the business data synchronization task needs to be executed. The external system calls the API interface of the low-code platform integration system according to the correspondence between the data forms of the low-code platform and the data forms of the external system, and the field mapping relationship in the data forms of the low-code platform and the external system, to send the business data of the external system to the low-code platform integration system. The low-code platform integration system then calls the internal API interface to send the business data of the external system to the low-code platform.

[0083] Specifically, the target terminal obtains business data from the low-code platform or external system based on the correspondence of the set data forms and the field mapping relationships in the data forms, which can improve the accuracy and consistency of obtaining business data from the low-code platform or external system.

[0084] Understandably, the initiative to execute business data synchronization tasks is handed over to external systems. Instead of the low-code platform being responsible for executing multiple business data synchronization tasks with external systems, multiple external systems are responsible for executing business data synchronization tasks with the low-code platform, which improves the efficiency of business data synchronization between multiple external systems within the enterprise and the low-code platform.

[0085] In some embodiments, the external system calls the API interface of the low-code platform integration system to perform business data synchronization tasks according to synchronization rules, and further includes:

[0086] If the data flow relationship of the business data specifies that the business data is synchronized from the low-code platform to the external system, the external system monitors whether the scheduled synchronization execution cycle of the business data has arrived. If the scheduled synchronization execution cycle of the business data arrives, the external system calls the API interface of the low-code platform integration system based on the correspondence between the data forms of the low-code platform and the data forms of the external system, and the field mapping relationship in the data forms of the low-code platform and the external system, and initiates a request to the low-code platform integration system to obtain the business data of the low-code platform; the low-code platform integration system responds to the request from the external system to obtain the business data of the low-code platform by calling the internal API interface to obtain the business data of the low-code platform; the low-code platform integration system returns the business data of the low-code platform to the external system;

[0087] If the data flow relationship of the business data specifies that the business data is synchronized from the external system to the low-code platform, the external system monitors whether the scheduled synchronization execution cycle of the business data has arrived. If the scheduled synchronization execution cycle of the business data has arrived, the external system calls the API interface of the low-code platform integration system according to the correspondence between the data forms of the low-code platform and the data forms of the external system, and the field mapping relationship in the data forms of the low-code platform and the external system, to send the business data of the external system to the low-code platform integration system. The low-code platform integration system then calls the internal API interface to send the business data of the external system to the low-code platform.

[0088] Understandably, by using the established data form mappings and field relationships to retrieve business data from the low-code platform or external systems, the target terminal can improve the accuracy and consistency of this data retrieval. Furthermore, the initiative to execute business data synchronization tasks is delegated to the external systems. Instead of the low-code platform handling multiple synchronization tasks with external systems, multiple external systems handle the synchronization with the low-code platform, thus improving the efficiency of business data synchronization between multiple external systems and the low-code platform within the enterprise.

[0089] Specifically, business data synchronization tasks can be executed by the target terminal on a scheduled basis, or they can be manually triggered by the target object to be executed by the target terminal, which improves the flexibility of synchronizing business data.

[0090] In some embodiments, the low-code platform integration system includes an integration configuration module and an integration data module. The integration configuration module is used to adapt and manage basic configuration data of external systems, and the integration data module is used to adapt business data of the low-code platform and external systems.

[0091] Specifically, the integrated configuration module and the integrated data module form the adaptation layer. The integrated configuration module is responsible for adapting and managing the basic configuration data of external systems, while the integrated data module is responsible for adapting the business data of the low-code platform and external systems. The adaptation layer can convert data from one format to another to adapt to different storage or transmission requirements, helping to optimize data storage and transmission efficiency and reduce data redundancy and unnecessary processing. The adaptation layer can also perform validation and filtering during data transmission, improving data accuracy and integrity, helping to reduce the overhead of data error and anomaly handling, and improving the stability and reliability of external systems and the low-code platform.

[0092] Step 107: The target terminal integrates the basic configuration data of the external system and the business data of the low-code platform one by one according to the data correspondence between the basic configuration data of the external system and the business data of the low-code platform, or integrates the basic configuration data of the external system and the business data of the external system one by one according to the data correspondence between the basic configuration data of the external system and the business data of the external system, to form a complete service.

[0093] As can be seen, the target terminal defines a unified and standardized data model and API interface for the low-code platform integration system, and also defines a unified and standardized data model and API interface for the external system, in accordance with the low-code platform specifications. The target terminal inputs the API call address and authentication information of the external system into the low-code platform integration system, which stores this information. The target terminal verifies the API call address and authentication information of the external system; if verification is successful, the low-code platform integration system calls the external system's API interface to obtain its basic configuration data. The target terminal configures the synchronization rules for the business data between the low-code platform and the external system. The target terminal uses the unified and standardized data model to set the format and structure of the external system's basic configuration data, the low-code platform's business data, and the external system's business data transmitted via the API interface. The external system, according to the synchronization rules, calls the low-code platform integration system's API interface to execute the business data synchronization task. The target terminal integrates the external system's basic configuration data and the low-code platform's business data one-to-one according to the data correspondence between them, or integrates the external system's basic configuration data and the external system's business data one-to-one according to the data correspondence between them, to form a complete business process. The target terminal, adhering to the low-code platform specifications, defines a unified and standardized data model and API interface for the low-code platform integration system, as well as for external systems. This standardizes and normalizes business integration, eliminating the need for continuous code modifications to extend the low-code platform integration system to adapt to different external system API interfaces. This reduces the workload of adapting the low-code platform integration system to various external system API interfaces, lowers the complexity and maintenance difficulty of the low-code platform integration system itself, and improves the development efficiency of cross-external system business integration using the low-code platform. Furthermore, it simplifies the interface between multiple internal external systems and the low-code platform, facilitating the maintenance and operation of cross-external system business integration using the low-code platform. Additionally, the target terminal uses a unified and standardized data model to set the format and structure of basic configuration data from external systems, business data from the low-code platform, and business data from external systems transmitted via API interfaces. This enables seamless integration and interaction of basic configuration data and business data between different external systems within the low-code platform, improving the data processing efficiency of the low-code platform.

[0094] In some embodiments, the target terminal defines a unified data model and API interface for the low-code platform integration system, and a unified data model and API interface for the external system, according to the low-code platform specifications. The target terminal configures synchronization rules for business data between the low-code platform and the external system, including: setting a correspondence between data forms on the low-code platform and data forms on the external system, and a field mapping relationship between the data forms on the low-code platform and the external system, so that the external system can call the API interface of the low-code platform integration system to obtain business data from the low-code platform or send business data from the external system to the low-code platform based on the correspondence between the data forms on the low-code platform and the field mapping relationship; setting a data flow relationship for business data, specifying whether business data is synchronized from the low-code platform to the external system or from the external system to the low-code platform; and setting the execution cycle for the timed synchronization of business data between the low-code platform and the external system. The target terminal uses a unified data model to set the format and structure of the basic configuration data of the external system, the business data of the low-code platform, and the business data of the external system transmitted through the API interface. (Refer to...) Figure 2 As shown, Figure 2 This is an optional flowchart of a scalable low-code platform cross-system business integration method provided in an embodiment of the present disclosure. The scalable low-code platform cross-system business integration method may include, but is not limited to, steps 201 to 211, which will be described in turn below.

[0095] Step 201: The target object enters the API call address and authentication information of the external system into the low-code platform integration system.

[0096] Step 202: The low-code platform integrates the system with the external system's API call addresses and authentication information.

[0097] Step 203: Set the correspondence between the data forms of the low-code platform and the data forms of the external system in the target object, and the field mapping relationship between the data forms of the low-code platform and the external system.

[0098] Step 204: The low-code platform integration system calls the API interface of the external system to obtain the basic configuration data of the external system based on the correspondence between the data forms of the low-code platform and the data forms of the external system, and the field mapping relationship in the data forms of the low-code platform and the external system.

[0099] Step 205: The target object triggers a business data synchronization task on the low-code platform.

[0100] Step 206: The low-code platform integration system notifies the external system that a business data synchronization task needs to be performed.

[0101] Step 207: The external system calls the API interface of the low-code platform integration system to obtain business data from the low-code platform or sends business data from the external system to the low-code platform.

[0102] Step 208: The low-code platform integration system responds by calling the internal API interface to obtain business data from the low-code platform and return it to the external system, or by sending business data from the external system to the low-code platform.

[0103] Step 209: Has the scheduled synchronization period for external system monitoring business data arrived?

[0104] Step 210: When the scheduled synchronization execution cycle arrives, the external system calls the API interface of the low-code platform integration system to obtain business data from the low-code platform or send business data from the external system to the low-code platform.

[0105] Step 211: The low-code platform integration system responds by calling the internal API interface to obtain business data from the low-code platform and return it to the external system, or by sending business data from the external system to the low-code platform.

[0106] It is understandable that the target terminal integrates the basic configuration data of the external system and the business data of the low-code platform one by one according to the data correspondence between the basic configuration data of the external system and the business data of the low-code platform, or integrates the basic configuration data of the external system and the business data of the external system one by one according to the data correspondence between the basic configuration data of the external system and the business data of the external system to form a complete business.

[0107] This disclosure also provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the aforementioned scalable low-code platform cross-system business integration method. This electronic device can be any smart terminal, including computers.

[0108] This disclosure also provides a storage medium storing a computer program that, when executed by a processor, implements the aforementioned scalable low-code platform cross-system business integration method.

[0109] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in this disclosure and the foregoing drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate to describe embodiments of this disclosure, for example, those that can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatuses.

[0110] It should be understood that in this disclosure, "at least one item" means one or more, and "more than one" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0111] It should be understood that in the description of the embodiments disclosed herein, "multiple" means two or more, "greater than", "less than", "exceeding" etc. are understood to exclude the number itself, and "above", "below", "within" etc. are understood to include the number itself.

[0112] It should also be understood that the various implementation methods provided in this disclosure can be combined arbitrarily to achieve different technical effects.

[0113] The above is a detailed description of the preferred embodiments of this disclosure. However, this disclosure is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of this disclosure. All such equivalent modifications or substitutions are included within the scope defined by the claims of this disclosure.

Claims

1. A scalable low-code platform cross-system business integration method, characterized in that, The application is applied to a three-party synchronization system, the three-party synchronization system includes a low-code platform, a low-code platform integration system, and an external system; The extensible low-code platform cross-system business integration method includes: The target terminal defines a unified specification of a data model and an API interface of the low-code platform integration system according to a specification of the low-code platform, and defines a unified specification of the data model and the API interface of the external system according to the specification of the low-code platform; The target terminal enters an API calling address and authentication information of the external system into the low-code platform integration system, and the low-code platform integration system stores the API calling address and the authentication information of the external system; The target terminal verifies the API calling address and the authentication information of the external system, and if the verification is passed, the low-code platform integration system calls the API interface of the external system to obtain basic configuration data of the external system; The target terminal configures a synchronization rule of business data of the low-code platform and the external system; The target terminal sets a format and a structure of the basic configuration data of the external system, the business data of the low-code platform, and the business data of the external system transmitted by the API interface using the unified specification of the data model; The external system calls the API interface of the low-code platform integration system according to the synchronization rule, and performs a business data synchronization task; The target terminal integrates the basic configuration data of the external system and the business data of the low-code platform according to a data correspondence relationship between the basic configuration data of the external system and the business data of the low-code platform, or integrates the basic configuration data of the external system and the business data of the external system according to a data correspondence relationship between the basic configuration data of the external system and the business data of the external system, to form complete business; The synchronization rule includes a correspondence relationship of data forms, a field mapping relationship in the data forms, a data flow direction relationship, and an execution period of timed synchronization, and the target terminal configuring the synchronization rule of the business data of the low-code platform and the external system includes: The target terminal sets the correspondence relationship of the data forms of the low-code platform and the data forms of the external system, and the field mapping relationship in the data forms of the low-code platform and the external system; The target terminal sets the data flow direction relationship of the business data, and the data flow direction relationship of the business data specifies that the business data is synchronized from the low-code platform to the external system or from the external system to the low-code platform; The target terminal sets the execution period of the timed synchronization of the business data of the low-code platform and the external system.

2. The extensible low-code platform cross-system business integration method of claim 1, wherein, The low-code platform integration system calling the API interface of the external system to obtain the basic configuration data of the external system includes: The target terminal sets the correspondence relationship of the data form of the low-code platform and the data form of the external system, the field mapping relationship in the data form of the low-code platform and the external system, and the low-code platform integration system calls the API interface of the low-code platform integration system according to the correspondence relationship of the data form of the low-code platform and the data form of the external system, and the field mapping relationship in the data form of the low-code platform and the external system to obtain the basic configuration data of the external system.

3. The method of claim 1, wherein the extensible low-code platform cross-system business integration method is characterized by, The external system calls the API interface of the low-code platform integration system according to the synchronization rule to perform a business data synchronization task, including: If the data flow direction relationship of the business data specifies that the business data is synchronized from the low-code platform to the external system, the target terminal triggers the business data synchronization task on the low-code platform in response to the operation of the target object triggering the business data synchronization task on the low-code platform, the low-code platform integration system notifies the external system that the business data synchronization task needs to be performed, the external system calls the API interface of the low-code platform integration system according to the correspondence relationship of the data form of the low-code platform and the data form of the external system, and the field mapping relationship in the data form of the low-code platform and the external system to initiate a request to the low-code platform integration system for obtaining the business data of the low-code platform; the low-code platform integration system calls the internal API interface to obtain the business data of the low-code platform in response to the request of the external system for obtaining the business data of the low-code platform; and the low-code platform integration system returns the business data of the low-code platform to the external system; If the data flow direction relationship of the business data specifies that the business data is synchronized from the external system to the low-code platform, the target terminal triggers the business data synchronization task on the low-code platform in response to the operation of the target object triggering the business data synchronization task on the low-code platform, the low-code platform integration system notifies the external system that the business data synchronization task needs to be performed, the external system calls the API interface of the low-code platform integration system according to the correspondence relationship of the data form of the low-code platform and the data form of the external system, and the field mapping relationship in the data form of the low-code platform and the external system to send the business data of the external system to the low-code platform integration system, and the low-code platform integration system calls the internal API interface to send the business data of the external system to the low-code platform.

4. The extensible low-code platform cross-system business integration method of claim 1, wherein, The external system calls the API interface of the low-code platform integration system according to the synchronization rule to perform a business data synchronization task, and further includes: If the data flow direction relationship of the business data specifies that the business data is synchronized from the low-code platform to the external system, the external system monitors whether the execution period of the timing synchronization of the business data arrives, if the execution period of the timing synchronization of the business data arrives, the external system calls the API interface of the low-code platform integration system according to the correspondence relationship between the data form of the low-code platform and the data form of the external system, the field mapping relationship in the data form of the low-code platform and the external system, initiates a request to the low-code platform integration system to obtain the business data of the low-code platform; the low-code platform integration system responds to the request of the external system to obtain the business data of the low-code platform, calls the internal API interface to obtain the business data of the low-code platform; the low-code platform integration system returns the business data of the low-code platform to the external system; If the data flow direction relationship of the business data specifies that the business data is synchronized from the external system to the low-code platform, the external system monitors whether the execution period of the timing synchronization of the business data arrives, if the execution period of the timing synchronization of the business data arrives, the external system calls the API interface of the low-code platform integration system according to the correspondence relationship between the data form of the low-code platform and the data form of the external system, the field mapping relationship in the data form of the low-code platform and the external system, sends the business data of the external system to the low-code platform integration system, and the low-code platform integration system calls the internal API interface to send the business data of the external system to the low-code platform.

5. The extensible low-code platform cross-system business integration method of claim 1, wherein, The authentication information is an account and a password, or the authentication information is a key and a secret, or the authentication information is a token.

6. The extensible low-code platform cross-system business integration method of claim 1, wherein, The API interface defined in the uniform specification includes: The API interface is set using the RESTful specification, wherein the HTTP request mode of the API interface uses GET, POST, PUT, and DELETE, the request parameter of the API interface uses the JSON format, and the response parameter of the API interface uses the JSON format or the XML format.

7. The extensible low-code platform cross-system business integration method of claim 1, wherein, The low-code platform integration system includes an integration configuration module and an integration data module, the integration configuration module is used to adaptively manage the basic configuration data of the external system, and the integration data module is used to adaptively manage the business data of the low-code platform and the external system.

8. An electronic device, comprising: The electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the method when executing the computer program.

9. A storage medium storing a computer program, characterized by The computer program is executed by the processor to implement the method.

Images