CN115775132A - Automatic generation system, method, device and storage medium for backlog - Google Patents
Automatic generation system, method, device and storage medium for backlog Download PDFInfo
- Publication number
- CN115775132A CN115775132A CN202211323429.5A CN202211323429A CN115775132A CN 115775132 A CN115775132 A CN 115775132A CN 202211323429 A CN202211323429 A CN 202211323429A CN 115775132 A CN115775132 A CN 115775132A
- Authority
- CN
- China
- Prior art keywords
- backlog
- leaving
- rpa
- handled
- employee
- 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
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application discloses a system, a method, a device and a storage medium for automatically generating backlog, wherein the system comprises an RPA system, a first system and a second system; the method comprises the steps that a first system initiates a leaving process, an RPA system is triggered to operate by the leaving process, the RPA system captures unprocessed to-be-handled process items of a leaving employee, and the unprocessed to-be-handled process items of the leaving employee are written into to-be-handled event lists of leaving process interfaces of the first system and a second system; and the RPA system judges whether the leave employee does not process the to-be-handled flow items or not, and if so, the RPA system urges the leave employee to remind the responsible person. According to the method, the method for generating the incomplete backlog list of each system is realized by utilizing the RPA technology, the method is incorporated into the process link of the leaving process, an urging mechanism is automatically initiated, the leaving staff is urged to complete the processing of the related backlog, the efficiency of the processing of the leaving process is improved, the backlog of each system is ensured to be cleaned and completed after staff leave, the dead process is avoided, and the management efficiency and quality of enterprise staff are improved.
Description
Technical Field
The application relates to the field of office systems, in particular to an automatic generation system, method, device and storage medium of leave-to-do matters.
Background
The RPA (resilient process automation, called RPA for short) robot process automation is a business process automation technology based on software robot and Artificial Intelligence (AI), and simulates the operation of a human on a computer through specific robot software to automatically execute process tasks according to rules.
In the development process of enterprises, personnel optimization and job leaving are the normal state, and for some large enterprises or rapidly expanding enterprises, personnel change and leave jobs are daily routine. Based on the reasons of company data confidentiality, workflow, use of various third-party office software and the like, a plurality of mutually independent office software are often provided for employees to use. Therefore, when personnel of the department of Human Resources (HR) transacts a leave process for the personnel, work handover needs to be performed, in order to ensure that the relevant processes of each system are in an approval stage and ensure that the phenomenon of dead processes of bad processes due to the fact that the relevant current processes or work is blocked because of personnel leave is avoided, multiple office software needs to be logged in to confirm whether the relevant processes are pending or not and notify the leave personnel of completing the pending items of the relevant system before leaving, and for a system which is not managed and controlled by HR authority, the flow is required to be traced and notify relevant system managers to supervise the leave personnel of completing the relevant system work. These works are very cumbersome and cumbersome. And when the number of staff leaving the office is large, the staff of the human resource department is required to repeatedly operate the jobs, so that a large amount of working time is occupied, and the working efficiency is low. Therefore, how to improve the efficiency of the processing of the leaving flow on the basis of reducing the manpower, ensure that the staff clear and complete the backlog of each system after leaving the work, and avoid the occurrence of dead flow and bad flow is a urgent solution.
There are 2 ways currently on the market to try to solve this type of problem:
1. and the RPA generates a to-do list. At present, a method exists in the market, an RPA technology is triggered regularly according to scene requirements, a to-be-handled list related to a main scene and sub-scenes is generated, the to-be-handled list is automatically triggered and sent to related personnel to supplement sub-scene information, and then the to-be-handled list is gathered and summarized into the main scene, so that cross-domain fusion statistical capability is realized. The method mainly comprises the steps of automatically generating the sub-tasks to be handled through the RPA, sending the sub-tasks to relevant personnel for processing, and collecting the sub-tasks to the main task after processing, so that the cross-domain fusion statistical capacity is realized, and the relevant personnel still need to process according to the received list to be handled.
2. The system realizes data interface communication. The enterprise internal information degree is high, related data interfaces are opened through all the systems, the first system compiles script rules, when the first system triggers the leaving process, the rules are triggered by the background, the employee process backlog interfaces of the second system are inquired to collect the backlog rules, and the backlog rules are updated to the subsidiary forms to be processed of the leaving process of the first system, but the method has 2 problems: a. the method has the problems of high cost, long period and complex flow, the personnel to-be-handled flow forms of each system are different, different interface rules are often required to be appointed, data conversion is carried out at the same time, and the data are written back to a flow to-be-processed sub-table; b. if the second system does not provide a relevant interface, the personnel relevant backlogs of the system cannot be acquired, and manual operation is still needed.
Therefore, the above technical problems in the related art need to be solved.
Disclosure of Invention
The present application is directed to solving one of the technical problems in the related art. Therefore, the embodiment of the application provides a system, a method, a device and a storage medium for automatically generating the backlog, which can automatically generate the backlog based on the RPA technology.
According to one aspect of the embodiment of the application, an automatic generation system of the backlog is provided, and the system comprises an RPA system, a first system and a second system;
the first system initiates a job leaving process, the job leaving process triggers the RPA system to operate, the RPA system captures the unprocessed to-be-handled process items of the job-leaving staff, and the unprocessed to-be-handled process items of the job-leaving staff are written into the to-be-handled event list of the job-leaving process interfaces of the first system and the second system;
and the RPA system judges whether the leave employee does not process the to-be-handled flow items or not, if so, the RPA system urges the leave employee to be handled and reminds a responsible person.
In one embodiment, the RPA system grabs the non-processed to-do flow items of the employee, including:
the RPA system detects whether an interface for inquiring the employee process backlog exists, and if so, the RPA system inquires the employee process backlog through the interface for inquiring the employee process backlog;
and if the information does not exist, the RPA system acquires the employee process backlog by logging in an administrator page of the second system.
In one embodiment, after the employee is promoted to leave, the RPA system determines whether the leave employee does not process the to-be-handled flow item again, and if not, the RPA system transfers to the next node of the leave flow.
In one embodiment, the first system initiates an out-of-job flow, comprising:
the staff of the first system initiates a job leaving process;
or after the first system detects that the job leaving information exists, the first system automatically initiates a job leaving process.
In one embodiment, writing the non-processed to-do flow items of the job leaving employee into the to-do event list of the job leaving flow interface of the first system and the second system includes:
the RPA system acquires the modification permission of the to-be-handled event list of the departure flow interfaces of the first system and the second system;
and the RPA system writes the non-processed backlog flow items of the job leaving staff into backlog event promotion lists of the job leaving flow interfaces of the first system and the second system.
In one embodiment, the RPA system obtains the modification authority of the to-be-done event list of the leave flow interface of the first system and the second system through a call interface.
According to an aspect of the embodiment of the present application, there is provided an automatic generation method of backlog, which is applied to the automatic generation system of backlog in the foregoing embodiment, and includes:
initiating a leave process;
capturing unprocessed to-be-done flow items of the off-workers, and writing the unprocessed to-be-done flow items of the off-workers into to-be-done promotion item lists of off-work flow interfaces of the first system and the second system;
and judging whether the leave employee does not process the to-be-handled flow items or not, if so, prompting the leave employee to remind a responsible person.
According to an aspect of an embodiment of the present application, an apparatus for automatically generating a leave-to-do item is provided, the apparatus including:
the system comprises a first module, a second module and a third module, wherein the first module is used for initiating a job leaving process;
the second module is used for capturing the unprocessed to-be-done flow items of the staff leaves and writing the unprocessed to-be-done flow items of the staff leaves into the to-be-done promotion item list of the leave flow interfaces of the first system and the second system;
and the third module is used for judging whether the leave employee does not process the to-be-handled flow items or not, if so, the leave employee is urged to be handled, and a responsible person is reminded.
According to an aspect of an embodiment of the present application, an apparatus for automatically generating a leave-to-do item is provided, the apparatus including:
at least one processor;
at least one memory for storing at least one program;
at least one of the programs when executed by at least one of the processors implements the automated generation system of leave backlogs as described in previous embodiments.
According to an aspect of the embodiments of the present application, there is provided a storage medium storing a program executable by a processor, the program executable by the processor implementing the automatic generation system of the leave-to-do-work according to the foregoing embodiments when executed by the processor.
The system, the method and the device for automatically generating the backlog and the storage medium provided by the embodiment of the application have the advantages that: the system comprises an RPA system, a first system and a second system; the first system initiates a job leaving process, the job leaving process triggers the RPA system to operate, the RPA system captures the unprocessed to-be-handled process items of the job-leaving staff, and the unprocessed to-be-handled process items of the job-leaving staff are written into the to-be-handled event list of the job-leaving process interfaces of the first system and the second system; and the RPA system judges whether the leave employee does not process the to-be-handled flow items or not, if so, the RPA system urges the leave employee to be handled and reminds a responsible person. The method can generate the incomplete backlog list form of each system by utilizing the RPA technology, is incorporated into the process link of the leaving process, automatically initiates an urging mechanism to urge the leaving staff to complete the processing of the related backlog until the staff complete the processing of the related backlog, and the leaving process can be carried out backwards.
Additional aspects and advantages of the present application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the present application.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic workflow diagram of an automatic generation system of leave-to-do matters according to an embodiment of the present application;
FIG. 2 is a to-do event list provided by an embodiment of the present application;
fig. 3 is a schematic diagram of an automatic generation apparatus for leave-to-do matters according to an embodiment of the present application;
fig. 4 is a schematic diagram of another automatic generation apparatus for backlog according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions better understood by those skilled in the art, 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 partial embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "first," "second," "third," and "fourth," etc. in the description and claims of this application and the accompanying drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
The RPA (resilient process automation, called RPA for short) robot process automation is a business process automation technology based on software robot and Artificial Intelligence (AI), and simulates the operation of a human on a computer through specific robot software to automatically execute process tasks according to rules.
In the development process of enterprises, personnel optimization and job leaving are normal, and for some large enterprises or rapidly expanding enterprises, personnel change and leave jobs are daily routine. Based on the reasons of company data confidentiality, workflow, use of various third-party office software and the like, a plurality of mutually independent office software are often provided for employees to use. Therefore, when a person (HR for short) in the human resource department handles a leaving process for a person, the person needs to perform work handover, in order to ensure that a relevant process of each system is in an approval stage, and ensure that a bad process and a dead process are not generated due to the fact that the relevant process or work is blocked because of the person leaving, a plurality of office software needs to be logged in to confirm whether the relevant process is pending, and notify the leaving person to complete the pending items of the relevant system before leaving, and for a system which is not managed and controlled by HR, the person needs to go around to notify a relevant system manager to supervise the leaving person to complete the relevant system work. These works are very cumbersome and cumbersome. And when the number of staff leaving the office is large, the staff of the human resource department is required to repeatedly operate the jobs, so that a large amount of working time is occupied, and the working efficiency is low. Therefore, how to improve the efficiency of the processing of the leaving flow on the basis of reducing the manpower, ensure that the staff clear and complete the backlog of each system after leaving the work, and avoid the occurrence of dead flow and bad flow is a urgent solution.
There are 2 ways currently on the market to try to solve such problems:
1. and the RPA generates a to-do list. At present, a method exists in the market, an RPA technology is triggered periodically according to scene requirements, a to-do list related to a main scene and a sub-scene is generated, the to-do list is automatically triggered and sent to related personnel to supplement sub-scene information, and the to-do list is gathered and summarized into the main scene, so that the cross-domain fusion statistical capability is realized. The method mainly comprises the steps of automatically generating the subtasks to be handled through the RPA, issuing the subtasks to relevant personnel for processing, and summarizing the subtasks to the main task after processing, so that the cross-domain fusion statistical capability is realized, and the relevant personnel still need to process according to the received list to be handled.
2. The system realizes data interface communication. The enterprise internal information degree is high, related data interfaces are opened through all the systems, the first system compiles script rules, when the first system triggers the leaving process, the rules are triggered by the background, the employee process backlog interfaces of the second system are inquired to collect the backlog rules, and the backlog rules are updated to the subsidiary forms to be processed of the leaving process of the first system, but the method has 2 problems: a. the method has the problems of high cost, long period and complex flow, the personnel to-be-handled flow forms of each system are different, different interface rules are often required to be appointed, data conversion is carried out at the same time, and the data are written back to a flow to-be-processed sub-table; b. if the second system does not provide a relevant interface, the personnel relevant backlogs of the system cannot be acquired, and manual operation is still needed.
In order to solve the above problems, the present application provides a system, a method, an apparatus, and a storage medium for automatically generating backlog. The method aims to collect backlogs of all systems to form an urging form so as to urge relevant personnel to process, the backlogs related to the relevant personnel in all systems are uniformly captured through the RPA technology, the urging form is associated to a leaving flow link, and the leaving personnel cannot perform the next step if the leaving personnel do not complete related task handover and flow processing. The method solves the problem of system data handover which is the most difficult to supervise in staff leaving, and can be introduced into a manual system or a leaving process of each system. When the handling of the to-be-handled items in the job leaving process work handover link is completed, the to-be-handled items can be twisted to the next node, so that the normal operation of the system process is ensured after the staff leave.
Fig. 1 is a schematic workflow diagram of an automatic generation system of leave-to-do matters according to an embodiment of the present application. As shown in fig. 1, the system for automatically generating the leave-to-do-work proposed by the present application includes: the system comprises an RPA system, a first system and a second system; the first system initiates a job leaving process, the job leaving process triggers the RPA system to operate, the RPA system captures the unprocessed to-be-handled process items of the job-leaving staff, and the unprocessed to-be-handled process items of the job-leaving staff are written into the to-be-handled event list of the job-leaving process interfaces of the first system and the second system; and the RPA system judges whether the leave employee does not process the to-be-handled flow items or not, if so, the RPA system urges the leave employee to be handled and reminds a responsible person.
As shown in fig. 2, the to-do and event list of the leave-job flow interface clearly indicates the type of the tool flow, the corresponding number of the to-do items and the located system, so that the employee can know the incomplete to-do items and correspondingly process the incomplete to-do items, thereby improving the leave-job efficiency, improving the leave-job flow processing efficiency on the basis of reducing manpower, ensuring that the personnel can clear the to-do items of each system after leaving the job, and avoiding the bad flow of the dead flow.
Optionally, the RPA system captures an unprocessed to-do flow item of the employee who leaves, including: the RPA system detects whether an interface for inquiring the employee process backlog exists, and if so, the RPA system inquires the employee process backlog through the interface for inquiring the employee process backlog; and if the information does not exist, the RPA system acquires the employee process backlog by logging in the administrator page of the second system.
Specifically, the obtaining of the employee process backlogs by the RPA system through logging in the administrator page of the second system includes: and logging in a designated second system administrator page through simulating manual operation according to the RPA page operation capacity, inquiring the backlog items of related personnel, collecting the backlog event submenus after collection, and displaying the backlog event submenus in the next process link of the first system, wherein the next step is carried out after the backlog event submenus in the link are solved.
The non-intrusive connection interface is adopted in the embodiment, the cross-system docking of the second side system interface is realized through the RPA, the related backlogs of the staff are automatically collected into the backlog event hastening list, a hastening mechanism is automatically initiated, the backlog staff are urged to complete the processing of the related backlogs, and the backlog process can be carried out only after the staff complete the processing of the related backlogs.
It should be noted that, after the employee is urged to be dealt with, the RPA system determines again whether the process items to be dealt with which are not processed by the employee exist, and if not, the RPA system transfers to the next node of the leave process.
Specifically, the first system initiates a leave process, which includes: the employees of the first system initiate a job leaving process; or after the first system detects that the job leaving information exists, the first system automatically initiates a job leaving process.
In this embodiment, writing the non-processed backlog process items of the job leaving employee into the backlog event list of the job leaving process interfaces of the first system and the second system includes: the RPA system acquires modification permission of the to-be-processed event list of the job leaving process interfaces of the first system and the second system; and the RPA system writes the non-processed backlog flow items of the job leaving staff into backlog event promotion lists of the job leaving flow interfaces of the first system and the second system. And the RPA system acquires the modification permission of the to-be-handled event list of the departure process interfaces of the first system and the second system through a calling interface.
Specifically, as shown in fig. 1, the workflow of the automatic generation system for the leave-to-do matters provided by the embodiment includes:
(1) The first system employee initiates a leave process.
(2) And triggering the RPA technology from the process node to the work handover link.
(3) The RPA captures the unprocessed backlog events of the employees by (the system provides the interface for inquiring the backlog events of the employee process/if the interface condition does not exist, the RPA designates a second system administrator page by login).
(4) And the RPA writes the information of the employee backlog flow into a backlog event list of a first system backlog flow interface system.
(5) And the RPA automatically triggers the flow to promote the employees and remind the relevant system flow relevant responsible persons according to whether the backlog exists or not.
(6) And the job leaving process work handover link processing can be twisted to the next node after the backlog processing is finished.
In addition, the present application also provides an automatic generation method of backlog, which is applied to the automatic generation system of backlog in the foregoing embodiment, and the method includes:
initiating a leave process;
capturing the unprocessed to-be-handled flow items of the employees, and writing the unprocessed to-be-handled flow items of the employees into the to-be-handled event list of the departure flow interfaces of the first system and the second system;
and judging whether the flow items to be handled which are not processed by the staff leaving the office exist, if so, urging the staff leaving the office to remind the responsible person.
In addition, the present application also proposes an automatic generation apparatus for the leave-to-do event, as shown in fig. 3, the apparatus includes:
a first module 301, configured to initiate a leave process;
the second module 302 is configured to capture the unprocessed to-be-handled flow items of the employee, and write the unprocessed to-be-handled flow items of the employee into the to-be-handled event list of the leave flow interfaces of the first system and the second system;
a third module 303, configured to determine whether the leave employee does not process the to-do flow item, and if yes, prompt the leave employee to prompt a responsible person.
In addition, the present application also proposes an automatic generation apparatus for backlog, as shown in fig. 4, the apparatus includes:
at least one processor 401;
at least one memory 402, the memory 402 for storing at least one program;
at least one of the programs, when executed by at least one of the processors 401, implements an automatic generation system for out-of-job backlogs as described in the previous embodiments.
Further, the present application proposes a storage medium storing a program executable by a processor, the program executable by the processor implementing the automatic generation system of the leave-to-do-work as described in the foregoing embodiment when executed by the processor.
Similarly, the contents in the foregoing method embodiments are all applicable to this storage medium embodiment, the functions specifically implemented by this storage medium embodiment are the same as those in the foregoing method embodiments, and the beneficial effects achieved by this storage medium embodiment are also the same as those achieved by the foregoing method embodiments.
In alternative embodiments, the functions/acts noted in the block diagrams may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Furthermore, the embodiments presented and described in the flowcharts of the present application are provided by way of example in order to provide a more thorough understanding of the technology. The disclosed methods are not limited to the operations and logic flows presented herein. Alternative embodiments are contemplated in which the order of various operations is changed and in which sub-operations described as part of larger operations are performed independently.
Furthermore, although the present application is described in the context of functional modules, it should be understood that, unless otherwise stated to the contrary, one or more of the functions and/or features may be integrated in a single physical device and/or software module, or one or more functions and/or features may be implemented in separate physical devices or software modules. It will also be appreciated that a detailed discussion regarding the actual implementation of each module is not necessary for an understanding of the present application. Rather, the actual implementation of the various functional modules in the apparatus disclosed herein will be understood within the ordinary skill of an engineer given the nature, function, and interrelationships of the modules. Accordingly, those of ordinary skill in the art will be able to implement the present application as set forth in the claims without undue experimentation. It is also to be understood that the specific concepts disclosed are merely illustrative of and not intended to limit the scope of the application, which is defined by the appended claims and their full scope of equivalents.
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 computer readable storage medium. 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: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk, and various media capable of storing program codes.
The logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
In the foregoing description of the specification, reference to the description of "one embodiment/example," "another embodiment/example," or "certain embodiments/examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
While embodiments of the present application have been shown and described, it will be understood by those of ordinary skill in the art that: numerous changes, modifications, substitutions and variations can be made to the embodiments without departing from the principles and spirit of the application, the scope of which is defined by the claims and their equivalents.
The above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.
Claims (10)
1. The automatic generation system of the backlog is characterized in that the system comprises an RPA system, a first system and a second system;
the first system initiates a job leaving process, the job leaving process triggers the RPA system to operate, the RPA system captures the unprocessed to-be-handled process items of the job-leaving staff, and the unprocessed to-be-handled process items of the job-leaving staff are written into the to-be-handled event list of the job-leaving process interfaces of the first system and the second system;
and the RPA system judges whether the leave employee does not process the to-be-handled flow items or not, if so, the RPA system urges the leave employee to be handled and reminds a responsible person.
2. The system for automatically generating backlogs for departures according to claim 1, wherein the RPA system grabs backlog employee unprocessed backlog flow events, comprising:
the RPA system detects whether an interface for inquiring the employee process backlog exists, and if so, the RPA system inquires the employee process backlog through the interface for inquiring the employee process backlog;
and if the information does not exist, the RPA system acquires the employee process backlog by logging in an administrator page of the second system.
3. The system for automatically generating backlog according to claim 1, wherein after the backlog is promoted, the RPA system determines again whether there is a backlog process item that is not processed by the backlog employee, and if not, transfers to a next node of the backlog process.
4. The system for automatically generating backlog according to claim 1, wherein the first system initiates a backlog process comprising:
the staff of the first system initiates a job leaving process;
or after the first system detects that the job leaving information exists, the first system automatically initiates a job leaving process.
5. The system for automatically generating backlog of claim 1, wherein writing the backlog unprocessed backlog events for the backlog employee to a backlog event list of a backlog event interface of the first system and the second system comprises:
the RPA system acquires the modification permission of the to-be-handled event list of the departure flow interfaces of the first system and the second system;
and the RPA system writes the non-processed backlog flow items of the job leaving staff into backlog event promotion lists of the job leaving flow interfaces of the first system and the second system.
6. The system of claim 5, wherein the RPA system obtains modification rights for the list of todo events for the job departure flow interface of the first and second systems via a call interface.
7. The automatic generation method of the leave backlog, which is applied to the automatic generation system of the leave backlog according to claim 1, the method comprising:
initiating a leave process;
capturing unprocessed to-be-done flow items of the off-workers, and writing the unprocessed to-be-done flow items of the off-workers into to-be-done promotion item lists of off-work flow interfaces of the first system and the second system;
and judging whether the flow items to be handled which are not processed by the staff leaving the office exist, if so, urging the staff leaving the office to remind the responsible person.
8. An automatic generation device of leave-to-do matters, characterized in that the device comprises:
the system comprises a first module, a second module and a third module, wherein the first module is used for initiating a job leaving process;
the second module is used for capturing the unprocessed to-be-handled flow items of the employees, and writing the unprocessed to-be-handled flow items of the employees into the to-be-handled hastening item list of the first system and the second system;
and the third module is used for judging whether the leave employee does not process the to-be-handled flow items or not, if so, the leave employee is urged to be handled, and a responsible person is reminded.
9. An automatic generation device of leave-to-do matters, characterized in that the device comprises:
at least one processor;
at least one memory for storing at least one program;
the system for automatically generating backlog when at least one said program is executed by at least one said processor as recited in any one of claims 1-6.
10. A storage medium storing a program executable by a processor, the program being executed by the processor to implement the automatic generation system of the out-of-office backlog according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211323429.5A CN115775132A (en) | 2022-10-27 | 2022-10-27 | Automatic generation system, method, device and storage medium for backlog |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211323429.5A CN115775132A (en) | 2022-10-27 | 2022-10-27 | Automatic generation system, method, device and storage medium for backlog |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115775132A true CN115775132A (en) | 2023-03-10 |
Family
ID=85388577
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211323429.5A Pending CN115775132A (en) | 2022-10-27 | 2022-10-27 | Automatic generation system, method, device and storage medium for backlog |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115775132A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117273663A (en) * | 2023-11-13 | 2023-12-22 | 杭银消费金融股份有限公司 | Automatic processing method and system for worker mobilization flow |
-
2022
- 2022-10-27 CN CN202211323429.5A patent/CN115775132A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117273663A (en) * | 2023-11-13 | 2023-12-22 | 杭银消费金融股份有限公司 | Automatic processing method and system for worker mobilization flow |
| CN117273663B (en) * | 2023-11-13 | 2024-02-27 | 杭银消费金融股份有限公司 | Automatic processing method and system for worker mobilization flow |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10397161B2 (en) | Electronic mail (email) message lifecycle management | |
| CN1573691B (en) | Method and system for automatically generating, tracking and calling off a message | |
| US8489729B2 (en) | System and method for social service event processing and management | |
| CN102592195A (en) | Project control system and method based on development of products | |
| CN102722771A (en) | Method for realizing service flow monitoring | |
| MXPA03004858A (en) | System and method for automating a process of business decision and workflow. | |
| CN115775132A (en) | Automatic generation system, method, device and storage medium for backlog | |
| JP2004038516A (en) | Work processing system, operation management method and program for performing operation management | |
| CN104933495A (en) | Work task assessment system on Android-based mobile terminal | |
| CN113641483A (en) | Robot process automation system based on artificial intelligence | |
| CN111144830A (en) | Enterprise-level computing resource management method, system and computer equipment | |
| CN104052764A (en) | Meeting room resource monitoring method and meeting monitoring system | |
| CN109831323A (en) | Management method, management system and the server of server info | |
| CN113119127A (en) | Task scheduling method and system for RPA robot | |
| CN110351178A (en) | A kind of information monitoring method and device | |
| CN108171469A (en) | A kind of demand processing method, apparatus and system | |
| CN107943567A (en) | A kind of high reliability method for scheduling task and system based on AMQP agreements | |
| CN116645060A (en) | Automatic work order system operation and maintenance method and device based on SOAR and processing equipment | |
| CN107122954A (en) | A kind of file automated processing system and method, platform are the marketing method of service | |
| CN113269387A (en) | Real-time management system and management method for digital labor force | |
| KR101194379B1 (en) | Method and System for supporting execution of collaborative process among enterprises | |
| CN106980950B (en) | Material supply management method and system based on mobile social contact | |
| CN110738580A (en) | Configuration method, device and equipment for defaulting power-off and power-restoration automatic tracking work order | |
| CN109344039A (en) | A kind of host intelligent control method and device | |
| CN104616118A (en) | Business request processing method, device and system |
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 |