Data interaction method, device, computer equipment and storage medium between systems
By initiating business requests in the first system and using the robot process automation system for data interaction, the second system is solved without providing an interface, and efficient data exchange between systems is realized, which improves interaction efficiency and stability.
Patent Information
- Application Number
- CN202011562920.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-12-25
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2040-12-25
AI Technical Summary
In some systems, the second system does not provide a calling interface, which causes the first system to be unable to interact with the second system, limiting the efficiency of data exchange between systems.
The first system initiates a business request, determines the implementation method of the business request, and sends the implementation method to the robot process automation system, so that it can interact with the second system according to the specified operating process, and uses the robot process automation system as an intermediate system to achieve interaction , avoiding manual operation.
The data interaction between the first system and the second system is realized, the interaction efficiency is improved, and the second system does not require the second system to provide an interface, ensuring system stability and data security.
Smart Images

Figure CN112612624B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a method, apparatus, computer device and storage medium for processing a business request. Background Art
[0002] In different systems, the first system usually communicates with the second system in an embedded manner. However, in some special systems, the second system does not provide a calling interface to the outside, resulting in the system being unable to exchange data with the second system. Summary of the invention
[0003] Based on this, it is necessary to provide a data interaction method, device, computer equipment and storage medium between systems that can interact with each other in order to solve the above technical problems.
[0004] A data interaction method between systems, the method comprising:
[0005] Initiate a business request through the first system;
[0006] Determine the service implementation method corresponding to the service request;
[0007] The business implementation method is sent to the robotic process automation system to instruct the robotic process automation system to perform data interaction with the second system according to the operation process corresponding to the business implementation method.
[0008] A data interaction system comprises a first system, a robotic process automation system and a second system;
[0009] The first system initiates a service request and determines a service implementation method corresponding to the service request;
[0010] The first system sends the business implementation method to the robotic process automation system;
[0011] The robotic process automation system exchanges data with the second system according to the operation process corresponding to the business implementation method.
[0012] A data interaction device between systems, the device comprising:
[0013] A service request initiating module, used to initiate a service request through the first system;
[0014] A service implementation method determination module, used to determine the service implementation method corresponding to the service request;
[0015] The business implementation method sending module is used to send the business implementation method to the robot process automation system, so that the robot process automation system can exchange data with the second system according to the received business implementation method and the operation process corresponding to the business implementation method.
[0016] A computer device comprises a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:
[0017] Initiate a business request through the first system;
[0018] Determine the service implementation method corresponding to the service request;
[0019] The business implementation method is sent to the robotic process automation system to instruct the robotic process automation system to perform data interaction with the second system according to the operation process corresponding to the business implementation method.
[0020] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the following steps:
[0021] Initiate a business request through the first system;
[0022] Determine the service implementation method corresponding to the service request;
[0023] The business implementation method is sent to the robotic process automation system to instruct the robotic process automation system to perform data interaction with the second system according to the operation process corresponding to the business implementation method.
[0024] The above-mentioned data interaction method, device, computer equipment and storage medium between systems initiate a business request through the first system, determine the business implementation method corresponding to the business request, and send the business implementation method to the robotic process automation system to instruct the robotic process automation system to interact with the second system according to the operation process corresponding to the business implementation method; the robotic process automation system does not interact with the second system through an interface, so through the robotic process automation system as an intermediate system, data interaction between the first system and the second system can be realized, and there is no need for manual entry into the second system for operation, thereby improving the data interaction efficiency between the systems. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] Figure 1 An application environment diagram of a data interaction method between systems in one embodiment;
[0026] Figure 2 is a flow chart of a method for data interaction between systems in one embodiment;
[0027] Figure 3 A system architecture diagram of a data interaction system in an embodiment;
[0028] Figure 4 A schematic diagram of the architecture of an enterprise resource planning system and a banking system in one embodiment;
[0029] Figure 5 A schematic diagram of the architecture of a data interaction system in another embodiment;
[0030] Figure 6 is a structural block diagram of a data interaction device between systems in one embodiment;
[0031] Figure 7 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION
[0032] 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.
[0033] The data interaction method between systems provided in this application can be applied to Figure 1 In the application environment shown. Among them, the first computer device 102 exchanges data with the second computer device 104 through the network, and the second computer device 104 exchanges data with the third computer device 106 through the network. The first computer device 102 is equipped with an ERP system, the second computer device 104 is equipped with a robotic automation process system, and the third computer device 106 is equipped with a second system. The second system is not the same system as the first system and the robotic process automation system. The first computer device 102, the second computer device 104 and the third computer device 106 can all be terminal devices or servers. Among them, the terminal device can be but is not limited to various personal computers, laptops, smart phones, tablet computers and portable wearable devices, and the server can be implemented with an independent server or a server cluster consisting of multiple servers.
[0034] In one embodiment, Figure 2 As shown, a data interaction method between systems is provided, and the method is applied to Figure 1 Taking the first computer device 102 in the example as an example, the following steps are included:
[0035] Step 202: Initiate a service request through the first system.
[0036] Specifically, the first system can be any system that needs to interact with other systems. For example, the first system can be a database system, an enterprise management system, etc. The enterprise management system can specifically be an ERP system. ERP system is the abbreviation of Enterprise Resource Planning, which refers to a management platform that is built on information technology, integrates information technology and advanced management ideas, and uses systematic management ideas to provide decision-making means for enterprise employees and decision-makers. Business requests are used to implement different business functions. For example, business requests can be requests to import details, declare projects, etc. The first computer device obtains a business request initiated by the first system it carries.
[0037] Step 204: determine the service implementation method corresponding to the service request.
[0038] Specifically, the first computer device stores a mapping relationship between each business request and a business implementation method. The business implementation method may specifically include a process identifier, a process parameter, and a client identifier of a robotic process automation system. The first computer device determines the business implementation method corresponding to the business request based on the mapping relationship between the business request and the business implementation method. For example, the business implementation method may be an import detail method, an import balance method, an import receipt method, a tax reporting method (the tax data in the first system is reported to the national tax system through the robotic process automation system), etc., but is not limited thereto.
[0039] Step 206: Send the business implementation method to the robotic process automation system to instruct the robotic process automation system to perform data exchange with the second system according to the operation process corresponding to the business implementation method.
[0040] Among them, Robotic Process Automation is a new type of enterprise business process automation technology based on software robots and artificial intelligence (AI), also known as digital labor, which helps enterprise employees complete repetitive and intensive work in a zero-integration manner and helps enterprises improve their core competitiveness. The Robotic Process Automation (RPA) system can imitate the manual operation of users on computer equipment. The operation process refers to the operation process that simulates manual operation. The second system refers to a system that does not provide an interface for other systems to access. The second system can be a banking system, a government system, etc., but is not limited to this.
[0041] Specifically, the first computer device sends a business implementation method to the second computer device where the robotic process automation system is located, so as to instruct the robotic process automation system to perform non-embedded interaction with the second system according to the operation process corresponding to the business implementation method.
[0042] In this embodiment, the robotic process automation system is used to store the operation process corresponding to the interaction with at least two second systems; the robotic process automation system is used to interact with the second system corresponding to the operation process according to the received business implementation method and the operation process corresponding to the business implementation method.
[0043] In the above-mentioned method for data interaction between systems, a business request is initiated by the first system, a business implementation method corresponding to the business request is determined, and the business implementation method is sent to the robotic process automation system to instruct the robotic process automation system to perform data interaction with the second system according to the operation process corresponding to the business implementation method; the robotic process automation system does not perform data interaction with the second system through an interface, so the data interaction between the first system and the second system can be realized by using the robotic process automation system as an intermediate system, and there is no need for manual entry into the second system for operation, thereby improving the data interaction efficiency between the systems.
[0044] In one embodiment, sending a business implementation to a robotic process automation system includes: calling an interface for the first system to communicate with the robotic process automation system, and sending the business implementation to the robotic process automation system; the interface integrates the business implementation.
[0045] Specifically, the interface can realize data interaction between the first system and the robotic process automation system. The interface between the first system and the robotic process automation system integrates business implementation methods, such as operation process identification, robotic process automation system client identification, robotic process automation system scheduling parameters, and robotic process automation system execution startup information. The first computer device calls the interface for the first system to communicate with the robotic process automation system, and sends the business implementation method to the robotic process automation system. Compared with the non-integrated method, when the menu directory in the first system changes, the operation process of the non-integrated method needs to be changed at the same time, otherwise the process will fail to find the menu according to the original menu directory, while the integrated method does not need to change the operation process.
[0046] The data interaction method between systems in this embodiment calls the interface for the first system to communicate with the robotic process automation system, and sends the business implementation method to the robotic process automation system. The interface integrates the business implementation method, that is, the data and communication between the first system and the robotic process automation system are realized through the interface, which greatly reduces the operation process changes and failures caused by frequent system changes.
[0047] In one embodiment, the number of business requests is at least two. Determining the business implementation method corresponding to the business request includes: determining the business implementation method corresponding to each business request in the at least two business requests; each business implementation method includes a robotic process automation system identifier and an operation process identifier.
[0048] Calling an interface for the first system to communicate with the robotic process automation system, and sending a business implementation method to the robotic process automation system, including: calling an interface for the first system to communicate with the robotic process automation system, and sending a corresponding operation process identifier to the robotic process automation system corresponding to each robotic process automation system identifier.
[0049] The RPA system identifier may be an identifier of a client corresponding to the RPA system, or may be a system identifier of the RPA system itself, etc. Each RPA system may store multiple operation processes.
[0050] Specifically, when the number of initiated business requests is at least two, determine the business implementation method corresponding to each business request in the at least two business requests; each business implementation method includes a robotic process automation system and an operation process identifier. The first computer device calls the interface for the first system to communicate with the robotic process automation system, and sends the corresponding operation process identifier to each robotic process automation system corresponding to the robotic process automation system identifier, so that the robotic process automation system interacts with the second system according to the operation process corresponding to the operation process identifier. For example, the first system is connected to the robotic process automation system A, and the corresponding business implementation method is to import details, balances and receipts. At present, the first system is connected to the robotic process automation system B, and the corresponding business implementation method is to import details and report national taxes. Then, in the first system, the import details method corresponding to the robotic process automation system A can be set, and the national tax reporting method corresponding to the robotic process automation system B can also be set.
[0051] In this embodiment, the business implementation method also includes an operation process parameter. Taking the business request of exporting details as an example, the corresponding operation process parameter can be a time parameter. For example, if the details from August 2020 to 2020 are exported, "August 2020 to 2020" can be an operation process parameter. Calling the interface for the first system to communicate with the robotic process automation system and sending the business implementation method to the robotic process automation system includes: calling the interface for the first system to communicate with the robotic process automation system, and sending the corresponding operation process identifier and operation process parameter to each robotic process automation system corresponding to the robotic process automation system identifier, so that the robotic process automation system executes the corresponding operation process according to the operation process identifier and the operation process parameter to interact with the second system for data.
[0052] In the data interaction method between systems in this embodiment, when the number of business requests is at least two, the business implementation mode corresponding to each business request in the at least two business requests is determined, and each business implementation mode includes a robot process automation system identifier and an operation process identifier, which can be used to specify which robot process automation system to interact with and which operation process to call; the interface for the first system to communicate with the robot process automation system is called, and the corresponding operation process identifier is sent to the robot process automation system corresponding to each robot process automation system identifier, that is, one first system provides an interface once, and can interact with multiple robot process automation systems, which is easy to use.
[0053] In one embodiment, the second system is a third-party system; the second system does not provide an interface for other systems to access; and the business implementation method includes a third-party business implementation method. Sending the business implementation method to the robotic process automation system includes: sending the third-party business implementation method to the robotic process automation system to instruct the robotic process automation system to perform non-embedded data interaction with the second system according to the operation process corresponding to the third-party business implementation method.
[0054] Among them, the second system is a third-party system, that is, the second system is a system other than the first system and the robotic process automation system, and the second system does not provide an interface for other systems to access. For example, the second system can be a banking system, a government system, etc. Similarly, the third-party business implementation method refers to the method that the third-party system can implement, such as the detailed method of importing the third-party system, the receipt method of importing the third-party system, etc. are not limited to this. Non-embedded data interaction is an interaction method that can be carried out without providing an interface.
[0055] Specifically, the first computer device sends a third-party business implementation method to the robotic process automation system to instruct the robotic process automation system to perform non-embedded data interaction with the second system according to the operation process corresponding to the third-party business implementation method.
[0056] The data interaction method between systems in this embodiment sends a third-party business implementation method to the robotic process automation system to instruct the robotic process automation system to perform non-embedded data interaction with the second system according to the operation process corresponding to the third-party business implementation method. In this way, there is no need for the third-party system to provide an external interface, and the interaction between the two systems can be performed under the premise of ensuring system stability and data security.
[0057] In one embodiment, the data interaction method between the systems also includes: receiving third-party data sent by the robotic process automation system through the first system; when the robotic process automation system obtains the third-party data returned by the third-party system, the third-party data is sent to the first system by calling an interface set in the robotic process automation system for communicating with the first system.
[0058] Among them, third-party data refers to data provided by a third-party system. Different types of third-party systems provide different third-party data. For example, if the third-party system is a bank system, the third-party data can be bank transaction details. The third-party data is specifically obtained by the robotic process automation system after operating the second system according to the operation process corresponding to the business implementation method, and the third-party data is sent to the first system by the robotic process automation system calling the interface set by itself to communicate with the first system.
[0059] Specifically, the robotic process automation system operates the third-party system according to the operation process corresponding to the business implementation method, and obtains the third-party data corresponding to the operation process returned by the third-party system. The robotic process automation system calls the interface set in the robotic process automation system for communicating with the first system, and sends the third-party data to the first system. The first system receives the third-party data sent by the robotic process automation system.
[0060] In this embodiment, the RPA system can integrate the interface of the operation process corresponding to each business implementation. The third-party data is the third-party data sent by the RPA system, and the interface corresponding to the operation process set in the RPA system is called to send the third-party data to the first system. That is, the RPA system needs to call different interfaces according to the different data when transmitting data back to the first system. For example, importing details, importing balances, and importing receipts are three interfaces.
[0061] In the method for data interaction between systems in this embodiment, the first system receives third-party data sent by the robotic process automation system. When the robotic process automation system obtains the third-party data returned by the third-party system, the interface set in the robotic process automation system for communicating with the first system is called and sent to the first system. The data obtained from the second system can be transmitted back to the first system, thereby realizing data interaction between systems.
[0062] In one embodiment, sending a business implementation method to a robotic process automation system includes: obtaining a scheduling period for the business implementation method; and sending the business implementation method to the robotic process automation system regularly according to the scheduling period.
[0063] The scheduling cycle refers to the cycle of calling the interface for communicating between the first system and the robotic process automation system, or the cycle of sending the business implementation method. The scheduling cycle can be daily, weekly, monthly, quarterly, etc., and can also be executed several times a day, at what time to start execution, etc.
[0064] Specifically, the first computer device obtains a scheduling cycle for the business implementation method, and sends the business implementation method to the robot process automation system regularly according to the scheduling cycle. For example, if the scheduling cycle of the first computer device for the business implementation method is once a day, then the business implementation method is regularly executed once a day.
[0065] The data interaction method between systems in this embodiment obtains the scheduling cycle for the business implementation method, and sends the business implementation method to the robotic process automation system at a regular interval according to the scheduling cycle. It can automatically realize the interaction with the second system without human intervention, thereby improving the interaction efficiency between systems.
[0066] In one embodiment, a method for data interaction between systems includes the following steps:
[0067] Step (a1), initiating a service request through the first system;
[0068] Step (a2), determining a business implementation method corresponding to each of the at least two business requests, each business implementation method including a robotic process automation system identifier and an operation process identifier;
[0069] Step (a3), obtaining a scheduling period for a service implementation method;
[0070] Step (a4), sending the third-party business implementation method to the robotic process automation system regularly according to the scheduling cycle to instruct the robotic process automation system to perform non-embedded data interaction and interface integration business implementation method with the second system according to the operation process corresponding to the third-party business implementation method.
[0071] Step (a5), receiving the third-party data sent by the robotic process automation system through the first system; when the robotic process automation system obtains the third-party data returned by the third-party system, the third-party data is sent to the first system by calling the interface set in the robotic process automation system for communicating with the first system.
[0072] The above-mentioned data interaction method between systems initiates a business request through the first system, determines the business implementation method corresponding to the business request, and sends the third-party business implementation method to the robotic process automation system to instruct the robotic process automation system to perform non-embedded data interaction with the second system according to the operation process corresponding to the third-party business implementation method. There is no need for the third-party system to provide an external interface, and the interaction between the two systems can be carried out under the premise of ensuring system stability and data security; the robotic process automation system does not interact with the second system through the interface. Therefore, through the robotic process automation system as an intermediate system, data interaction between the first system and the robotic process automation system can be realized, and there is no need for manual entry into the second system for operation, which improves the data interaction efficiency between the systems; the data and communication between the first system and the robotic process automation system are realized through the interface, which greatly reduces the changes and failures of the operation process caused by frequent system changes; that is, the data and communication between the first system and the robotic process automation system are realized through the interface, which greatly reduces the changes and failures of the operation process caused by frequent system changes.
[0073] In one embodiment, Figure 3 As shown, it is a system architecture diagram of a data interaction system in an embodiment. It includes a first system 302, a robotic process automation system 304 and a second system 306. The first system 302 interacts with the robotic process automation system 304 through a network, and the robotic process automation system 304 interacts with the second system 306 through a network. The first system 302 initiates a business request and determines the business implementation method corresponding to the business request. The first system 302 sends the business implementation method to the robotic process automation system 304. The robotic process automation system 304 interacts with the second system 306 according to the operation process corresponding to the business implementation method.
[0074] In the above-mentioned data interaction system, the first system initiates a business request, determines the business implementation method corresponding to the business request, and sends the business implementation method to the robotic process automation system. The robotic process automation system interacts with the second system according to the operation process corresponding to the business implementation method. The robotic process automation system does not interact with the second system through an interface. Therefore, by using the robotic process automation system as an intermediate system, data interaction between the first system and the second system can be achieved, and there is no need for manual entry into the second system for operation, thereby improving the data interaction efficiency between systems.
[0075] In one embodiment, the first system calls an interface for communicating between the first system and the robotic process automation system, and sends a business implementation method to the robotic process automation system; the interface integrates the business implementation method.
[0076] The data interaction system in this embodiment calls the interface for the first system to communicate with the robotic process automation system, and sends the business implementation method to the robotic process automation system. The interface integrates the business implementation method, that is, the data and communication between the first system and the robotic process automation system are realized through the interface, which greatly reduces the operation process changes and failures caused by frequent system changes.
[0077] In one embodiment, the number of business requests is at least two. The first system determines a business implementation method corresponding to each of the at least two business requests; each business implementation method includes a robotic process automation system identifier and an operation process identifier. The first system calls an interface for the first system to communicate with the robotic process automation system, and sends a corresponding operation process identifier to each robotic process automation system corresponding to the robotic process automation system identifier.
[0078] The data interaction system in this embodiment, when the number of business requests is at least two, determines the business implementation method corresponding to each business request in the at least two business requests, each business implementation method includes a robot process automation system identifier and an operation process identifier, which can be used to specify which robot process automation system to interact with and which operation process to call; calls the interface for the first system to communicate with the robot process automation system, and sends the corresponding operation process identifier to the robot process automation system corresponding to each robot process automation system identifier, that is, one first system provides an interface once, can interact with multiple robot process automation systems, and is easy to use.
[0079] In one embodiment, the second system is a third-party system; the second system does not provide an interface for other systems to access; the business implementation method includes the third-party business implementation method. The first system sends the third-party business implementation method to the robotic process automation system; the robotic process automation system performs non-embedded data interaction with the second system according to the operation process corresponding to the third-party business implementation method.
[0080] The data interaction system in this embodiment sends a third-party business implementation method to the robotic process automation system to instruct the robotic process automation system to perform non-embedded data interaction with the second system according to the operation process corresponding to the third-party business implementation method. In this way, there is no need for the third-party system to provide an external interface, and the interaction between the two systems can be carried out under the premise of ensuring system stability and data security.
[0081] In one embodiment, the third-party system generates third-party data corresponding to the operation process. The robotic process automation system acquires and calls an interface set in the robotic process automation system to communicate with the first system, and sends the third-party data to the first system. The first system receives the third-party data sent by the first system.
[0082] In the data interaction system between systems in this embodiment, the first system receives third-party data sent by the robotic process automation system. The third-party data is sent to the first system by calling the interface for communicating with the first system set in the robotic process automation system when the robotic process automation system obtains the third-party data returned by the third-party system. The data obtained from the second system can be transmitted back to the first system to realize data interaction between the systems.
[0083] In one embodiment, the first system obtains a scheduling period for a business implementation method; and sends the business implementation method to the robot process automation system regularly according to the scheduling period.
[0084] The data interaction system in this embodiment obtains the scheduling cycle for the business implementation method, and sends the business implementation method to the robot process automation system regularly according to the scheduling cycle. It can automatically realize the interaction with the second system without human intervention, thereby improving the interaction efficiency between systems.
[0085] In one embodiment, the robotic process automation system stores operation procedures corresponding to interactions with at least two second systems; the robotic process automation system interacts with the second systems corresponding to the operation procedures according to the received business implementation methods and the operation procedures corresponding to the business implementation methods.
[0086] The data interaction system in this embodiment can set different operation processes in the robotic process automation system to log in to different second systems, thereby improving the scalability of the robotic process automation system.
[0087] In one embodiment, the first system is an enterprise resource planning system and the second system is an online bank. Figure 4 The figure shows an architecture diagram of an enterprise resource planning system and online banking in one embodiment. It includes an enterprise resource planning system and online banking X, online banking Y and online banking Z. Online banking X, online banking Y and online banking Z are all banking systems. Online banking: Online banking is also called network banking, online banking or electronic banking. It is a virtual counter set up by banks on the Internet. Banks use network technology to provide customers with traditional services such as account opening, account cancellation, inquiry, reconciliation, intra-bank transfer, inter-bank transfer, credit, online securities, investment and financial management through the Internet, so that customers can manage current and time deposits, checks, credit cards and personal investments safely and conveniently without leaving home. And Figure 4 The enterprise resource planning system and online bank X, online bank Y and online bank Z cannot directly interact with each other. Not all online banks provide a bank-enterprise direct connection mode to directly connect and obtain balance information in real time, but all banks provide online banking services. In addition, for some online banks with low usage frequency, customers will not open a bank-enterprise direct connection due to cost reasons, but will only open the online banking of the bank. As a result, users are currently unable to quickly obtain the latest account balance and other information of the group. Among them, the bank-enterprise direct connection refers to the connection between the bank system and the enterprise's ERP system, and the enterprise directly handles account management, transfer payment and other banking services through the ERP system. In addition, users can obtain data through online banking, but currently all bank online banking has not opened an interface, and the enterprise resource planning system cannot call its data.
[0088] Corresponding to enterprise resource planning systems and online banking, the current heterogeneous system integration solutions are:
[0089] (1) Embedded interaction requires the caller and the called system to provide a calling interface for embedded interaction. However, online banking does not provide an interface and cannot use this method.
[0090] (2) Manual processing: The data of the calling system is manually exported, processed manually, and then imported or filled into the called system.
[0091] As for the above (1), embedded interaction requires both the caller and the called party to develop external interfaces, which has a certain impact on system stability and data security, and the development cost is high. In addition, bank online banking does not open interfaces for enterprise resource planning systems to call, resulting in the inability of enterprise resource planning systems to interact with online banking data.
[0092] Regarding the above (2), manual processing requires logging into online banking manually. The amount of data to be processed manually is large, the process is complex, and repeated operations are required. For example, to download bank transaction records, it is necessary to log into different online banking systems every day, enter accounts, enter dates, and perform other operations such as querying and exporting. This is time-consuming and has low data acquisition efficiency.
[0093] Therefore, a data interaction system between systems in the embodiment of the present application is proposed. Figure 5 FIG. 1 is a schematic diagram of the architecture of a data interaction system in another embodiment. Figure 5 In the description, an example is taken in which the first system is an enterprise resource planning system and the second system includes online bank X, online bank Y and online bank Z. Figure 5 The system includes an enterprise resource planning system (ERP system), an enterprise resource planning system (RPA system), a client of a robotic process automation system (RPA client), and online bank X, online bank Y, and online bank Z.
[0094] 1. If ERP wants to interact with online banking, it can use RPA as a bridge.
[0095] 2. Users only need to manually set up plans for interacting with heterogeneous system data in ERP, such as importing details, that is, exporting transaction flows from the online banking system and importing them into the ERP system, and setting the scheduling cycle of the plan, that is, daily scheduling or monthly scheduling, how many times a day, and at what time, etc. Among them, the heterogeneous system refers to the online banking system.
[0096] 3. After the plan is set, ERP can initiate manual calls to execute the plan in real time or schedule it according to the scheduling settings. ERP initiates a plan execution request to the RPA console based on the set plan.
[0097] 4. The RPA system will interact with third-party heterogeneous systems based on the received solution and the preset process.
[0098] The above-mentioned data interaction system uses the connection between ERP and RPA to realize non-embedded interaction between ERP and online banking. It does not require the called online bank to provide an external interface, and the interaction between the two systems is carried out under the premise of ensuring system stability and data security. Since ERP systems are generally used by groups, the connection between ERP and RPA only requires manual configuration of the solution. RPA robots can simulate human operations and complete complex, repetitive, and data-intensive tasks on behalf of humans, freeing up a large amount of human resources. Out-of-the-box RPA processes can be built into ERP and integrated with RPA processes through interfaces, greatly reducing RPA process changes and failures caused by frequent system changes.
[0099] It should be understood that although Figure 2 and 5 The steps in the figure are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 2 and 5 At least part of the steps may include multiple steps or multiple stages. These steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed in turn or alternately with other steps or at least part of the steps or stages in other steps.
[0100] In one embodiment, Figure 6 As shown, a data interaction device between systems is provided, including: a service request initiating module 602, a service implementation method determining module 604 and a service implementation method sending module 606, wherein:
[0101] The service request initiating module 602 is used to initiate a service request through the first system.
[0102] The service implementation method determination module 604 is used to determine the service implementation method corresponding to the service request.
[0103] The business implementation method sending module 606 is used to send the business implementation method to the robotic process automation system, so that the robotic process automation system interacts with the second system according to the received business implementation method and the operation process corresponding to the business implementation method.
[0104] The data interaction device between the above-mentioned systems initiates a business request through the first system, determines the business implementation method corresponding to the business request, and sends the business implementation method to the robotic process automation system to instruct the robotic process automation system to interact with the second system according to the operation process corresponding to the business implementation method; the robotic process automation system does not interact with the second system through an interface, so through the robotic process automation system as an intermediate system, data interaction between the first system and the second system can be realized, and there is no need for manual entry into the second system for operation, thereby improving the data interaction efficiency between the systems.
[0105] In one embodiment, the business implementation sending module 606 is used to call an interface for the first system to communicate with the robotic process automation system, and send the business implementation to the robotic process automation system; the interface integrates the business implementation.
[0106] The data interaction device between systems in this embodiment calls the interface for the first system to communicate with the robotic process automation system, and sends the business implementation method to the robotic process automation system. The interface integrates the business implementation method, that is, the data and communication between the first system and the robotic process automation system are realized through the interface, which greatly reduces the operation process changes and failures caused by frequent system changes.
[0107] In one embodiment, the number of business requests is at least two. The business implementation method determination module 604 is used to determine the business implementation method corresponding to each of the at least two business requests; each business implementation method includes a robotic process automation system identifier and an operation process identifier.
[0108] In the data interaction device between systems in this embodiment, when the number of business requests is at least two, the business implementation method corresponding to each business request in the at least two business requests is determined, and each business implementation method includes a robot process automation system identifier and an operation process identifier, which can be used to specify which robot process automation system to interact with and which operation process to call; the interface for the first system to communicate with the robot process automation system is called, and the corresponding operation process identifier is sent to the robot process automation system corresponding to each robot process automation system identifier, that is, one first system provides an interface once, and can interact with multiple robot process automation systems, which is easy to use.
[0109] In one embodiment, the second system is a third-party system; the second system does not provide an interface for other systems to access; and the business implementation method includes a third-party business implementation method. The business implementation method sending module 606 is used to send the third-party business implementation method to the robotic process automation system to instruct the robotic process automation system to perform non-embedded data interaction with the second system according to the operation process corresponding to the third-party business implementation method.
[0110] The data interaction device between systems in this embodiment sends a third-party business implementation method to the robotic process automation system to instruct the robotic process automation system to perform non-embedded data interaction with the second system according to the operation process corresponding to the third-party business implementation method. In this way, there is no need for the third-party system to provide an external interface, and the interaction between the two systems can be performed under the premise of ensuring system stability and data security.
[0111] In one embodiment, the data interaction between systems also includes a receiving module, which is used to receive third-party data sent by the robotic process automation system through the first system; when the robotic process automation system obtains the third-party data returned by the third-party system, the third-party data is sent to the first system by calling an interface set in the robotic process automation system to communicate with the first system.
[0112] The data interaction device between systems in this embodiment receives third-party data sent by the robot process automation system through the first system. The third-party data is sent to the first system by calling an interface for communicating with the first system set in the robot process automation system when the robot process automation system obtains the third-party data returned by the third-party system. The data obtained from the second system can be transmitted back to the first system to realize data interaction between the systems.
[0113] In one embodiment, the business implementation method sending module 606 is used to obtain a scheduling period for the business implementation method; and send the business implementation method to the robot process automation system regularly according to the scheduling period.
[0114] The data interaction device between systems in this embodiment obtains the scheduling cycle for the business implementation method, and sends the business implementation method to the robot process automation system at a regular interval according to the scheduling cycle. It can automatically realize the interaction with the second system without human intervention, thereby improving the interaction efficiency between systems.
[0115] For the specific definition of the data interaction device between systems, please refer to the definition of the data interaction method between systems mentioned above, which will not be repeated here. Each module in the above-mentioned data interaction device between systems can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules 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 operations corresponding to the above modules.
[0116] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 7 As shown. The computer device includes a processor, a memory, a communication interface, a display screen and an input device 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 and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, an operator network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a method for data interaction between systems is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covered on the display screen, or a button, trackball or touchpad set on the computer device housing, or an external keyboard, touchpad or mouse, etc.
[0117] Those skilled in the art will understand that Figure 7 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.
[0118] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.
[0119] In one embodiment, a computer-readable storage medium is provided, storing a computer program, which implements the steps in the above method embodiments when executed by a processor.
[0120] In one embodiment, a computer program product or computer program is provided, the computer program product or computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the steps in the above-mentioned method embodiments.
[0121] Those of ordinary skill 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 memory, storage, database or other media used in the embodiments provided in this 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 or optical memory, etc. Volatile memory can include random access memory (RAM) or external cache memory. 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).
[0122] 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.
[0123] The above-mentioned 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 invention patent. 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 patent of the present application shall be subject to the attached claims.
Claims
1. A data interaction method between systems, characterized in that: The method comprises: Initiate a business request through the first system; Determine a third-party business implementation method corresponding to each of the at least two business requests; each third-party business implementation method includes a robotic process automation system identifier, an operation process identifier, and an operation process parameter; Obtaining a scheduling period for each third-party service implementation mode; According to the scheduling cycle of each third-party business implementation method, the interface for communicating between the first system and the robotic process automation system corresponding to the robotic process automation system identifier in each third-party business implementation method is regularly called, and the interface integrates the robotic process automation system identifier, operation process identifier and operation process parameters corresponding to each third-party business implementation method; the corresponding operation process identifier and operation process parameters are respectively sent to the robotic process automation system corresponding to each robotic process automation system identifier, so that the robotic process automation system corresponding to the robotic process automation system identifier in each third-party business implementation method executes the corresponding operation process according to the operation process identifier and operation process parameters to perform non-embedded data interaction with the third-party system, and the third-party system does not provide an interface.
2. The method according to claim 1, characterized in that The robotic process automation system identifier includes an identifier of a client corresponding to the robotic process automation system.
3. The method according to claim 1, characterized in that: The robotic process automation system identifier also includes the system identifier of the robotic process automation system identifier itself.
4. The method according to claim 1, characterized in that: The method further comprises: The third-party data sent by the robotic process automation system is received through the first system; when the robotic process automation system obtains the third-party data returned by the third-party system, the third-party data is sent to the first system by calling an interface set in the robotic process automation system for communicating with the first system.
5. A data interaction system, characterized in that: including a first system, a robotic process automation system, and a third-party system, wherein the third-party system does not provide an interface; The first system initiates a business request and determines a third-party business implementation method corresponding to each business request in at least two business requests; each third-party business implementation method includes a robotic process automation system identifier, an operation process identifier, and an operation process parameter; The first system sends the scheduling period of each third-party service implementation mode to the robotic process automation system; The robotic process automation system corresponding to the robotic process automation system identifier in each third-party business implementation method periodically calls an interface for communicating with the first system according to the scheduling period of each third-party business implementation method, and the interface integrates the robotic process automation system identifier, operation process identifier and operation process parameters corresponding to each third-party business implementation method, so that the robotic process automation system corresponding to the robotic process automation system identifier in each third-party business implementation method executes the corresponding operation process according to the operation process identifier and operation process parameters to perform non-embedded data interaction with the third-party system.
6. The system according to claim 5, characterized in that Different operation processes can be set in the robotic process automation system to log in to different third-party systems.
7. A data interaction device between systems, characterized in that: The device comprises: A service request initiating module, used to initiate a service request through the first system; A business implementation method determination module, used to determine a third-party business implementation method corresponding to each business request in at least two business requests; each third-party business implementation method includes a robotic process automation system identifier, an operation process identifier, and an operation process parameter; A business implementation method sending module is used to obtain the scheduling period for each third-party business implementation method; according to the scheduling period of each third-party business implementation method, regularly call the interface for communicating between the first system and the robot process automation system corresponding to the robot process automation system identifier in each third-party business implementation method, wherein the interface integrates the robot process automation system identifier, operation process identifier and operation process parameters corresponding to each third-party business implementation method; respectively send the corresponding operation process identifier and operation process parameters to the robot process automation system corresponding to each robot process automation system identifier, so that the robot process automation system corresponding to the robot process automation system identifier in each third-party business implementation method executes the corresponding operation process according to the operation process identifier and operation process parameters to perform non-embedded data interaction with the third-party system, and the third-party system does not provide an interface.
8. 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 4 are implemented.
9. 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 4 are implemented.
10. A computer program product, comprising a computer program, 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 4 are implemented.
Citation Information
Patent Citations
Single sign on system
CN107592321A
Voice service pushing methods, device and systems based on artificial intelligence
CN109618068A
System docking method and device, management system, terminal equipment and storage medium
CN110147397A
Intelligent all-in-one machine development and multi-service quick processing method based on RPA technology
CN110806934A
Automatic approval method based on RPA robot sharing center
CN110909962A
