Document docking method, device and computer equipment for business system

Abstract

The present application relates to a document docking method, device, computer equipment, storage medium and computer program product for a business system. The method includes: obtaining a first interface component belonging to a first business system and a first standard model corresponding to a first business type, combining the first interface component and the first standard model to obtain a first conversion component; obtaining a second interface component belonging to a second business system and a second standard model corresponding to a second business type, combining the second interface component and the second standard model to obtain a second conversion component; constructing a standard conversion component based on the first standard model and the second standard model; generating a target plug-in based on the first conversion component, the standard conversion component and the second conversion component. The method can be used to automatically dock business systems without manually writing corresponding logic programs, thereby improving the efficiency of business process processing.

Description

Technical Field

[0001] The present application relates to the field of computer network technology, and in particular to a document docking method, device, computer equipment, storage medium and computer program product for a business system. Background Art

[0002] With the development of enterprises, cooperation between enterprises is becoming more and more frequent. In the process of advancing business processes, it is often necessary to connect the business systems of two or more enterprises.

[0003] However, different enterprises often have their own business systems. If the existing technology is used to write a corresponding logic program for each business system to connect the systems two by two, it will consume considerable human resources and system resources.

[0004] As enterprises have an increasing demand for the automation of business processes, how to achieve automated docking between different business systems is a problem that needs to be solved urgently. Summary of the invention

[0005] Based on this, it is necessary to provide a document docking method, device, computer equipment, computer-readable storage medium and computer program product for a business system that can automatically dock with a business system in response to the above technical problems.

[0006] In a first aspect, the present application provides a document docking method for a business system. The method comprises:

[0007] Acquire a first interface component belonging to a first business system and a first standard model corresponding to a first business type, and combine the first interface component and the first standard model to obtain a first conversion component;

[0008] Acquire a second interface component belonging to a second business system and a second standard model corresponding to a second business type, and combine the second interface component and the second standard model to obtain a second conversion component;

[0009] Based on the first standard model and the second standard model, construct a standard conversion component;

[0010] A target plug-in is generated based on the first conversion component, the standard conversion component, and the second conversion component; the target plug-in is used to generate a second document of a second business type in a second business system based on a first document of a first business type in a first business system.

[0011] In one embodiment, the first interface component includes at least a system login interface and a data reading interface of the first business system, and the second interface component includes at least a system login interface and a data writing interface of the second business system; the method further includes a step of executing the target plug-in, and the step of executing the target plug-in includes:

[0012] Calling a system login interface corresponding to the first business system to perform a login operation, and acquiring a first document belonging to the first business type by calling a data reading interface after login;

[0013] Obtaining a document conversion instruction, and based on the document conversion instruction, calling a first standard model in a first conversion component to convert the first document into a first standard document;

[0014] Calling a standard conversion component to convert the first standard document into a second standard document corresponding to a second business type;

[0015] Calling a second standard model in a second conversion component to convert the second standard document into a second document applicable to a second business system;

[0016] The system login interface corresponding to the second business system is called to perform a login operation, and after login, the second document is output in the second business system by calling a data writing interface corresponding to the second business system.

[0017] In one embodiment, the first interface component is used to standardize the parameters input into the first business system to adapt to the parameter format specified by the first standard model; the second interface component is used to customize the parameters output by the second standard model to adapt to the parameter format specified by the second business system.

[0018] In one embodiment, the method further comprises:

[0019] Determine and store a relationship mapping table between a target plug-in and corresponding multiple conversion components; and, when executing the target plug-in, select and call a target conversion component associated with the target plug-in from multiple components stored in a database according to the relationship mapping table; wherein the target conversion component includes a first conversion component, a standard conversion component, and a second conversion component.

[0020] In one embodiment, the method is applied to a business management platform provided with a graphical configuration interface; the graphical configuration interface is used to modularly display the components and the connection relationships between the components, and edit the connection relationships between the components based on graphic editing operations and display them in real time; wherein the graphic editing operations include at least one of a selection operation, a drag operation, and a connection operation.

[0021] In one embodiment, combining the first interface component and the first standard model to obtain a first conversion component includes:

[0022] Displaying a first graphic control of the first interface component and a second graphic control of the first standard model in the graphical configuration interface;

[0023] Obtaining first component configuration information through a code editing interface in the graphical configuration interface;

[0024] In response to a connection operation for the first graphic control and the second graphic control, the first interface component and the first standard model are combined according to the first component configuration information to obtain a first conversion component.

[0025] In one embodiment, combining the second interface component and the second standard model to obtain the second conversion component includes:

[0026] Displaying a third graphic control of the second interface component and a fourth graphic control of the second standard model in the graphical configuration interface;

[0027] Obtaining second component configuration information through a code editing interface in the graphical configuration interface;

[0028] In response to the connection operation for the third graphic control and the fourth graphic control, the second interface component and the second standard model are combined according to the second component configuration information to obtain a second conversion component.

[0029] In one embodiment, constructing a standard conversion component based on the first standard model and the second standard model includes:

[0030] In response to the connection operation for the second graphic control and the fourth graphic control, the first standard model and the second standard model are docked to obtain a standard conversion component.

[0031] In one of the embodiments, the graphical configuration interface includes at least a component option area, a graphic editing area, and a property editing area; the component option area is used to display at least one component to be edited, so that the user can perform graphic editing operations in the graphic editing area; the graphic editing area is used to display the selected component in real time, so that the user can edit the connection relationship between the components; the property editing area is used for the user to edit the property information corresponding to the selected component; wherein, the component option area displays at least one of a system interface component, a data source component, a process control component, and a standard model component.

[0032] In a second aspect, the present application also provides a document docking device for a business system. The device comprises:

[0033] A combination module, used to obtain a first interface component belonging to a first business system and a first standard model corresponding to a first business type, and combine the first interface component and the first standard model to obtain a first conversion component;

[0034] The combining module is further used to obtain a second interface component belonging to a second business system and a second standard model corresponding to a second business type, and combine the second interface component and the second standard model to obtain a second conversion component;

[0035] A construction module, configured to construct a standard conversion component based on the first standard model and the second standard model;

[0036] A generation module is used to generate a target plug-in based on the first conversion component, the standard conversion component, and the second conversion component; the target plug-in is used to generate a second document of a second business type in a second business system based on a first document of a first business type in a first business system.

[0037] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:

[0038] Acquire a first interface component belonging to a first business system and a first standard model corresponding to a first business type, and combine the first interface component and the first standard model to obtain a first conversion component;

[0039] Acquire a second interface component belonging to a second business system and a second standard model corresponding to a second business type, and combine the second interface component and the second standard model to obtain a second conversion component;

[0040] Based on the first standard model and the second standard model, construct a standard conversion component;

[0041] A target plug-in is generated based on the first conversion component, the standard conversion component, and the second conversion component; the target plug-in is used to generate a second document of a second business type in a second business system based on a first document of a first business type in a first business system.

[0042] In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0043] Acquire a first interface component belonging to a first business system and a first standard model corresponding to a first business type, and combine the first interface component and the first standard model to obtain a first conversion component;

[0044] Acquire a second interface component belonging to a second business system and a second standard model corresponding to a second business type, and combine the second interface component and the second standard model to obtain a second conversion component;

[0045] Based on the first standard model and the second standard model, construct a standard conversion component;

[0046] A target plug-in is generated based on the first conversion component, the standard conversion component, and the second conversion component; the target plug-in is used to generate a second document of a second business type in a second business system based on a first document of a first business type in a first business system.

[0047] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0048] Acquire a first interface component belonging to a first business system and a first standard model corresponding to a first business type, and combine the first interface component and the first standard model to obtain a first conversion component;

[0049] Acquire a second interface component belonging to a second business system and a second standard model corresponding to a second business type, and combine the second interface component and the second standard model to obtain a second conversion component;

[0050] Based on the first standard model and the second standard model, construct a standard conversion component;

[0051] A target plug-in is generated based on the first conversion component, the standard conversion component, and the second conversion component; the target plug-in is used to generate a second document of a second business type in a second business system based on a first document of a first business type in a first business system.

[0052] The document docking method, device, computer equipment, storage medium and computer program product of the above-mentioned business system combine the interface components corresponding to each business system and the standard models corresponding to the corresponding business types according to the business types executed by each business system to obtain corresponding conversion components, which are then combined with standard conversion components. The standard conversion components realize the conversion from the standard model of one business type to the standard model of another business type, thereby realizing the docking between different business systems; after the combination, a target plug-in is formed, and the target plug-in can be directly executed to call the corresponding component during subsequent calls, without the need to manually write a set of corresponding logic programs for each business system, thereby realizing the automation of business processes and significantly improving the processing efficiency of business processes. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 An application environment diagram of a document docking method for a business system in an embodiment;

[0054] Figure 2 A schematic diagram of a process flow of a document docking method of a business system in one embodiment;

[0055] Figure 3 A flowchart of the steps of executing a target plug-in by a server in one embodiment;

[0056] Figure 4 A schematic diagram of a graphical configuration interface in one embodiment;

[0057] Figure 5 A schematic diagram of the logical architecture layer of a business management platform in one embodiment;

[0058] Figure 6 A schematic diagram of the execution logic of a business management platform in one embodiment;

[0059] Figure 7 This is a schematic diagram of a processing flow of a server when a user operates a service management platform in one embodiment;

[0060] Figure 8 It is a structural block diagram of a document docking device of a business system in one embodiment;

[0061] Fig. 9 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0062] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0063] The cooperation between commercial companies is becoming more frequent and closer. The cooperation between different commercial companies, such as e-commerce companies and payment companies, insurance companies and e-commerce companies, etc., all involve a group of companies accessing a company's business process and connecting to its business system. Different companies may have different personalized requirements when accessing a company's business system. At present, a corresponding logic program needs to be written for each request of different cooperation systems. Each cooperation system has a separate logic solution, which wastes human resources and system resources and is not convenient for operation and maintenance.

[0064] For example, in a cross-enterprise supply chain collaboration scenario, there are generally a large number of enterprises involved, and the business systems of each enterprise are quite different. When upstream and downstream customers or suppliers may send changes, a one-time development connection will incur a high cost, with large investment and long cycle. When suppliers are changed, the type of connected system and deployment mode may also change. At this time, the cost and benefit of system integration of upstream and downstream of the supply chain appear to be mismatched.

[0065] In view of this, the embodiments of the present application provide a document docking method, apparatus, computer equipment, storage medium and computer program product for a business system, which normalizes and standardizes personalized business processes that are different between systems but belong to the same business, and establishes conversion relationships between business processes corresponding to the same business in different systems, thereby achieving automatic docking between different systems without the need for adaptive conversion between systems.

[0066] It should be noted that the business systems involved in the embodiments of the present application include, but are not limited to, one or more of an ERP (Enterprise Resource Planning) system, a CRM (Customer Relationship Management) system, an SCM (Supply Chain Management) system, and an APS (Advanced Planning and Scheduling) system. Each business system involves multiple businesses, where a business refers to the affairs involved in commercial activities, and is divided into, but not limited to, one or more of a procurement business, a sales business, and a production business according to the business type. Each business is associated with multiple standard models, such as a purchase order, a sales order, a production order, and a delivery order, each corresponding to a standard model.

[0067] In different business systems, due to the inconsistency of specific design, implementation, and problem-solving methods, the same purchase order, such as the purchase order number, may be named as bill in business system A, with a length of 50 characters; and may be called billname in system B, with a length of 100 characters. The document docking method for business systems provided in the embodiment of the present application is to normalize and standardize the different systems that are the same business in terms of business, so that docking between various different systems no longer requires conversion between each other.

[0068] The document docking method of the business system provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. Among them, the first business system 102 and the second business system 104 communicate with the server 106 through the network respectively. The server 106 can be deployed with a business management platform for users to manage and monitor the business through the business management platform. In addition, the server 106 is deployed with a data storage system for data storage. The data storage system is, for example, a database. The server 104 can be implemented with an independent server or a server cluster consisting of multiple servers.

[0069] In one embodiment, Figure 2 As shown, a document docking method for a business system is provided, and the method is applied to Figure 1 The server in the example is used to illustrate the following steps:

[0070] Step S202: Acquire a first interface component belonging to a first business system and a first standard model corresponding to a first business type, and combine the first interface component and the first standard model to obtain a first conversion component.

[0071] The interface refers to a series of APIs (Application Programming Interfaces) that each business system encapsulates its own website services. When connecting different business systems, it is necessary to call the services in the system through the encapsulated interface, such as obtaining data through the interface. Due to the different designs and implementations of various business systems, the implementation differences between the systems are huge, making it difficult to directly call the original system interface across systems.

[0072] Therefore, in the embodiment of the present application, based on the native interface of the business system, the business-related interfaces are integrated to form interface components, thereby realizing standardized processing of interfaces. The server will call the interface of the business system, and perform input / output processing on the interface return value or process input parameters according to the parameters specified in the standard model, and save it as a component type to obtain an interface component; thus, when all business systems are processed in accordance with the input / output method specified in the standard model, the direct docking of the system is transformed into docking between standard models. For a new business system to add support, it only needs to complete standardization to dock all and standardized business systems, without the need to write code logic processing one by one when facing docking multiple systems.

[0073] The first / second interface component includes but is not limited to one or more of a login interface, a data reading interface, a data writing interface, and a data query interface corresponding to the first business system / second business system.

[0074] Among them, the standard model refers to a data processing model that is pre-set for business processes and business types. It is used to standardize input parameters and obtain output that conforms to a predetermined format. The output can be standardized output or personalized / customized output. Taking business documents as an example, the corresponding standard model for processing documents specifies metadata information such as headers, body fields, and field types. For example, the purchase order model specifies which fields are included, what the field types are, what the field names are, and what rules the fields need to meet (size, non-empty storage, etc.).

[0075] In the scenario of the embodiment of the present application, the first interface component is used to standardize the parameters input into the first business system to adapt to the parameter format specified by the first standard model; the second interface component is used to customize the parameters output by the second standard model to adapt to the parameter format specified by the second business system. Standardization refers to the conversion of personalized input parameters (such as parameter formats and variable rules set by each system) into a parameter format that conforms to the standard; conversely, customization refers to the conversion of output parameters in a standard parameter format into a parameter format that conforms to the settings of each system. The standards involved may be national or industry standards and specifications, etc.

[0076] It should be noted that the above terms "first" and "second" are used to describe different business systems in this application, but these business systems should not be limited by these terms. These terms are only used to distinguish one business system from another business system. For example, the first business system can be referred to as the second business system, and similarly, the second business system can be referred to as the first business system without departing from the scope of the various described embodiments, but unless the context clearly indicates otherwise, they are not the same business system. Similar situations also include the first interface component and the second interface component, the first business type and the second business type, the first standard model and the second standard model, the first conversion component and the second conversion component, and the first document and the second document, etc.

[0077] Specifically, the server obtains a first interface component belonging to the first business system, and determines the first business type corresponding to the first business system according to the business process, and then determines the first standard model corresponding to the first business type. After that, the server combines the first interface component and the first standard model to obtain a first conversion component. The first conversion component is used to read the source document in the first system through the data reading interface, and then convert the source document into a first standard document through the first business standard model. For example, the server determines that the purchaser's business type is a procurement business, extracts / calls the corresponding standard procurement model in the database, and calls the interface component corresponding to the purchaser's procurement business system, combines the interface component with the standard procurement model, and obtains a conversion component corresponding to the procurement business.

[0078] Step S204, obtaining a second interface component belonging to the second business system and a second standard model corresponding to the second business type, and combining the second interface component and the second standard model to obtain a second conversion component.

[0079] In a business process, it is necessary to connect the business systems of cooperating enterprises to realize the automation of the business process. Therefore, similar to the above steps, the server obtains the second interface component belonging to the second business system, and determines the second business type corresponding to the second business system according to the business process, and then determines the second standard model corresponding to the second business type. After that, the server combines the second interface component and the second standard model to obtain a second conversion component. The second conversion component is used to convert the second standard document output by the second standard model into a second document, and output it to the second system through the data write interface.

[0080] For example, the server determines that the seller's business type is sales business, extracts / calls the corresponding standard sales model in the database, and calls the interface component corresponding to the seller's sales business system, combines the interface component with the standard sales model, and obtains the conversion component corresponding to the sales business.

[0081] It should be noted that, in order to clearly explain the inventive concept of the present application, the docking of two business systems is used as an example in the embodiment of the present application, and it is not limited to docking by only two platforms. For example, when a business process involves multiple business systems, for the business systems connected in pairs, the initiator of the business or the executor of the previous step is the first business system, and the receiver of the business or the system executed in the next step is the second business system. For example, for the business process of "procurement-sales", the first business system is the procurement business system, and the second business system is the sales business system; for the business process of "procurement-production-sales", in the "procurement-production" part, the first business system is the procurement business system, and the second business system is the production business system, and in the "production-sales" part, the first business system is the production business system, and the second business system is the sales business system, and so on.

[0082] Step S206, constructing a standard conversion component based on the first standard model and the second standard model.

[0083] The standard conversion component can convert between standard models. The standard conversion component is used to connect the first standard model and the second standard model according to the process processing sequence specified by the preset business process template, so that when the first document is input, the connected multiple standard models are used to process in sequence, thereby outputting the second document. The business process template specifies the process processing sequence of the corresponding business, for example, for the procurement business, the process processing sequence is from procurement to sales.

[0084] Taking the "purchase-sales" business as an example, the standard conversion component is used to realize the conversion from the standard purchase model to the standard sales model, thereby realizing the conversion of corresponding specific parameters, such as converting a standard purchase order into a standard sales order.

[0085] Specifically, after determining the standard models corresponding to the business types executed by the first business system and the second business system respectively, the server combines the corresponding first standard model and the second standard model together and saves them as a component type to form a standard conversion component.

[0086] Step S208, generating a target plug-in based on the first conversion component, the standard conversion component, and the second conversion component; the target plug-in is used to generate a second document of a second business type in the second business system according to a first document of a first business type in the first business system.

[0087] Specifically, the server combines the first conversion component, the standard conversion component, and the second conversion component, saves the components as a plug-in type, and generates a target plug-in for subsequent calls. The target plug-in is used to generate a second document of a second business type in a second business system according to a first document of a first business type in a first business system during subsequent calls, thereby realizing automatic docking of business documents.

[0088] Exemplarily, the server connects the components in order according to the execution order of the business process, thereby obtaining the target plug-in. For example, for the "purchase-sales" business process, the server connects the components in order according to the "first conversion component-standard conversion component-second conversion component" to obtain the target plug-in.

[0089] When the target plug-in is generated, the corresponding component can be automatically called when the server executes the target plug-in later, and the business system can be connected.

[0090] In the document docking method of the above-mentioned business system, the interface components corresponding to each business system and the standard models corresponding to the corresponding business types are combined according to the business types executed by each business system to obtain the corresponding conversion components, which are then combined with the standard conversion components. The standard conversion components realize the conversion from the standard model of one business type to the standard model of another business type, thereby realizing the docking between different business systems; after the combination, a target plug-in is formed, and the target plug-in can be directly executed to call the corresponding component during subsequent calls, without the need to manually write a set of corresponding logic programs for each business system, thereby realizing the automation of business processes and significantly improving the processing efficiency of business processes.

[0091] As mentioned above, after the target plug-in is generated, when a purchase demand occurs, the target plug-in can be called and executed to complete the corresponding business process docking. Taking the "purchase-sales" business process as an example, the first business system generates a purchase document, and accordingly, the second business system automatically generates a sales document. Figure 3 As shown, the steps for the server to execute the target plug-in include:

[0092] Step S302, calling the system login interface corresponding to the first business system to perform a login operation, and after logging in, acquiring a first document belonging to the first business type by calling a data reading interface.

[0093] Step S304, obtaining a document conversion instruction, and based on the document conversion instruction, calling a first standard model in a first conversion component to convert the first document into a first standard document.

[0094] Step S306: calling the standard conversion component to convert the first standard document into a second standard document corresponding to the second business type.

[0095] Step S308: calling the second standard model in the second conversion component to convert the second standard document into a second document applicable to the second business system.

[0096] Step S310, calling the system login interface corresponding to the second business system to perform a login operation, and after logging in, outputting the second document in the second business system by calling the data writing interface corresponding to the second business system.

[0097] Specifically, the server calls the system login interface corresponding to the first business system, performs the login operation according to the relevant parameters (such as IP address, account number, and password, etc.) obtained through the user's input, and after the login is successful, reads the first document belonging to the first business type from the first business system by calling the data reading interface of the first business system. Then, the server converts the first document based on the acquired document conversion instruction, thereby generating a second document adapted to the second business system. Specifically, the server calls the first standard model in the first conversion component, and the first standard model performs standardization processing, thereby converting the first document into the first standard document. At the same time, the server calls the standard conversion component to convert the first standard document into the second standard document corresponding to the second business type. After obtaining the second standard document, the server converts the second standard document into the second document by calling the second standard model in the second conversion component according to the format requirements of the second business system. In order to realize the automatic generation of documents in the second system, the server calls the system login interface corresponding to the second business system to perform the login operation, and after the login, writes the second document in the second business system for output by calling the data writing interface corresponding to the second business system.

[0098] In this embodiment, the document docking process is executed by calling the target plug-in, without manually writing a set of corresponding logic programs for each business system, thereby realizing the automation of business processes and significantly improving the processing efficiency of business processes.

[0099] In order to improve processing efficiency, the generated components and plug-ins are flexibly stored in the database for reuse. In some embodiments, after the target plug-in is generated, the server further performs the following steps: determining a relationship mapping table between the target plug-in and the corresponding multiple conversion components, and storing it; and when executing the target plug-in, according to the relationship mapping table, selecting a target conversion component associated with the target plug-in from the multiple components stored in the database and calling it; wherein the target conversion component includes a first conversion component, a standard conversion component, and a second conversion component.

[0100] Specifically, after generating the target plug-in, the server establishes and stores a relationship mapping table based on the association relationship between the target plug-in and each conversion component, as well as the association relationship between each conversion component in the target plug-in; thus, when the target plug-in is subsequently executed, it can be determined which conversion components need to be called based on the relationship mapping table. The generated conversion components and plug-ins can be stored in different locations in the database respectively, and the conversion components and plug-ins can also be stored together without being bundled. During execution, the server selects the target conversion component associated with the target plug-in from the multiple components stored in the database (taking the above embodiment as an example, that is, the first conversion component, the standard conversion component, and the second conversion component) and calls it, thereby realizing component reuse.

[0101] In this embodiment, by flexibly storing various components and plug-ins, they can be directly reused when called, thereby improving the docking efficiency of the business system and further improving the processing efficiency of the business process.

[0102] In some embodiments, the document docking method of the business system provided in the embodiments of the present application is applied to a business management platform provided with a graphical configuration interface, and a visual graphical configuration interface is provided to the user through the business management platform to reduce the difficulty of operation and simplify the operation steps. The graphical configuration interface is used to modularly display the connection relationship between each component and each component, and edit the connection relationship between each component based on the graphic editing operation and display it in real time; wherein the graphic editing operation includes at least one of the selection operation, the drag operation, and the connection operation. For example, the graphic module used to represent the interface component and the graphic module used to represent the standard model are dragged and connected, and the components and the standard model are connected to combine the two, and the combination is saved as a component type.

[0103] Exemplarily, the server can receive graphical editing operations from the user on the graphical configuration interface provided by the platform, connect the graphic module used to represent the first standard model and the graphic module used to represent the second standard model together through graphic editing operations such as dragging and connecting, and connect the first interface component and the first standard model, thereby combining the two. The component formed by the combination is a conversion component.

[0104] In some embodiments, the above method also includes: using the code editing interface provided by the graphical configuration interface to obtain component configuration information obtained based on the input operation; and, according to the component configuration information, configuring the conversion component so that after the first conversion component reads the first document in the first system through the data reading interface, according to the component configuration information, the first business standard model is called to process the first document and convert the first document into a first standard document, and / or, so that the second conversion component is called to process the second standard document according to the component configuration information and convert the second standard document into a second document.

[0105] Specifically, based on the graphical configuration interface provided by the platform, the above step S202 can be performed in the following manner:

[0106] Step S2022, displaying a first graphic control of the first interface component and a second graphic control of the first standard model in the graphical configuration interface.

[0107] Step S2024, obtaining first component configuration information through the code editing interface in the graphical configuration interface.

[0108] Step S2026, in response to the connection operation for the first graphic control and the second graphic control, the first interface component and the first standard model are combined according to the first component configuration information to obtain a first conversion component.

[0109] The graphic control includes a graphical shape and basic properties of the object represented by the graphical shape. The object is a component, a model, and a plug-in. The basic properties include but are not limited to graphics, fonts, and background.

[0110] Specifically, the server displays a first graphical control of the first interface component and a second graphical control of the first standard model to the user in the graphical configuration interface. The graphical configuration interface also includes a code editing interface for the user to edit the code to input the configuration information of the component. For example, the server obtains the first component configuration information input by the user through the code editing interface in the graphical configuration interface. The component configuration information is used to describe the conversion rules followed by the conversion component.

[0111] Then, the user connects the graphic controls together by selecting, dragging, or connecting in the graphical configuration interface. Accordingly, in response to the user-triggered connection operation for the first graphic control and the second graphic control, the server combines the first interface component and the first standard model according to the first component configuration information to obtain a first conversion component.

[0112] Similarly, the above step S204 can be performed in the following manner:

[0113] Step S2042, displaying the third graphic control of the second interface component and the fourth graphic control of the second standard model in the graphical configuration interface.

[0114] Step S2044, obtaining the second component configuration information through the code editing interface in the graphical configuration interface.

[0115] Step S2046, in response to the connection operation for the third graphic control and the fourth graphic control, the second interface component and the second standard model are combined according to the second component configuration information to obtain a second conversion component.

[0116] Similar to the above embodiment, the server displays the third graphic control of the second interface component and the fourth graphic control of the second standard model to the user in the graphical configuration interface. The server obtains the second component configuration information input by the user through the code editing interface in the graphical configuration interface. Then, the user connects the graphic controls together in the graphical configuration interface by selecting, dragging, or connecting. Accordingly, in response to the connection operation triggered by the user for the third graphic control and the fourth graphic control, the server combines the second interface component and the second standard model according to the second component configuration information to obtain the second conversion component.

[0117] Similarly, the above step S206 can be performed in the following manner:

[0118] Step S2062, in response to the connection operation on the second graphic control and the fourth graphic control, the first standard model and the second standard model are connected to obtain a standard conversion component.

[0119] Specifically, the user can connect the second graphic control and the fourth graphic control together by selecting, dragging, or connecting in the graphical configuration interface; accordingly, the server responds to the connection operation on the second graphic control and the fourth graphic control by docking the first standard model with the second standard model to obtain a standard conversion component.

[0120] In this embodiment, a visual graphical configuration interface is provided to the user through the business management platform, which reduces the difficulty of operation, simplifies the operation steps, and improves the processing efficiency of the business process.

[0121] In some embodiments, the graphical configuration interface includes at least a component option area, a graphic editing area, and a property editing area. The component option area is used to display at least one component to be edited, so that the user can perform graphic editing operations in the graphic editing area. The graphic editing area is used to display the selected component in real time, so that the user can edit the connection relationship between the components. The property editing area is used for the user to edit the property information corresponding to the component. The component option area displays at least one of the system interface component, the data source component, the process control component, and the standard model component for the user to select. The system interface component is used for the user to select the interface components corresponding to the two business systems to be connected, such as the first interface component and the second interface component. The data source component is used for the user to select the component for connecting to the database. The process control component is used for the user to select the processing flow logic between the components, such as loops, judgments, and conditional selections. The standard model component is used for the user to select the standard model for standard conversion, such as the first standard model and the second standard model.

[0122] Of course, it is not limited to this. It can be understood by those skilled in the art that any adaptive modification of the components in the graphical configuration interface is within the protection scope of this application. For example, one or more component options can be added or deleted in the graphical configuration interface according to actual needs, and the positions of various areas in the graphical configuration interface can also be arbitrarily arranged according to actual needs.

[0123] In a specific example, Figure 4 As shown, the above-mentioned graphical configuration interface may include multiple areas, wherein the left area is used to provide users with corresponding selection operations, the graphic editing area in the middle area is used to provide users with graphic editing operations (such as dragging modules, connecting modules, etc.), and the property editing area in the right area is used for users to edit property information, and the property information includes but is not limited to one or more of the data source address, port, account number, and password.

[0124] Among them, the "System Interface Selection" on the left is used to provide native interface components for business systems such as ERP. Each interface component stores the necessary information for interface description (interface access relative address, request type, request parameters, etc.) in the OpenAPI2.0 (open interface) method. "System Component Selection" is used to provide components that are saved after combining and processing several system interfaces (for example, a general system first logs in for verification and then reads data through the interface, and performs standardized conversion through the model. This processing can be saved as a component for quick reuse when connecting to other systems). "Data Source Component" is a component that directly connects to the database and contains the necessary information for data source connection (data source address, port, type, account, password and other attributes). "Process Control Component" is a component for process control such as looping, judgment, and conditional selection. "Standard Model Component" is a component that processes data according to the business model. It is used to provide user-specified standard models and contains general processing operations for standard models.

[0125] In some embodiments, Figure 5 As shown, the business management platform involved in the aforementioned embodiments can implement a bottom-up logical hierarchy: "native interface" layer, "components standardized by model" layer, "standard model docking process" layer, and "heterogeneous system docking" layer.

[0126] Among them, the bottom layer "native interface" refers to the original system interface. Due to the different designs and implementations between various ERP business systems, the implementation differences between systems are very large, making it difficult to directly call interfaces across systems. Therefore, in the second layer of "components standardized by model", based on the native interface of a certain business system, the low-code platform is used to integrate the relevant interfaces and process the input / output of the interface return value or process input parameters according to the parameters specified in the standard model, and save it as a component type. In the third layer of "standard model docking process", since business documents naturally have the need for circulation, such as splitting production plans according to sales orders, the business circulation process configuration is completed according to the standard model to form a standard business circulation docking process. After completing model standardization, different business systems can automatically select the reused model docking process, thereby quickly realizing the business circulation collaboration process with the target system. For example, the manufacturer's business system generates a purchase order, and according to the business docking process, a sales order is automatically generated in the supplier's business system.

[0127] For example, Company B purchases hard disks and computer cases from Company A, manufactures motherboards and other components by itself, assembles them into computers and sells them to Company C; the business systems of Company A, B and C are connected through an integration platform; Company C purchases computers from Company B, and Company C places a purchase order in its business system. The integration platform initiates the "procurement-sales" business plug-in process and automatically creates a purchase order in Company B's business system. Certain materials in this purchase order need to be purchased from Company A, and Company B's business system automatically initiates a business processing flow to place an order with Company A. At this time, the "procurement-sales" business plug-in is called to automatically create a sales order (including purchased materials, quantity, delivery time, etc.) in Company A's business system, and production is carried out according to the order within Company A's internal business system. In this way, a cross-enterprise supply chain collaboration process is completed.

[0128] The top-level "heterogeneous system docking" means that the business system after the above layered processing can be quickly docked with other systems. The more systems connected to the docking platform, the more it means that the newly connected system only needs to complete the model standardization to automatically support the docking with the existing system.

[0129] In scenarios involving a large number of enterprises, such as cross-enterprise supply chain collaboration, the business systems of each enterprise are quite different. When upstream and downstream customers or suppliers may send changes, a one-time development connection will incur a high cost, large investment, and long cycle. When changing suppliers, the type of docking system and deployment mode may also change. Therefore, multiple business systems are connected through standard models in the business management platform, so that downstream suppliers only need to be replaced once according to the supplier's specific business system to quickly complete the replacement; if the newly joined enterprise uses a self-developed business system, it only needs to complete the connection between the self-developed system and the standard model, and it can be quickly included in the upstream and downstream collaborative system of the supply chain, without having to pay attention to the use of other companies' business systems.

[0130] Under this logical hierarchy, the execution logic of the corresponding business management platform is as follows: Figure 6As shown, it includes: the metadata of the design layer (i.e., the user's configuration or the design of the business process) is generated by the graphical configuration interface, and the environment parameters that need to be implemented are abstracted to form an environment parameter template, and the call parameters (such as account number, password, IP address, etc.) that need to be received when the process needs to provide a service interface to the outside world during operation are formed into a call parameter template. The code generation engine can automatically generate an executable target plug-in based on the preset component code template and the metadata generated by the graphical configuration interface; the target plug-in can be generated as the corresponding target language code as needed, and the plug-in code can be, for example, Java script, Java, Python, and other programming languages. Then, according to the actual enterprise, the environment parameters are set to specific parameter values ​​and published as a service; the business process is executed according to the operation plan or passively receives external service requests during operation. The environment parameters refer to the parameters required for the execution of the generated plug-in, such as what code is implemented, in what software environment, and so on.

[0131] In some embodiments, the above-mentioned business management platform can be implemented based on a low-code platform. Existing low-code development platforms are mainly oriented towards document / interface production, with the focus on providing users with interface drag generation and manual addition of business script logic. Existing low-code development platforms are oriented towards rapid document interface creation and interface logic interaction for the same business system. Therefore, on this basis, improvements have been made to the low-code platform in the embodiments of the present application, so that the improved business management platform formed based on the low-code platform is oriented towards cross-system data integration, and can realize the docking and interaction of different cross-system processes.

[0132] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0133] Let's use a specific example as an example. Figure 7As shown, first, the user imports / creates the OpenAPI business system interface, that is, imports the interface information specified in the OpenAPI protocol into the system (OpenAPI can fully describe the attributes and parameters that an external service interface may have), and configures parameters and completes the graphical interface call settings by dragging and dropping interfaces, process control components, and business model components (corresponding to standard models); the backend server encapsulates the business blocks (i.e., configured business processes, such as procurement business processes, sales business processes, etc.) into general components, standard model docking process templates, and business processing processes that are standardized according to standard models. Among them, the purpose of these three components is reuse. The general component refers to the conversion component from a specific system document to a standard document; the standard model docking component refers to the conversion between standard models, such as the standard purchase order-standard sales order conversion component in the above example, and the business processing process refers to which specific systems need to be docked, which usually varies according to different businesses.

[0134] For example, business system A itself opens various order operation interfaces (such as add, delete, check, modify, and review interfaces). The interface specifications require what parameters to pass when calling the interface, the type of parameters, whether the parameters are required, etc. Through certain interface description specifications such as OpenAPI specifications (calling the interface according to the interface specifications can write data into the system or query business data from the system), the interface of business system A can be imported into the business management platform; the interface call of business system B is also imported into the business management platform to perform the "purchase-sales" docking of "AB". During execution, the user graphically drags the A login interface, A purchase order reading interface, and purchase order standard model in the graphical configuration interface, connects and configures accordingly, extracts relevant parameters (such as specific account, password, etc.), and forms the conversion component from purchase order A to standard purchase order; then, the user graphically drags the B login interface, B sales order writing interface, and sales order standard model: connects and configures accordingly, extracts relevant parameters, and forms the conversion component from sales order B to standard sales order. Then, the user drags the line in the interface to complete the connection from the standard purchase order (data provision) to the standard sales order (data writing) to form a standard model docking component. Finally, the user drags A to the standard purchase component, the standard purchase order, the standard sales order, and B to the standard sales component to connect, and automatically extracts the environmental parameters to complete the plug-in development.

[0135] When in use, enterprise E1 uses business system A, and enterprise E2 uses business system B. When implementing the plug-in, the IP address, port, and identity credential information of enterprise E1's business system A and the IP address, port, and identity credential information of enterprise E2's business system B are configured to perform automatic docking. That is, the user of enterprise E1 initiates a purchase business from enterprise E2 in business system A. The user enters the purchase order information, purchased materials, quantity, delivery date, etc. into the platform, and the platform executes the plug-in, thereby automatically generating a sales order in business system B of enterprise E2, listing the purchase demand of enterprise E1 from enterprise E2. As a result, the user of enterprise E2 can arrange production plans for the purchase order, and continue the subsequent collaborative processes after completing production, such as delivery and delivery.

[0136] Therefore, the document docking method for the business system provided in the embodiment of the present application standardizes each business system through a model, and processes the originally widely varying system interfaces into interfaces that provide services according to the input and output parameters specified by the standard business model; at the same time, the business process combination is set according to the standardized business process, and business development can be carried out while ignoring the differences in the underlying systems. The newly added business system only needs to complete the process of standardization according to the model to quickly dock with the existing business system, and flexibly select the standardized business docking process, without the need for separate manual configuration programming. Furthermore, the document docking method for the business system provided in the embodiment of the present application solves the problem of rapid integration between heterogeneous and non-standard business systems, and achieves decoupling of docking between systems by standardizing the interfaces of each system using the main business model. The implemented business processes can be quickly reused, thereby greatly accelerating the system integration process. The more business systems are integrated, the more economies of scale can be formed, and the more obvious the degree of efficiency improvement.

[0137] Based on the same inventive concept, the embodiment of the present application also provides a document docking device for a business system for implementing the document docking method for the business system involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the document docking device embodiments of one or more business systems provided below can refer to the limitations of the document docking method for the business system above, and will not be repeated here.

[0138] In one embodiment, Figure 8 As shown, a document docking device 800 of a business system is provided, comprising: a combination module 801, a construction module 802 and a generation module 803, wherein:

[0139] The combining module 801 is used to obtain a first interface component belonging to a first business system and a first standard model corresponding to a first business type, and combine the first interface component and the first standard model to obtain a first conversion component.

[0140] The combining module 801 is further used to obtain a second interface component belonging to the second business system and a second standard model corresponding to the second business type, and combine the second interface component and the second standard model to obtain a second conversion component.

[0141] The construction module 802 is used to construct a standard conversion component based on the first standard model and the second standard model.

[0142] Generation module 803 is used to generate a target plug-in based on the first conversion component, the standard conversion component, and the second conversion component; the target plug-in is used to generate a second document of a second business type in a second business system based on a first document of a first business type in a first business system.

[0143] In one of the embodiments, the first interface component includes at least a system login interface and a data reading interface of the first business system, and the second interface component includes at least a system login interface and a data writing interface of the second business system; the above-mentioned device also includes an execution module, which is used to: call the system login interface corresponding to the first business system to perform a login operation, and obtain a first document belonging to the first business type by calling the data reading interface after login; obtain a document conversion instruction, and based on the document conversion instruction, call the first standard model in the first conversion component to convert the first document into a first standard document; call the standard conversion component to convert the first standard document into a second standard document corresponding to the second business type; call the second standard model in the second conversion component to convert the second standard document into a second document suitable for the second business system; call the system login interface corresponding to the second business system to perform a login operation, and output the second document in the second business system by calling the data writing interface corresponding to the second business system after login.

[0144] In one embodiment, the first interface component is used to standardize the parameters input into the first business system to adapt to the parameter format specified by the first standard model; the second interface component is used to customize the parameters output by the second standard model to adapt to the parameter format specified by the second business system.

[0145] In one of the embodiments, the above-mentioned device also includes a storage module, which is used to: determine and store a relationship mapping table consisting of a target plug-in and corresponding multiple conversion components; and, when executing the target plug-in, select and call a target conversion component associated with the target plug-in from multiple components stored in a database according to the relationship mapping table; wherein the target conversion component includes a first conversion component, a standard conversion component, and a second conversion component.

[0146] In one embodiment, the device is applied to a business management platform provided with a graphical configuration interface; the graphical configuration interface is used to modularly display the components and the connection relationships between the components, and edit the connection relationships between the components based on graphic editing operations and display them in real time; wherein the graphic editing operation includes at least one of a selection operation, a drag operation, and a connection operation.

[0147] In one of the embodiments, the combination module is also used to: display a first graphic control of a first interface component and a second graphic control of a first standard model in a graphical configuration interface; obtain first component configuration information through a code editing interface in the graphical configuration interface; and in response to a connection operation between the first graphic control and the second graphic control, combine the first interface component and the first standard model according to the first component configuration information to obtain a first conversion component.

[0148] In one of the embodiments, the combination module is also used to: display a third graphic control of the second interface component and a fourth graphic control of the second standard model in a graphical configuration interface; obtain second component configuration information through a code editing interface in the graphical configuration interface; and in response to a connection operation on the third graphic control and the fourth graphic control, combine the second interface component and the second standard model according to the second component configuration information to obtain a second conversion component.

[0149] In one of the embodiments, the construction module is further used to: in response to a connection operation on the second graphic control and the fourth graphic control, dock the first standard model with the second standard model to obtain a standard conversion component.

[0150] Each module in the document docking device of the above business system can be implemented in whole or in part by software, hardware and their combination. Each module can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the corresponding operations of each module.

[0151] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Fig. 9As shown. The computer device includes a processor, a memory and a network interface connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store component or plug-in data, etc. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a document docking method for a business system is implemented.

[0152] Those skilled in the art will understand that Fig. 9 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0153] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the following steps when executing the computer program: obtaining a first interface component belonging to a first business system and a first standard model corresponding to a first business type, and combining the first interface component and the first standard model to obtain a first conversion component; obtaining a second interface component belonging to a second business system and a second standard model corresponding to a second business type, and combining the second interface component and the second standard model to obtain a second conversion component; constructing a standard conversion component based on the first standard model and the second standard model; generating a target plug-in based on the first conversion component, the standard conversion component, and the second conversion component; the target plug-in is used to generate a second document of a second business type in a second business system according to a first document of a first business type in the first business system.

[0154] In one embodiment, when the processor executes the computer program, the following steps are also implemented: calling the system login interface corresponding to the first business system to perform a login operation, and obtaining a first document belonging to the first business type by calling the data reading interface after login; obtaining a document conversion instruction, and based on the document conversion instruction, calling the first standard model in the first conversion component to convert the first document into a first standard document; calling the standard conversion component to convert the first standard document into a second standard document corresponding to the second business type; calling the second standard model in the second conversion component to convert the second standard document into a second document suitable for the second business system; calling the system login interface corresponding to the second business system to perform a login operation, and after login, outputting the second document in the second business system by calling the data writing interface corresponding to the second business system.

[0155] In one embodiment, when the processor executes the computer program, the following steps are also implemented: determining a relationship mapping table consisting of a target plug-in and corresponding multiple conversion components, and storing it; and, when executing the target plug-in, selecting and calling a target conversion component associated with the target plug-in from multiple components stored in a database according to the relationship mapping table; wherein the target conversion component includes a first conversion component, a standard conversion component, and a second conversion component.

[0156] In one embodiment, the processor further implements the following steps when executing the computer program: displaying a first graphic control of a first interface component and a second graphic control of a first standard model in a graphical configuration interface; obtaining first component configuration information through a code editing interface in the graphical configuration interface; in response to a connection operation for the first graphic control and the second graphic control, combining the first interface component and the first standard model according to the first component configuration information to obtain a first conversion component; and, displaying a third graphic control of a second interface component and a fourth graphic control of a second standard model in the graphical configuration interface; obtaining second component configuration information through a code editing interface in the graphical configuration interface; in response to a connection operation for the third graphic control and the fourth graphic control, combining the second interface component and the second standard model according to the second component configuration information to obtain a second conversion component; and, in response to a connection operation for the second graphic control and the fourth graphic control, docking the first standard model and the second standard model to obtain a standard conversion component.

[0157] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented: obtaining a first interface component belonging to a first business system and a first standard model corresponding to a first business type, and combining the first interface component and the first standard model to obtain a first conversion component; obtaining a second interface component belonging to a second business system and a second standard model corresponding to a second business type, and combining the second interface component and the second standard model to obtain a second conversion component; constructing a standard conversion component based on the first standard model and the second standard model; generating a target plug-in based on the first conversion component, the standard conversion component, and the second conversion component; the target plug-in is used to generate a second document belonging to a second business type in a second business system according to a first document belonging to a first business type in the first business system.

[0158] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: calling the system login interface corresponding to the first business system to perform a login operation, and obtaining a first document belonging to the first business type by calling the data reading interface after login; obtaining a document conversion instruction, and based on the document conversion instruction, calling the first standard model in the first conversion component to convert the first document into a first standard document; calling the standard conversion component to convert the first standard document into a second standard document corresponding to the second business type; calling the second standard model in the second conversion component to convert the second standard document into a second document suitable for the second business system; calling the system login interface corresponding to the second business system to perform a login operation, and after login, outputting the second document in the second business system by calling the data writing interface corresponding to the second business system.

[0159] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: determining a relationship mapping table consisting of a target plug-in and corresponding multiple conversion components, and storing it; and, when executing the target plug-in, selecting and calling a target conversion component associated with the target plug-in from multiple components stored in a database according to the relationship mapping table; wherein the target conversion component includes a first conversion component, a standard conversion component, and a second conversion component.

[0160] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: displaying a first graphic control of a first interface component and a second graphic control of a first standard model in a graphical configuration interface; obtaining first component configuration information through a code editing interface in the graphical configuration interface; in response to a connection operation for the first graphic control and the second graphic control, combining the first interface component and the first standard model according to the first component configuration information to obtain a first conversion component; and, displaying a third graphic control of a second interface component and a fourth graphic control of a second standard model in the graphical configuration interface; obtaining second component configuration information through a code editing interface in the graphical configuration interface; in response to a connection operation for the third graphic control and the fourth graphic control, combining the second interface component and the second standard model according to the second component configuration information to obtain a second conversion component; and, in response to a connection operation for the second graphic control and the fourth graphic control, docking the first standard model and the second standard model to obtain a standard conversion component.

[0161] In one embodiment, a computer program product is provided, including a computer program, which implements the following steps when executed by a processor: obtaining a first interface component belonging to a first business system and a first standard model corresponding to a first business type, combining the first interface component and the first standard model to obtain a first conversion component; obtaining a second interface component belonging to a second business system and a second standard model corresponding to a second business type, combining the second interface component and the second standard model to obtain a second conversion component; constructing a standard conversion component based on the first standard model and the second standard model; generating a target plug-in based on the first conversion component, the standard conversion component, and the second conversion component; the target plug-in is used to generate a second document of a second business type in a second business system according to a first document of a first business type in the first business system.

[0162] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: calling the system login interface corresponding to the first business system to perform a login operation, and obtaining a first document belonging to the first business type by calling the data reading interface after login; obtaining a document conversion instruction, and based on the document conversion instruction, calling the first standard model in the first conversion component to convert the first document into a first standard document; calling the standard conversion component to convert the first standard document into a second standard document corresponding to the second business type; calling the second standard model in the second conversion component to convert the second standard document into a second document suitable for the second business system; calling the system login interface corresponding to the second business system to perform a login operation, and after login, outputting the second document in the second business system by calling the data writing interface corresponding to the second business system.

[0163] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: determining a relationship mapping table consisting of a target plug-in and corresponding multiple conversion components, and storing it; and, when executing the target plug-in, selecting and calling a target conversion component associated with the target plug-in from multiple components stored in a database according to the relationship mapping table; wherein the target conversion component includes a first conversion component, a standard conversion component, and a second conversion component.

[0164] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: displaying a first graphic control of a first interface component and a second graphic control of a first standard model in a graphical configuration interface; obtaining first component configuration information through a code editing interface in the graphical configuration interface; in response to a connection operation for the first graphic control and the second graphic control, combining the first interface component and the first standard model according to the first component configuration information to obtain a first conversion component; and, displaying a third graphic control of a second interface component and a fourth graphic control of a second standard model in the graphical configuration interface; obtaining second component configuration information through a code editing interface in the graphical configuration interface; in response to a connection operation for the third graphic control and the fourth graphic control, combining the second interface component and the second standard model according to the second component configuration information to obtain a second conversion component; and, in response to a connection operation for the second graphic control and the fourth graphic control, docking the first standard model and the second standard model to obtain a standard conversion component.

[0165] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0166] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0167] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A document docking method for a business system, characterized in that: The method comprises: Acquire a first interface component belonging to a first business system and a first standard model corresponding to a first business type, and combine the first interface component and the first standard model to obtain a first conversion component; the first interface component is used to perform standardization processing on parameters input in the first business system to adapt to the parameter format specified by the first standard model; Acquire a second interface component belonging to the second business system and a second standard model corresponding to the second business type, and combine the second interface component and the second standard model to obtain a second conversion component; the second interface component is used to customize the parameters output by the second standard model to adapt to the parameter format specified by the second business system; Based on the first standard model and the second standard model, a standard conversion component is constructed; the standard model refers to a data processing model preset for a business process and a business type, which is used to perform standard processing on input parameters to obtain output that conforms to a preset format; the standard conversion component is used for conversion between standard models; A target plug-in is generated based on the first conversion component, the standard conversion component, and the second conversion component; the target plug-in is used to generate a second document of a second business type in a second business system based on a first document of a first business type in a first business system.

2. The method according to claim 1, characterized in that The first interface component includes at least a system login interface and a data reading interface of the first business system, and the second interface component includes at least a system login interface and a data writing interface of the second business system; The method further comprises the step of executing the target plug-in, wherein the step of executing the target plug-in comprises: Calling a system login interface corresponding to the first business system to perform a login operation, and acquiring a first document belonging to the first business type by calling a data reading interface after login; Obtaining a document conversion instruction, and based on the document conversion instruction, calling a first standard model in a first conversion component to convert the first document into a first standard document; Calling a standard conversion component to convert the first standard document into a second standard document corresponding to a second business type; Calling a second standard model in a second conversion component to convert the second standard document into a second document applicable to a second business system; The system login interface corresponding to the second business system is called to perform a login operation, and after login, the second document is output in the second business system by calling a data writing interface corresponding to the second business system.

3. The method according to claim 1, characterized in that The first interface component is used to standardize the parameters input into the first business system to adapt to the parameter format specified by the first standard model; the second interface component is used to customize the parameters output by the second standard model to adapt to the parameter format specified by the second business system.

4. The method according to claim 1, characterized in that: The method further comprises: Determine and store a relationship mapping table between a target plug-in and corresponding multiple conversion components; and, when executing the target plug-in, select and call a target conversion component associated with the target plug-in from multiple components stored in a database according to the relationship mapping table; wherein the target conversion component includes a first conversion component, a standard conversion component, and a second conversion component.

5. The method according to any one of claims 1 to 4, characterized in that: The method is applied to a business management platform provided with a graphical configuration interface; the graphical configuration interface is used to modularly display the components and the connection relationships between the components, and edit the connection relationships between the components based on graphic editing operations and display them in real time; wherein the graphic editing operations include at least one of a selection operation, a drag operation, and a connection operation.

6. The method according to claim 5, characterized in that The step of combining the first interface component and the first standard model to obtain a first conversion component includes: Displaying a first graphic control of the first interface component and a second graphic control of the first standard model in the graphical configuration interface; Obtaining first component configuration information through a code editing interface in the graphical configuration interface; In response to a connection operation on the first graphic control and the second graphic control, combining the first interface component and the first standard model according to the first component configuration information to obtain a first conversion component; The step of combining the second interface component with the second standard model to obtain a second conversion component includes: Displaying a third graphic control of the second interface component and a fourth graphic control of the second standard model in the graphical configuration interface; Obtaining second component configuration information through a code editing interface in the graphical configuration interface; In response to a connection operation on the third graphic control and the fourth graphic control, combining the second interface component and the second standard model according to the second component configuration information to obtain a second conversion component; The constructing of a standard conversion component based on the first standard model and the second standard model includes: In response to the connection operation for the second graphic control and the fourth graphic control, the first standard model and the second standard model are docked to obtain a standard conversion component.

7. The method according to claim 5, characterized in that The graphical configuration interface at least includes a component selection area, a graphic editing area, and a property editing area; the component selection area is used to display at least one component to be edited, so that the user can perform graphic editing operations in the graphic editing area; the graphic editing area is used to display the selected component in real time, so that the user can edit the connection relationship between the components; the property editing area is used to allow the user to edit the property information corresponding to the selected component; The component option area displays at least one of a system interface component, a data source component, a process control component, and a standard model component.

8. A document docking device for a business system, characterized in that: The device comprises: a combination module, used to obtain a first interface component belonging to a first business system and a first standard model corresponding to a first business type, and to combine the first interface component and the first standard model to obtain a first conversion component; the first interface component is used to perform standardization processing on parameters input in the first business system to adapt to the parameter format specified by the first standard model; The combination module is further used to obtain a second interface component belonging to the second business system and a second standard model corresponding to the second business type, and combine the second interface component and the second standard model to obtain a second conversion component; the second interface component is used to customize the parameters output by the second standard model to adapt to the parameter format specified by the second business system; A construction module, configured to construct a standard conversion component based on the first standard model and the second standard model; the standard model refers to a data processing model preset for a business process and a business type, and is configured to perform standard processing on input parameters to obtain output in a preset format; the standard conversion component is configured to convert between standard models; A generation module is used to generate a target plug-in based on the first conversion component, the standard conversion component, and the second conversion component; the target plug-in is used to generate a second document of a second business type in a second business system based on a first document of a first business type in a first business system.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

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

Images