CN115756800A

CN115756800A - Task scheduling method and task scheduling device

Info

Publication number: CN115756800A
Application number: CN202211504661.9A
Authority: CN
Inventors: 何婧
Original assignee: Zhongdian Jinxin Software Co Ltd
Current assignee: Zhongdian Jinxin Software Co Ltd
Priority date: 2022-11-28
Filing date: 2022-11-28
Publication date: 2023-03-07
Anticipated expiration: 2042-11-28
Also published as: CN115756800B

Abstract

The application provides a task scheduling method and a task scheduling device, which respond to the triggering of a task scheduling event and determine to complete a main task flow of a main task to be executed; for each subtask flow, referring to an interface calling parameter of a target RPA robot executing the subtask flow, and generating an interface calling script for calling the target RPA robot; the execution interface calls the script to control the target RPA robot to execute the subtask flow, and generates a task execution result of the subtask flow according to the information generation format in the interface calling script in the execution process; and acquiring a task execution result from the target RPA robot, and storing the task execution result into a local database. Therefore, the script can be called through the execution interface, and all the target RPA robots can be called and managed uniformly through the same platform, so that the management flow of the target RPA robots is simplified.

Description

Task scheduling method and task scheduling device

Technical Field

The present application relates to the field of robot control technologies, and in particular, to a task scheduling method and a task scheduling apparatus.

Background

Robot Process Automation (RPA), which is widely used in digital transformation of domestic enterprises in recent years, many automated business processes related to the enterprises exceed 100, and the same enterprise has a phenomenon of using RPA robots developed by a plurality of different manufacturers, but the RPA robots developed by each manufacturer at present are only controlled by a matching console developed by the manufacturer; that is, the RPA robot can only be monitored by its own manufacturer.

With the increasing number of RPA robots of different manufacturers used by enterprises, the difficulty of managing the RPA robots is also increased synchronously; because the RPA robots of different manufacturers cannot be managed in a unified manner, the RPA robots of different manufacturers need to be managed correspondingly through monitoring platforms provided by different manufacturers, so that the RPA robots are complex in management process and difficult to manage.

Disclosure of Invention

In view of the above, an object of the present invention is to provide a task scheduling method and a task scheduling apparatus, which solve the problem that RPA robots from different manufacturers cannot be managed uniformly in the prior art.

The embodiment of the application provides a task scheduling method, which comprises the following steps:

responding to the triggering of a task scheduling event, and determining to finish a main task flow of a main task to be executed; the main task process comprises at least one subtask process;

aiming at each subtask flow, determining a target RPA robot executing the subtask flow;

generating an interface calling script for calling the target RPA robot by referring to the interface calling parameter of the target RPA robot;

controlling the target RPA robot to complete the subtask flow by executing the interface calling script, generating a format according to the information indicated in the interface calling script in the execution process, and generating a task execution result of the subtask flow;

and acquiring the task execution result from the target RPA robot, and storing the task execution result into a local database.

In a possible implementation manner, the interface calling script comprises embedded point information; the task scheduling method further comprises the following steps:

setting a progress buried point in the target RPA robot by executing the interface calling script;

responding to the triggering of the progress buried point, and determining the current task completion progress of the main task to be executed based on the buried point information of the progress buried point;

and responding to the progress inquiry operation, and displaying the current task completion progress in a graphical user interface of the terminal equipment used by the user.

In a possible implementation manner, the controlling the target RPA robot to complete the sub-task process by executing the interface call script includes:

and in response to the subtask flow reaching the preset execution time, calling an external access interface reserved by the target RPA robot by executing the interface calling script, and controlling the target RPA robot to finish executing the subtask flow.

In one possible implementation, the determining, in response to the triggering of the task scheduling event, to complete the main task process of the main task to be executed includes:

responding to the triggering of a task scheduling event, and acquiring the execution work order information of a main task to be executed;

determining at least one to-be-executed subtask included in the to-be-executed main task based on the execution work order information;

determining and completing a subtask flow of each subtask to be executed;

and combining the subtask flows of each subtask to be executed according to the execution logic of each subtask to be executed to obtain a main task flow of the main task to be executed, and associating the main task number of the main task to be executed with the subtask number of each subtask to be executed.

In one possible embodiment, the preset execution time of each subtask flow is set by:

aiming at each subtask flow, acquiring the execution time information of the subtask flow;

and setting the preset execution time of the subtask flow by using a Cron expression based on the execution time information of the subtask flow.

In one possible embodiment, the execution work order information of the main task to be executed is generated by:

displaying a work order configuration interface in a graphical user interface in response to the task creation instruction; wherein the work order configuration interface comprises at least one information filling item;

for each information filling item, responding to the information configuration operation aiming at the information filling item, and acquiring task detail information input by a user aiming at the information filling item;

and generating the execution work order information of the main task to be executed based on the task detail information input in each information filling item.

In a possible implementation manner, the task scheduling method further includes:

responding to the schedule inquiry operation, and acquiring schedule information of a user in a first preset time period; and displaying the schedule information in a graphical user interface of the terminal equipment used by the user.

responding to log query operation, and acquiring execution log information of the RPA robot to be queried in a second preset time period; and displaying the execution log information in a graphical user interface of the terminal equipment used by the user.

In a possible implementation, the storing the task execution result in a local database includes:

and responding to the arrival of a preset storage time node, and storing the task execution result into a local database.

An embodiment of the present application further provides a task scheduling apparatus, where the task scheduling apparatus includes:

the flow planning module is used for responding to the triggering of the task scheduling event and determining to complete the main task flow of the main task to be executed; the main task process comprises at least one subtask process;

the robot determining module is used for determining a target RPA robot executing each subtask flow;

the script generation module is used for generating an interface calling script for calling the target RPA robot by referring to the interface calling parameter of the target RPA robot;

the task execution module is used for controlling the target RPA robot to finish executing the subtask flow by executing the interface calling script, and generating a task execution result of the subtask flow according to an information generation format indicated in the interface calling script in the execution process;

and the result acquisition module is used for acquiring the task execution result from the target RPA robot and storing the task execution result into a local database.

In a possible implementation manner, the interface calling script comprises embedded point information; the task scheduling device further comprises a progress monitoring module, and the progress monitoring module is used for:

In a possible implementation manner, when the task execution module is configured to control the target RPA robot to complete executing the subtask flow by executing the interface call script, the task execution module is configured to:

In one possible embodiment, when the flow planning module is configured to determine that a main task flow of a main task to be executed is completed in response to triggering of a task scheduling event, the flow planning module is configured to:

determining to complete the subtask flow of each subtask to be executed;

In a possible embodiment, the process planning module is configured to set the preset execution time of each subtask process by:

In a possible implementation manner, the task scheduling apparatus further includes a work order configuration module, and the work order configuration module is configured to generate the execution work order information of the main task to be executed by:

In a possible implementation manner, the task scheduling apparatus further includes a schedule query module, and the schedule query module is configured to:

In a possible implementation manner, the task scheduling apparatus further includes a log query module, and the log query module is configured to:

In one possible implementation, when the result obtaining module is configured to store the task execution result in a local database, the result obtaining module is configured to:

An embodiment of the present application further provides an electronic device, including: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory communicating via the bus when the electronic device is running, the machine-readable instructions when executed by the processor performing the steps of the task scheduling method as described above.

Embodiments of the present application further provide a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to perform the steps of the task scheduling method as described above.

The task scheduling method and the task scheduling device provided by the embodiment of the application respond to the triggering of the task scheduling event and determine to complete the main task flow of the main task to be executed; aiming at each subtask flow, determining a target RPA robot executing the subtask flow; generating an interface calling script for calling the target RPA robot by referring to the interface calling parameter of the target RPA robot; controlling the target RPA robot to finish executing the subtask flow by executing the interface calling script, and generating a task execution result of the subtask flow according to an information generation format indicated in the interface calling script in the executing process; and acquiring the task execution result from the target RPA robot, and storing the task execution result into a local database. Therefore, the target RPA robots from different manufacturers can be called and managed uniformly through the same platform by executing the interface calling script, and the management flow of the target RPA robots is simplified.

In order to make the aforementioned objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.

Fig. 1 is a schematic diagram of a physical architecture of a digital employee management and control system according to an embodiment of the present disclosure;

fig. 2 is a flowchart of a task scheduling method according to an embodiment of the present application;

fig. 3 is a schematic diagram of a task scheduling process according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a task scheduling device according to an embodiment of the present application;

fig. 5 is a second schematic structural diagram of a task scheduling device according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. Every other embodiment that can be obtained by a person skilled in the art without making creative efforts based on the embodiments of the present application falls within the protection scope of the present application.

Research shows that as the number of RPA robots of different manufacturers used by enterprises is continuously increased, the management difficulty of the RPA robots is synchronously increased; because the RPA robots of different manufacturers cannot be managed in a unified manner, the RPA robots of different manufacturers need to be managed correspondingly through monitoring platforms provided by different manufacturers, so that the RPA robots are complex in management process and difficult to manage.

Based on this, the embodiment of the present application provides a task scheduling method, which may refer to an interface call parameter of a target RPA robot, and generate an interface call script for calling the target RPA robot, so as to implement the call of the target RPA robot, so that the interface call script may be executed, and the target RPA robots of different manufacturers may be uniformly called and managed through the same platform, so as to reduce the management difficulty of the RPA robot, and implement the control of the RPA robot more efficiently.

In specific implementation, the task scheduling method provided in the embodiment of the present application may be executed based on a terminal device, where the terminal device may be a local electronic device, such as a smart phone, a personal computer, and a tablet computer, that has downloaded and can run a task scheduling program. The terminal device (for example, the local electronic device) can interact with the user through the scheduling interface, receive a task scheduling event triggered by the user through the scheduling interface, and call the target RPA robot by executing the interface call script.

In addition, when the task scheduling method provided by the embodiment of the application is applied to a server, the task scheduling method can be implemented and executed based on a cloud interaction system, wherein the cloud interaction system can include the server and a client device. In an optional embodiment, a plurality of cloud applications may be run in a server under the cloud interaction system, for example: a plurality of task schedulers. In the operation mode, the operation main body of the task scheduling program related to the task scheduling method and the presentation main body of the scheduling interface are separated, the storage and the operation of the task scheduling method are completed on the server, and the client device is used for presenting the calling interface, for example, the client device may be a display device with a data transmission function near a user side. When the target RPA robot is called, a user operates the client device to trigger a task scheduling event to the server, and the server responds to the task scheduling event and realizes the calling of the target RPA robot by executing the interface calling script.

It should be noted that, when the task scheduling process involves multiple task scheduling devices, the multiple task scheduling devices may be respectively disposed in different servers, or may be integrally disposed in the same server; when a plurality of users participate in the task scheduling process, the plurality of users can use different client devices respectively, or can use the same client device and switch roles in a software mode.

Referring to fig. 1, fig. 1 is a schematic diagram of a physical architecture of a digital employee management and control system according to an embodiment of the present disclosure. As shown in fig. 1, the digital staff member management and control system 100 includes a terminal device 101 used by a user, at least one target RPA robot 102, at least one search server (elastic search) 103, a local database (My SQL) 104, and at least one web server 105 by which the terminal device 101 communicates with the at least one target RPA robot 102.

Referring to fig. 2, fig. 2 is a flowchart of a task scheduling method according to an embodiment of the present application. As shown in fig. 2, a task scheduling method provided in an embodiment of the present application includes:

s201, responding to the trigger of a task scheduling event, and determining to complete a main task flow of a main task to be executed; wherein, the main task flow comprises at least one subtask flow.

S202, aiming at each subtask flow, a target RPA robot for executing the subtask flow is determined.

And S203, generating an interface calling script for calling the target RPA robot by referring to the interface calling parameter of the target RPA robot.

And S204, controlling the target RPA robot to finish executing the subtask flow by executing the interface calling script, and generating a task execution result of the subtask flow according to an information generation format indicated in the interface calling script in the executing process.

S205, obtaining the task execution result from the target RPA robot, and storing the task execution result into a local database.

The task scheduling method provided by the embodiment of the application responds to the triggering of the task scheduling event, and automatically plans and completes the main task flow of the main task to be executed; and according to the execution time of each subtask flow in the main task flow, calling of the target RPA robot corresponding to each subtask flow is realized one by one through the generated interface calling script for calling the target RPA robot, so that the script can be called through the execution interface, and all target RPA robots from different manufacturers can be called and managed uniformly through the same platform, thereby simplifying the management flow of the target RPA robot.

In step S201, when the user needs the assistance of the target RPA robot of the third party to complete the main task to be executed, a task scheduling event may be triggered by the used terminal device, so as to implement the invocation of the target RPA robot of the third party; at this time, the digital employee management and control system for calling, which is provided in the terminal device, may determine to complete the main task flow related to the main task to be executed of the user in response to the trigger of the task scheduling event.

Here, when the main task to be executed is complicated, one main task to be executed may need to be completed by multiple target RPA robots in a cooperative manner, that is, completing the main task to be executed needs target RPA robots of different manufacturers to be completed in a cooperative manner, so that actually, the main task to be executed should include multiple sub tasks to be executed; each subtask to be executed may be considered as an independent task processing flow, and then, the planned main task flow includes at least one subtask flow.

When the main task flow of the main task to be executed is determined, the execution work order information about the main task to be executed, which is filled by the user, can be referred to, and under the condition that the user needs to be known, the main task flow suitable for the main task to be executed is reasonably planned, so that all task requirements provided by the user in the execution work order information are met.

In one embodiment, step S201 includes:

and S2011, responding to the trigger of the task scheduling event, and acquiring the execution work order information of the main task to be executed.

In the step, in response to the triggering of a task scheduling event, acquiring the execution work order information about the main task to be executed, which is submitted by a user; the execution work order information is information which is filled and submitted by a user through terminal equipment and is used for stipulating relevant task requirements of a main task to be executed.

When the main task flow of the main task to be executed is formulated, the execution work order information needs to be referred to, so that the formulated main task flow can meet all task requirements in the execution work order information.

S2012, determining at least one to-be-executed subtask included in the to-be-executed main task based on the execution work order information.

In this step, the main task to be executed that the user needs to complete may need to be completed cooperatively by different target RPA robots, and the task that the different target RPA robots need to execute may be regarded as one sub task to be executed in the main task to be executed, so that at least one sub task to be executed included in the main task to be executed may be determined with reference to the execution work order information.

It should be noted that, here, the "execution main body" is taken as a unit, and the main task to be executed is divided, that is, the main task to be executed is divided into at least one sub-task to be executed according to the target RPA robot for executing the task.

Illustratively, 3 target RPA robots are required for completing the main task to be executed, and the target RPA robot a, the target RPA robot B, and the target RPA robot C, so the main task to be executed may be divided into 3 sub-tasks to be executed according to the target RPA robot, and the sub-tasks to be executed respectively include: a to-be-executed subtask 1, a to-be-executed subtask 2, and a to-be-executed subtask 3; the subtask to be executed 1 is executed by the target RPA robot a, the subtask to be executed 2 is executed by the target RPA robot B, and the subtask to be executed 3 is executed by the target RPA robot C.

And S2013, determining to finish the subtask flow of each subtask to be executed.

In the step, a corresponding subtask flow is planned for each subtask to be executed, and the subtask flow of each subtask to be executed is determined.

S2014, combining the subtask flows of each subtask to be executed according to the execution logic of each subtask to be executed to obtain a main task flow of the main task to be executed, and associating the main task number of the main task to be executed with the subtask number of each subtask to be executed.

In the step, after the subtask flow of each subtask to be executed is obtained, the main task flow of the main task to be executed can be determined by combining the subtask flows of each subtask to be executed; specifically, the position of each subtask flow in the task flow may be determined according to the execution logic of each subtask to be executed, and then each subtask flow is combined according to the position of each subtask flow to obtain the main task flow of the main task to be executed.

In order to ensure that the to-be-executed subtasks under the to-be-executed main task are not omitted to be executed when the to-be-executed main task is executed, when the main task flow of the to-be-executed main task is generated, the subtask number of the to-be-executed subtask is associated with the main task number of the to-be-executed main task; for example, if the main task number of the main task to be executed is "1", then the sub task number of the 1 st sub task to be executed under the main task to be executed is associated with the main task number to obtain the sub task number of the 1 st sub task to be executed as "11", the sub task number of the 2 nd sub task to be executed under the main task to be executed is associated with the main task number to obtain the sub task number of the 2 nd sub task to be executed as "12", and so on.

The execution logic comprises an execution sequence and an execution time of the subtasks to be executed; that is, each subtask flow may be combined according to the execution sequence of the subtask to be executed corresponding to each subtask flow, so as to obtain a main task flow of the main task to be executed; and combining the subtask flows according to the execution time of the subtask to be executed corresponding to each subtask flow to obtain the main task flow of the main task to be executed.

Here, a main task number of a main task to be executed and a sub task number of each sub task to be executed are stored in a search server (elastic search); the elastic search is a distributed, highly-extended and highly-real-time search and data analysis engine, and provides near-real-time search and analysis for all types of data.

In one embodiment, the execution work order information of the main task to be executed is generated by:

step a, responding to a task creating instruction, and displaying a work order configuration interface in a graphical user interface.

In the step, when the user has the work order configuration requirement, a task creation instruction can be issued; at the moment, the terminal device responds to the task creating instruction, and displays a work order configuration interface in a graphical user interface of the terminal device, so that a user can create execution work order information of the main task to be executed through the work order configuration interface.

In the scheme provided by the application, in response to the task creation instruction, specifically, a user can issue the task creation instruction through the task creation control and/or the preset combination key; specifically, a user can create a control through a finger, a mouse and other touch tasks; or through preset combination keys in the keyboard, for example, the keys such as ctrl key, alt key, a key, etc. in the keyboard, the preset keys may be manually set according to the user's requirements.

Here, the work order configuration interface displayed in the graphic user interface includes at least one information filling item therein.

And b, aiming at each information filling item, responding to the information configuration operation aiming at the information filling item, and acquiring the task detail information input by the user aiming at the information filling item.

In the step, aiming at each information filling item of the work order configuration interface, a user can complete the input of the information filling item through information configuration operation; and in response to the information configuration operation applied by the user to the information filling item, acquiring the task detail information input by the user to the information filling item through the information configuration operation.

In the scheme provided by the application, in response to the information configuration operation for the information filling item, specifically, a user can apply the information configuration operation through an information configuration control and/or a preset combination key; specifically, a user can create a control through a finger, a mouse and other touch tasks; or through preset combination keys in the keyboard, for example, the keys of ctrl key, alt key, a key, etc. in the keyboard, the preset keys may be manually set according to the user's requirements.

The information configuration operation comprises at least one of an input operation, a selection operation, a pasting operation, a double-click operation, a single-click operation and a dragging operation.

And c, generating the execution work order information of the main task to be executed based on the task detail information input in each information filling item.

The RPA robot, i.e. Robot Process Automation (RPA), has a main function of controlling the RPA robot to execute a main task to be executed according to a prepared main task flow.

For a main task to be executed, different target RPA robots may need to be called to complete subtask flows related to different subtasks to be executed in the main task to be executed, and therefore, for each subtask flow, a target RPA robot to be called for completing the subtask flow needs to be determined.

In step S202, for each subtask flow, a target RPA robot that completes the subtask flow is determined.

In general, when calling the target RPA robot, a monitor station of the target RPA robot needs to be registered to control the target RPA robot in the monitor station.

In step S203, the target RPA robot is called by generating an interface call script of the target RPA robot, so that the target RPA robot can be called without logging in a monitoring console of the target RPA robot; specifically, an interface calling script for calling the target RPA robot may be generated with reference to an interface calling parameter of the target RPA robot, so as to implement autonomous docking and calling of the target RPA robot through the interface calling script.

Here, the execution times of different subtask flows are different, and therefore, when each subtask flow is executed, it is also necessary to consider that each subtask flow reaches the preset execution time, so as to complete the execution of the subtask flow at the corresponding execution time.

In step S204, the generated interface call script for calling the target RPA robot corresponding to the subtask flow is executed, so as to implement the call of the target RPA robot through the interface call script, and control the target RPA robot to complete the execution of the subtask flow.

Because the terminal device used by the user has a certain format requirement for the received information, in order to avoid the unavailability of the task execution result obtained in the subsequent process of the terminal device, when the target RPA robot is called, the generation format of the task execution result is also limited by the interface calling script.

Specifically, in the process of executing the subtask flow by the control target RPA robot, the control target RPA robot generates a task execution result of the subtask flow according to the information generation format indicated in the interface call script.

In one embodiment, said invoking a script by executing said interface to control said target RPA robot to complete executing the subtask flow includes: and in response to the subtask flow reaching the preset execution time, calling an external access interface reserved by the target RPA robot by executing the interface calling script, and controlling the target RPA robot to finish executing the subtask flow.

Here, when each target RPA robot leaves the factory, an external access interface is reserved, that is, the target RPA robot can be called through the external access interface, so that when the target RPA robot has a calling requirement, the target RPA robot can be called through calling the reserved external access interface.

In the step, in response to that the subtask flow reaches the preset execution time, the script is called through the execution interface, so that the terminal device used by the user is autonomously docked with the external access interface reserved by the target RPA robot, and at the moment, the target RPA robot can be controlled to complete the subtask flow through the reserved external access interface.

In one embodiment, the preset execution time of each subtask flow is set by: aiming at each subtask flow, acquiring the execution time information of the subtask flow; and setting the preset execution time of the subtask flow by using a Cron expression based on the execution time information of the subtask flow.

In the step, in order to flexibly implement the configuration of the preset execution time of the subtask flow, here, the configuration of the preset execution time of the subtask flow needs to be implemented by means of a Cron expression; specifically, for each subtask flow, the execution time information of the subtask flow is obtained, the execution time of the subtask flow is determined, and then, based on the execution time information of the subtask flow, the preset execution time of the subtask flow is set by using a Cron expression.

The Cron expression is a character string with time meaning, the character string is separated by 5-6 blank spaces and divided into 6-7 fields, and the format is X X X X X X X X X. Where X is a placeholder for a field. The last year-representative domain is not essential and may be omitted. When a single field has multiple values, half-angle commas are used to separate the values. Each field may be a definite value or a special character with logical meaning. Each domain supports at most one leading zero.

For example, assuming that the execution time information of the subtask flow is "10 execute tasks every morning in 10", the expression "0 15 10? * "wherein" "indicates all possible values, in particular, when" "is in the" month field "position, then each month is indicated; when the 'x' is positioned in the 'week field' position, the 'x' represents each day in the week; "? "means that no value is specified, only the date and week field supports the character, and after one of the date or week field is specified with a value, the value of the other field needs to be set to"? ".

In step S205, a task execution result generated in accordance with the indicated information generation format during the process of executing the subtask flow by the target RPA robot is obtained from the target RPA robot side; and storing the obtained task execution result in a local database of the terminal equipment.

Here, the local database is a My SQL database.

Here, in consideration of the fact that the target RPA robot executes a subtask flow and simultaneously acquires a task execution result generated by the target RPA robot in real time, which may affect the execution process of the target RPA robot, a "decoupling design" is adopted in the present application, and the task execution result is acquired from the target RPA robot at regular time by setting a timing acquisition device, so as to avoid causing interference to the target RPA robot.

In one embodiment, step S205 includes: and responding to the preset trigger time of the timing collector, and acquiring a task execution result generated by the target RPA robot according to the indicated information generation format in the process of executing the subtask flow from the target RPA robot side.

In the step, a decoupling design mode is adopted, the timing collector is set, the timing collector responds to the fact that the timing collector reaches the preset trigger time, the task execution result of the main task to be executed is obtained from the target RPA robot at regular time, the situation that the task execution result obtained in real time interferes with the target RPA robot, and execution is abnormal is avoided, further, interference on the target RPA robot execution process is reduced, and the accuracy of the execution result is improved.

Here, in order to reduce the number of times of writing data into the local database, the task execution result is periodically written into the local database by using a periodic storage method.

In one embodiment, the storing the task execution result in a local database includes: and responding to the arrival of a preset storage time node, and storing the task execution result into a local database.

In the step, in response to the preset storage time node being reached, the task execution result of the subtask flow acquired from the target RPA robot side is stored in the local database at regular time.

Here, in order to accurately know the execution progress of the target RPA robot, the target RPA robot may be monitored in a point-buried manner.

In one embodiment, the interface calling script comprises embedded point information; the task scheduling method further comprises the following steps:

and step 1, setting a progress buried point in the target RPA robot by executing the interface calling script.

In the step, the buried point information is written into an interface calling script, the interface calling script is executed, and a progress buried point is set in the target RPA robot by using the buried point information.

And 2, responding to the trigger of the progress buried point, and determining the current task completion progress of the main task to be executed based on the buried point information of the progress buried point.

In the step, in response to the set progress buried point being triggered, acquiring buried point information of the triggered progress buried point; determining the current task completion progress of the main task to be executed according to the acquired embedded point information; illustratively, assuming that a progress buried point representing 80% of task completion progress is set on the target RPA robot side, when the progress buried point is triggered, it indicates that the current task completion progress of the main task to be executed is 80%.

And 3, responding to progress inquiry operation, and displaying the current task completion progress in a graphical user interface of the terminal equipment used by the user.

In the step, when the user has a requirement for completing the progress query, the task completion progress query can be realized through the progress query operation; specifically, in response to a progress query operation applied by a user, the current task completion progress is displayed in a graphical user interface of a terminal device used by the user.

In the scheme provided by the application, in response to the progress query operation, specifically, a user can apply the progress query operation through the progress query control and/or the preset combination key; specifically, the user can query the control through a finger, a mouse and the like; or through preset combination keys in the keyboard, for example, the keys such as ctrl key, alt key, a key, etc. in the keyboard, the preset keys may be manually set according to the user's requirements.

The progress query operation comprises at least one of an input operation, a selection operation, a pasting operation, a double-click operation, a single-click operation and a dragging operation.

In order to facilitate the user to check different information related to the main task to be executed, the user can check the different information through different operations; for example, the user may also choose to view schedule information of the user, execution log information generated by the target RPA robot executing the main task to be executed, and the like.

In one embodiment, the task scheduling method further includes: responding to the schedule inquiry operation, and acquiring schedule information of a user in a first preset time period; and displaying the schedule information in a graphical user interface of the terminal equipment used by the user.

In the step, a user can check the schedule in a certain time period by applying schedule inquiry operation through the used terminal equipment; responding to a schedule inquiry operation applied by a user, and acquiring schedule information of the user in a first preset time period; and displaying the acquired schedule information in a graphical user interface of the terminal equipment used by the user for facilitating the viewing of the user.

In the scheme provided by the application, in response to the schedule query operation, specifically, a user can apply the schedule query operation through the schedule query control and/or the preset combination key; specifically, the user can query the control by touching the schedule through a finger, a mouse and the like; or through preset combination keys in the keyboard, for example, the keys such as ctrl key, alt key, a key, etc. in the keyboard, the preset keys may be manually set according to the user's requirements.

The schedule inquiry operation comprises at least one of an input operation, a selection operation, a pasting operation, a double-click operation, a single-click operation and a dragging operation.

In another embodiment, the task scheduling method further includes: responding to log query operation, and acquiring execution log information of the RPA robot to be queried in a second preset time period; and displaying the execution log information in a graphical user interface of the terminal equipment used by the user.

In the step, the user can realize the query of the execution log by applying the log query operation through the used terminal equipment; responding to a log query operation applied by a user, and acquiring execution log information generated when the RPA robot to be queried executes a corresponding task within a second preset time period; in order to facilitate the viewing of the user, the acquired execution log information is displayed in a graphical user interface of the terminal device used by the user.

In the scheme provided by the application, in response to the log query operation, a user can specifically apply the log query operation through a log query control and/or a preset combination key; specifically, the user can query the control through a touch log such as a finger and a mouse; or through preset combination keys in the keyboard, for example, the keys such as ctrl key, alt key, a key, etc. in the keyboard, the preset keys may be manually set according to the user's requirements.

The log query operation comprises at least one of an input operation, a selection operation, a paste operation, a double-click operation, a single-click operation and a drag operation.

Referring to fig. 3, fig. 3 is a schematic diagram of a task scheduling process according to an embodiment of the present application. As shown in fig. 3, step 301: the terminal equipment plans a main task flow of a main task to be executed; step 302: the terminal equipment distributes a main task to be executed to the started target RPA robot according to the main task flow; step 303: if user cooperation is needed in the process that the target RPA robot executes the main task to be executed, the cooperation information is sent to a cooperation user; step 304: after the cooperative users finish the cooperation, returning a cooperation result to the cooperative users; step 305: and after the target RPA robot finishes the main task to be executed, feeding back an execution result to the terminal equipment.

The task scheduling method provided by the embodiment of the application responds to the triggering of the task scheduling event and determines to complete the main task flow of the main task to be executed; aiming at each subtask flow, determining a target RPA robot executing the subtask flow; generating an interface calling script for calling the target RPA robot by referring to the interface calling parameter of the target RPA robot; controlling the target RPA robot to finish executing the subtask flow by executing the interface calling script, and generating a task execution result of the subtask flow according to an information generation format indicated in the interface calling script in the executing process; and acquiring the task execution result from the target RPA robot, and storing the task execution result into a local database. Therefore, the script can be called through the execution interface, and all target RPA robots from different manufacturers can be called and managed uniformly through the same platform, so that the management flow of the target RPA robots is simplified; meanwhile, a decoupling design mode is adopted, and a timing collector is arranged to obtain task execution results of main tasks to be executed from the target RPA robot at regular time, so that the situation that the task execution results obtained in real time interfere with the target RPA robot and execution is abnormal is avoided, further, the interference on the target RPA robot execution process is reduced, and the accuracy of the execution results is improved.

Referring to fig. 4 and 5, fig. 4 is a first schematic structural diagram of a task scheduling device according to an embodiment of the present application, and fig. 5 is a second schematic structural diagram of a task scheduling device according to an embodiment of the present application. As shown in fig. 4, the task scheduling device 400 includes:

a flow planning module 410, configured to determine to complete a main task flow of a main task to be executed in response to triggering of a task scheduling event; the main task process comprises at least one subtask process;

a robot determining module 420, configured to determine, for each subtask flow, a target RPA robot to execute the subtask flow;

a script generating module 430, configured to refer to the interface call parameter of the target RPA robot, and generate an interface call script for calling the target RPA robot;

the task execution module 440 is configured to control the target RPA robot to complete execution of the subtask flow by executing the interface call script, and generate a task execution result of the subtask flow according to an information generation format indicated in the interface call script in an execution process;

a result obtaining module 450, configured to obtain the task execution result from the target RPA robot, and store the task execution result in a local database.

Further, as shown in fig. 5, the interface call script includes embedded point information; the task scheduling device 400 further includes a progress monitoring module 460, and the progress monitoring module 460 is configured to:

Further, when the task execution module 440 is configured to control the target RPA robot to complete executing the subtask flow by executing the interface call script, the task execution module 440 is configured to:

Further, when the flow planning module 410 is configured to determine that the main task flow of the main task to be executed is completed in response to the triggering of the task scheduling event, the flow planning module 410 is configured to:

determining and completing a subtask flow of each subtask to be executed;

Further, the flow planning module 410 is configured to set the preset execution time of each subtask flow by the following steps:

aiming at each subtask to be executed, acquiring execution time information of the subtask to be executed;

and setting the preset execution time of the subtask to be executed by using a Cron expression based on the execution time information of the subtask to be executed.

Further, as shown in fig. 5, the task scheduling device 400 further includes a work order configuration module 470, where the work order configuration module 470 is configured to generate the execution work order information of the main task to be executed by:

displaying a work order configuration interface in a graphical user interface in response to the task creation instruction; the work order configuration interface comprises at least one information filling item;

Further, as shown in fig. 5, the task scheduling device 400 further includes a schedule query module 480, where the schedule query module 480 is configured to:

Further, as shown in fig. 5, the task scheduling apparatus 400 further includes a log query module 490, where the log query module 490 is configured to:

Further, when the result obtaining module 450 is configured to store the task execution result in the local database, the result obtaining module 450 is configured to:

The task scheduling device provided by the embodiment of the application responds to the triggering of the task scheduling event and determines to complete the main task flow of the main task to be executed; aiming at each subtask flow, determining a target RPA robot executing the subtask flow; generating an interface calling script for calling the target RPA robot by referring to the interface calling parameter of the target RPA robot; responding to the fact that the subtask flow reaches a preset execution time, controlling the target RPA robot to finish executing the subtask flow by executing the interface calling script, and generating a task execution result of the subtask flow according to an information generation format indicated in the interface calling script in the execution process; and responding to the preset trigger time of the timing collector, acquiring the task execution result from the target RPA robot, and storing the task execution result in a local database. Therefore, the target RPA robots from different manufacturers can be uniformly managed through the same platform by calling the script through the execution interface, and the calling and managing processes of the target RPA robots are simplified.

Referring to fig. 6, fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure. As shown in fig. 6, the electronic device 600 includes a processor 610, a memory 620, and a bus 630.

The memory 620 stores machine-readable instructions executable by the processor 610, when the electronic device 600 runs, the processor 610 communicates with the memory 620 through the bus 630, and when the machine-readable instructions are executed by the processor 610, the steps of the task scheduling method in the method embodiment shown in fig. 1 may be executed.

An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the step of the task scheduling method in the method embodiment shown in fig. 1 may be executed.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer-readable storage medium executable by a processor. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present application, and are used for illustrating the technical solutions of the present application, but not limiting the same, and the scope of the present application is not limited thereto, and although the present application is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope disclosed in the present application; such modifications, changes or substitutions do not depart from the spirit and scope of the exemplary embodiments of the present application, and are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A task scheduling method is characterized by comprising the following steps:

controlling the target RPA robot to finish executing the subtask flow by executing the interface calling script, and generating a task execution result of the subtask flow according to an information generation format indicated in the interface calling script in the executing process;

2. The task scheduling method according to claim 1, wherein the interface call script includes embedded point information; the task scheduling method further comprises the following steps:

and responding to progress inquiry operation, and displaying the current task completion progress in a graphical user interface of the terminal equipment used by the user.

3. The task scheduling method according to claim 1, wherein the controlling the target RPA robot to complete the sub-task process by executing the interface call script comprises:

4. The task scheduling method according to claim 1, wherein the determining to complete the main task flow of the main task to be executed in response to the triggering of the task scheduling event comprises:

determining to complete the subtask flow of each subtask to be executed;

5. The task scheduling method according to claim 3, wherein the preset execution time of each subtask flow is set by:

6. The task scheduling method according to claim 4, wherein the execution work order information of the main task to be executed is generated by:

7. The task scheduling method according to claim 1, wherein the task scheduling method further comprises:

8. The task scheduling method according to claim 1, wherein the task scheduling method further comprises:

9. The task scheduling method according to claim 1, wherein the storing the task execution result in a local database comprises:

10. A task scheduling apparatus, characterized in that the task scheduling apparatus comprises: