CN116541195A - Abnormality processing method and related device for robot flow automation program RPA - Google Patents
Abnormality processing method and related device for robot flow automation program RPA Download PDFInfo
- Publication number
- CN116541195A CN116541195A CN202310361722.9A CN202310361722A CN116541195A CN 116541195 A CN116541195 A CN 116541195A CN 202310361722 A CN202310361722 A CN 202310361722A CN 116541195 A CN116541195 A CN 116541195A
- Authority
- CN
- China
- Prior art keywords
- abnormal
- rpa
- scene
- execution
- flow
- 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
- 230000005856 abnormality Effects 0.000 title claims description 11
- 238000003672 processing method Methods 0.000 title claims description 7
- 230000002159 abnormal effect Effects 0.000 claims abstract description 242
- 238000000034 method Methods 0.000 claims abstract description 126
- 230000008569 process Effects 0.000 claims abstract description 83
- 238000012544 monitoring process Methods 0.000 claims abstract description 80
- 238000012545 processing Methods 0.000 claims abstract description 68
- 238000004590 computer program Methods 0.000 claims description 34
- 239000000725 suspension Substances 0.000 claims description 13
- 230000006870 function Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 5
- 238000004801 process automation Methods 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000012423 maintenance Methods 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
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
- G06F11/3093—Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention provides an exception handling method and a related device for an RPA (remote procedure access) of a robot flow automation program, which are used for improving the handling efficiency of the RPA program exception. The method of the embodiment of the invention comprises the following steps: executing a business process; judging whether the business process is abnormal or not during the execution of the business process; if yes, screenshot is carried out on the scene of the abnormal flow; sending the scene screenshot of the abnormal flow to an RPA monitoring end, so that the RPA monitoring end carries out abnormal judgment on the scene screenshot of the abnormal flow; receiving an execution instruction which is returned by the RPA monitoring end and is aimed at an abnormal scene; and processing the abnormal business flow according to the execution instruction aiming at the abnormal scene.
Description
Technical Field
The present invention relates to data processing of a Robot Program Automation (RPA), and more particularly, to a method and apparatus for processing an abnormality of a Robot Program Automation (RPA).
Background
RPA: robot Process Automation (RPA) is a business process automation technology based on software robots and Artificial Intelligence (AI). A Robotic Process Automation (RPA) system is an application that provides another way to automate an end user's manual process by mimicking the end user's manual process at a computer.
In the existing RPA program running process, the RPA program cannot be processed normally due to the program change, the machine environment difference, the data difference which cannot be considered in advance, and other scenes. Most of the current schemes are to directly suspend the operation of the RPA program and wait for operation maintenance personnel to process, and the manual way of processing the RPA abnormal program is often inefficient.
Disclosure of Invention
The embodiment of the invention provides an exception handling method and a related device for an RPA (remote procedure access) of a robot flow automation program, which are used for improving the handling efficiency of the RPA program exception.
An embodiment of the present application provides an exception handling method of an RPA of a robot flow automation program, applied to one or more RPA execution ends, where the method includes:
executing a business process;
judging whether the business process is abnormal or not during the execution of the business process;
if yes, screenshot is carried out on the scene of the abnormal flow;
sending the scene screenshot of the abnormal flow to an RPA monitoring end, so that the RPA monitoring end carries out abnormal judgment on the scene screenshot of the abnormal flow;
receiving an execution instruction which is returned by the RPA monitoring end and is aimed at an abnormal scene;
and processing the abnormal business flow according to the execution instruction aiming at the abnormal scene.
Preferably, the one or more RPA execution ends pre-store rule bases of abnormal scenes, and the judging whether the business process is abnormal during the execution of the business process includes:
during the execution of the business process, matching the obtained process screenshot with a rule base of the abnormal scene;
if the matching is successful, determining that the business process is abnormal.
Preferably, the execution instruction for the abnormal scene includes a processing instruction or an abort instruction of a known problem;
the processing the abnormal business process according to the execution instruction aiming at the abnormal scene comprises the following steps:
and processing the abnormal business flow according to the processing instruction or the stopping instruction of the known problem.
Preferably, the one or more RPA execution ends are deployed at a client or a server, and the method further includes:
and recording the work log information of the abnormal business process.
A second aspect of the present embodiment provides an exception handling method of an RPA of a robot flow automation program, applied to an RPA monitoring end, where the method includes:
receiving a scene screenshot of an abnormal flow sent by one or more RPA execution ends;
matching the scene screenshot of the abnormal flow with a preset abnormal problem library to obtain an execution instruction aiming at the abnormal scene;
and sending an execution instruction aiming at the abnormal scene to the one or more RPA execution ends.
Preferably, the RPA monitoring end is deployed at a server side, and the execution instruction for the abnormal scene includes a processing instruction or a suspension instruction of a known problem;
matching the scene screenshot of the abnormal flow with a preset abnormal problem library to obtain an execution instruction aiming at the abnormal scene, and sending the execution instruction aiming at the abnormal scene to the one or more RPA execution ends, wherein the method comprises the following steps:
matching the scene screenshot of the abnormal flow with a preset abnormal problem library to obtain a processing instruction or a suspension instruction of the known problem;
the processing instructions or suspension instructions of the known problem are sent to one or more RPA execution ends.
A third aspect of the embodiments of the present application provides an RPA execution end, including:
the execution unit is used for executing the business process;
the judging unit is used for judging whether the business process is abnormal or not during the execution of the business process;
the screenshot unit is used for screenshot of a scene of the abnormal flow if the scene is the abnormal flow;
the sending unit is used for sending the scene screenshot of the abnormal flow to the RPA monitoring end so that the RPA monitoring end can perform abnormal judgment on the scene screenshot of the abnormal flow;
the receiving unit is used for receiving an execution instruction which is returned by the RPA monitoring end and is aimed at an abnormal scene;
and the processing unit is used for processing the abnormal business flow according to the execution instruction aiming at the abnormal scene.
Preferably, the judging unit is specifically configured to:
during the execution of the business process, matching the obtained process screenshot with a rule base of the abnormal scene;
if the matching is successful, determining that the business process is abnormal.
Preferably, the execution instruction for the abnormal scene includes a processing instruction or an abort instruction of a known problem;
the processing unit is specifically configured to:
and processing the abnormal business flow according to the processing instruction or the stopping instruction of the known problem.
Preferably, the one or more RPA execution ends are deployed at a client or a server, and the RPA execution ends further include:
and the recording unit is used for recording the work log information of the abnormal business process.
A fourth aspect of the present embodiment provides an RPA monitoring terminal, including:
the receiving unit is used for receiving the scene screenshot of the abnormal flow sent by one or more RPA execution ends;
the matching unit is used for matching the scene screenshot of the abnormal flow with a preset abnormal problem library to obtain an execution instruction aiming at the abnormal flow;
and the sending unit is used for sending the execution instruction aiming at the abnormal scene to the one or more RPA execution ends.
Preferably, the RPA monitoring end is deployed at a server side, and the execution instruction for the abnormal scene includes a processing instruction or a suspension instruction of a known problem;
the sending unit is specifically configured to:
the processing instructions or suspension instructions of the known problem are sent to one or more RPA execution ends.
A fifth aspect of the present embodiment provides an exception handling system for an RPA of a robot flow automation program, including an RPA execution end provided in the third aspect of the present embodiment and an RPA monitoring end provided in the fourth aspect of the present embodiment.
A sixth aspect of the embodiments of the present application provides a computer apparatus, including a processor, where the processor is configured to implement the method for exception handling of the robot flow automation program RPA provided in the first aspect or the second aspect of the embodiments of the present application when executing a computer program stored on a memory.
A seventh aspect of the embodiments of the present application provides a computer-readable storage medium having stored thereon a computer program for implementing the abnormality processing method of the robot flow automation program RPA provided in the first aspect or the second aspect of the embodiments of the present application when the computer program is executed by a processor.
An eighth aspect of the embodiments of the present application provides a computer program product, which stores a computer program, where the computer program is executed by a processor, is configured to implement the method for exception handling of the robot flow automation program RPA provided in the first aspect or the second aspect of the embodiments of the present application.
From the above technical solutions, the embodiment of the present invention has the following advantages:
in the embodiment of the application, the RPA monitoring end is configured for one or more RPA execution ends, so that when one or more RPA execution ends are abnormal, the screenshot of the abnormal flow can be sent to the RPA monitoring end, the RPA monitoring end processes the abnormal flow, and the execution instruction aiming at the abnormal scene is sent to the RPA execution end, thereby realizing the automatic processing of the abnormal flow by the RPA execution end and improving the processing efficiency of the abnormal flow by the RPA execution end.
Drawings
FIG. 1 is a schematic diagram of an embodiment of an exception handling method of a Robot Program Automation (RPA) in an embodiment of the application;
FIG. 2 is a schematic diagram of another embodiment of an exception handling method of a Robot Program Automation (RPA) in an embodiment of the application;
FIG. 3 is a schematic diagram of an embodiment of an RPA execution end according to an embodiment of the present application;
FIG. 4 is a schematic diagram of an embodiment of an RPA monitoring end in an embodiment of the present application;
FIG. 5 is a schematic diagram of an embodiment of an exception handling system of a robot flow automation program RPA in an embodiment of the application.
Detailed Description
The embodiment of the invention provides an exception handling method and a related device for an RPA (remote procedure access) of a robot flow automation program, which are used for improving the handling efficiency of the RPA program exception.
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
The terms first, second, third, fourth and the like in the description and in the claims and in the above drawings are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
For convenience of understanding, the following describes, in an interactive manner, an exception handling method of a robot flow automation program RPA in the present application, where the exception handling method of the robot flow automation program RPA in the embodiment of the present application is applied to an RPA execution end and an RPA monitoring end, and the RPA execution end in the embodiment of the present application includes one or more, please refer to fig. 1, and one embodiment of the exception handling method of the robot flow automation program RPA in the embodiment of the present application includes:
101. one or more RPA execution ends execute the business flow;
specifically, the execution end of the Robot Process Automation (RPA) may be deployed on a client, such as a computer, a PAD, or a wearable device, or may be deployed on a cloud server, and the service process executed by the execution end of the RPA may be a search task, a calculation task, or a drawing task, which is not limited in this case.
102. One or more RPA execution ends determine whether a business process abnormality occurs during the execution of the business process, and if yes, execute step 103;
during the execution of the service flow, the RPA execution end determines whether the service flow is abnormal, and if yes, step 103 is executed.
Specifically, when judging whether the service flow is abnormal, the RPA executing end may match the obtained flow screenshot with a rule base of an abnormal scene, if the matching is successful, it is determined that the service flow is abnormal, otherwise, it is determined that the service flow is normal.
103. One or more RPA execution ends screen capture the scene of the abnormal flow;
if the RPA executing end determines that the business process is abnormal, the scene of the abnormal process is captured, and the scene capture of the abnormal process is sent to the RPA monitoring end.
Specifically, when the screen capturing is performed, the WindowsAPI may be used to perform the screen capturing on the full screen, or the screen capturing may be performed by using a screen capturing applet, which is not limited herein.
104. One or more RPA execution ends send the scene screenshot of the abnormal flow to an RPA monitoring end;
after the RPA executing end obtains the scene screenshot of the abnormal flow, the scene screenshot of the abnormal flow is sent to the RPA monitoring end, so that the RPA monitoring end processes the scene screenshot of the abnormal flow.
105. The RPA monitoring end matches the scene screenshot of the abnormal flow with a preset abnormal problem library;
after the RPA monitoring end obtains the scene screenshot of the abnormal flow, the scene screenshot of the abnormal flow is matched with a preset abnormal problem library, and then after the matching is finished, an execution instruction aiming at the abnormal scene is sent to one or more RPA execution ends.
106. The RPA monitoring end sends an execution instruction aiming at the abnormal scene to one or more RPA execution ends.
After the matching is finished, the RPA monitoring end sends an execution instruction aiming at the abnormal scene to one or more RPA execution ends.
107. And the one or more RPA execution ends process the abnormal business flow according to the execution instruction aiming at the abnormal scene.
After one or more RPA execution ends receive the execution instruction for the abnormal scene sent by the RPA monitoring end, the abnormal business process is processed according to the execution instruction for the abnormal scene so as to ensure the normal work of the RPA execution end.
In the embodiment of the application, the RPA monitoring end is configured for one or more RPA execution ends, so that when one or more RPA execution ends are abnormal, the screenshot of the abnormal flow can be sent to the RPA monitoring end, the RPA monitoring end processes the abnormal flow, and the execution instruction aiming at the abnormal scene is sent to the RPA execution end, thereby realizing the automatic processing of the abnormal flow by the RPA execution end and improving the processing efficiency of the abnormal flow by the RPA execution end.
Based on the embodiment described in fig. 1, when the RPA executing end sends the screenshot of the abnormal flow to the RPA monitoring end, the following steps may be further executed, please refer to fig. 2, fig. 2 is another embodiment of the method for processing the abnormality of the robot flow automation program RPA in the embodiment of the present application:
201. one or more RPA execution ends execute the business flow;
specifically, the execution end of the Robot Process Automation (RPA) may be deployed on a client, such as a computer, a PAD, or a wearable device, or may be deployed on a cloud server, and the service process executed by the execution end of the RPA may be a search task, a calculation task, or a drawing task, which is not limited in this case.
202. During the execution of the business process, judging whether the business process is abnormal, if so, executing step 203;
during the execution of the service flow, the RPA executing end determines whether the service flow is abnormal, and if yes, step 203 is executed.
Specifically, when judging whether the service flow is abnormal, the RPA executing end may match the obtained flow screenshot with a rule base of an abnormal scene, if the matching is successful, it is determined that the service flow is abnormal, otherwise, it is determined that the service flow is normal.
203. Screenshot is carried out on the scene of the abnormal flow, and the work log information of the abnormal business flow is recorded;
if the RPA executing end determines that the business process is abnormal, the scene of the abnormal process is captured, and the scene capture of the abnormal process is sent to the RPA monitoring end.
Specifically, when the screen capturing is performed, the WindowsAPI may be used to perform the screen capturing on the full screen, or the screen capturing may be performed by using a screen capturing applet, which is not limited herein.
Furthermore, in the embodiment of the application, the RPA execution end further records the work log information of the abnormal flow besides performing screenshot on the scene of the abnormal flow, so as to be used for manually processing the abnormal flow in the later period.
204. The scene screenshot of the abnormal flow is sent to an RPA monitoring end;
after the RPA executing end obtains the scene screenshot of the abnormal flow, the scene screenshot of the abnormal flow is sent to the RPA monitoring end, so that the RPA monitoring end processes the scene screenshot of the abnormal flow.
205. The RPA monitoring end matches the scene screenshot of the abnormal flow with a preset abnormal problem library;
after the RPA monitoring end obtains the scene screenshot of the abnormal flow, the scene screenshot of the abnormal flow is matched with a preset abnormal problem library, and then after the matching is finished, an execution instruction aiming at the abnormal scene is sent to one or more RPA execution ends.
206. The RPA monitoring end sends a processing instruction or an abort instruction of a known problem to one or more RPA execution ends.
After the matching is finished, the RPA monitoring end sends an execution instruction aiming at the abnormal scene to one or more RPA execution ends.
Specifically, the execution instruction for the abnormal scene may be a processing instruction or a suspension instruction of a known problem, for example, the RPA monitoring end matches the scene screenshot of the abnormal flow with a preset abnormal problem library, if the matching is successful, it indicates that the abnormal flow is a known problem, then the processing instruction of the known problem is sent to the RPA executing end, otherwise, it indicates that the abnormal flow is an unknown problem which has not occurred before, and then the suspension instruction is sent to the RPA executing end.
207. And the one or more RPA execution ends process the abnormal business flow according to the processing instruction or the suspension instruction of the known problem.
After one or more RPA execution ends receive the processing instruction or the suspension instruction of the known problem sent by the RPA monitoring end, the abnormal business flow is processed according to the processing instruction or the suspension instruction of the known problem, so as to ensure the normal work of the RPA execution end.
In the embodiment of the application, the RPA monitoring end is configured for one or more RPA execution ends, so that when one or more RPA execution ends are abnormal, the screenshot of the abnormal flow can be sent to the RPA monitoring end, the RPA monitoring end processes the abnormal flow, and the execution instruction aiming at the abnormal scene is sent to the RPA execution end, thereby realizing the automatic processing of the abnormal flow by the RPA execution end and improving the processing efficiency of the abnormal flow by the RPA execution end.
Furthermore, in the embodiment of the application, when the RPA executing end sends the scene screenshot of the abnormal flow, the working log information of the abnormal flow is further recorded, so that when the RPA monitoring end cannot send a processing instruction of a known problem, the abnormal flow can be processed manually at a later stage, and the completeness of the RPA abnormal problem solution is improved.
The foregoing describes an exception handling method of an RPA in an embodiment of the present application, and the following describes an RPA execution end in an embodiment of the present application, referring to fig. 3, and one embodiment of the RPA execution end in an embodiment of the present application includes:
an execution unit 301, configured to execute a business process;
a judging unit 302, configured to judge whether a business process abnormality occurs during the execution of the business process;
the screenshot unit 303 is configured to, when an anomaly occurs in the service flow, screenshot a scene of the anomaly flow;
the sending unit 304 is configured to send the screenshot of the abnormal flow to an RPA monitoring end, so that the RPA monitoring end performs an abnormal judgment on the screenshot of the abnormal flow;
a receiving unit 305, configured to receive an execution instruction for an abnormal scene returned by the RPA monitoring end;
and the processing unit 306 is configured to process the abnormal business process according to the execution instruction for the abnormal scene.
Preferably, the judging unit 302 is specifically configured to:
during the execution of the business process, matching the obtained process screenshot with a rule base of the abnormal scene;
if the matching is successful, determining that the business process is abnormal.
Preferably, the execution instruction for the abnormal scene includes a processing instruction or an abort instruction of a known problem;
the processing unit 306 is specifically configured to:
and processing the abnormal business flow according to the processing instruction or the stopping instruction of the known problem.
Preferably, the one or more RPA execution ends are deployed at a client or a server, and the RPA execution ends further include:
a recording unit 307 for recording the work log information of the abnormal business process.
The RPA executing terminal in the embodiment of the present application may send, when an abnormal service flow occurs, a scene screenshot of the abnormal flow to the RPA monitoring terminal through the sending unit 304, so that the RPA monitoring terminal sends an execution instruction for the abnormal scene to the RPA monitoring terminal, and the processing unit 306 processes the abnormal service flow according to the execution instruction for the abnormal scene, thereby improving the efficiency of solving the abnormal flow.
Next, description will be made on the RPA monitoring end in the embodiment of the present application, referring to fig. 4, and one embodiment of the RPA monitoring end in the embodiment of the present application includes:
a receiving unit 401, configured to receive a screenshot of an abnormal flow sent by one or more RPA execution ends;
the matching unit 402 is configured to match the screenshot of the abnormal flow with a preset abnormal problem library, so as to obtain an execution instruction for the abnormal scene;
a sending unit 403, configured to send an execution instruction for an abnormal scenario to the one or more RPA execution ends.
Preferably, the RPA monitoring end is deployed at a server side, and the execution instruction for the abnormal scene includes a processing instruction or a suspension instruction of a known problem;
the transmitting unit 403 is specifically configured to:
and sending a processing instruction or an abort instruction of the known problem to one or more RPA execution ends.
In the embodiment of the application, the RPA monitoring end is configured for one or more RPA execution ends, so that when an abnormal flow occurs in the RPA execution end, the RPA monitoring end can send the execution instruction aiming at the abnormal scene to the RPA execution end, thereby improving the solution efficiency of the abnormal flow in the RPA execution end.
The embodiment of the application further provides an exception handling system of the robot flow automation program RPA, please refer to fig. 5, specifically including one or more RPA execution ends provided in the embodiment of fig. 3 and an RPA monitoring end provided in fig. 4, wherein the roles of the RPA execution end and the RPA monitoring end are as described in fig. 3 and fig. 4, and are not repeated herein.
The embodiment of the application further provides a computer program product, on which a computer program is stored, the computer program is used for implementing the exception handling method of the robot flow automation program RPA as shown in fig. 1 or fig. 2 when being executed by computer equipment.
The RPA execution end and the RPA monitoring end in the embodiment of the present invention are described above from the point of view of modularized functional entities, and the computer device in the embodiment of the present invention is described below from the point of view of hardware processing:
the computer device is used for realizing the function of the side of the RPA execution end, and one embodiment of the computer device in the embodiment of the invention comprises the following components:
a processor and a memory;
the memory is used for storing a computer program, and the processor is used for executing the computer program stored in the memory, and the following steps can be realized:
executing a business process;
judging whether the business process is abnormal or not during the execution of the business process;
if yes, screenshot is carried out on the scene of the abnormal flow;
sending the scene screenshot of the abnormal flow to an RPA monitoring end, so that the RPA monitoring end carries out abnormal judgment on the scene screenshot of the abnormal flow;
receiving an execution instruction which is returned by the RPA monitoring end and is aimed at an abnormal scene;
and processing the abnormal business flow according to the execution instruction aiming at the abnormal scene.
In some embodiments of the invention, the processor may be further configured to implement the steps of:
during the execution of the business process, matching the obtained process screenshot with a rule base of the abnormal scene;
if the matching is successful, determining that the business process is abnormal.
In some embodiments of the present invention, the execution instruction for the exception scenario includes a processing instruction or an abort instruction of a known problem, and the processor may be further configured to implement the following steps:
and processing the abnormal business flow according to the processing instruction or the stopping instruction of the known problem.
In some embodiments of the present invention, the one or more RPA execution ends are deployed at a client or a server, and the processor may be further configured to implement the following steps:
and recording the work log information of the abnormal business process.
The computer device is further configured to implement a function of an RPA monitoring end side, and in an embodiment of the present invention, another embodiment of the computer device includes:
receiving a scene screenshot of an abnormal flow sent by one or more RPA execution ends;
matching the scene screenshot of the abnormal flow with a preset abnormal problem library to obtain an execution instruction aiming at the abnormal scene;
and sending an execution instruction aiming at the abnormal scene to the one or more RPA execution ends.
In some embodiments of the present invention, the RPA monitoring end is disposed on the server side, the execution instruction for the abnormal scenario includes a processing instruction or an abort instruction of a known problem, and the processor may be further configured to implement the following steps:
and sending a processing instruction or an abort instruction of the known problem to one or more RPA execution ends.
It can be understood that, whether on the side of the RPA executing end or the side of the RPA monitoring end, the processor in the above-described computer device may also implement the functions of each unit in the above-described corresponding embodiments of each device when executing the computer program, which is not described herein. The computer program may be divided into one or more modules/units, which are stored in the memory and executed by the processor to accomplish the present invention, for example. The one or more modules/units may be a series of computer program instruction segments capable of performing a specific function for describing the execution of the computer program in the RPA executing/RPA monitoring side. For example, the computer program may be divided into units in the above-mentioned RPA execution end, and each unit may implement a specific function as described in the above-mentioned corresponding RPA execution end.
The computer device can be a desktop computer, a notebook computer, a palm computer, a cloud server and other computing equipment. The computer device may include, but is not limited to, a processor, a memory. It will be appreciated by those skilled in the art that the processor, memory, etc. are merely examples of computer apparatus and are not limiting of computer apparatus, and may include more or fewer components, or may combine certain components, or different components, e.g., the computer apparatus may also include input and output devices, network access devices, buses, etc.
The processor may be a central processing unit (CentralProcessingUnit, CPU), but may also be other general purpose processors, digital signal processors (DigitalSignalProcessor, DSP), application specific integrated circuits (ApplicationSpecificIntegratedCircuit, ASIC), off-the-shelf programmable gate arrays (Field-ProgrammableGateArray, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like that is a control center of the computer device, connecting various parts of the overall computer device using various interfaces and lines.
The memory may be used to store the computer program and/or modules, and the processor may implement various functions of the computer device by running or executing the computer program and/or modules stored in the memory, and invoking data stored in the memory. The memory may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to the use of the terminal, etc. In addition, the memory may include high-speed random access memory, and may also include non-volatile memory, such as a hard disk, memory, plug-in hard disk, smart memory card (SmartMediaCard, SMC), secure Digital (SD) card, flash card (FlashCard), at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
The present invention also provides a computer readable storage medium for implementing the function of the RPA execution side, on which a computer program is stored, which when executed by a processor, can be used to perform the following steps:
executing a business process;
judging whether the business process is abnormal or not during the execution of the business process;
if yes, screenshot is carried out on the scene of the abnormal flow;
sending the scene screenshot of the abnormal flow to an RPA monitoring end, so that the RPA monitoring end carries out abnormal judgment on the scene screenshot of the abnormal flow;
receiving an execution instruction which is returned by the RPA monitoring end and is aimed at an abnormal scene;
and processing the abnormal business flow according to the execution instruction aiming at the abnormal scene.
In some embodiments of the present invention, a computer program stored on a computer readable storage medium, when executed by a processor, may also be used to implement the steps of:
during the execution of the business process, matching the obtained process screenshot with a rule base of the abnormal scene;
if the matching is successful, determining that the business process is abnormal.
In some embodiments of the present invention, the execution instructions for the abnormal scene include processing instructions or suspension instructions for a known problem, and the computer program stored in the computer readable storage medium may be further used by the processor to implement the following steps when the computer program is executed by the processor:
and processing the abnormal business flow according to the processing instruction or the stopping instruction of the known problem.
In some embodiments of the present invention, the one or more RPA execution ends are deployed on a client or a server, and when the computer program stored in the computer readable storage medium is executed by the processor, the processor may be further configured to implement the following steps:
and recording the work log information of the abnormal business process.
The present invention also provides another computer readable storage medium for implementing the function of the RPA monitoring end side, on which a computer program is stored, which when executed by a processor, can be used to execute the following steps:
receiving a scene screenshot of an abnormal flow sent by one or more RPA execution ends;
matching the scene screenshot of the abnormal flow with a preset abnormal problem library to obtain an execution instruction aiming at the abnormal scene;
and sending an execution instruction aiming at the abnormal scene to the one or more RPA execution ends.
In some embodiments of the present invention, the RPA monitoring end is disposed on the server side, the execution instruction for the abnormal scenario includes a processing instruction or an abort instruction of a known problem, and when the computer program stored in the computer readable storage medium is executed by the processor, the processor may be further configured to implement the following steps:
and sending a processing instruction or an abort instruction of the known problem to one or more RPA execution ends.
It will be appreciated that the integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a corresponding one of the computer readable storage media. Based on such understanding, the present invention may implement all or part of the above-described respective embodiment methods, or may be implemented by a computer program for instructing relevant hardware, where the computer program may be stored in a computer readable storage medium, and the computer program may implement the steps of each of the above-described method embodiments when being executed by a processor. Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer memory, a Read-only memory (ROM), a random access memory (RAM, random AccessMemory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the computer readable medium contains content that can be appropriately scaled according to the requirements of jurisdictions in which such content is subject to legislation and patent practice, such as in certain jurisdictions in which such content is subject to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims (10)
1. An exception handling method for an RPA of a Robot Program Automation (RPA), the method being applied to one or more RPA execution ends, the method comprising:
executing a business process;
judging whether the business process is abnormal or not during the execution of the business process;
if yes, screenshot is carried out on the scene of the abnormal flow;
sending the scene screenshot of the abnormal flow to an RPA monitoring end, so that the RPA monitoring end carries out abnormal judgment on the scene screenshot of the abnormal flow;
receiving an execution instruction which is returned by the RPA monitoring end and is aimed at an abnormal scene;
and processing the abnormal business flow according to the execution instruction aiming at the abnormal scene.
2. The method of claim 1, wherein the one or more RPA execution terminals pre-store rule bases of abnormal scenes, and wherein the determining whether the abnormal business process occurs during the execution of the business process comprises:
during the execution of the business process, matching the obtained process screenshot with a rule base of the abnormal scene;
if the matching is successful, determining that the business process is abnormal.
3. The method of claim 1, wherein the execution instructions for the exception scenario comprise processing instructions or abort instructions for known problems;
the processing the abnormal business process according to the execution instruction aiming at the abnormal scene comprises the following steps:
and processing the abnormal business flow according to the processing instruction or the stopping instruction of the known problem.
4. A method according to any one of claims 1 to 3, wherein the one or more RPA execution ends are deployed at a client or server end, the method further comprising:
and recording the work log information of the abnormal business process.
5. An exception handling method of an automatic program RPA of a robot flow, which is characterized by being applied to an RPA monitoring end, the method comprising:
receiving a scene screenshot of an abnormal flow sent by one or more RPA execution ends;
matching the scene screenshot of the abnormal flow with a preset abnormal problem library to obtain an execution instruction aiming at the abnormal scene;
and sending the execution instruction aiming at the abnormal scene to the one or more RPA execution ends.
6. The method of claim 5, wherein the RPA monitor is deployed on a server side, and the execution instruction for the abnormal scenario includes a processing instruction or an abort instruction of a known problem;
matching the scene screenshot of the abnormal flow with a preset abnormal problem library to obtain an execution instruction aiming at an abnormal scene, and sending the execution instruction aiming at the abnormal scene to the one or more RPA execution ends, wherein the method comprises the following steps:
matching the scene screenshot of the abnormal flow with a preset abnormal problem library to obtain a processing instruction or a suspension instruction of the known problem;
and sending a processing instruction or an abort instruction of the known problem to the one or more RPA execution ends.
7. An RPA execution terminal, comprising:
the execution unit is used for executing the business process;
the judging unit is used for judging whether the business process is abnormal or not during the execution of the business process;
the screenshot unit is used for screenshot of a scene of the abnormal flow if the scene is the abnormal flow;
the sending unit is used for sending the scene screenshot of the abnormal flow to the RPA monitoring end so that the RPA monitoring end can perform abnormal judgment on the scene screenshot of the abnormal flow;
the receiving unit is used for receiving an execution instruction which is returned by the RPA monitoring end and is aimed at an abnormal scene;
and the processing unit is used for processing the abnormal business flow according to the execution instruction aiming at the abnormal scene.
8. An RPA monitoring terminal, comprising:
the receiving unit is used for receiving the scene screenshot of the abnormal flow sent by one or more RPA execution ends;
the matching unit is used for matching the scene screenshot of the abnormal flow with a preset abnormal problem library to obtain an execution instruction aiming at the abnormal scene;
and the sending unit is used for sending the execution instruction aiming at the abnormal scene to the one or more RPA execution ends.
9. A computer device comprising a processor, characterized in that the processor, when executing a computer program stored on a memory, is adapted to perform the abnormality processing method of the robot flow automation program RPA according to any one of claims 1 to 4 or the abnormality processing method of the robot flow automation program RPA according to claim 5 or 6.
10. A computer-readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, is for executing the abnormality processing method of the robot flow automation program RPA according to any one of claims 1 to 4 or the abnormality processing method of the robot flow automation program RPA according to claim 5 or 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310361722.9A CN116541195A (en) | 2023-03-29 | 2023-03-29 | Abnormality processing method and related device for robot flow automation program RPA |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310361722.9A CN116541195A (en) | 2023-03-29 | 2023-03-29 | Abnormality processing method and related device for robot flow automation program RPA |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116541195A true CN116541195A (en) | 2023-08-04 |
Family
ID=87453208
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310361722.9A Pending CN116541195A (en) | 2023-03-29 | 2023-03-29 | Abnormality processing method and related device for robot flow automation program RPA |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116541195A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117333127A (en) * | 2023-10-09 | 2024-01-02 | 广州嘉磊元新信息科技有限公司 | Service automatic processing method based on RPA |
-
2023
- 2023-03-29 CN CN202310361722.9A patent/CN116541195A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117333127A (en) * | 2023-10-09 | 2024-01-02 | 广州嘉磊元新信息科技有限公司 | Service automatic processing method based on RPA |
| CN117333127B (en) * | 2023-10-09 | 2024-04-05 | 广州嘉磊元新信息科技有限公司 | Service automatic processing method based on RPA |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108600029B (en) | Configuration file updating method and device, terminal equipment and storage medium | |
| CN110225078B (en) | Application service updating method, system and terminal equipment | |
| CN109814531B (en) | Automatic diagnosis method and system based on cloud platform and related equipment | |
| CN104991821A (en) | Monitor task batch processing method and apparatus | |
| CN116541195A (en) | Abnormality processing method and related device for robot flow automation program RPA | |
| CN109240802B (en) | Request processing method and device | |
| CN111221727A (en) | Test method, test device, electronic equipment and computer readable medium | |
| CN108667872B (en) | Archiving method and device for scheduling server | |
| CN113904450B (en) | Misoperation prevention method, device and equipment of power grid dispatching system | |
| CN117215953A (en) | Verification method and device for equipment configuration information, storage medium and electronic equipment | |
| CN115130911A (en) | Method and device for processing delivery tasks failed to execute by robot | |
| CN108255549B (en) | Server program visual control method and device | |
| CN115741708A (en) | Method and device for determining manipulator state and storage medium | |
| CN112650615B (en) | Fault emergency management method, device, electronic equipment and system | |
| CN111290873B (en) | Fault processing method and device | |
| CN114386894A (en) | Logistics abnormity processing method and system, storage medium and electronic equipment | |
| CN113420713A (en) | Abnormity monitoring method and device, electronic equipment and computer readable medium | |
| CN114253628A (en) | Automatic deployment device and automatic deployment method for middleware | |
| CN114418142A (en) | Equipment inspection method and device | |
| CN113138935A (en) | Program testing method and device, electronic equipment and storage medium | |
| CN114425787A (en) | Control method and device for robot automatic test, server and storage medium | |
| CN113656210A (en) | Processing method and device for error reporting information, server and readable storage medium | |
| CN113806312A (en) | File processing method and device, electronic equipment and storage medium | |
| CN112328481A (en) | Automatic testing method, device and equipment for multi-task scene and storage medium | |
| CN110716747A (en) | Program operation efficiency optimization method based on function parameter statistics and terminal equipment |
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 |