CN112612624A - Data interaction method and device between systems, computer equipment and storage medium - Google Patents
Data interaction method and device between systems, computer equipment and storage medium Download PDFInfo
- Publication number
- CN112612624A CN112612624A CN202011562920.4A CN202011562920A CN112612624A CN 112612624 A CN112612624 A CN 112612624A CN 202011562920 A CN202011562920 A CN 202011562920A CN 112612624 A CN112612624 A CN 112612624A
- Authority
- CN
- China
- Prior art keywords
- robot
- implementation mode
- automation system
- service implementation
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 230000003993 interaction Effects 0.000 title claims abstract description 132
- 238000000034 method Methods 0.000 title claims abstract description 85
- 230000000977 initiatory effect Effects 0.000 claims abstract description 10
- 238000004801 process automation Methods 0.000 claims description 123
- 230000008569 process Effects 0.000 claims description 41
- 238000004891 communication Methods 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims description 15
- 238000010586 diagram Methods 0.000 description 13
- 230000008859 change Effects 0.000 description 10
- 230000008676 import Effects 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 6
- 238000007726 management method Methods 0.000 description 6
- 230000003203 everyday effect Effects 0.000 description 3
- 230000010354 integration Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 210000001503 joint Anatomy 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000002354 daily effect Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000003278 mimic effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000029305 taxis Effects 0.000 description 1
- 230000003442 weekly effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/549—Remote execution
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Manipulator (AREA)
Abstract
The application relates to a method and a device for data interaction between systems, computer equipment and a storage medium. The method comprises the following steps: initiating a service request through a first system; determining a service implementation mode corresponding to the service request; and sending the service implementation mode to a robot flow automation system to instruct the robot flow automation system to perform data interaction with a second system according to the operation flow corresponding to the service implementation mode. The data interaction between the first system and the second system can be realized through the method.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for processing a service request, a computer device, and a storage medium.
Background
In a different system, a first system will typically communicate with a second system by way of an embedded communication. However, in some special systems, the second system does not provide a calling interface to the outside, so that the system cannot perform data interaction with the second system.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a method, an apparatus, a computer device and a storage medium for data interaction between systems capable of performing interaction.
A method of data interaction between systems, the method comprising:
initiating a service request through a first system;
determining a service implementation mode corresponding to the service request;
and sending the service implementation mode to a robot flow automation system to instruct the robot flow automation system to perform data interaction with a second system according to the operation flow corresponding to the service implementation mode.
A data interaction system comprises a first system, a robot process automation system and a second system;
the first system initiates a service request and determines a service implementation mode corresponding to the service request;
the first system sends the service implementation mode to the robot process automation system;
and the robot process automation system performs data interaction with the second system according to the operation process corresponding to the service implementation mode.
An apparatus for data interaction between systems, the apparatus comprising:
a service request initiating module, configured to initiate a service request through a first system;
a service implementation mode determining module, configured to determine a service implementation mode corresponding to the service request;
and the service implementation mode sending module is used for sending the service implementation mode to the robot flow automation system so that the robot flow automation system performs data interaction with the second system according to the received service implementation mode and the operation flow corresponding to the service implementation mode.
A computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program:
initiating a service request through a first system;
determining a service implementation mode corresponding to the service request;
and sending the service implementation mode to a robot flow automation system to instruct the robot flow automation system to perform data interaction with a second system according to the operation flow corresponding to the service implementation mode.
A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:
initiating a service request through a first system;
determining a service implementation mode corresponding to the service request;
and sending the service implementation mode to a robot flow automation system to instruct the robot flow automation system to perform data interaction with a second system according to the operation flow corresponding to the service implementation mode.
The data interaction method, the device, the computer equipment and the storage medium among the systems initiate a service request through the first system, determine a service implementation mode corresponding to the service request, send the service implementation mode to the robot flow automation system, and instruct the robot flow automation system to perform data interaction with the second system according to an operation flow corresponding to the service implementation mode; the robot process automation system does not perform data interaction with the second system through an interface, so that the robot process automation system is used as an intermediate system, data interaction between the first system and the second system can be realized, manual operation is not required to enter the second system for operation, and the data interaction efficiency between the systems is improved.
Drawings
FIG. 1 is a diagram of an application environment in which a method for data interaction between systems is implemented, according to an embodiment;
FIG. 2 is a flow diagram that illustrates a method for data interaction between systems, according to one embodiment;
FIG. 3 is a system architecture diagram of a data interaction system in one embodiment;
FIG. 4 is an architectural diagram of an enterprise resource planning system and a banking system, under an embodiment;
FIG. 5 is a block diagram of a data interaction system according to another embodiment;
FIG. 6 is a block diagram showing an example of a data exchange apparatus;
FIG. 7 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 inter-system data interaction method provided by the application can be applied to the application environment shown in fig. 1. Wherein the first computer device 102 performs data interaction with the second computer device 104 via the network, and the second computer device 104 performs data interaction with the third computer device 106 via the network. The first computer device 102 has an ERP system installed therein, the second computer device 104 has a robot automation flow system installed therein, and the third computer device 106 has a second system installed therein. The second system is not the same system as the first system and the robotic process automation system. First computer device 102, second computer device 104, and third computer device 106 may each be a terminal device or a server. The terminal device may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the server may be implemented by an independent server or a server cluster formed by a plurality of servers.
In one embodiment, as shown in fig. 2, a method for data interaction between systems is provided, which is described by taking the method as an example applied to the first computer device 102 in fig. 1, and includes the following steps:
In particular, the first system may be any system that requires interaction with other systems. For example, the first system may be a database system, an enterprise management system, or the like. The enterprise management system may specifically be an ERP system. The ERP system is a short term for Enterprise Resource Planning (Enterprise Resource Planning), and is a management platform which is established on the basis of information technology, integrates the information technology and advanced management ideas, and provides decision means for Enterprise employees and decision layers by using a systematized management idea. The service request is used for implementing different service functions, for example, the service request may be a request for importing details, declaring a project, and the like. The first computer equipment acquires the service request initiated by the carried first system.
And step 204, determining a service implementation mode corresponding to the service request.
Specifically, the first computer device stores a mapping relationship between each service request and a service implementation manner. The service implementation mode may specifically include a process identifier, a process parameter, and a client identifier of the robot process automation system. And the first computer equipment determines the service implementation mode corresponding to the service request based on the mapping relation between the service request and the service implementation mode. For example, the service implementation manner may be, but is not limited to, an import detail manner, an import balance manner, an import receipt manner, a tax return manner (tax data in the first system is reported to the national tax system through the robot flow automation system), and the like.
And step 206, sending the service implementation mode to the robot flow automation system to instruct the robot flow automation system to perform data interaction with the second system according to the operation flow corresponding to the service implementation mode.
The robot Process Automation is a novel enterprise business Process Automation technology based on a software robot and Artificial Intelligence (AI), is also called digital labor, helps enterprise staff to complete repeated and intensive work in a zero-integration mode, and helps enterprises to improve core competitiveness. A Robotic Process Automation (RPA) system may mimic the manner in which a user manually operates on a computer device. The operation flow refers to an operation flow simulating manual operation. The second system refers to a system that does not provide an interface for other systems to access. The second system may specifically be a banking system, a government system, etc., without being limited thereto.
Specifically, the first computer device sends a service implementation manner to a second computer device where the robot flow automation system is located, so as to instruct the robot flow automation system to perform non-embedded interaction with the second system according to an operation flow corresponding to the service implementation manner.
In this embodiment, the robot process automation system is configured to store an operation process corresponding to interaction with the at least two second systems; and the robot process automation system is used for performing data interaction with the second system corresponding to the operation process according to the received service implementation mode and the operation process corresponding to the service implementation mode.
The data interaction method among the systems initiates a service request through the first system, determines a service implementation mode corresponding to the service request, and sends the service implementation mode to the robot process automation system so as to instruct the robot process automation system to perform data interaction with the second system according to an operation process corresponding to the service implementation mode; the robot process automation system does not perform data interaction with the second system through an interface, so that the robot process automation system is used as an intermediate system, data interaction between the first system and the second system can be realized, manual operation is not required to enter the second system for operation, and the data interaction efficiency between the systems is improved.
In one embodiment, sending a business implementation to a robotic process automation system comprises: calling an interface for communicating the first system with the robot flow automation system, and sending a service implementation mode to the robot flow automation system; the interface integrates the service implementation.
In particular, the interface may enable data interaction between the first system and the robotic process automation system. The interface between the first system and the robot process automation system integrates service implementation modes, such as operation process identification, robot process automation system client identification, robot process automation system scheduling parameters, and robot process automation system execution starting information. And the first computer equipment calls an interface for communication between the first system and the robot flow automation system and sends a service implementation mode to the robot flow automation system. Compared with the non-integrated mode, for example, when the menu directory in the first system is changed, the operation flow of the non-integrated mode needs to be changed at the same time, otherwise, the flow fails to find the menu according to the original menu directory, and the operation flow does not need to be changed in the integrated mode.
In the inter-system data interaction method in this embodiment, an interface through which the first system communicates with the robot flow automation system is called, and a service implementation manner is sent to the robot flow automation system, where the interface integrates the service implementation manner, that is, data and communication between the first system and the robot flow automation system are implemented through the interface, so that the situations of operation flow change and failure caused by frequent change of the system are greatly reduced.
In one embodiment, the number of service requests is at least two. Determining a service implementation mode corresponding to the service request comprises the following steps: determining a service implementation mode corresponding to each service request in at least two service requests; each service implementation mode comprises a robot process automation system identification and an operation process identification.
Calling an interface for communicating the first system with the robot flow automation system, and sending a service implementation mode to the robot flow automation system, wherein the interface comprises: and calling an interface for communication between the first system and the robot flow automation system, and respectively sending the corresponding operation flow identification to the robot flow automation system corresponding to each robot flow automation system identification.
The robot process automation system identifier may be an identifier of a client corresponding to the robot process automation system, or may be a system identifier of the robot process automation system identifier itself, which is not limited thereto. Each robot process automation system can store a plurality of operation processes.
Specifically, when the number of the initiated service requests is at least two, determining a service implementation manner corresponding to each service request in the at least two service requests; each service implementation mode comprises a robot process automation system and an operation process identifier. And calling an interface for communication between the first system and the robot flow automation system by the first computer equipment, and respectively sending corresponding operation flow identifiers to the robot flow automation system corresponding to each robot flow automation system identifier so as to enable the robot flow automation system to perform data interaction with the second system according to the operation flow corresponding to the operation flow identifier. For example, the first system interfaces with a robot process automation system a, and the corresponding service implementation manner is to import details, balance and receipt. At present, the first system is connected with a robot process automation system B, and the corresponding service implementation mode is to import details and report national taxes. Then, the import detail mode corresponding to the robot flow automation system a may be set in the first system, and the national tax reporting mode corresponding to the robot flow automation system B may also be set.
In this embodiment, the service implementation manner further includes an operation flow parameter. Taking the service request as an example of deriving the detail, the corresponding operation flow parameter may be a time parameter, for example, the detail from 8 months to 2020 in 2020 is derived, and "8 months to 2020 in 2020" may be the operation flow parameter. Calling an interface for communicating the first system with the robot flow automation system, and sending a service implementation mode to the robot flow automation system, wherein the interface comprises: and calling an interface for the first system to communicate with the robot process automation system, and respectively sending the corresponding operation process identification and the operation process parameter to the robot process automation system corresponding to each robot process automation system identification so that the robot process automation system executes the corresponding operation process according to the operation process identification and the operation process parameter to perform data interaction with the second system.
In the inter-system data interaction method in this embodiment, when the number of the service requests is at least two, a service implementation manner corresponding to each service request in the at least two service requests is determined, where each service implementation manner includes a robot flow automation system identifier and an operation flow identifier, and may be used to specify with which robot flow automation system the interaction is performed, and which operation flow is called; the method comprises the steps of calling an interface of a first system for communicating with the robot process automation system, sending corresponding operation process identifications to the robot process automation system corresponding to each robot process automation system identification, namely, providing a primary interface for one first system, interacting with a plurality of robot process automation systems, and being simple and convenient to use.
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 service implementation mode comprises a third-party service implementation mode. Sending a service implementation mode to a robot process automation system, comprising: and sending the third-party service implementation mode to the robot process automation system so as to instruct the robot process automation system to perform non-embedded data interaction with the second system according to the operation flow corresponding to the third-party service implementation mode.
Wherein the second system is a third-party system, that is, the second system is a system other than the first system and the robot process automation system, and the second system does not provide an interface for other systems to access. For example, the second system may be a banking system, a government system, or the like. Similarly, the third-party service implementation mode refers to a mode that can be implemented by the third-party system, and for example, the detailed mode of importing the third-party system, the receipt mode of importing the third-party system, and the like are not limited to this. Non-embedded data interaction is an interaction mode which can interact without providing an interface.
Specifically, the first computer device sends a third-party service implementation mode to the robot flow automation system to instruct the robot flow automation system to perform non-embedded data interaction with the second system according to an operation flow corresponding to the third-party service implementation mode.
In the data interaction method between systems in this embodiment, the third-party service implementation manner is sent to the robot flow automation system to instruct the robot flow automation system to perform non-embedded data interaction with the second system according to the operation flow corresponding to the third-party service implementation manner, so that an external interface is not required to be provided by the third-party system, and the interaction between the two systems can be performed on the premise of ensuring system stability and data security.
In one embodiment, the method for data interaction between systems further comprises: receiving third-party data sent by the robot process automation system through the first system; and the third-party data is sent to the first system by calling an interface which is arranged in the robot flow automation system and is communicated with the first system when the robot flow automation system acquires the third-party data returned by the third-party system.
The third-party data refers to data provided by a third-party system. And the third party data provided by different third party system categories is not the same. For example, the third party system is a banking system, and the third party data may be banking particulars. The third-party data is specifically obtained after the robot flow automation system operates the second system according to the operation flow corresponding to the service implementation mode, and the third-party data is sent to the first system by the robot flow automation system calling an interface which is set by the robot flow automation system and communicates with the first system.
Specifically, the robot process automation system operates the third-party system according to the operation process corresponding to the service implementation mode, and obtains third-party data corresponding to the operation process, which is returned by the third-party system. The robot process automation system calls an interface which is arranged in the robot process automation system and is communicated with the first system, and the third-party data is sent to the first system. And the first system receives third-party data sent by the robot process automation system.
In this embodiment, an interface for implementing an operation flow corresponding to each service may be integrated in the robot flow automation system. The third-party data is the third-party data sent by the robot process automation system, and the interface corresponding to the operation process and set in the robot process automation system is called to send the third-party data to the first system. That is, the robot process automation system returns data to the first system and calls different interfaces according to different data. For example, importing details, importing balances, and importing receipt are three interfaces.
In the data interaction method between systems in this embodiment, third-party data sent by the robot flow automation system is received by the first system, and when the third-party data is the third-party data returned by the third-party system, the interface which is set in the robot flow automation system and communicates with the first system is called, and the third-party data is sent to the first system, and the data obtained from the second system can be transmitted back to the first system, so that data interaction between systems is realized.
In one embodiment, sending a business implementation to a robotic process automation system comprises: acquiring a scheduling period of a service implementation mode; and sending a service implementation mode to the robot process automation system at regular time according to the scheduling period.
The scheduling period refers to a period of calling an interface for the first system to communicate with the robot process automation system, or a period of sending a service implementation manner. The scheduling period may be daily, weekly, monthly, quarterly, etc., or may be performed several times per day, may be started at several points, etc.
Specifically, the first computer device obtains a scheduling period for the service implementation. And sending the service implementation mode to the robot process automation system at regular time according to the scheduling period. For example, the scheduling period of the first computer device for the service implementation is 1 time per 1 day, and then the timing execution is performed according to 1 time per 1 day.
The inter-system data interaction method in this embodiment obtains a scheduling period for the service implementation manner, and sends the service implementation manner to the robot process automation system at regular time according to the scheduling period, so that interaction with the second system can be automatically implemented without manual intervention, and the inter-system interaction efficiency is improved.
In one embodiment, a method for data interaction between systems includes the following steps:
a step (a1) of initiating a service request through a first system;
step (a2), determining a service implementation mode corresponding to each service request in at least two service requests, wherein each service implementation mode comprises a robot process automation system identifier and an operation process identifier;
step (a3), obtaining a scheduling period for a service implementation mode;
and (a4) sending a third-party service implementation mode to the robot process automation system at regular time according to the scheduling period so as to instruct the robot process automation system to perform non-embedded data interaction with a second system according to an operation flow corresponding to the third-party service implementation mode, and interface integration the service implementation mode.
A step (a5) of receiving, by the first system, third-party data sent by the robot process automation system; and the third-party data is sent to the first system by calling an interface which is arranged in the robot flow automation system and is communicated with the first system when the robot flow automation system acquires the third-party data returned by the third-party system.
According to the data interaction method between the systems, the first system initiates a service request, determines a service implementation mode corresponding to the service request, sends a third-party service implementation mode to the robot process automation system, and instructs the robot process automation system to perform non-embedded data interaction with the second system according to an operation process corresponding to the third-party service implementation mode, so that the third-party system is not required to provide an external interface, and the interaction between the two systems can be performed on the premise of ensuring the system stability and data safety; the robot process automation system does not perform data interaction with the second system through an interface, so that the robot process automation system is used as an intermediate system, data interaction between the first system and the robot process automation system can be realized, manual operation in the second system is not required, and the data interaction efficiency between the systems is improved; data and communication between the first system and the robot process automation system are realized through an interface, so that the conditions of operation process change and failure caused by frequent change of the system are greatly reduced; namely, data and communication between the first system and the robot process automation system are realized through an interface, so that the situations of operation process change and failure caused by frequent change of the system are greatly reduced.
In one embodiment, as shown in FIG. 3, a system architecture diagram of a data interaction system in one embodiment is provided. Including a first system 302, a robotic process automation system 304, and a second system 306. The first system 302 performs data interaction with the robot process automation system 304 through a network, and the robot process automation system 304 performs data interaction with the second system 306 through the network. The first system 302 initiates a service request and determines a service implementation corresponding to the service request. The first system 302 sends the business implementation to the robotic process automation system 304. The robot process automation system 304 performs data interaction with the second system 306 according to the operation process corresponding to the service implementation manner.
In the data interaction system, the first system initiates a service request, determines a service implementation mode corresponding to the service request, and sends the service implementation mode to the robot flow automation system, and the robot flow automation system performs data interaction with the second system according to an operation flow corresponding to the service implementation mode; the robot process automation system does not perform data interaction with the second system through an interface, so that the robot process automation system is used as an intermediate system, data interaction between the first system and the second system can be realized, manual operation is not required to enter the second system for operation, and the data interaction efficiency between the systems is improved.
In one embodiment, the first system calls an interface for the first system to communicate with the robot flow automation system, and sends a service implementation mode to the robot flow automation system; and integrating the service implementation mode by the interface.
The data interaction system in this embodiment calls an interface through which the first system communicates with the robot process automation system, and sends a service implementation manner to the robot process automation system, where the interface integrates the service implementation manner, that is, data and communication between the first system and the robot process automation system are implemented through the interface, thereby greatly reducing situations of operation flow change and failure caused by frequent change of the system.
In one embodiment, the number of service requests is at least two. The first system determines a service implementation mode corresponding to each service request in at least two service requests; each service implementation mode comprises a robot process automation system identification and an operation process identification. And the first system calls an interface for communication between the first system and the robot process automation system, and sends the corresponding operation process identification to the robot process automation system corresponding to each robot process automation system identification.
In the data interaction system in this embodiment, when the number of the service requests is at least two, a service implementation manner corresponding to each service request in the at least two service requests is determined, where each service implementation manner includes a robot flow automation system identifier and an operation flow identifier, that is, the data interaction system may be used to specify with which robot flow automation system to interact and call which operation flow; the method comprises the steps of calling an interface of a first system for communicating with the robot process automation system, sending corresponding operation process identifications to the robot process automation system corresponding to each robot process automation system identification, namely, providing a primary interface for one first system, interacting with a plurality of robot process automation systems, and being simple and convenient to use.
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 service implementation mode comprises a third-party service implementation mode. The first system sends a third-party service implementation mode to the robot process automation system; and the robot process automation system performs non-embedded data interaction with the second system according to the operation process corresponding to the third-party service implementation mode.
The data interaction system in this embodiment sends the third-party service implementation manner to the robot flow automation system to instruct the robot flow automation system to perform non-embedded data interaction with the second system according to the operation flow corresponding to the third-party service implementation manner, so that an external interface is not required to be provided by the third-party system, and the interaction between the two systems can be performed on the premise of ensuring system stability and data security.
In one embodiment, the third party system generates third party data corresponding to the operational flow. The robot process automation system acquires and calls an interface which is arranged in the robot process automation system and is communicated with the first system, and sends the third-party data to the first system. And the first system receives the third-party data sent by the first system.
In the intersystem data interaction system in this embodiment, the first system receives third-party data sent by the robot flow automation system, and when the third-party data is third-party data returned by the third-party system, the third-party data is sent to the first system by calling an interface, which is set in the robot flow automation system and communicates with the first system, and the third-party data is sent to the first system, so that data obtained from the second system can be transmitted back to the first system, and intersystem data interaction is achieved.
In one embodiment, a first system obtains a scheduling period for a service implementation; and sending a service implementation mode to the robot process automation system at regular time according to the scheduling period.
The data interaction system in this embodiment obtains a scheduling period for the service implementation manner, and sends the service implementation manner to the robot process automation system at regular time according to the scheduling period, so that interaction with the second system can be automatically implemented without manual intervention, and interaction efficiency between the systems is improved.
In one embodiment, the robot process automation system stores operation processes corresponding to interaction with at least two second systems; and the robot process automation system performs data interaction with the second system corresponding to the operation process according to the received service implementation mode and the operation process corresponding to the service implementation mode.
In the data interaction system in this embodiment, different operation flows may be set in the robot flow automation system to log in different second systems, so as to improve the extensibility of the robot flow automation system.
In one embodiment, the first system is an enterprise resource planning system and the second system is an example of an online banking behavior. FIG. 4 is a block diagram that illustrates an architecture of the enterprise resource planning system and online banking, according to an embodiment. The system comprises an enterprise resource planning system, an online bank X, an online bank Y and an online bank Z. The internet bank X, the internet bank Y and the internet bank Z are all banking systems. Internet banking: the network bank is also called network bank, on-line bank or electronic bank, it is a virtual counter set in the Internet of every bank, and the bank utilizes network technology to provide traditional service items of opening an account, selling account, inquiry, account checking, in-line transfer, cross-line transfer, credit, network securities, investment and financing, etc. to customer by means of Internet, so that the customer can safely and conveniently manage life time and regular deposit, check, credit card and personal investment, etc. without going out. In addition, the enterprise resource planning system in fig. 4 cannot directly interact with the internet bank X, the internet bank Y and the internet bank Z. Because not all online banks provide a bank-enterprise direct connection mode to directly connect with each other to know balance information in real time, but all banks provide online banking services, and some online banks with low use frequency do not open bank-enterprise direct connection, but only open the online banks of the banks, so that the user cannot quickly obtain information such as the latest account balance of a group at present. The bank-enterprise direct connection refers to the connection of a bank system and an ERP system of an enterprise, and the enterprise directly handles bank services such as account management, transfer payment and the like through the ERP system. In addition, the user can obtain data through the internet bank, but at present, all the internet banks of the bank do not have an open interface, and the enterprise resource planning system cannot call the data.
Corresponding to an enterprise resource planning system and an online bank, the current heterogeneous system integration scheme comprises the following steps:
(1) embedded interaction, which requires the system of the calling party and the called party to provide and develop a calling interface for embedded interaction, but online banking does not provide an interface and cannot use the method.
(2) Manual processing: and manually exporting the data of the caller system, and after the data is manually processed, importing or filling the data into the callee system.
For the above (1), embedded interaction requires external interface development of both the calling party and the called party, which has certain influence on system stability and data security, and the development cost is high. And the bank internet bank does not open an interface to call the enterprise resource planning system, so that the enterprise resource planning system cannot perform data interaction with the internet bank.
For the above (2), manual processing, manual logging in of the internet bank, large amount of data and many processes are performed, and repeated operations are required, for example, downloading of a bank transaction flow, logging in different internet bank systems every day, logging in an account, logging in a date and the like, querying, exporting … and the like are required, so that the time consumption is long, and the data acquisition efficiency is low.
Therefore, the data interaction system between the systems in the embodiment of the application is provided. Fig. 5 is a schematic structural diagram of a data interaction system in another embodiment. Fig. 5 illustrates an example in which the first system is an enterprise resource planning system, and the second system includes an internet bank X, an internet bank Y, and an internet bank Z. Fig. 5 includes an enterprise resource planning system (ERP system), an enterprise resource planning system (RPA system), and a client of a robot process automation system (RPA client), and an internet bank X, an internet bank Y, and an internet bank Z.
1. If the ERP wants to perform data interaction with the online bank, the intermediate RPA is used as a bridge.
2. The user only needs to manually set a scheme for interacting with data of the heterogeneous system in the ERP, for example, import details, namely exporting transaction flow from the online banking system and importing the transaction flow into the ERP system, and set a scheduling period of the scheme, namely scheduling every day or scheduling every month, executing several times every day, executing several points and the like. Wherein, heterogeneous system refers to internet banking.
3. After the scheme is set, the ERP can initiate a manual call to the scheme to execute in real time or execute the scheme at regular time according to the scheduling setting, and the ERP initiates a scheme execution request to the RPA console according to different set schemes.
4. And the RPA system performs data interaction with a third-party heterogeneous system according to the received scheme and a preset flow.
The data interaction system realizes the non-embedded interaction between the ERP and the online bank by utilizing the butt joint of the ERP and the RPA, does not need an external interface provided by the called online bank, and carries out the interaction of the systems of the two parties on the premise of ensuring the stability of the systems and the data safety; because the ERP system is generally used by groups, the butt joint of the ERP and the RPA is realized, the RPA robot can simulate the operation of a human only by manually configuring a scheme, and the RPA robot can replace the human to complete the work with complicated flow, high repeatability and large data volume, thereby liberating a large amount of human resources; the RPA flow which is used after being opened can be built in the ERP, and the integration is carried out through the interface and the RPA flow, so that the conditions of RPA flow change and failure caused by frequent change of the system are greatly reduced.
It should be understood that although the various steps in the diagrams of fig. 2 and 5 are shown in order as indicated by the arrows, the steps are not necessarily performed in order 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 some of the steps in fig. 2 and 5 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps.
In one embodiment, as shown in fig. 6, there is provided an inter-system data interaction apparatus, including: a service request initiating module 602, a service implementation determining module 604 and a service implementation sending module 606, wherein:
a service request initiating module 602, configured to initiate a service request through the first system.
A service implementation determining module 604, configured to determine a service implementation corresponding to the service request.
And a service implementation manner sending module 606, configured to send the service implementation manner to the robot flow automation system, so that the robot flow automation system performs data interaction with the second system according to the received service implementation manner and according to the operation flow corresponding to the service implementation manner.
The data interaction device between the systems initiates a service request through the first system, determines a service implementation mode corresponding to the service request, and sends the service implementation mode to the robot process automation system so as to instruct the robot process automation system to perform data interaction with the second system according to an operation process corresponding to the service implementation mode; the robot process automation system does not perform data interaction with the second system through an interface, so that the robot process automation system is used as an intermediate system, data interaction between the first system and the second system can be realized, manual operation is not required to enter the second system for operation, and the data interaction efficiency between the systems is improved.
In one embodiment, the service implementation sending module 606 is configured to call an interface through which the first system communicates with the robot flow automation system, and send the service implementation to the robot flow automation system; the interface integrates the service implementation.
The inter-system data interaction device in this embodiment calls an interface through which the first system communicates with the robot flow automation system, and sends a service implementation manner to the robot flow automation system, where the interface integrates the service implementation manner, that is, data and communication between the first system and the robot flow automation system are implemented through the interface, so that changes and failures of an operation flow caused by frequent changes of the system are greatly reduced.
In one embodiment, the number of service requests is at least two. A service implementation determining module 604, configured to determine a service implementation corresponding to each service request in the at least two service requests; each service implementation mode comprises a robot process automation system identification and an operation process identification.
In the inter-system data interaction device in this embodiment, when the number of the service requests is at least two, a service implementation manner corresponding to each service request in the at least two service requests is determined, where each service implementation manner includes a robot flow automation system identifier and an operation flow identifier, that is, the data interaction device may be used to specify which robot flow automation system to interact with and call which operation flow; the method comprises the steps of calling an interface of a first system for communicating with the robot process automation system, sending corresponding operation process identifications to the robot process automation system corresponding to each robot process automation system identification, namely, providing a primary interface for one first system, interacting with a plurality of robot process automation systems, and being simple and convenient to use.
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 service implementation mode comprises a third-party service implementation mode. And a service implementation manner sending module 606, configured to send the third-party service implementation manner to the robot flow automation system, so as to instruct the robot flow automation system to perform non-embedded data interaction with the second system according to the operation flow corresponding to the third-party service implementation manner.
The inter-system data interaction device in this embodiment sends the third-party service implementation manner to the robot flow automation system to instruct the robot flow automation system to perform non-embedded data interaction with the second system according to the operation flow corresponding to the third-party service implementation manner, so that an external interface is not required to be provided by the third-party system, and interaction between the two systems can be performed on the premise of ensuring system stability and data security.
In one embodiment, the data interaction between the systems further comprises a receiving module, wherein the receiving module is used for receiving third-party data sent by the robot process automation system through the first system; and the third-party data is sent to the first system by calling an interface which is arranged in the robot flow automation system and is communicated with the first system when the robot flow automation system acquires the third-party data returned by the third-party system.
In the inter-system data interaction device in this embodiment, the first system is used to receive third-party data sent by the robot flow automation system, and when the third-party data is the third-party data returned by the third-party system obtained by the robot flow automation system, an interface which is set in the robot flow automation system and communicates with the first system is called, and the third-party data is sent to the first system, so that data obtained from the second system can be transmitted back to the first system, and inter-system data interaction is achieved.
In one embodiment, the service implementation sending module 606 is configured to obtain a scheduling period of the service implementation; and sending a service implementation mode to the robot process automation system at regular time according to the scheduling period.
The inter-system data interaction device in this embodiment obtains a scheduling period for the service implementation manner, and sends the service implementation manner to the robot process automation system at regular time according to the scheduling period, so that interaction with the second system can be automatically implemented without manual intervention, and the inter-system interaction efficiency is improved.
For specific limitations of the inter-system data interaction device, reference may be made to the above limitations of the inter-system data interaction method, which is not described herein again. The modules in the data interaction device between the systems can be wholly or partially 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 terminal, and its internal structure diagram may be as shown in fig. 7. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device 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 comprises a nonvolatile 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 an operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a method of data interaction between systems. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
Those skilled in the art will appreciate that the architecture shown in fig. 7 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 further provided, which includes a memory and a processor, the memory stores a computer program, and the processor implements the steps of the above method embodiments when executing the computer program.
In an embodiment, a computer-readable storage medium is provided, in which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.
In one embodiment, a computer program product or computer program is provided that includes computer instructions stored in a computer-readable storage medium. The computer instructions are read by a processor of a computer device from a computer-readable storage medium, and the computer instructions are executed by the processor to cause the computer device to perform the steps in the above-mentioned method embodiments.
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, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. 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 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 invention. 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 patent shall be subject to the appended claims.
Claims (10)
1. A method for data interaction between systems, the method comprising:
initiating a service request through a first system;
determining a service implementation mode corresponding to the service request;
and sending the service implementation mode to a robot flow automation system to instruct the robot flow automation system to perform data interaction with a second system according to the operation flow corresponding to the service implementation mode.
2. The method of claim 1, wherein sending the business implementation to a robotic process automation system comprises:
calling an interface for communicating the first system with the robot flow automation system, and sending a service implementation mode to the robot flow automation system; the interface integrates the service implementation.
3. The method of claim 2, wherein the number of service requests is at least two;
determining a service implementation mode corresponding to the service request includes:
determining a service implementation mode corresponding to each service request in at least two service requests; each service implementation mode comprises a robot process automation system identifier and an operation process identifier;
the calling of the interface for communication between the first system and the robot process automation system and the sending of the service implementation mode to the robot process automation system comprise:
and calling an interface for communicating the first system with the robot process automation system, and respectively sending the corresponding operation process identification to the robot process automation system corresponding to each robot process automation system identification.
4. The method of claim 1, wherein the second system is a third party system; the second system does not provide an interface for other systems to access; the service implementation mode comprises a third-party service implementation mode;
the sending the service implementation mode to the robot process automation system includes:
and sending the third-party service implementation mode to a robot process automation system so as to instruct the robot process automation system to perform non-embedded data interaction with the second system according to the operation flow corresponding to the third-party service implementation mode.
5. The method of claim 4, further comprising:
receiving third-party data sent by the robot process automation system through the first system; and the third-party data is sent to the first system by calling an interface which is arranged in the robot process automation system and is communicated with the first system when the robot process automation system acquires the third-party data returned by the third-party system.
6. The method of claim 1, wherein sending the business implementation to a robotic process automation system comprises:
acquiring a scheduling period of the service implementation mode;
and sending the service implementation mode to a robot process automation system at regular time according to the scheduling period.
7. A data interaction system is characterized by comprising a first system, a robot process automation system and a second system;
the first system initiates a service request and determines a service implementation mode corresponding to the service request;
the first system sends the service implementation mode to the robot process automation system;
and the robot process automation system performs data interaction with the second system according to the operation process corresponding to the service implementation mode.
8. An apparatus for data interaction between systems, the apparatus comprising:
a service request initiating module, configured to initiate a service request through a first system;
a service implementation mode determining module, configured to determine a service implementation mode corresponding to the service request;
and the service implementation mode sending module is used for sending the service implementation mode to the robot flow automation system so that the robot flow automation system performs data interaction with the second system according to the received service implementation mode and the operation flow corresponding to the service implementation mode.
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 6.
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 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011562920.4A CN112612624A (en) | 2020-12-25 | 2020-12-25 | Data interaction method and device between systems, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011562920.4A CN112612624A (en) | 2020-12-25 | 2020-12-25 | Data interaction method and device between systems, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112612624A true CN112612624A (en) | 2021-04-06 |
Family
ID=75247841
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011562920.4A Pending CN112612624A (en) | 2020-12-25 | 2020-12-25 | Data interaction method and device between systems, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112612624A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112926954A (en) * | 2021-04-26 | 2021-06-08 | 南京微雀信息技术有限公司 | Cross-network government affair information exchange system and method based on artificial intelligent robot |
| CN113467879A (en) * | 2021-07-20 | 2021-10-01 | 上海数慧系统技术有限公司 | Multi-system data processing method and device based on RPA robot |
| CN114035860A (en) * | 2021-11-04 | 2022-02-11 | 四川启睿克科技有限公司 | Process parameter configuration system based on RPA global variable module |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060206246A1 (en) * | 2004-10-28 | 2006-09-14 | Walker Richard C | Second national / international management and security system for responsible global resourcing through technical management to brige cultural and economic desparity |
| CN107592321A (en) * | 2017-10-27 | 2018-01-16 | 天津港中煤华能煤码头有限公司 | Single-node login system |
| CN109618068A (en) * | 2018-11-08 | 2019-04-12 | 上海航动科技有限公司 | A kind of voice service method for pushing, device and system based on artificial intelligence |
| CN110147397A (en) * | 2019-04-10 | 2019-08-20 | 管南风 | System docking method, apparatus, management system and terminal device, storage medium |
| CN110806934A (en) * | 2019-11-15 | 2020-02-18 | 四川中电启明星信息技术有限公司 | RPA technology-based intelligent all-in-one machine development and multi-service rapid processing method |
| CN111798216A (en) * | 2020-07-14 | 2020-10-20 | 上海智子信息科技股份有限公司 | Robot process automation multi-tool integration method and system |
-
2020
- 2020-12-25 CN CN202011562920.4A patent/CN112612624A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060206246A1 (en) * | 2004-10-28 | 2006-09-14 | Walker Richard C | Second national / international management and security system for responsible global resourcing through technical management to brige cultural and economic desparity |
| CN107592321A (en) * | 2017-10-27 | 2018-01-16 | 天津港中煤华能煤码头有限公司 | Single-node login system |
| CN109618068A (en) * | 2018-11-08 | 2019-04-12 | 上海航动科技有限公司 | A kind of voice service method for pushing, device and system based on artificial intelligence |
| CN110147397A (en) * | 2019-04-10 | 2019-08-20 | 管南风 | System docking method, apparatus, management system and terminal device, storage medium |
| CN110806934A (en) * | 2019-11-15 | 2020-02-18 | 四川中电启明星信息技术有限公司 | RPA technology-based intelligent all-in-one machine development and multi-service rapid processing method |
| CN111798216A (en) * | 2020-07-14 | 2020-10-20 | 上海智子信息科技股份有限公司 | Robot process automation multi-tool integration method and system |
Non-Patent Citations (1)
| Title |
|---|
| 庄严等: "基于网络的机器人控制技术研究现状与发展", 机器人, no. 03 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112926954A (en) * | 2021-04-26 | 2021-06-08 | 南京微雀信息技术有限公司 | Cross-network government affair information exchange system and method based on artificial intelligent robot |
| CN113467879A (en) * | 2021-07-20 | 2021-10-01 | 上海数慧系统技术有限公司 | Multi-system data processing method and device based on RPA robot |
| CN114035860A (en) * | 2021-11-04 | 2022-02-11 | 四川启睿克科技有限公司 | Process parameter configuration system based on RPA global variable module |
| CN114035860B (en) * | 2021-11-04 | 2023-06-13 | 四川启睿克科技有限公司 | Flow parameter configuration system based on RPA global variable module |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112612624A (en) | Data interaction method and device between systems, computer equipment and storage medium | |
| US11132183B2 (en) | Software development platform for testing and modifying decision algorithms | |
| WO2021135169A1 (en) | Blockchain-based management method, terminal, apparatus, and storage medium | |
| CN104216912A (en) | Method and device for achieving non-intrusive service form workflow | |
| CN110471951A (en) | Determine the method for the sequence of Transaction Information, accounting nodes and medium in data block | |
| CN110941630A (en) | Database operation and maintenance method, device and system | |
| CN110458572B (en) | User risk determining method and target risk recognition model establishing method | |
| CN110046900A (en) | Invoice based on block chain cancels method and apparatus, electronic equipment | |
| CN112288400A (en) | Multi-system data interaction method and device, computer equipment and storage medium | |
| CN109543891A (en) | Method for building up, equipment and the computer readable storage medium of capacity prediction model | |
| CN115344888A (en) | Data access method and device, electronic equipment and storage medium | |
| CN106533718B (en) | Data processing method and device | |
| CN112035676A (en) | User operation behavior knowledge graph construction method and device | |
| CN112102099A (en) | Policy data processing method and device, electronic equipment and storage medium | |
| TW202103076A (en) | Resource transfer and allocation method and device Resource transfer and allocation method and device | |
| CN114996577A (en) | Service management method, device, apparatus, storage medium, and program product | |
| US20030163472A1 (en) | Operational system for operating on client defined rules | |
| CN109858959A (en) | Credit card recommended method, device, computer equipment and storage medium | |
| CN114298694A (en) | Block chain service platform management method and device, computer equipment and storage medium | |
| CN114254278A (en) | User account merging method and device, computer equipment and storage medium | |
| CN112231377A (en) | Data mapping method, system, device, server and storage medium | |
| CN114428723A (en) | Test system, system test method, related device and storage medium | |
| CN111429125A (en) | Account management method and device, storage medium and electronic equipment | |
| Maulana et al. | Enterprise System Modeling for Business Licensing Services | |
| CN114666116A (en) | Verification processing method, device, equipment and storage medium based on small program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |