CN112099972A

CN112099972A - Office file processing method, device, equipment and storage medium based on RPA robot

Info

Publication number: CN112099972A
Application number: CN202010937285.7A
Authority: CN
Inventors: 刘继超; 邹芳
Original assignee: Ping An Life Insurance Company of China Ltd
Current assignee: Ping An Life Insurance Company of China Ltd
Priority date: 2020-09-08
Filing date: 2020-09-08
Publication date: 2020-12-18
Anticipated expiration: 2040-09-08
Also published as: CN112099972B

Abstract

The embodiment of the application belongs to the field of research and development management, and relates to an office file processing method based on an RPA robot, which comprises the steps of receiving a remote calling request transmitted by an agent interface; decapsulating the remote call request to obtain a processing method name and a first RPA dictionary object, wherein the first RPA dictionary object comprises an RPA request parameter; inquiring a calling method corresponding to the processing method name to obtain an inquiry result; if the query result is that the calling method is not registered, returning a processing result of abnormal method registration to the proxy interface to indicate the proxy interface to send the processing result to the RPA robot; and if the query result is that the calling method is registered, calling the calling method to process the office file according to the request parameter to obtain a processing result, and indicating the proxy interface to send the processing result to the RPA robot. The office template file is also stored in a blockchain. The method solves the technical problem that the return value cannot be obtained in the prior art.

Description

Office file processing method, device, equipment and storage medium based on RPA robot

Technical Field

The application relates to the field of research and development management, in particular to an office file processing method and device based on an RPA robot, computer equipment and a storage medium.

Background

Office automation processing is performed through an RPA robot, generally, office application programs are subjected to automated data processing through an external calling interface opened by the office application programs according to a VBA object-oriented programming model. However, this method has the following technical problems:

because the service flow of the RPA is processed serially from top to bottom, the next task needs to wait for the completion result of the previous task to judge whether to execute or not, but the existing RPA robot has incomplete office automation support, cannot acquire a return value and a call result for office file processing, cannot process the office file in the next step, and thus causes errors in office file processing.

Disclosure of Invention

Based on this, in order to solve the above technical problems, the present application provides an office file processing method, an office file processing device, a computer device, and a storage medium based on an RPA robot, so as to solve the technical problem in the prior art that an error occurs in processing an office file due to the fact that a return value and a call result for processing the office file cannot be acquired.

An office file processing method based on an RPA robot, the method comprising:

receiving a remote calling request transmitted by an agent interface;

decapsulating the remote call request to obtain a processing method name and a first RPA dictionary object, wherein the first RPA dictionary object comprises an RPA request parameter;

inquiring a calling method corresponding to the processing method name to obtain an inquiry result;

if the query result is that the calling method is not registered, returning a processing result of abnormal method registration to the proxy interface to indicate the proxy interface to send the processing result to the RPA robot;

and if the query result is that the calling method is registered, calling the calling method to process the office file according to the RPA request parameter to obtain a processing result, and indicating the proxy interface to send the processing result to the RPA robot.

An RPA robot-based office document processing apparatus, the apparatus comprising:

the receiving module is used for receiving the remote calling request transmitted by the proxy interface;

a decapsulation module, configured to decapsulate the remote call request to obtain a processing method name and a first RPA dictionary object, where the first RPA dictionary object includes an RPA request parameter;

the query module is used for querying the calling method corresponding to the processing method name to obtain a query result;

the first processing module is used for returning a processing result of abnormal method registration to the proxy interface if the query result indicates that the calling method is not registered, so as to indicate the proxy interface to send the processing result to the RPA robot;

and the second processing module is used for calling the calling method to process office files according to the RPA request parameters to obtain a processing result and indicating the proxy interface to send the processing result to the RPA robot if the query result indicates that the calling method is registered.

A computer device comprising a memory and a processor, and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the above-described RPA robot-based office file processing method when executing the computer program.

A computer-readable storage medium storing a computer program which, when executed by a processor, implements the steps of the above-described RPA robot-based office document processing method.

According to the office file processing method, the office file processing device, the computer equipment and the storage medium based on the RPA robot, the proxy interface is used for creating a file processing background process, the file processing background process is sent to the stub interface registered with the calling method to perform corresponding processing on an office file, then the stub interface is used for timely obtaining the processing result including method registration, method calling and method execution, and the processing result is returned to the RPA robot through the proxy interface.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.

FIG. 1 is a schematic diagram of an application environment of an office document processing method based on an RPA robot;

fig. 2 is a schematic flow chart of an office document processing method based on an RPA robot in embodiment 1;

fig. 3 is a schematic flowchart of an office document processing method based on an RPA robot in embodiment 2;

FIG. 4 is a schematic view of an office document processing apparatus based on an RPA robot according to example 3;

FIG. 5 is a diagram of a computer device in one embodiment.

Detailed Description

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "including" and "having," and any variations thereof, in the description and claims of this application and the description of the above figures are intended to cover non-exclusive inclusions. The terms "first," "second," and the like in the description and claims of this application or in the above-described drawings are used for distinguishing between different objects and not for describing a particular order.

Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is further described in 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. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The office file processing method based on the RPA robot provided by the embodiment of the invention can be applied to the application environment shown in FIG. 1. The application environment may include a terminal 102, a network for providing a communication link medium between the terminal 102 and the server 104, and a server 104, wherein the network may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

A user may use the terminal 102 to interact with the server 104 over a network to receive or send messages, etc. The terminal 102 may have installed thereon various communication client applications, such as a web browser application, a shopping application, a search application, an instant messaging tool, a mailbox client, social platform software, and the like.

The terminal 102 may be various electronic devices having a display screen and supporting web browsing, including but not limited to a smart phone, a tablet computer, an e-book reader, an MP3 player (Moving Picture Experts Group Audio Layer III, mpeg compression standard Audio Layer 3), an MP4 player (Moving Picture Experts Group Audio Layer IV, mpeg compression standard Audio Layer 4), a laptop portable computer, a desktop computer, and the like.

The server 104 may be a server that provides various services, such as a background server that provides support for pages displayed on the terminal 102.

It should be noted that, the method for processing office documents based on the RPA robot provided in the embodiment of the present application is generally executed by a server/terminal, and accordingly, the apparatus for processing office documents based on the RPA robot is generally disposed in the server/terminal.

The application is operational with numerous general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet-type devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like. The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

It should be understood that the number of terminals, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Wherein, the terminal 102 communicates with the server 104 through the network. The agent interface on the server 104 initiates a local call request, then creates a file processing background process to open a local office file, and then initiates a remote call request to the file processing background process, and the stub interface receives the remote call request and then correspondingly processes the office template file, and returns the processing result to the terminal 102 through the server 104. The terminal 102 and the server 104 are connected through a network, the network may be a wired network or a wireless network, the terminal 102 may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the server 104 may be implemented by an independent server or a server cluster formed by a plurality of servers.

In embodiment 1, as shown in fig. 2, an office document processing method based on an RPA robot is provided, which is described by taking the method applied to the server in fig. 1 as an example, and includes the following steps:

step 202, when detecting that the proxy interface receives the local call request sent by the receiving PRA robot, the local call request is packaged through the proxy interface.

The RPA robot, namely the RPA program application, can generate a calling request according to the requirement of the terminal; in this embodiment, a server is used as a stub interface for explanation, where the server may be the stub interface and also a basic component on an RPA robot, but other interfaces need to initiate a request to the stub interface in a remote invocation manner. The proxy interface is a basic component in the RPA robot, can receive a call request sent by the RPA robot, and is generally used for processing Excel data filtering, conversion and the like. The local call request received by the proxy interface includes a processing method name, namely an office method name and an office template file path. After receiving the local call request, the proxy interface repackages the local call request to unify the data format of the local call request, thereby facilitating the acquisition of parameters of other interfaces. The Office method name is the name of the Office calling method which needs to be registered or called in the local calling request, and the Office template file path is the Office file to be processed, such as the local storage path of the Office template file. The dictionary object is a dynamic data structure object adopting key value pairs, supports common data types such as objects, arrays, character strings and numbers, and supports multi-level nesting. The parameter of the first dictionary object in this embodiment is a parameter in the dictionary object, and may be, for example, a last name parameter required for desensitization processing of a name in an Excel file.

When the fact that the agent interface receives the local calling request is detected, the conference service end can indicate the agent interface to package the local calling request again, so that the data format of the local calling request is unified, and parameter acquisition of other interfaces is facilitated.

And step 204, instructing the agent interface to create a file processing background process and opening the office file.

The Office file is an Office template file stored in a local or server database, such as an Excel file, a Word file and the like, and is a data template with a VBA script, the server calls a file process creation interface to create a file processing background process after receiving a local call request through an indication agent interface, such as an Excel form background process, a Word background process and the like in the Office background process, and indicates the agent interface to open a specified Office template file according to an Office template file path in the local call request. Wherein the file process creation interface is a third party interface that can be invoked to process a corresponding event.

And step 206, after detecting that the office file is successfully opened, indicating the proxy interface to generate a remote calling request according to the local calling request and sending the remote calling request.

The service end calls the office programming interface to initiate a remote calling request to the office background process through the office automation macro on the office template file by indicating the proxy interface, and indicates that the office background process office template file is successfully created, so that the service end can correspondingly process the office template file according to the processing method name in the remote calling request and the first RPA dictionary object according to the remote calling request sent by the proxy interface.

For example, in this embodiment, after receiving the remote invocation request, the stub interface decapsulates the remote invocation request, so as to obtain the office method name and the first RPA dictionary object. For example, the office method name may be a desensitization function, then the registration condition of the desensitization function is acquired from the stub interface, the office method is called according to the registration condition, and finally desensitization processing is performed on the office template file, such as a name of a person in an Excel document, according to the called desensitization function. And particularly, fields needing desensitization need to be obtained from a first RPA dictionary object in the remote calling request, and then the stub interface sends the processing result of the Excel document to the RPA robot through the proxy interface.

The proxy interface can finally obtain processing results of method registration, method calling and method execution, no matter what the processing result of the office template file is, the stub interface generates a corresponding processing result, the processing result is fed back to the proxy interface, and then the proxy interface returns to the RPA robot. Before processing the office template file, the remote calling interface needs to be unpacked to obtain the office method name and the first RPA dictionary object. The local call request is different from the remote call request in that the initiator is different and information included therein is different, and the local call request includes an office template file path for specifying an office template file in addition to an office method name and the first RPA dictionary object. Secondly, high-level abstraction is carried out on a development calling interface by adopting remote calling, so that technical details do not need to be concerned in the development process, and only business logic codes need to be compiled; finally, compared with the operation through an interface, the new scheme has better compatibility, because the operation interfaces of different Office versions are continuously changed, the RPA automatic flow has no universality under different system environments, but because the Office open programming interface ensures backward compatibility, the compatibility is better after the new scheme is adopted.

In the office file processing method based on the RPA robot, various processing results of the office template file are returned to the proxy interface in time and then returned to the RPA robot through the proxy interface, so that the technical problems that in the prior art, a processing return value of the office template file cannot be obtained, and the office template file cannot be accurately processed in the next step are solved, so that when the RPA robot carries out large-scale data processing, the processing results can be obtained more quickly through a new scheme, and the processing efficiency of the office template file is improved.

In embodiment 2, there is provided an office file processing method based on an RPA robot, as shown in fig. 3, including:

step 302, receiving a remote invocation request transmitted by a proxy interface.

The proxy interface sends a remote call request to the office background process, but because the proxy interface and the stub interface are in a one-to-one relationship and the stub interface and the office process creation interface are in a one-to-many relationship, the stub interface can directly take the remote call request sent by the proxy interface and autonomously find out which call method to call, namely the office call method.

Step 304, decapsulating the remote invocation request to obtain a processing method name and a first RPA dictionary object, wherein the first RPA dictionary object comprises RPA request parameters.

Because the proxy interface encapsulates the office method name and the first RPA dictionary object parameter, in order to enable the storage interface to normally acquire the above information, the encapsulated information needs to be decapsulated to obtain a data format that can be recognized by the stub interface, and finally the office method name and the RPA request parameter in the first RPA dictionary object are read.

The office method name may be desensitization, such as: the RPA robot needs to desensitize the name in the EXCEL file (Zhang three- > Zhang X), and a name desensitization method is realized in the EXCEL file, so that the RPA robot application can initiate a remote call request through a proxy interface, and a server side can call a corresponding desensitization function to desensitize the EXCEL file, wherein the RPA request parameter can be a character which needs to be desensitized.

And step 306, inquiring the calling method corresponding to the processing method name to obtain an inquiry result.

The stub interface is registered with a plurality of calling methods, which are stored on the stub interface from the creation of the file processing background process, so as to provide external service, such as desensitization processing, formatting processing, batch processing and the like, the input parameter is a VBA dictionary object, and the return value is not limited. A VBA dictionary object may be simply understood as a special two-dimensional array. The first column of the VBA dictionary object is Key (Key), the column has uniqueness and non-repeatability, and the Key is one of the most important characteristics of the dictionary object; the second column is Item (entry) that can hold various types of variables.

And 308, if the query result is that the calling method is not registered, returning a processing result of abnormal method registration to the proxy interface to indicate the proxy interface to send the processing result to the RPA robot.

If the office calling method corresponding to the office method name is not registered, the method registers an abnormal processing result to the proxy interface to indicate the proxy interface to throw the RPA abnormity to the RPA program application, namely, the information that the query result is calling failure is returned to the proxy interface, then returned to the RPA robot, and calling is finished.

And 310, if the query result is that the calling method is registered, calling the calling method to process the office file according to the RPA request parameter to obtain a processing result, and indicating the proxy interface to send the processing result to the RPA robot.

The dispatch request is a processing request sent to the calling method of the stub interface through the proxy interface after the RPA application program knows the name of the calling method is registered, that is, if the office calling method is registered, the RPA application dispatches the processing request to the office calling method for execution.

For example, desensitization of names in Excel files:

zhangsan- > Zhang

The parameters required in the desensitization process are then obtained from the first RPA dictionary object parameters. The RPA request parameter in the first RPA dictionary object may be a character which needs desensitization processing, for example, desensitization processing needs to be performed on the first character or the first and second characters after the last name.

And if the execution is successful, serializing and packaging the processing result, wherein the processing result not only comprises the information that the execution of the method is successful, but also comprises RPA dictionary object response data. Wherein, the response data comprises the result after desensitization treatment.

And after packaging, returning the packaged data to the proxy interface to instruct the proxy interface to decapsulate the packaged data to obtain a second RPA dictionary object, and returning the second RPA dictionary object to the RPA program application, wherein the second RPA dictionary object comprises the processed response data.

Optionally, if the processing result is that the method fails to be executed, sending execution failure information to the proxy interface to instruct the proxy interface to send an execution failure prompt to the RPA robot.

Optionally, if the processing result is that the method is abnormally called, obtaining an abnormal type of the method call abnormality according to the processing result, and sending the processing result to the proxy interface to instruct the proxy interface to return the abnormal type to the RPA robot. Specifically, the stub interface automatically captures the exception occurring in desensitization processing, such as program crash, code error, exception caught by an engine, and the like, and combines the exception into the execution result to return the exception information to the proxy interface, and the proxy interface sends the exception information to the RPA program application after acquiring the returned exception information, and ends processing.

Further, the remote invocation request may also include a timer parameter.

For example, a timer is set in the background processing process, the timer parameter may be set to 10 minutes, when the processing of the office template file at the stub interface exceeds 10 minutes, and the server has not finished processing the office template file, the timer may generate a processing result of execution failure, and the stub interface throws out the exception to the proxy interface to instruct the proxy interface to send the exception information to the RPA program application, and finish the processing of the office template file by the stub interface. So as to be convenient for the next round of calling request or restart the processing after the developer repairs the abnormity. If the treatment is finished within 10 minutes, the timer is directly closed. In the embodiment, the program is prevented from being trapped in a dead loop in a timer mode, the data processing amount of the server is reduced, and the output processing efficiency is improved.

In this embodiment, an expansion interface for Office remote invocation is newly added through an external component expansion mechanism of the RPA robot: the new interface supports timely returning of an RPA dictionary object, the proxy interface creates an office background process, then sends a remote calling request to the stub interface registered with an office calling method, then the stub interface performs corresponding processing on the office template file and returns a corresponding processing result to the proxy interface, the processing result comprises processing results of method registration, method calling and method execution, and finally the processing result is returned to the RPA robot through the proxy interface.

It is emphasized that to further ensure the privacy and security of the office template file, the office template file may also be stored in a node of a block chain.

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

In embodiment 3, as shown in fig. 4, there is provided an office document processing apparatus based on an RPA robot, which corresponds one-to-one to the office document processing method based on the RPA robot in embodiment 1 described above. The office file processing device based on the RPA robot comprises:

a receiving module 402, configured to receive a remote invocation request transmitted by an agent interface;

a decapsulation module 404, configured to decapsulate the remote call request to obtain a processing method name and a first RPA dictionary object, where the first RPA dictionary object includes an RPA request parameter;

the query module 406 is configured to query the calling method corresponding to the processing method name to obtain a query result;

the first processing module 408 is configured to, if the query result is that the calling method is not registered, return a processing result of abnormal method registration to the proxy interface to instruct the proxy interface to send the processing result to the RPA robot;

and a second processing module 410, configured to, if the query result is that the calling method is registered, call the calling method to process the office file according to the RPA request parameter, obtain a processing result, and instruct the proxy interface to send the processing result to the RPA robot.

Further, before the receiving module 402, the method further includes:

the detection module is used for packaging the local calling request through the proxy interface when detecting that the proxy interface receives the local calling request sent by the RPA robot; and are

The creating module is used for indicating the agent interface to create a file processing background process and open the office file;

and the generation module is used for indicating the agent interface to generate a remote calling request according to the local calling request and sending the remote calling request after detecting that the office file is successfully opened.

Further, a creation module comprising:

the creating submodule is used for calling a file process creating interface through the proxy interface to create a file processing background process;

and the opening submodule is used for indicating the file processing background process to open the office file in the local database according to the template file path.

Further, a second processing module comprising:

the monitoring submodule is used for monitoring the processing time of the office file through a timer;

the first processing submodule is used for indicating the timer to generate a processing result if the processing time length exceeds the parameter of the timer;

and the second processing submodule is used for closing the timer and generating a processing result if the processing time length is less than the parameter of the timer.

Further, the second processing module further includes:

the first sending submodule is used for serializing the packaging processing result if the processing result is successful, returning the packaged processing result to the proxy interface, instructing the proxy interface to acquire a second RPA dictionary object from the packaged processing result, and returning RAP response data in the second RPA dictionary object to the RPA robot;

the second sending submodule is used for sending execution failure information to the proxy interface if the processing result is that the method fails to execute, so as to indicate the proxy interface to send an execution failure prompt to the RPA robot;

and the third sending submodule is used for acquiring the abnormal type of the method call exception according to the processing result if the processing result is the method call exception, and sending the processing result to the proxy interface so as to indicate the proxy interface to return the abnormal type to the RPA robot.

The Office file processing device based on the RPA robot adds an expansion interface for Office remote call through an external component expansion mechanism of the RPA robot: the new interface supports returning of an RPA dictionary object, the dictionary object is a dynamic data structure object adopting key value pairs, common data types such as objects, arrays, character strings and numbers are supported, and multi-level nesting is supported. The stub interface creates an Office background process, then sends the Office background process to the stub interface registered with the Office calling method to correspondingly process the Office template file, then the stub interface responds to the remote calling request of the proxy interface, calls the corresponding Office method, obtains the response result and returns the response result to the proxy interface, and the response result comprises the method registration, the method calling and the processing result of the method execution and returns the processing result to the RPA robot through the proxy interface.

In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 5. The computer device includes a processor, a memory, a network interface, and a database 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, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing the office template file. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement the RPA robot-based office document processing method in the above embodiment. In this embodiment, an expansion interface for Office remote invocation is newly added through an external component expansion mechanism of the RPA robot: the new interface supports returning of an RPA dictionary object, the dictionary object is a dynamic data structure object adopting key value pairs, common data types such as objects, arrays, character strings and numbers are supported, and multi-level nesting is supported. The stub interface creates an Office background process, then sends the Office background process to the stub interface registered with the Office calling method to correspondingly process the Office template file, then the stub interface responds to a remote calling request of the proxy interface, calls a corresponding Office method, obtains a response result, and returns the response result to the proxy interface, wherein the response result comprises processing results of method registration, method calling and method execution, and is returned to the RPA robot through the proxy interface.

As will be understood by those skilled in the art, the computer device is a device capable of automatically performing numerical calculation and/or information processing according to a preset or stored instruction, and the hardware includes, but is not limited to, a microprocessor, an Application Specific Integrated Circuit (ASIC), a Programmable Gate Array (FPGA), a Digital Signal Processor (DSP), an embedded device, and the like.

In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, which when executed by a processor implements the steps of the RPA robot-based office file processing method in the above-described embodiments, such as the steps 202 to 210 shown in fig. 2, or the processor implements the functions of the modules/units of the RPA robot-based office file processing apparatus in the above-described embodiments, such as the functions of the modules 402 to 410 shown in fig. 4.

In this embodiment, an expansion interface for Office remote invocation is newly added through an external component expansion mechanism of the RPA robot: the new interface supports returning of an RPA dictionary object, the dictionary object is a dynamic data structure object adopting key value pairs, common data types such as objects, arrays, character strings and numbers are supported, and multi-level nesting is supported. The stub interface creates an Office background process, then sends the Office background process to the stub interface registered with the Office calling method to correspondingly process the Office template file, then the stub interface responds to the remote calling request of the proxy interface, calls the corresponding Office method, obtains the response result and returns the response result to the proxy interface, and the response result comprises the method registration, the method calling and the processing result of the method execution and returns the processing result to the RPA robot through the proxy interface.

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 may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

The block chain referred by the application is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions.

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 those skilled in the art, without departing from the spirit and scope of the present invention, several changes, modifications and equivalent substitutions of some technical features may be made, and these changes or substitutions do not make the essence of the same technical solution depart from the spirit and scope of the technical solution of the embodiments of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. An office file processing method based on an RPA robot is characterized by comprising the following steps:

receiving a remote calling request transmitted by an agent interface;

2. The method of claim 1, further comprising, prior to receiving the remote invocation request transmitted by the proxy interface:

when detecting that the proxy interface receives a local calling request sent by an RPA robot, packaging the local calling request through the proxy interface; and are

Instructing the agent interface to create a file processing background process and opening the office file;

and after detecting that the office file is successfully opened, indicating the proxy interface to generate the remote calling request according to the local calling request and sending the remote calling request.

3. The method of claim 2, wherein the local call request includes a template file path, and wherein instructing the agent interface to create a file processing background process and open the office file according to the template file path comprises:

calling a file process creation interface through the proxy interface to create the file processing background process;

and instructing the file processing background process to open the office file in a local database according to the template file path.

4. The method according to claim 1, wherein the remote invocation request further includes a timer parameter, and the invoking of the invocation method processes the office file according to the RPA request parameter to obtain a processing result, including:

monitoring the processing time of the office file through a timer;

if the processing duration exceeds the timer parameter, indicating the timer to generate the processing result;

and if the processing time length is less than the timer parameter, closing the timer and generating a processing result.

5. The method of claim 1, wherein said instructing the proxy interface to send the processing results to the RPA robot comprises:

if the processing result is successful, performing serialization encapsulation on the processing result, returning the encapsulated processing result to the proxy interface, instructing the proxy interface to acquire a second RPA dictionary object from the encapsulated processing result, and returning RAP response data in the second RPA dictionary object to the RPA robot;

if the processing result is that the method fails to be executed, sending execution failure information to the proxy interface to indicate the proxy interface to send an execution failure prompt to the RPA robot;

and if the processing result is abnormal method calling, acquiring the abnormal type of the abnormal method calling according to the processing result, and sending the processing result to the proxy interface to indicate the proxy interface to return the abnormal type to the RPA robot.

6. The method according to any one of claims 1 to 5, wherein the office files are deployed in a distributed manner on a blockchain.

7. An office document processing apparatus based on an RPA robot, comprising:

8. The apparatus of claim 7, wherein before the receiving module, further comprising:

and the generation module is used for indicating the agent interface to generate the remote calling request according to the local calling request and sending the remote calling request after detecting that the office file is successfully opened.

9. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the steps of the method of any one of claims 1 to 6 when executing the computer program.

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.