CN114089977A

CN114089977A - Receipt docking method and device for business system and computer equipment

Info

Publication number: CN114089977A
Application number: CN202111353216.2A
Authority: CN
Inventors: 杨坤元; 林洲
Original assignee: Yundy Intelligent Technology Co ltd
Current assignee: Yundy Intelligent Technology Co ltd
Priority date: 2021-11-16
Filing date: 2021-11-16
Publication date: 2022-02-25

Abstract

The application relates to a document docking method, a document docking device, a computer device, a storage medium and a computer program product for a business system. The method comprises the following steps: acquiring a first interface component belonging to a first service system and a first standard model corresponding to a first service type, and combining the first interface component and the first standard model to obtain a first conversion component; acquiring a second interface component belonging to a second service system and a second standard model corresponding to a second service 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; and generating the target plug-in based on the first conversion component, the standard conversion component and the second conversion component. By adopting the method, the service system can be automatically docked without manually compiling corresponding logic programs, and the processing efficiency of the service process is improved.

Description

Receipt docking method and device for business system and computer equipment

Technical Field

The present application relates to the field of computer network technologies, and in particular, to a method, an apparatus, a computer device, a storage medium, and a computer program product for docking documents in a business system.

Background

As enterprises evolve, collaboration between enterprises is more and more frequent. In the process of advancing business process, the business systems of two or more enterprises are often needed to be connected.

However, different enterprises often have their own business systems, and if a set of corresponding logic programs is written for each business system in the prior art to perform pairwise docking of the systems, considerable human resources and system resources are consumed.

Under the condition that the demand of enterprises on the automation of business processes is higher and higher, how to realize the automatic docking between different business systems is a problem to be solved urgently at present.

Disclosure of Invention

In view of the above, it is necessary to provide a document docking method, apparatus, computer device, computer readable storage medium and computer program product for automatically docking a business system of the business system.

In a first aspect, the present application provides a document docking method for a business system. The method comprises the following steps:

acquiring a first interface component belonging to a first service system and a first standard model corresponding to a first service type, and combining the first interface component and the first standard model to obtain a first conversion component;

acquiring a second interface component belonging to a second service system and a second standard model corresponding to a second service 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; and the target plug-in is used for generating a second bill belonging to a second service type in a second service system according to a first bill belonging to the first service type in the first service system.

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

calling a system login interface corresponding to the first service system to execute login operation, and acquiring a first document belonging to the first service type by calling a data reading interface after login;

acquiring a bill conversion instruction, calling a first standard model in a first conversion assembly based on the bill conversion instruction, and converting a first bill into a first standard bill;

calling a standard conversion component to convert the first standard bill into a second standard bill corresponding to a second service type;

calling a second standard model in a second conversion component, and converting the second standard bill into a second bill suitable for a second business system;

and calling a system login interface corresponding to the second service system to execute login operation, and outputting the second bill in the second service system by calling a data writing interface corresponding to the second service system after login.

In one embodiment, the first interface component is used for standardizing parameters input in the first business system so as to adapt to a parameter format specified by the first standard model; and the second interface component is used for customizing the parameters output by the second standard model so as to adapt to the parameter format specified by the second service system.

In one embodiment, the method further comprises:

determining a relational mapping table formed by the target plug-in and the corresponding plurality of conversion components, and storing the relational mapping table; when the target plug-in is executed, selecting a target conversion component associated with the target plug-in from a plurality of components stored in a database according to the relation mapping table and calling; wherein the target conversion component comprises a first conversion component, a standard conversion component, and a second conversion component.

In one embodiment, the method is applied to a service management platform provided with a graphical configuration interface; the graphical configuration interface is used for displaying the components and the connection relation among the components in a modularized manner, editing the connection relation among the components based on a graphical editing operation and displaying the connection relation in real time; the graphic editing operation at least comprises one of a selection operation, a dragging operation and a connecting operation.

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

displaying a first graphic control of the first interface component and a second graphic control of a first standard model in the graphic configuration interface;

acquiring first component configuration information through a code editing interface in the graphical configuration interface;

and responding to the connection operation aiming at the first graphic control and the second graphic control, and combining the first interface component and the first standard model according to the first component configuration information to obtain a first conversion component.

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

displaying a third graphical control of the second interface component and a fourth graphical control of a second standard model in the graphical configuration interface;

acquiring second component configuration information through a code editing interface in the graphical configuration interface;

and responding to the connection operation aiming at the third graphic control and the fourth graphic control, and combining the second interface component and the second standard model according to the second component configuration information to obtain a second conversion component.

In one embodiment, the building a standard conversion component based on the first standard model and the second standard model includes:

and responding to the connection operation aiming at the second graphic control and the fourth graphic control, and butting the first standard model and the second standard model to obtain a standard conversion component.

In one embodiment, the graphical configuration interface at least comprises a component option area, a graphical editing area and a property editing area; the component option area is used for displaying at least one component to be edited so that a user can perform graphic editing operation in the graphic editing area; the graphic editing area is used for displaying the selected components in real time so that a user can edit the connection relation among the components; the attribute editing area is used for a user to edit the attribute information corresponding to the selected component; wherein, at least one of a system interface component, a data source component, a flow control component and a standard model component is displayed in the component option area.

In a second aspect, the application further provides a document docking device of the business system. The device comprises:

the combination module is used for acquiring a first interface component belonging to a first service system and a first standard model corresponding to a first service type, and combining the first interface component and the first standard model to obtain a first conversion component;

the combination module is further used for acquiring a second interface component belonging to a second service system and a second standard model corresponding to a second service type, and combining the second interface component and the second standard model to obtain a second conversion component;

the building module is used for building a standard conversion component based on the first standard model and the second standard model;

a generation module for generating a target plug-in based on the first conversion component, the standard conversion component, and the second conversion component; and the target plug-in is used for generating a second bill belonging to a second service type in a second service system according to a first bill belonging to the first service type in the first service system.

In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor implementing the following steps when executing the computer program:

In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of:

In a fifth aspect, the present application further provides a computer program product. The computer program product comprising a computer program which when executed by a processor performs the steps of:

The bill docking method, the bill docking device, the computer equipment, the storage medium and the computer program product of the service system combine the interface component corresponding to each service system and the standard model corresponding to the corresponding service type according to the service type executed by each service system respectively to obtain the corresponding conversion component, and then combine the conversion component with the standard conversion component together, and the standard conversion component realizes the conversion from the standard model of one service type to the standard model of another service type, thereby realizing the docking between different service systems; the target plug-ins are formed after combination, the target plug-ins can be directly executed to call corresponding components during subsequent calling, a set of corresponding logic programs do not need to be respectively compiled for each business system manually, the automation of business processes is realized, and the processing efficiency of the business processes is obviously improved.

Drawings

FIG. 1 is a diagram of an application environment of a document docking method of a business system in one embodiment;

FIG. 2 is a flow diagram illustrating a method for document docking in a business system in one embodiment;

FIG. 3 is a flowchart illustrating steps performed by a server to execute a target plug-in one embodiment;

FIG. 4 is an interface diagram of a graphical configuration interface in one embodiment;

FIG. 5 is a logical architecture layer diagram of a service management platform in one embodiment;

FIG. 6 is a flow diagram that illustrates logic performed by the business management platform in one embodiment;

FIG. 7 is a diagram illustrating a process flow of a server when a user operates a service management platform according to an embodiment;

FIG. 8 is a block diagram showing the structure of a document docking apparatus of the business system in one embodiment;

FIG. 9 is a diagram illustrating an internal structure of a computer device according to an embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

The collaboration between business companies is more and more frequent and tighter. Different business companies, such as e-commerce company and payment company, insurance company and e-commerce company, all involve a group of companies accessing the business process of a certain company and interfacing with its business system. Different companies access the business system of a company and may have different personalization requirements. At present, each request of different cooperation systems needs to compile a set of corresponding logic programs, and the scheme that each cooperation system independently makes a set of logic wastes human resources and system resources and is inconvenient to operate and maintain.

For example, in a cross-enterprise supply chain collaboration scenario, there are generally a large number of involved enterprises, and business systems of the enterprises have large differences, when upstream and downstream customers or suppliers may send changes, high cost is incurred by one-time development and docking, the investment is large, the period is long, and when the suppliers are changed, the docking system types and deployment modes may also change, and at this time, the cost and the profit are not matched when upstream and downstream system integration of the supply chain is performed.

In view of this, embodiments of the present application provide a method, an apparatus, a computer device, a storage medium, and a computer program product for docking documents in business systems, which respectively establish a conversion relationship between business processes corresponding to a same business in different systems by standardizing and standardizing personalized business processes that are different among the systems but belong to the same business in business, thereby implementing automatic docking between the different systems without performing adaptive conversion between two systems.

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, an APS (Advanced Planning and Scheduling) system, and the like. Each business system relates to a plurality of businesses, wherein the businesses refer to business related to business behaviors and are divided according to business types, and the business systems comprise but are not limited to one or more of purchasing businesses, selling businesses, producing businesses and the like. Each business is associated with a plurality of standard models, such as a purchase order, a sales order, a production order and a delivery order, which respectively correspond to one standard model.

In different business systems, because the specific design, implementation and problem solving modes are not consistent, a purchase order, such as the order number of the purchase order, may be named as: bill, 50 characters in length; in system B, it may be called billname, 100 characters in length. The document docking method for the business systems provided by the embodiment of the application is to standardize and standardize different but same business among the systems, so that conversion between every two different systems is not needed for docking.

The document docking method of the business system provided by the embodiment of the application can be applied to the application environment shown in fig. 1. The first service system 102 and the second service system 104 are respectively in communication with the server 106 through a network. The server 106 may be deployed with a service management platform, so that a user can manage and monitor services through the service management platform. In addition, the server 106 is deployed with a data storage system for storage of data. The data storage system is for example a database. The server 104 may be implemented as a stand-alone server or as a server cluster comprised of multiple servers.

In an embodiment, as shown in fig. 2, a document docking method for a business system is provided, which is described by taking the application of the method to the server in fig. 1 as an example, and includes the following steps:

step S202, a first interface component belonging to a first service system and a first standard model corresponding to a first service type are obtained, and the first interface component and the first standard model are combined to obtain a first conversion component.

The Interface refers to a series of APIs (Application Programming interfaces) that each business system encapsulates its own web service. When interfacing between different service systems, it is necessary to call services in the system through a packaged interface, for example, obtaining data through the interface. Due to different design implementation among various service systems, the implementation difference among the systems is very large, and the calling of an original system interface of a cross-system is difficult to directly carry out.

Therefore, in the embodiment of the present application, interfaces related to services are integrated based on a native interface of a service system to form an interface component, so that the standardized processing of the interfaces can be realized. The server calls an interface of the service system, performs input/output processing on an interface return value or a process input parameter according to a parameter specified by the standard model, and stores the interface return value or the process input parameter into a component type to obtain an interface component; therefore, after all the service systems are processed according to the input/output mode specified by the standard model, the direct butt joint of the systems is changed into the butt joint between the standard models, and the support is added to a new service system, all the service systems and the service systems after the standardization can be butt jointed only by completing the standardization, and the code logic processing does not need to be written one by one when a plurality of systems are butt jointed.

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/the second business system.

The standard model refers to a data processing model preset for a business process and a business type, and is used for standardizing input parameters to obtain output in accordance with a predetermined format, wherein the output can be standardized output or personalized/customized output. Taking a business document as an example, a corresponding standard model for processing documents specifies metadata information such as a header, a body field, a field type and the like. For example, the purchase order model specifies which fields are present, what the field type is, what the field name is, and which rules (size, non-empty save, etc.) the fields need to satisfy, etc.

In the scenario of the embodiment of the present application, the first interface component is configured to perform normalization processing on a parameter input in the first service system to adapt to a parameter format specified by the first standard model; and the second interface component is used for customizing the parameters output by the second standard model so as to adapt to the parameter format specified by the second service system. Wherein, the standardization processing refers to converting personalized input parameters (such as parameter formats and variable rules set by each system) into parameter formats conforming to standards; in contrast, the customizing process refers to converting the output parameters in the standard parameter format into a parameter format conforming to the respective system settings. The standard involved may be a national or industry standard specification, or the like.

It should be noted that the above terms "first" and "second" are used in this application to describe different business systems, but these business systems should not be limited by these terms. These terms are only used to distinguish one service system from another. For example, a first business system may be referred to as a second business system, and similarly, a second business system may be referred to as a first business system, without departing from the scope of the various described embodiments, but they are not the same business system unless the context clearly dictates otherwise. Similar situations also exist for a first interface component and a second interface component, a first business type and a second business type, a first standard model and a second standard model, a first conversion component and a second conversion component, a first receipt and a second receipt, and the like.

Specifically, the server acquires a first interface component belonging to a first service system, determines a first service type corresponding to the first service system according to a service process, and further determines a first standard model corresponding to the first service type. And then, the server combines the first interface component and the first standard model to obtain a first conversion component. The first conversion assembly is used for converting a source document in the first system into a first standard document through the first business standard model after the source document is read through the data reading interface. For example, the server determines that the service type of the purchasing party is a purchasing service, extracts/calls a corresponding standard purchasing model from the database, calls an interface component corresponding to a purchasing service system of the purchasing party, and combines the interface component with the standard purchasing model to obtain a conversion component corresponding to the purchasing service.

Step S204, a second interface component belonging to a second service system and a second standard model corresponding to a second service type are obtained, and the second interface component and the second standard model are combined to obtain a second conversion component.

In one business process, business systems of enterprises cooperating with each other need to be docked, so that automation of the business process is realized. Therefore, similar to the above steps, the server obtains a second interface component belonging to a second service system, and determines a second service type corresponding to the second service system according to the service flow, thereby determining a second standard model corresponding to the second service type. And then, the server combines the second interface component and the second standard model to obtain a second conversion component. And the second conversion component is used for converting a second standard bill output by the second standard model into a second bill and outputting the second bill to the second system through the data writing interface.

For example, the server determines that the service type of the seller is a sales service, extracts/calls a corresponding standard sales model from the database, calls an interface component corresponding to a sales service system of the seller, and combines the interface component with the standard sales model to obtain a conversion component corresponding to the sales service.

It should be noted that, in order to clearly illustrate the inventive concept of the present application, the embodiment of the present application uses the docking of two service systems as an example, and is not limited to the docking performed by only two platforms. For example, when one business process involves multiple business systems, for two-by-two connected business systems, 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 by the next step is the second business system. For example, for the business process of "purchase-sale", the first business system is a purchase business system, and the second business system is a sale business system; for the "purchase-production-sale" business process, in the "purchase-production" part, the first business system is the purchase business system, the second business system is the industry business system, in the "production-sale" part, the first business system is the industry business system, the second business system is the sale business system, and so on.

And step S206, constructing a standard conversion component based on the first standard model and the second standard model.

Wherein, the standard conversion component can perform conversion between standard models. The standard conversion component is used for connecting the first standard model and the second standard model according to a flow processing sequence specified by a preset business flow template, so that when a first bill is input, the connected standard models are used for processing in sequence, and a second bill is output. The business process template specifies the process processing sequence of the corresponding business, for example, for the purchase business, the process processing sequence from purchase to sale.

Also taking "purchase-sale" business as an example, the standard conversion component is used for realizing conversion from a standard purchase model to a standard sale model, thereby realizing conversion of corresponding specific parameters, such as converting a standard purchase order into a standard sale order.

Specifically, after determining standard models corresponding to service types executed by a first service system and a second service system respectively, the server combines the corresponding first standard model and the second standard model together, and stores the combined standard models as component types to form a standard conversion component.

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 for generating a second bill belonging to a second business type in a second business system according to a first bill belonging to a first business type in the first business system.

Specifically, the server combines the components together according to the formed first conversion component, the standard conversion component and the second conversion component, and stores the components as a plug-in type, so as to generate a target plug-in for subsequent calling. The target plug-in is used for generating a second bill belonging to a second business type in a second business system according to a first bill belonging to the first business type in the first business system when in subsequent calling, so that the automatic butt joint of the business bills is realized.

Illustratively, the server sequentially connects the components according to the sequence of execution of the business process, so as to obtain the target plug-in. For example, for the business process of "purchase-sale", two-by-two connection is performed in the order of "first conversion component-standard conversion component-second conversion component" in sequence, so as to obtain the target plug-in.

And after the target plug-in is generated, automatically calling the corresponding component when the server subsequently executes the target plug-in, and carrying out butt joint on the service system.

In the bill docking method of the business system, the interface module corresponding to each business system and the standard model corresponding to the corresponding business type are combined respectively according to the business type executed by each business system to obtain the corresponding conversion module, and then the conversion module is combined with the standard conversion module, and the standard conversion module realizes 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; the target plug-ins are formed after combination, the target plug-ins can be directly executed to call corresponding components during subsequent calling, a set of corresponding logic programs do not need to be respectively compiled for each business system manually, the automation of business processes is realized, and the processing efficiency of the business processes is obviously improved.

Before the generation, after the target plug-in is generated, when the purchase demand appears, the target plug-in can be called and executed, so that the corresponding business process is docked. Still taking the business flow of "purchase-sale" as an example, the first business system generates a purchase document, and correspondingly, the second business system automatically generates a sale document. As shown in fig. 3, the step of the server executing the target plug-in includes:

step S302, a system login interface corresponding to the first service system is called to execute login operation, and a first bill belonging to the first service type is obtained by calling a data reading interface after login.

Step S304, a bill conversion instruction is obtained, and based on the bill conversion instruction, a first standard model in the first conversion assembly is called, and the first bill is converted into a first standard bill.

And step S306, calling a standard conversion component to convert the first standard bill into a second standard bill corresponding to the second service type.

And step S308, calling a second standard model in the second conversion component, and converting the second standard bill into a second bill suitable for the second business system.

And step S310, calling a system login interface corresponding to the second service system to execute login operation, and outputting a second bill in the second service system by calling a data write-in interface corresponding to the second service system after login.

Specifically, the server calls a system login interface corresponding to the first service system, executes login operation according to relevant parameters (such as an IP address, an account number, a password and the like) acquired through input of a user, and reads a first document belonging to the first service type from the first service system by calling a data reading interface of the first service system after login is successful. And then, the server converts the first bill based on the acquired bill conversion instruction, so that a second bill adapted to a second business system is generated. Specifically, the server calls a first standard model in the first conversion component, and the first standard model carries out standardization processing, so that the first bill is converted into the first standard bill. And simultaneously, the server calls a standard conversion component to convert the first standard bill into a second standard bill corresponding to the second service type. And after the second standard bill is obtained, the server converts the second standard bill into a second bill by calling a second standard model in the second conversion component according to the format requirement of the second service system. In order to realize automatic generation of the document in the second system, the server calls a system login interface corresponding to the second business system to execute login operation, and after login, writes the second document in the second business system for output by calling a data writing interface corresponding to the second business system.

In the embodiment, the target plug-in is called to execute the document docking process, and a set of corresponding logic program does not need to be written for each service system manually, so that the automation of the service flow is realized, and the processing efficiency of the service flow is obviously improved.

To improve processing efficiency, the generated components and plug-ins are flexibly stored in a database for reuse. In some embodiments, after generating the target plug-in, the server further performs the following steps: determining a relational mapping table formed by the target plug-in and the corresponding plurality of conversion components, and storing the relational mapping table; when the target plug-in is executed, selecting a target conversion component associated with the target plug-in from a plurality of components stored in the database according to the relational mapping table and calling; the target conversion component comprises a first conversion component, a standard conversion component and a second conversion component.

Specifically, after a target plug-in is generated, the server establishes and stores a relation mapping table according to the incidence relation between the target plug-in and each conversion component and the incidence relation between the conversion components in the target plug-in; therefore, when the target plug-in is executed subsequently, which conversion components need to be called can be determined according to the relation mapping table. The generated conversion components and plug-ins can be stored in different positions in the database respectively, and the conversion components and the plug-ins can also be stored together without being bound. When the server executes, the server selects and calls a target conversion component (i.e. the first conversion component, the standard conversion component and the second conversion component, for example, in the above embodiment) associated with the target plug-in from the plurality of components stored in the database, thereby realizing the reuse of the components.

In the embodiment, each component and the plug-in are flexibly stored, and can be directly multiplexed when being called, so that the butt joint efficiency of the service system is improved, and the processing efficiency of the service process is further improved.

In some embodiments, the document docking method of the business system provided by the embodiment of the application is applied to a business management platform provided with a graphical configuration interface, and the visual graphical configuration interface is provided for a user through the business management platform, so that the operation difficulty is reduced, and the operation steps are simplified. The graphical configuration interface is used for displaying the components and the connection relation among the components in a modularized manner, editing the connection relation among the components based on a graphical editing operation and displaying the connection relation in real time; the graphic editing operation at least comprises one of a selection operation, a dragging operation and a connecting operation. For example, a graphic module for representing an interface component and a graphic module for representing a standard model are dragged and connected, and the component and the standard model are connected to combine the two and are stored as a component type after being combined.

Illustratively, the server may connect the graphic module for representing the first standard model and the graphic module for representing the second standard model together through receiving a graphic editing operation of a user on a graphic configuration interface provided by the platform, and connect the first interface component and the first standard model through a graphic editing operation such as dragging, connecting a wire and the like, so as to combine the two, and the combined component is a conversion component.

In some embodiments, the above method further comprises: acquiring component configuration information obtained based on input operation by using a code editing interface provided by a graphical configuration interface; and configuring the conversion assembly according to the assembly configuration information so that the first conversion assembly can call the first service standard model to process the first document and convert the first document into the first standard document after reading the first document in the first system through the data reading interface according to the assembly configuration information, and/or enabling the second conversion assembly to call the second service standard model to process the second standard document and convert the second standard document into the second document according to the assembly configuration information.

Specifically, based on the graphical configuration interface provided by the platform, the step S202 may be performed as follows:

step S2022, displaying the first graphic control of the first interface component and the second graphic control of the first standard model in the graphical configuration interface.

Step S2024, acquiring the first component configuration information through a code editing interface in the graphical configuration interface.

Step S2026, in response to the 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.

Wherein the graphical control comprises a graphical shape and basic properties of an object represented by the graphical shape. The objects are components, models, plug-ins, and the like. Basic properties include, but are not limited to, graphics, fonts, and backgrounds, among others.

Specifically, the server presents 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. In the graphical configuration interface, a code editing interface is further included for a user to edit the code to input configuration information of the component. For example, the server acquires the first component configuration information input by the user through a code editing interface in the graphical configuration interface. Wherein the component configuration information is used to describe a transformation rule followed by the transformation component.

The user then connects the graphical controls together in the graphical configuration interface by a selection, dragging, or wiring operation. Correspondingly, the server responds to the connection operation which is triggered by the user and aims at the first graphic control and the second graphic control, combines the first interface component and the first standard model according to the configuration information of the first component, and obtains a first conversion component.

Similarly, the above step S204 may be performed as follows:

step S2042, showing a third graphic control of the second interface component and a fourth graphic control of the second standard model in the graphical configuration interface.

Step S2044, acquiring second component configuration information through a code editing interface in the graphical configuration interface.

Step S2046, in response to the 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.

Similar to the above embodiment, the server presents the third graphical control of the second interface component and the fourth graphical control of the second standard model to the user in the graphical configuration interface. And the server acquires the second component configuration information input by the user through a code editing interface in the graphical configuration interface. The user then connects the graphical controls together in the graphical configuration interface by a selection, dragging, or wiring operation. Correspondingly, the server responds to the connection operation which is triggered by the user and aims at the third graphic control and the fourth graphic control, and combines the second interface component and the second standard model according to the second component configuration information to obtain a second conversion component.

Similarly, the above step S206 may be performed by:

step S2062, in response to the connection operation aiming at the second graphic control and the fourth graphic control, the first standard model and the second standard model are butted to obtain the standard conversion assembly.

Specifically, a user can connect the second graphical control and the fourth graphical control together through selecting, dragging or connecting operation on a graphical configuration interface; correspondingly, the server responds to the connection operation aiming at the second graphic control and the fourth graphic control, and the first standard model and the second standard model are butted to obtain the standard conversion assembly.

In the embodiment, the service management platform provides a visual graphical configuration interface for a user, so that the operation difficulty is reduced, the operation steps are simplified, and the processing efficiency of the service process is improved.

In some embodiments, the graphical configuration interface includes at least a component options area, a graphical editing area, and a properties editing area. The component option area is used for displaying at least one component to be edited so that a user can perform graphic editing operation in the graphic editing area. And the graphic editing area is used for displaying the selected components in real time so that a user can edit the connection relation among the components. And the attribute editing area is used for a user to edit the attribute information corresponding to the component. Wherein, at least one of a system interface component, a data source component, a flow control component and a standard model component is displayed in the component option area for a user to select. The system interface component is used for a user to select interface components corresponding to two service systems to be docked respectively, such as a first interface component and a second interface component. The data source component is used for a user to select a component connected with the database. The flow control component is used for the user to select the processing flow logic between the components, such as circulation, judgment, condition selection and the like. The standard model component is used for the user to select standard models for standard conversion, such as a first standard model and a second standard model.

Of course, not limited thereto, and it will be understood by those skilled in the art that any adaptation of the components of the graphical configuration interface is within the scope of the present application. For example, one or more component options may be added or deleted according to actual requirements in the graphical configuration interface, and for example, the positions of the regions in the graphical configuration interface may also be randomly arranged according to actual requirements.

In a specific example, as shown in fig. 4, the graphical configuration interface may include a plurality of areas, where a left area is used for providing a user to perform a corresponding selection operation, a middle area is used for providing a user to perform a graphical editing operation (e.g., dragging a module, connecting modules, etc.), and a right area is used for a user to edit attribute information, where the attribute information includes, but is not limited to, one or more of a data source address, a port, an account number, a password, etc.

The left system interface is selected to provide native interface components of a business system such as ERP, and each interface component stores information (interface access relative address, request type, request parameter, etc.) necessary for interface description in an openapi2.0 (open interface) manner. The "system component selection" is used to provide a component that combines and processes several system interfaces and then stores the combined system interfaces (for example, a general system firstly logs in and verifies, then reads data through the interfaces, and performs standardized conversion through a model, and this processing can be stored as a component to be conveniently and quickly reused when being docked with other systems). The 'data source component' is directly connected with the components of the database and contains necessary information (data source address, port, type, account number, password and other attributes) of data source connection. The "flow control module" is a module that performs flow control such as circulation, judgment, and condition selection. The standard model component is a component for processing data according to the business model, is used for providing a user-specified standard model and comprises standard model general processing operation.

In some embodiments, as shown in fig. 5, the business management platform involved in the foregoing embodiments may implement a bottom-up logical hierarchy: the system comprises a 'native interface' layer, a 'component standardized by a model' layer, a 'standard model docking process' layer and a 'heterogeneous system docking' layer.

The primary interface at the bottom layer refers to an original system interface, and due to different design implementation among various ERP service systems, the implementation difference among the systems is extremely large, and direct calling across the interfaces among the systems is difficult to directly carry out. Therefore, in the "component standardized by model" of the second layer, based on the native interface of a certain business system, a flow of integrating the relevant interfaces and performing input/output processing on the interface return value or the flow input parameter according to the parameter specified by the standard model is stored as a component type by using a low-code platform. In the 'standard model docking process' of the third layer, if a production plan sheet is split according to a sales order because a business document naturally has a transfer requirement, the configuration of the business transfer process is completed according to the standard model, and a standard business transfer docking process is formed. After different business systems complete model standardization, the multiplexing model docking process can be automatically selected, so that the business flow cooperation process with the target system is quickly realized, for example, a purchase order is generated by the business system of a manufacturer, and a sales order is automatically generated in the business system of a supplier according to the business docking process.

For example, enterprise B purchases hard disks and cases from enterprise a, and manufactures motherboards by itself to assemble computers for sale to enterprise C; A. b, C3 business systems of enterprises are communicated through an integration platform; the method comprises the following steps that an enterprise C purchases a computer from an enterprise B, the enterprise C puts a purchase order in a business system of the enterprise C, an integrated platform initiates a 'purchase-sale' business plug-in process, a purchase order is automatically established in the business system of the enterprise B, some materials in the purchase order need to be purchased from an enterprise A, the business system B automatically initiates a business processing process for placing orders to the enterprise A, the 'purchase-sale' business plug-in is called at the moment, a sale order (comprising purchase materials, quantity, delivery time and the like) is automatically established in the business system of the enterprise A, and the interior of the business system of the enterprise A is produced according to orders; this completes a cross-enterprise supply chain collaboration flow.

The top-level heterogeneous system docking means that the service system subjected to the layered processing can be rapidly docked with other systems, and the more systems the docking platform is connected to, means that the newly connected system can automatically support docking with the existing system only by completing model standardization.

In a scenario where the number of enterprises involved is large, such as inter-enterprise supply chain collaboration, the business systems of the enterprises are relatively different, and when upstream and downstream customers or suppliers may send changes, one-time development and docking may involve relatively high cost, large investment and long cycle, and in the case of replacing the suppliers, the type and deployment mode of the docked system may also change. Therefore, a plurality of service systems are butted in the service management platform through the standard model, so that a downstream replacement supplier can quickly complete replacement only by implementing once according to the specific service system of the supplier; if the newly added enterprise uses the self-research business system, the self-research system can be quickly brought into the upstream and downstream cooperative systems of the supply chain only by completing the butt joint of the self-research system and the standard model, and the service conditions of the business systems of other enterprises do not need to be concerned.

Under this logic hierarchy, the execution logic of the corresponding service management platform is as shown in fig. 6, and includes: the method comprises the steps that a graphical configuration interface generates metadata of a design layer (namely configuration of a user or design of a business process), environment parameters needing to be implemented are abstracted to form an environment parameter template, and calling parameters (such as parameters of an account number, a password, an IP address and the like) needing to be received when a service interface is needed to be provided to the outside during running of the process form a calling parameter template, and a code generation engine automatically generates an executable target plug-in according to a preset component code template and in combination with the metadata generated by the graphical configuration interface; the target plug-in may be generated as a corresponding target language code as required, and the plug-in code may be, for example, a programming language such as javascript, Java, Python, or the like. Setting the environment parameters as specific parameter values according to actual enterprises, and issuing the specific parameter values to form a service; and executing the business process according to the operation plan or passively receiving the external service request during the operation. The environment parameter refers to a parameter required for the generated plug-in to execute, such as in what code to implement, in what software environment to execute, and the like.

In some embodiments, the business management platform may be implemented by a low-code platform. The existing low-code development platform is mainly oriented to document/interface manufacturing, and is mainly used for providing an operation mode of interface drag generation and manual business script logic adding for a user. The existing low-code development platform is oriented to the quick document interface creation and interface logic interaction of the same business system. Therefore, on the basis, the low-code platform is improved in the embodiment of the application, so that the service management platform formed by relying on the low-code platform after improvement is oriented to cross-system data integration, and the butt joint and interaction of different cross-system processes can be realized.

It should be understood that, although the steps in the flowcharts related to the embodiments are shown in sequence as indicated by the arrows, the steps are not necessarily executed in sequence as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the flowcharts related to the above embodiments may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the steps or stages is not necessarily sequential, but may be performed alternately or alternately with other steps or at least a part of the steps or stages in other steps.

Taking a specific example as an explanation, as shown in fig. 7, firstly, a user imports/creates an OpenAPI service system interface, that is, an interface information import system (OpenAPI can completely describe an attribute and a parameter that an external service interface may have) defined by an OpenAPI protocol, and configures the parameter and completes the graphical interface call setting by dragging the interface, the process control component and the service model component (corresponding to the standard model); the background server respectively encapsulates the business blocks (namely configured business processes such as purchasing business process, selling business process and the like) into a general component, a standard model docking process template and a business processing process which are standardized according to a standard model. The purpose of the three components is multiplexing, and the universal component refers to a 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 exemplified above, and the business processing flow refers to which specific systems need to be docked, which generally varies according to the business.

For example, the a service system itself opens various order operation interfaces (such as interfaces for addition, deletion, check, modification, and audit), the interface specification requires what parameters need to be transferred from the call interface, the type of the parameters, whether the parameters are necessary, and the like, and the interface of the a service system can be imported into the service management platform through a certain interface description specification such as the OpenAPI specification (data can be written into the system or service data can be queried from the system by calling the interface according to the interface specification); the B service system call interface is also imported into the service management platform to execute the 'purchase-sale' docking of the 'A-B'. During execution, a user graphically drags the login interface A, the purchase order reading interface A and the purchase order standard model in the graphical configuration interface, connects the lines and performs corresponding configuration, and extracts relevant parameters (such as specific account numbers, passwords and other data) to form a conversion assembly from the purchase order A to the standard purchase order; then, the user graphically drags the B login interface, the B sales order writing interface and the sales order standard model: and connecting the lines and carrying out corresponding configuration, and extracting relevant parameters to form a conversion component from the sales order B to the standard sales order. Then, the user drags the connecting line in the interface to complete the connection from the standard purchase order (data supply) to the standard sale order (data write-in) to form the standard model butt-joint component. And finally, dragging the A-conversion standard purchasing component, the standard purchasing order, the standard selling order and the B-conversion standard selling component by a user to be connected, and automatically extracting the environmental parameters, thereby completing the development of the plug-in.

In use, enterprise E1 uses the a business system and enterprise E2 uses the B business system, and when the plug-in is implemented, the IP address, port, and identity credential information of the a business system of enterprise E1 and the IP address, port, and identity credential information of the B business system of enterprise E2 are configured to perform automated docking. That is, the user of enterprise E1 initiates a purchase transaction to enterprise E2 at business a system, and the user transfers purchase order information, purchased materials, quantities, delivery dates, etc. to the platform and executes plug-ins by the platform, thereby automatically generating a sales order listing the purchase needs of enterprise E1 to enterprise E2 in business B system of enterprise E2. Thus, the user of enterprise E2 can schedule a production plan for the purchase order and continue subsequent collaborative processes, such as delivery, etc., after completion of production.

Therefore, in the document docking method for the business systems provided by the embodiment of the application, each business system is standardized through a model, and originally, system interfaces which are different are processed into interfaces which provide services according to input and output parameters specified by a standard business model; meanwhile, the service flow combination is set according to the standardized service flow, and service development is carried out under the condition that the difference of a bottom system can be ignored. The newly added service system can be quickly docked with the existing service system only by finishing the process of standardization according to the model, and the standardized service docking process is flexibly selected without independent manual configuration programming. Furthermore, the document docking method for the service system provided by the embodiment of the application solves the problem of rapid integration between heterogeneous nonstandard service systems, and achieves the decoupling of docking between the systems by standardizing each system interface by using the main service model. And the realized business process can be multiplexed quickly, so that the system integration process is greatly accelerated, the more the integrated business systems are, the more scale effect can be formed, and the more obvious the efficiency is improved.

Based on the same inventive concept, the embodiment of the application also provides a document docking device of the business system, which is used for realizing the document docking method of the business system. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the method, so that specific limitations in the following embodiments of the document docking device of one or more business systems can be referred to the above limitations on the document docking method of the business system, and details are not described here.

In one embodiment, as shown in fig. 8, there is provided a document docking apparatus 800 of a business system, including: a combining module 801, a building module 802 and a generating module 803, wherein:

the combining module 801 is configured to obtain a first interface component belonging to a first service system and a first standard model corresponding to a first service type, and combine the first interface component and the first standard model to obtain a first conversion component.

The combining module 801 is further configured to obtain a second interface component belonging to a second service system and a second standard model corresponding to a second service type, and combine the second interface component and the second standard model to obtain a second conversion component.

A building module 802 for building a standard conversion component based on the first standard model and the second standard model.

A generating module 803, configured 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 for generating a second bill belonging to a second business type in a second business system according to a first bill belonging to a first business type in the first business system.

In one embodiment, the first interface component at least comprises a system login interface and a data reading interface of a first business system, and the second interface component at least comprises a system login interface and a data writing interface of a second business system; the apparatus further comprises an execution module configured to: calling a system login interface corresponding to the first service system to execute login operation, and acquiring a first document belonging to the first service type by calling a data reading interface after login; acquiring a bill conversion instruction, calling a first standard model in a first conversion assembly based on the bill conversion instruction, and converting a first bill into a first standard bill; calling a standard conversion component to convert the first standard bill into a second standard bill corresponding to the second service type; calling a second standard model in a second conversion component, and converting the second standard bill into a second bill suitable for a second business system; and calling a system login interface corresponding to the second service system to execute login operation, and outputting a second document in the second service system by calling a data write-in interface corresponding to the second service system after login.

In one embodiment, the apparatus further includes a storage module configured to: determining a relational mapping table formed by the target plug-in and the corresponding plurality of conversion components, and storing the relational mapping table; when the target plug-in is executed, selecting a target conversion component associated with the target plug-in from a plurality of components stored in the database according to the relational mapping table and calling; the target conversion component comprises a first conversion component, a standard conversion component and a second conversion component.

In one embodiment, the device is applied to a service management platform provided with a graphical configuration interface; the graphical configuration interface is used for displaying the components and the connection relation among the components in a modularized manner, editing the connection relation among the components based on a graphical editing operation and displaying the connection relation in real time; the graphic editing operation at least comprises one of a selection operation, a dragging operation and a connecting operation.

In one embodiment, the combining module is further configured to: displaying a first graphic control of the first interface component and a second graphic control of the first standard model in a graphic configuration interface; acquiring first component configuration information through a code editing interface in a graphical configuration interface; and responding to the connection operation aiming at the first graphic control and the second graphic control, and combining the first interface component and the first standard model according to the first component configuration information to obtain a first conversion component.

In one embodiment, the combining module is further configured to: 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; acquiring second component configuration information through a code editing interface in the graphical configuration interface; and responding to the connection operation aiming at the third graphic control and the fourth graphic control, and combining the second interface component and the second standard model according to the second component configuration information to obtain a second conversion component.

In one embodiment, the building module is further configured to: and responding to the connection operation aiming at the second graphic control and the fourth graphic control, and butting the first standard model and the second standard model to obtain the standard conversion component.

All or part of the modules in the bill pairing device of the business system can be realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 9. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured 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 an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing component or plug-in data and the like. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a document docking method for a business system.

Those skilled in the art will appreciate that the architecture shown in fig. 9 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program: acquiring a first interface component belonging to a first service system and a first standard model corresponding to a first service type, and combining the first interface component and the first standard model to obtain a first conversion component; acquiring a second interface component belonging to a second service system and a second standard model corresponding to a second service 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 for generating a second bill belonging to a second business type in a second business system according to a first bill belonging to a first business type in the first business system.

In one embodiment, the processor, when executing the computer program, further performs the steps of: calling a system login interface corresponding to the first service system to execute login operation, and acquiring a first document belonging to the first service type by calling a data reading interface after login; acquiring a bill conversion instruction, calling a first standard model in a first conversion assembly based on the bill conversion instruction, and converting a first bill into a first standard bill; calling a standard conversion component to convert the first standard bill into a second standard bill corresponding to the second service type; calling a second standard model in a second conversion component, and converting the second standard bill into a second bill suitable for a second business system; and calling a system login interface corresponding to the second service system to execute login operation, and outputting a second document in the second service system by calling a data write-in interface corresponding to the second service system after login.

In one embodiment, the processor, when executing the computer program, further performs the steps of: determining a relational mapping table formed by the target plug-in and the corresponding plurality of conversion components, and storing the relational mapping table; when the target plug-in is executed, selecting a target conversion component associated with the target plug-in from a plurality of components stored in the database according to the relational mapping table and calling; the target conversion component comprises a first conversion component, a standard conversion component and a second conversion component.

In one embodiment, the processor, when executing the computer program, further performs the steps of: displaying a first graphic control of the first interface component and a second graphic control of the first standard model in a graphic configuration interface; acquiring first component configuration information through a code editing interface in a graphical configuration interface; responding to the connection operation aiming at the first graphic control and the second graphic control, and combining the first interface component and the first standard model according to the first component configuration information to obtain a first conversion component; 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; acquiring second component configuration information through a code editing interface in the graphical configuration interface; responding to the connection operation aiming at the third graphic control and the fourth graphic control, and combining the second interface component and the second standard model according to the configuration information of the second component to obtain a second conversion component; and in response to the connection operation aiming at the second graphic control and the fourth graphic control, the first standard model and the second standard model are butted to obtain the standard conversion component.

In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: acquiring a first interface component belonging to a first service system and a first standard model corresponding to a first service type, and combining the first interface component and the first standard model to obtain a first conversion component; acquiring a second interface component belonging to a second service system and a second standard model corresponding to a second service 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 for generating a second bill belonging to a second business type in a second business system according to a first bill belonging to a first business type in the first business system.

In one embodiment, the computer program when executed by the processor further performs the steps of: calling a system login interface corresponding to the first service system to execute login operation, and acquiring a first document belonging to the first service type by calling a data reading interface after login; acquiring a bill conversion instruction, calling a first standard model in a first conversion assembly based on the bill conversion instruction, and converting a first bill into a first standard bill; calling a standard conversion component to convert the first standard bill into a second standard bill corresponding to the second service type; calling a second standard model in a second conversion component, and converting the second standard bill into a second bill suitable for a second business system; and calling a system login interface corresponding to the second service system to execute login operation, and outputting a second document in the second service system by calling a data write-in interface corresponding to the second service system after login.

In one embodiment, the computer program when executed by the processor further performs the steps of: determining a relational mapping table formed by the target plug-in and the corresponding plurality of conversion components, and storing the relational mapping table; when the target plug-in is executed, selecting a target conversion component associated with the target plug-in from a plurality of components stored in the database according to the relational mapping table and calling; the target conversion component comprises a first conversion component, a standard conversion component and a second conversion component.

In one embodiment, the computer program when executed by the processor further performs the steps of: displaying a first graphic control of the first interface component and a second graphic control of the first standard model in a graphic configuration interface; acquiring first component configuration information through a code editing interface in a graphical configuration interface; responding to the connection operation aiming at the first graphic control and the second graphic control, and combining the first interface component and the first standard model according to the first component configuration information to obtain a first conversion component; 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; acquiring second component configuration information through a code editing interface in the graphical configuration interface; responding to the connection operation aiming at the third graphic control and the fourth graphic control, and combining the second interface component and the second standard model according to the configuration information of the second component to obtain a second conversion component; and in response to the connection operation aiming at the second graphic control and the fourth graphic control, the first standard model and the second standard model are butted to obtain the standard conversion component.

In one embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, performs the steps of: acquiring a first interface component belonging to a first service system and a first standard model corresponding to a first service type, and combining the first interface component and the first standard model to obtain a first conversion component; acquiring a second interface component belonging to a second service system and a second standard model corresponding to a second service 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 for generating a second bill belonging to a second business type in a second business system according to a first bill belonging to a first business type in the first business system.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high-density embedded nonvolatile Memory, resistive Random Access Memory (ReRAM), Magnetic Random Access Memory (MRAM), Ferroelectric Random Access Memory (FRAM), Phase Change Memory (PCM), graphene Memory, and the like. Volatile Memory can include Random Access Memory (RAM), external cache Memory, and the like. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others. The databases referred to in various embodiments provided herein may include at least one of relational and non-relational databases. The non-relational database may include, but is not limited to, a block chain based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, quantum computing based data processing logic devices, etc., without limitation.

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.

Claims

1. A receipt docking method for a business system, the method comprising:

2. The method of claim 1, wherein the first interface component comprises at least a system login interface and a data reading interface of a first business system, and the second interface component comprises at least a system login interface and a data writing interface of a second business system; the method further comprises the step of executing the target plug-in, the step of executing the target plug-in comprising:

3. The method of claim 1, wherein the first interface component is configured to standardize parameters entered in the first business system to fit a parameter format specified by the first standard model; and the second interface component is used for customizing the parameters output by the second standard model so as to adapt to the parameter format specified by the second service system.

4. The method of claim 1, further comprising:

5. The method according to any one of claims 1 to 4, wherein the method is applied to a service management platform provided with a graphical configuration interface; the graphical configuration interface is used for displaying the components and the connection relation among the components in a modularized manner, editing the connection relation among the components based on a graphical editing operation and displaying the connection relation in real time; the graphic editing operation at least comprises one of a selection operation, a dragging operation and a connecting operation.

6. The method of claim 5, wherein combining the first interface component and the first standard model to obtain a first converted component comprises:

responding to the connection operation aiming at the first graphic control and the second graphic control, and combining the first interface component and the first standard model according to the first component configuration information to obtain a first conversion component;

the combining the second interface component and the second standard model to obtain a second conversion component includes:

responding to the connection operation aiming at the third graphic control and the fourth graphic control, and combining the second interface component and the second standard model according to the second component configuration information to obtain a second conversion component;

constructing a standard conversion component based on the first standard model and the second standard model, including:

7. The method of claim 5, wherein the graphical configuration interface comprises at least a component option area, a graphical editing area, and a property editing area; the component option area is used for displaying at least one component to be edited so that a user can perform graphic editing operation in the graphic editing area; the graphic editing area is used for displaying the selected components in real time so that a user can edit the connection relation among the components; the attribute editing area is used for a user to edit the attribute information corresponding to the selected component;

wherein, at least one of a system interface component, a data source component, a flow control component and a standard model component is displayed in the component option area.

8. A document docking apparatus for a business system, the apparatus comprising:

9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 7.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.