CN113110867A - RPA robot management method, device, server and storage medium - Google Patents
RPA robot management method, device, server and storage medium Download PDFInfo
- Publication number
- CN113110867A CN113110867A CN202110361442.9A CN202110361442A CN113110867A CN 113110867 A CN113110867 A CN 113110867A CN 202110361442 A CN202110361442 A CN 202110361442A CN 113110867 A CN113110867 A CN 113110867A
- Authority
- CN
- China
- Prior art keywords
- robot
- work task
- execution time
- task
- work
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Manipulator (AREA)
Abstract
The application discloses a management method, a device, a storage medium and a server of an RPA robot, wherein the method comprises the following steps: selecting at least one RPA robot from a robot library to form a work task package; configuring attribute information and execution time rules of a work task packet; wherein the attribute information includes: one or more of task name, task identification, task description information, creation user identification and creation time, and the execution time rule comprises: execution time and/or number of executions; running at least one RPA robot contained in the work task package based on the execution time rule; and recording the operation result information and the persistent operation result information of the work task package in the operation life cycle. According to the RPA robot monitoring system, the complexity of work can be reduced, extra work is not needed to be added to monitor the RPA robot, and the workload of a user is reduced to a certain extent, and the work efficiency is improved.
Description
Technical Field
The present application relates to the field of computers, and in particular, to a method, a system, a server, an apparatus, and a storage medium for managing an RPA robot.
Background
An RPA (robot Process Automation) robot is an application program for simulating a manual operation mode of a user on a computer, so as to realize Automation of manual operation and improve accuracy and speed of task execution. For example: the enterprise deploys the RPA robot to realize certificate bill verification, paper file entry, cross-system data migration, data extraction from e-mails and documents and the like. In an actual scene, the RPA robot may face different work tasks, and a user needs to start the RPA robot and monitor the operation process of the RPA robot at a certain time, so how to improve the execution efficiency of the work tasks is a problem to be solved urgently at present.
Disclosure of Invention
In order to solve the above technical problems, the present application provides a management method for an RPA robot, a related apparatus, and a storage medium, which solve the problem in the related art that efficiency of performing a work task by using an RPA robot is not high.
In a first aspect, the present application provides a method for managing an RPA robot, including:
selecting at least one RPA robot from a robot library to form a work task package;
configuring attribute information and execution time rules of the work task package; wherein the attribute information includes: one or more of task name, task identifier, task description information, creation user identifier and creation time, wherein the execution time rule comprises: execution time and/or number of executions;
running the at least one RPA robot contained in the work task package based on the execution time rule;
and recording the operation result information of the work task packet in the operation life cycle and persisting the operation result information.
In a second aspect, the present application provides a management apparatus for an RPA robot, comprising:
the selection unit is used for selecting at least one RPA robot from the robot library to form a work task package;
the configuration unit is used for configuring the attribute information and the execution time rule of the work task package; wherein the attribute information includes: one or more of task name, task identifier, task description information, creation user identifier and creation time, wherein the execution time rule comprises: execution time and/or number of executions;
the operation unit is used for operating the at least one RPA robot contained in the work task package based on the execution time rule;
and the recording unit is used for recording the operation result information of the work task packet in the operation life cycle and persisting the operation result information.
In still another aspect, the present application provides an apparatus that can implement the RPA robot management method according to the first or second aspect. For example, the apparatus may be a chip (such as a baseband chip, or a communication chip, etc.) or a server. The above-described method may be implemented by software, hardware, or by executing corresponding software by hardware.
In one possible implementation manner, the structure of the apparatus includes a processor, a memory; the processor is configured to support the apparatus to perform corresponding functions in the application testing method. The memory is used for coupling with the processor, which holds the necessary programs (instructions) and/or data for the device. Optionally, the apparatus may further include a communication interface for supporting communication between the apparatus and other network elements.
In another possible implementation manner, the apparatus may include unit modules for performing corresponding actions in the above-described method.
In yet another possible implementation, the wireless communication device includes a processor and a transceiver, the processor is coupled to the transceiver, and the processor is configured to execute a computer program or instructions to control the transceiver to receive and transmit information; the processor is further configured to implement the above-described method when the processor executes the computer program or instructions. The transceiver may be a transceiver, a transceiver circuit, or an input/output interface. When the device is a chip, the transceiver is a transceiver circuit or an input/output interface.
When the device is a chip, the sending unit may be an output unit, such as an output circuit or a communication interface; the receiving unit may be an input unit, such as an input circuit or a communication interface. When the device is a network device, the sending unit may be a transmitter or a transmitter; the receiving unit may be a receiver or a receiver.
Yet another aspect of the present application provides an apparatus, comprising: a memory and a processor; wherein the memory stores a set of program codes, and the processor is configured to call the program codes stored in the memory and execute the method of the aspects.
Yet another aspect of the present application provides a computer-readable storage medium having stored therein instructions, which when executed on a computer, cause the computer to perform the method of the above-described aspects.
Yet another aspect of the present application provides a computer program product containing instructions which, when run on a computer, cause the computer to perform the method of the above-described aspects.
According to the above embodiments, when a task needs to be executed, at least one RPA robot is selected from the robot library to form a work task package, the execution time rule and the attribute information of the work task package are configured, the RPA robot corresponding to the work task package is operated based on the configured execution time rule, and after the operation of the work task package is finished, the operation result information is recorded, so that the problems of complexity and low efficiency in the related art caused by manually executing the RPA robot are solved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a network structure diagram provided in an embodiment of the present application;
fig. 2 is a schematic flowchart of a management method of an RPA robot according to an embodiment of the present disclosure;
fig. 3 is another schematic flow chart of a management method of an RPA robot according to an embodiment of the present application;
FIG. 4 is another schematic structural diagram of an apparatus according to an embodiment of the present disclosure;
fig. 5 is another schematic structural diagram of an apparatus according to an embodiment of the present disclosure.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance. It will be apparent to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
Referring to fig. 1, a network architecture diagram provided for the prior art is that, when the network architecture includes a user equipment 10, a database 11 and a server 12, the server 12 may include one or more servers, and when the number of the servers 12 is multiple, the multiple servers are in a distributed deployment. The user device 10 and the server 12 have a communication interface for mutual communication, and the user device 10 and the server 12 can communicate in a wired manner or a wireless manner. It should be understood that the connection manner and number of the devices of the network architecture in fig. 1 are only for illustration and are not limiting to the present application.
The user device 10 mainly provides a graphical interface through which the user configures the server 12. For example: the user device 10 configures attribute information and execution time rules of the job task package. The server 12 is configured to run at least one RPA robot in the work task package based on the configured temporal rules. The database 11 is used for recording and persisting the operation result information of the work task package, and the database 11 may be a relational database or a non-relational database.
The server in the application can be a rack-mounted server, a blade server, a tower server or a cabinet server and other computing equipment, and the server can be an independent server or a server cluster formed by a plurality of servers.
The user equipment in the present application includes but is not limited to: personal computers, tablet computers, handheld devices, in-vehicle devices, wearable devices, computing devices or other processing devices connected to a wireless modem, and the like. The terminal devices in different networks may be called different names, for example: user equipment, access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent or user equipment, cellular telephone, cordless telephone, Personal Digital Assistant (PDA), terminal equipment in a 5G network or future evolution network, and the like.
In order to explain the technical solution described in the present application, the following description will be given by way of specific examples.
Referring to fig. 2, fig. 2 is a schematic flowchart of a management method of an RPA robot according to an embodiment of the present application, where the method includes:
s201, selecting at least one RPA robot from a robot library to form a work task package.
Wherein, the server is configured with a robot library in advance, and the robot library comprises a plurality of different RPA robots. And the server selects at least one RPA robot from the robot library according to the task requirement to form a work task package, wherein the work task package comprises one or more RPA robots.
S202, configuring attribute information and execution time rules of the work task package.
The server creates the work task package, and configures attribute information of the work task package, including: the task information includes a task name, a task identifier, task description information, a creation user identifier, and creation time, where the task name is a name of a work task package, the task identifier is a character string representing an identity of the work task package, and the task description information is information describing task content, for example: the task description information is 'extracting all attachments in PDF format from the e-mail'; the creating user identification is the identification of the user creating the work task package, and the creating time is the time of creating the work task package. The execution time rule represents a rule for how each RPA robot in at least one RPA robot included in the work task package executes, and includes an execution number and/or an execution time, the execution number represents the number of times each RPA robot executes, and the execution time represents an execution time point of each RPA robot.
And S203, running at least one RPA robot contained in the work task package based on the execution time rule.
Wherein the server executes at least one RPA robot based on the configured execution time rules, for example: the server may execute in a variety of time dimensions, such as times, dates, weeks, months, and so forth. At least one RAP robot contained in the work task package is a transaction, namely all RAP robots contained in the work task package are considered to be successfully executed after being successfully executed, and if one or more RAP robots are unsuccessfully executed, the work task package is failed to be executed.
And S204, recording the operation result information and the persistent operation result information of the work task package in the operation life cycle.
The operation life cycle is a time interval from the beginning to the end of the execution of the work task package, the operation result information comprises the operation state, the work log and the service data of each RPA robot, and then the server stores the operation result information into the database in a lasting mode so as to be convenient for follow-up inquiry.
By implementing the embodiment of the application, when a task needs to be executed, at least one RPA robot is selected from the robot library to form a work task package, the execution time rule and the attribute information of the work task package are configured, the RPA robot corresponding to the work task package is operated based on the configured execution time rule, and the operation result information is recorded after the operation of the work task package is finished, so that the problems of complexity and low efficiency in the execution caused by manually executing the RPA robot in the related technology are solved.
Referring to fig. 3, another schematic flow chart of a management method of an RPA robot according to an embodiment of the present application is provided, where the method includes:
and S301, inputting basic information of the RPA robot through a visual interface.
The server displays a visual interface, namely a user interface, on the user equipment, where the visual interface includes a plurality of controls, for example: buttons, an input box, a sliding bar and the like, wherein the user operates controls on the visual interface through the input device to configure basic information of the RPA robot, and the basic information comprises one or more of a robot name, a version number and a creation time. The robot name represents the name of the RPA robot, the version number represents the serial number of the version of the RPA robot, and the version number can be represented by using numbers; the creation time represents the time at which the RAP robot was created. Furthermore, the user can also configure the operation parameters of the RAP robot through a visual interface, wherein the operation parameters comprise the parameter name, the parameter value and other attributes.
And S302, after the input is finished, generating a robot library based on the input RPA robot.
And after the server finishes the input of the RPA robot, generating a robot library based on the input RPA robot. Further, the server can perform operations such as adding, deleting, modifying, querying, disabling and the like on the operation parameters of the RAP robot in the robot library according to requirements.
S303, grouping a plurality of robots contained in the robot library based on the application scene to obtain a plurality of robot scene groups.
When the number of RPA robots in the robot library is large, a user takes time to select the RPA robots, the RAP robots in the robot library are grouped according to the functions of the RAP robots to obtain a plurality of robot scene groups, and each robot scene group comprises one or more RPA robots. For example: the operational parameters of the RAP robot include application scenarios, such as: the application scene comprises the following steps: file verification, data screening, document entry and the like, and the server divides the RPA robots in the same scene into a group based on the application scene.
S304, selecting at least one RPA robot from the robot library to form a work task package.
The server selects at least one RPA robot from the robot library according to task requirements to form a work task package, wherein the work task package comprises one or more RPA robots.
S305, configuring attribute information and execution time rules of the work task package.
The server creates the work task package, and configures attribute information of the work task package, including: the task information includes a task name, a task identifier, task description information, a creation user identifier, and creation time, where the task name is a name of a work task package, the task identifier is a character string representing an identity of the work task package, and the task description information is information describing task content, for example: the task description information is 'extracting all attachments in PDF format from the e-mail'; the creating user identification is the identification of the user creating the work task package, and the creating time is the time of creating the work task package. The execution time rule represents a rule for how each RPA robot in at least one RPA robot included in the work task package executes, and includes an execution number and/or an execution time, the execution number represents the number of times each RPA robot executes, and the execution time represents an execution time point of each RPA robot.
Further, the execution time rule is one or more of time, day, week and month.
The execution rules of the work task package are planned according to the common time dimensions of time, day, week and month, so that a user can easily understand how to select and plan the work task of the user. The time point at which a desired task is to be performed can be selected like a calendar by a time representation. The time by day is the interval time of selecting triggering while selecting the time node by time, the time by week is the time node selected while selecting any one or more days from monday to sunday to trigger the work task package, the time by month is the time node selected from any one or more months from 1 month to 12 months and any one or more days from the month or any one or more days from the first week to the fifth week. The multi-time-dimension combination mode can well meet the requirements of users, and after the execution time rule is determined, one or more robots can be selected from the robot scene group to be combined into a work task package.
And S306, when the work task packet meets the trigger condition, moving the work task packet into a queue to be operated.
The triggering condition is a preset execution time rule, when the execution time rule is met, the work task packages which do not start to run are moved into a queue to be run, the queue to be run has a certain length, and a plurality of work task packages can be stored. For example: when the runtime point is reached, the work task package is moved into the queue to be run.
S307, when idle running resources exist, the work tasks are moved out of the queue to be run, the work task packages are moved into the running queue, and the work task packages are run based on the execution time rules.
Wherein the running resources are resources for running the RPA robot, and include hardware resources and software resources, such as: the running resource can be a virtual machine or a physical machine, and when the existence of idle running resources is monitored, the work task packets in the queue to be run are removed and then moved into the running queue, and a plurality of working task packets which are running are stored in the running queue.
And S308, when the work task package finishes running, removing the work task package from the running queue.
And when the work task package finishes running, removing the work task package in the running queue. Furthermore, the queue to be run and the queue in running can be distributed queues based on Redis, reading, enqueuing, executing and dequeuing of the work task package are packaged into an atomic operation based on the single thread operating characteristic of Redis, the problems that the work task package is repeatedly executed in a distributed environment and the work task package occupies resources can be solved, and the utilization rate of the resources is improved.
S309, monitoring the running state of the work task package, and displaying a running state mark associated with the running state.
Wherein, the running state includes: the server may display running state marks with different colors on the user equipment to indicate different running states, wherein the running state marks represent that the work task package is in execution and the work task package is finished after the work task package is stopped.
And S310, recording the operation result information and the persistent operation result information of the work task package in the operation life cycle.
The operation life cycle is a time interval from the beginning to the end of the execution of the work task package, the operation result information comprises the operation state, the work log and the service data of each RPA robot, and then the server stores the operation result information into the database in a lasting mode so as to be convenient for follow-up inquiry.
S311, receiving a query request of a user.
Wherein the query request carries the task name.
And S312, inquiring the running result information corresponding to the task identification.
And S313, returning the operation result information to the user.
The operation result information of the completed work task package is traced in a query mode, the overall execution state of the work task package can be known, and the generated operation result information comprises the operation state, the result data and the like of each RPA robot.
By implementing the embodiment of the application, when a task needs to be executed, at least one RPA robot is selected from the robot library to form a work task package, the execution time rule and the attribute information of the work task package are configured, the RPA robot corresponding to the work task package is operated based on the configured execution time rule, and the operation result information is recorded after the operation of the work task package is finished, so that the problems of complexity and low efficiency in the execution caused by manually executing the RPA robot in the related technology are solved.
Fig. 2 to 3 describe the management method of the RPA robot in detail. Correspondingly, the structure of a device in the embodiment of the application is schematically shown.
Referring to fig. 4, fig. 4 is a schematic structural diagram of an apparatus 4 according to an embodiment of the present disclosure, where the apparatus 4 may include: a selection unit 401, a configuration unit 402, an execution unit 403, and a recording unit 404.
The selection unit is used for selecting at least one RPA robot from the robot library to form a work task package;
the configuration unit is used for configuring the attribute information and the execution time rule of the work task package; wherein the attribute information includes: one or more of task name, task identifier, task description information, creation user identifier and creation time, wherein the execution time rule comprises: execution time and/or number of executions;
the operation unit is used for operating the at least one RPA robot contained in the work task package based on the execution time rule;
and the recording unit is used for recording the operation result information of the work task packet in the operation life cycle and persisting the operation result information.
In one or more possible embodiments, the apparatus 4 further comprises:
the input unit is used for inputting the basic information of the RPA robot through a visual interface; wherein the basic information comprises one or more of robot name, version number and creation time;
after the input is finished, a robot library is generated based on the input RPA robot;
grouping a plurality of robots contained in the robot library based on an application scene to obtain a plurality of robot scene groups; wherein each robot scene group comprises one or more RPA robots.
In one or more possible embodiments, the execution time rule is one or more of a time-by-time rule, a day-by-day rule, a week-by-week rule, and a month-by-month rule.
In one or more possible embodiments, the running the at least one RPA robot included in the work task package based on the execution time rule includes:
when the work task packet meets a trigger condition, moving the work task packet into a queue to be operated;
when idle running resources exist, the work tasks are moved out of the queue to be run, the work task packets are moved into the running queue, and the work task packets are run based on the execution time rules;
and when the work task package finishes running, removing the work task package from the running queue.
In one or more possible embodiments, the apparatus 4 further comprises:
the monitoring unit is used for monitoring the running state of the work task package and displaying a running state mark associated with the running state; wherein the operating state comprises: any one of to be executed, in execution, and stopped.
In one or more possible embodiments, the queue to be run and the queue to be run are a Redis-based distributed queue, and the work task is executed in parallel by a plurality of nodes.
In one or more possible embodiments, the apparatus 4 further comprises:
the query unit is used for receiving a query request of a user; wherein the query request carries a task name;
inquiring running result information corresponding to the task identification;
returning the running result information to the user
The embodiment of the present application and the method embodiments of fig. 2 and 3 are based on the same concept, and the technical effects brought by the embodiment are also the same, and the specific process may refer to the description of the method embodiments of fig. 2 and 3, and will not be described again here.
The device 4 may be a control node, and the device 4 may also be a field-programmable gate array (FPGA), an application-specific integrated chip (asic), a system on chip (SoC), a Central Processing Unit (CPU), a Network Processor (NP), a digital signal processing circuit, a Micro Controller Unit (MCU), or a Programmable Logic Device (PLD) or other integrated chips.
Fig. 5 is a schematic structural diagram of an apparatus according to an embodiment of the present disclosure. As shown in fig. 5, the apparatus may be the server in fig. 1, and the load classification and metering apparatus 500 may include: at least one processor 501, at least one network interface 504, a user interface 503, memory 505, at least one communication bus 502.
Wherein a communication bus 502 is used to enable connective communication between these components.
The user interface 503 is an interface for a user to interact with the server, and may include a Display screen (Display) and a Camera (Camera). Optionally, the user interface 503 may also include a standard wired interface, a wireless interface.
The network interface 504 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface), among others.
The Memory 505 may include a Random Access Memory (RAM) or a Read-Only Memory (Read-Only Memory). Optionally, the memory 505 includes a non-transitory computer-readable medium. The memory 505 may be used to store instructions, programs, code sets, or instruction sets. The memory 505 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the various method embodiments described above, and the like; the storage data area may store data and the like referred to in the above respective method embodiments. The memory 505 may alternatively be at least one memory device located remotely from the processor 501. As shown in fig. 5, the memory 505, which is a type of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and an application program.
In the electronic device 500 shown in fig. 5, the user interface 503 is mainly used as an interface for providing input for a user, and acquiring data input by the user; and the processor 501 may be configured to call an application program stored in the memory 505 for configuring an application program interface, and specifically perform the following operations:
selecting at least one RPA robot from a robot library to form a work task package;
configuring attribute information and execution time rules of the work task package; wherein the attribute information includes: one or more of task name, task identifier, task description information, creation user identifier and creation time, wherein the execution time rule comprises: execution time and/or number of executions;
running the at least one RPA robot contained in the work task package based on the execution time rule;
and recording the operation result information of the work task packet in the operation life cycle and persisting the operation result information.
In one or more possible embodiments, the processor 501 is further configured to perform: inputting basic information of the RPA robot through a visual interface; wherein the basic information comprises one or more of robot name, version number and creation time;
after the input is finished, a robot library is generated based on the input RPA robot;
grouping a plurality of robots contained in the robot library based on an application scene to obtain a plurality of robot scene groups; wherein each robot scene group comprises one or more RPA robots.
In one or more possible embodiments, the execution time rule is one or more of a time-by-time rule, a day-by-day rule, a week-by-week rule, and a month-by-month rule.
In one or more possible embodiments, the executing the at least one RPA robot included in the work task package based on the execution time rule by the processor 501 includes:
when the work task packet meets a trigger condition, moving the work task packet into a queue to be operated;
when idle running resources exist, the work tasks are moved out of the queue to be run, the work task packets are moved into the running queue, and the work task packets are run based on the execution time rules;
and when the work task package finishes running, removing the work task package from the running queue.
In one or more possible embodiments, the processor 501 is further configured to perform:
monitoring the running state of the work task package, and displaying a running state mark associated with the running state; wherein the operating state comprises: any one of to be executed, in execution, and stopped.
In one or more possible embodiments, the queue to be run and the queue to be run are distributed queues based on Redis, the work task package is executed in parallel by a plurality of nodes, and the plurality of nodes, that is, a plurality of servers, can execute the work task package in parallel on the plurality of servers based on a load balancing manner, so as to improve the execution speed.
In one or more possible embodiments, the processor 501 is further configured to perform:
receiving a query request of a user; wherein the query request carries a task name;
inquiring running result information corresponding to the task identification;
returning the running result information to the user
The concept of this embodiment is the same as that of the embodiment of the method in fig. 2 or fig. 3, and the technical effects brought by the embodiment are also the same, and the specific process can refer to the description of the embodiment in fig. 2 or fig. 3, which is not described again here.
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 a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory or a random access memory.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present application and is not to be construed as limiting the scope of the present application, so that the present application is not limited thereto, and all equivalent variations and modifications can be made to the present application.
Claims (10)
1. A method for managing an RPA robot, comprising:
selecting at least one RPA robot from a robot library to form a work task package;
configuring attribute information and execution time rules of the work task package; wherein the attribute information includes: one or more of task name, task identifier, task description information, creation user identifier and creation time, wherein the execution time rule comprises: execution time and/or number of executions;
running the at least one RPA robot contained in the work task package based on the execution time rule;
and recording the operation result information of the work task packet in the operation life cycle and persisting the operation result information.
2. The method of claim 1, wherein prior to selecting at least one RPA robot in the robot library to compose the work task package, further comprising:
inputting basic information of the RPA robot through a visual interface; wherein the basic information comprises one or more of robot name, version number and creation time;
after the input is finished, a robot library is generated based on the input RPA robot;
grouping a plurality of robots contained in the robot library based on an application scene to obtain a plurality of robot scene groups; wherein each robot scene group comprises one or more RPA robots.
3. The method of claim 1, wherein the execution time rules are one or more of time-wise, day-wise, week-wise, and month-wise.
4. The method according to claim 1, 2 or 3, wherein said running the at least one RPA robot included in the job task package based on the execution time rules comprises:
when the work task packet meets a trigger condition, moving the work task packet into a queue to be operated;
when idle running resources exist, the work tasks are moved out of the queue to be run, the work task packets are moved into the running queue, and the work task packets are run based on the execution time rules;
and when the work task package finishes running, removing the work task package from the running queue.
5. A method according to claim 1, 2 or 3, characterized in that the method further comprises:
monitoring the running state of the work task package, and displaying a running state mark associated with the running state; wherein the operating state comprises: any one of to be executed, in execution, and stopped.
6. The method of claim 5, wherein the queue to be run and the queue to be run are Redis-based distributed queues, and wherein the work task package is executed in parallel by a plurality of nodes.
7. The method of claim 1, 2 or 3, further comprising:
receiving a query request of a user; wherein the query request carries a task name;
inquiring running result information corresponding to the task identification;
and returning the running result information to the user.
8. A management apparatus of an RPA robot, comprising:
the selection unit is used for selecting at least one RPA robot from the robot library to form a work task package;
the configuration unit is used for configuring the attribute information and the execution time rule of the work task package; wherein the attribute information includes: one or more of task name, task identifier, task description information, creation user identifier and creation time, wherein the execution time rule comprises: execution time and/or number of executions;
the operation unit is used for operating the at least one RPA robot contained in the work task package based on the execution time rule;
and the recording unit is used for recording the operation result information of the work task packet in the operation life cycle and persisting the operation result information.
9. A server comprising a processor and a memory, wherein the memory is configured to store a computer program comprising program instructions, and wherein the processor is configured to invoke the program instructions to perform the method of any of claims 1-7.
10. A computer-readable storage medium, characterized in that the computer storage medium stores a computer program comprising program instructions that, when executed by a processor, cause the processor to perform the method according to any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110361442.9A CN113110867A (en) | 2021-04-02 | 2021-04-02 | RPA robot management method, device, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110361442.9A CN113110867A (en) | 2021-04-02 | 2021-04-02 | RPA robot management method, device, server and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113110867A true CN113110867A (en) | 2021-07-13 |
Family
ID=76713528
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110361442.9A Pending CN113110867A (en) | 2021-04-02 | 2021-04-02 | RPA robot management method, device, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113110867A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113467879A (en) * | 2021-07-20 | 2021-10-01 | 上海数慧系统技术有限公司 | Multi-system data processing method and device based on RPA robot |
| CN113741860A (en) * | 2021-09-03 | 2021-12-03 | 中国工商银行股份有限公司 | Data processing method and device based on RPA robot |
| CN117193232A (en) * | 2023-07-26 | 2023-12-08 | 珠海金智维信息科技有限公司 | RPA-based flow node fault processing method, system, device and medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109656698A (en) * | 2018-12-14 | 2019-04-19 | 平安城市建设科技(深圳)有限公司 | Task processing method, management platform, actuating station and computer readable storage medium |
| CN111210136A (en) * | 2019-12-31 | 2020-05-29 | 深圳优地科技有限公司 | Robot task scheduling method and server |
| CN111787089A (en) * | 2020-06-28 | 2020-10-16 | 中国建设银行股份有限公司 | Method, device and system for network integration service of process robot |
| CN112025711A (en) * | 2020-09-09 | 2020-12-04 | 上海有个机器人有限公司 | Timed task execution method and device for robot and robot |
| CN112182655A (en) * | 2020-10-13 | 2021-01-05 | 深圳壹账通智能科技有限公司 | Data interaction method among multiple devices and related devices |
-
2021
- 2021-04-02 CN CN202110361442.9A patent/CN113110867A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109656698A (en) * | 2018-12-14 | 2019-04-19 | 平安城市建设科技(深圳)有限公司 | Task processing method, management platform, actuating station and computer readable storage medium |
| CN111210136A (en) * | 2019-12-31 | 2020-05-29 | 深圳优地科技有限公司 | Robot task scheduling method and server |
| CN111787089A (en) * | 2020-06-28 | 2020-10-16 | 中国建设银行股份有限公司 | Method, device and system for network integration service of process robot |
| CN112025711A (en) * | 2020-09-09 | 2020-12-04 | 上海有个机器人有限公司 | Timed task execution method and device for robot and robot |
| CN112182655A (en) * | 2020-10-13 | 2021-01-05 | 深圳壹账通智能科技有限公司 | Data interaction method among multiple devices and related devices |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113467879A (en) * | 2021-07-20 | 2021-10-01 | 上海数慧系统技术有限公司 | Multi-system data processing method and device based on RPA robot |
| CN113741860A (en) * | 2021-09-03 | 2021-12-03 | 中国工商银行股份有限公司 | Data processing method and device based on RPA robot |
| CN117193232A (en) * | 2023-07-26 | 2023-12-08 | 珠海金智维信息科技有限公司 | RPA-based flow node fault processing method, system, device and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113110867A (en) | RPA robot management method, device, server and storage medium | |
| CN109684054B (en) | Information processing method and device, electronic equipment and memory | |
| CN111506444A (en) | Form approval method and device, storage medium and electronic equipment | |
| CN107741950A (en) | Processing method, device, processor and the service end of data syn-chronization task | |
| CN111507674B (en) | Task information processing method, device and system | |
| CN111427576B (en) | Method, device, storage medium and terminal for configuring application program interface | |
| CN113741860A (en) | Data processing method and device based on RPA robot | |
| CN114356761A (en) | Test case document generation method and device, storage medium and computer equipment | |
| CN111104281B (en) | Game performance monitoring method, device, system and storage medium | |
| CN113076186A (en) | Task processing method and device, electronic equipment and storage medium | |
| CN115344370A (en) | Task scheduling method, device, equipment and storage medium | |
| CN115617441A (en) | Method and device for binding model and primitive, storage medium and computer equipment | |
| CN112416995B (en) | Data statistics method, device, computer equipment and storage medium | |
| CN114675940A (en) | Application instance construction method, device and equipment | |
| CN114066398A (en) | Business model management method and device, storage medium and terminal equipment | |
| CN114995931A (en) | Display method and device of project bulletin board, storage medium and computer equipment | |
| CN112000669B (en) | Environment monitoring data processing method and device, storage medium and terminal | |
| CN114564249A (en) | Recommendation scheduling engine, recommendation scheduling method, and computer-readable storage medium | |
| CN111581932A (en) | Data-driven big data analysis method, system, device, storage medium and terminal | |
| CN112380031A (en) | Method and device for pushing messages in real time in cross-application mode and computing equipment | |
| CN112860419A (en) | Multi-instance task execution method and device, terminal equipment and computer storage medium | |
| CN111339422A (en) | Recommendation system task management platform, recommendation method and system | |
| CN110765610A (en) | PDM (product data management) integration method and device, computer equipment and storage medium | |
| CN114968707A (en) | Method and device for controlling work item state, storage medium and computer equipment | |
| CN114048721A (en) | Report compilation monitoring method and device, storage medium and electronic 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 |