Task processing method and device, electronic equipment and readable storage medium
By querying the on-duty status of target personnel and sending reminder messages to those about to leave their posts, combined with the automatic transfer of unprocessed tasks to those who have already left their posts, the problem of insufficient timeliness in task processing has been solved, and timely processing and efficient management of tasks have been achieved.
Patent Information
- Application Number
- CN202410452248.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-04-15
- Publication Date
- 2025-10-21
AI Technical Summary
In existing technologies, the task processing of off-duty employees relies excessively on the familiarity of on-duty employees, which makes it difficult to guarantee the timeliness of task processing and easily leads to omissions.
By querying the on-duty status of the target object, task processing reminders are sent to the object about to leave the post, and the unprocessed tasks of the object who has left the post are automatically transferred according to the pre-set handover process to ensure timely processing of tasks.
This effectively avoids task omissions, improves the timeliness and efficiency of task processing, and ensures that all tasks are processed in a timely manner.
Smart Images
Figure CN120822720A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a task processing method, device, electronic device, and readable storage medium. Background Art
[0002] In any office setting, every employee has tasks to handle. When an employee leaves their job, tasks related to them need to be promptly processed. Currently, in related technologies, tasks related to departing employees are typically reassigned by task managers to remaining employees, who then take over the tasks.
[0003] However, this approach relies heavily on the on-the-job employee's familiarity with the off-the-job employee's corresponding work. If an on-the-job employee misses a task, it will not be processed in a timely manner, thus reducing the timeliness of task processing. Therefore, how to effectively improve the timeliness of task processing is an urgent problem that needs to be solved. Summary of the Invention
[0004] In view of this, embodiments of the present application provide a task processing method, apparatus, electronic device, and readable storage medium to improve the timeliness of task processing.
[0005] In a first aspect, a task processing method is provided, the method comprising:
[0006] Query the on-the-job status of each target object.
[0007] In response to detecting a pre-leave object in a pre-leave state, sending task processing reminder information to the pre-leave object.
[0008] In response to detecting that a resigned object is in a resigned state and that there are unprocessed pending tasks under the resigned object, the pending tasks of the resigned object are transferred according to a preset transfer process.
[0009] In some embodiments, the method further comprises:
[0010] Get the newly created task.
[0011] Query the on-the-job status of the target object corresponding to the newly created task.
[0012] In response to detecting that the target object corresponding to the newly created task is in an off-duty state, the newly created task is handed over according to a preset handover process.
[0013] In some embodiments, obtaining a new task includes:
[0014] The received new task is written into the system message queue.
[0015] The newly created task is obtained from the system message queue.
[0016] In some embodiments, querying the on-the-job status of each target object includes:
[0017] Get the list of pre-leave objects.
[0018] The list of pre-leave objects is traversed to query the pre-leave objects in each target object.
[0019] In some embodiments, querying the on-the-job status of each target object includes:
[0020] Get the list of objects that have left their jobs.
[0021] The list of resigned objects is traversed to search for the resigned objects in each target object.
[0022] In some embodiments, the off-duty state includes a new off-duty state, and the newly off-duty object in the new off-duty state is a target object whose formal off-duty duration is less than or equal to an off-duty time threshold.
[0023] In response to detecting that a departed object is in a departed state and there are unprocessed pending tasks under the departed object, transferring the pending tasks of the departed object according to a preset transfer process includes:
[0024] In response to detecting a new off-duty object in a new off-duty state, and there being unprocessed pending tasks under the new off-duty object, the pending tasks of the new off-duty object are transferred according to a preset transfer process.
[0025] In some embodiments, querying the on-the-job status of each target object includes:
[0026] Get the list of newly departed objects.
[0027] The newly resigned object list is traversed to query the newly resigned object in each target object.
[0028] In some embodiments, the pre-set handover process includes one or more of the following combinations:
[0029] Transfer the task to be transferred to the superior processing object of the corresponding target object.
[0030] Sending an assignment task to a superior processing object corresponding to a target object of the task to be transferred, so that the superior processing object assigns the task to be transferred.
[0031] The task to be transferred is sent to a task allocation queue, and the task to be transferred is transferred according to the task allocation queue.
[0032] In some embodiments, transferring the task to be transferred according to the task allocation queue includes:
[0033] Determine the task type of each task to be transferred in the task allocation queue.
[0034] According to the preset association relationship between the task type and the target object, the transfer object corresponding to each of the tasks to be transferred is determined.
[0035] The task to be transferred is transferred to the transfer object.
[0036] In some embodiments, transferring the task to be transferred according to the task allocation queue includes:
[0037] Each of the tasks to be transferred in the task allocation queue is transferred to a predetermined object.
[0038] In a second aspect, a task processing device is provided, the device comprising:
[0039] The on-the-job status query module is configured to query the on-the-job status of each target object.
[0040] The pre-leave object task processing module is configured to execute, in response to detecting a pre-leave object in a pre-leave state, sending task processing reminder information to the pre-leave object.
[0041] The task processing module for the resigned object is configured to execute a response to detecting that the resigned object is in the resigned state and there are unprocessed pending tasks under the resigned object, and transfer the pending tasks of the resigned object according to a pre-set transfer process.
[0042] In some embodiments, the apparatus further comprises:
[0043] The task acquisition module is configured to execute and acquire newly created tasks.
[0044] The newly created task query module is configured to query the on-the-job status of the target object corresponding to the newly created task.
[0045] The newly created task handover module is configured to execute, in response to detecting that the target object corresponding to the newly created task is in the off-duty state, handover the newly created task according to a preset handover process.
[0046] In some embodiments, the task acquisition module is specifically configured to perform:
[0047] The received new task is written into the system message queue.
[0048] The newly created task is obtained from the system message queue.
[0049] In some embodiments, the on-the-job status query module is specifically configured to perform:
[0050] Get the list of pre-leave objects.
[0051] The list of pre-leave objects is traversed to query the pre-leave objects in each target object.
[0052] In some embodiments, the on-the-job status query module is specifically configured to perform:
[0053] Get the list of objects that have left their jobs.
[0054] The list of resigned objects is traversed to search for the resigned objects in each target object.
[0055] In some embodiments, the off-duty state includes a new off-duty state, and the newly off-duty object in the new off-duty state is a target object whose formal off-duty duration is less than or equal to an off-duty time threshold.
[0056] The task processing module for the resigned object is specifically configured to execute:
[0057] In response to detecting a new off-duty object in a new off-duty state, and there being unprocessed pending tasks under the new off-duty object, the pending tasks of the new off-duty object are transferred according to a preset transfer process.
[0058] In some embodiments, the on-the-job status query module is specifically configured to perform:
[0059] Get the list of newly departed objects.
[0060] The newly resigned object list is traversed to query the newly resigned object in each target object.
[0061] In some embodiments, the pre-set handover process includes one or more of the following combinations:
[0062] Transfer the task to be transferred to the superior processing object of the corresponding target object.
[0063] Sending an assignment task to a superior processing object corresponding to a target object of the task to be transferred, so that the superior processing object assigns the task to be transferred.
[0064] The task to be transferred is sent to a task allocation queue, and the task to be transferred is transferred according to the task allocation queue.
[0065] In some embodiments, transferring the task to be transferred according to the task allocation queue includes:
[0066] Determine the task type of each task to be transferred in the task allocation queue.
[0067] According to the preset association relationship between the task type and the target object, the transfer object corresponding to each of the tasks to be transferred is determined.
[0068] The task to be transferred is transferred to the transfer object.
[0069] In some embodiments, transferring the task to be transferred according to the task allocation queue includes:
[0070] Each of the tasks to be transferred in the task allocation queue is transferred to a predetermined object.
[0071] In a third aspect, an embodiment of the present application provides an electronic device comprising a memory and a processor, wherein the memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method described in the first aspect.
[0072] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium storing computer program instructions, which implement the method described in the first aspect when executed by a processor.
[0073] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program / instruction, which implements the method described in the first aspect when executed by a processor.
[0074] The embodiment of the present application can determine whether there are pre-leave objects and already-leave objects by querying the on-the-job status of the target object. If a pre-leave object is detected, the embodiment of the present application can send a task processing reminder to the pre-leave object. If a already-leave object is detected and there are unprocessed pending tasks under the already-leave object, the embodiment of the present application can transfer the pending tasks of the already-leave object according to a pre-set transfer process. In this way, the embodiment of the present application can avoid the problem of pending tasks being missed, so that all tasks can be processed in a timely manner, effectively improving the timeliness of task processing, that is, improving the efficiency of task processing. BRIEF DESCRIPTION OF THE DRAWINGS
[0075] The above and other objects, features and advantages of the embodiments of the present application will become more apparent through the following description of the embodiments of the present application with reference to the accompanying drawings, in which:
[0076] Figure 1 This is a flowchart of a task processing method according to an embodiment of the present application;
[0077] Figure 2This is a flowchart of the process of querying the list of pre-leave objects in the embodiment of the present application;
[0078] Figure 3 This is a flowchart of the process of querying the list of resigned objects in an embodiment of the present application;
[0079] Figure 4 This is a flowchart of the process of querying the list of newly resigned objects in an embodiment of the present application;
[0080] Figure 5 A flowchart of the process of handing over a new task in an embodiment of the present application;
[0081] Figure 6 A flowchart of the process of obtaining a new task for the embodiment of the present application;
[0082] Figure 7 A flow chart of a handover process according to an embodiment of the present application;
[0083] Figure 8 A schematic diagram of a task processing system provided in an embodiment of the present application;
[0084] Figure 9 A flowchart of a task processing method provided in an embodiment of the present application;
[0085] Figure 10 A flowchart of a task processing method provided in an embodiment of the present application;
[0086] Figure 11 A flowchart of a task processing method provided in an embodiment of the present application;
[0087] Figure 12 This is a structural diagram of a task processing device according to an embodiment of the present application;
[0088] Figure 13 This is a schematic structural diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION
[0089] The present application is described below based on the following embodiments, but the present application is not limited to these embodiments. In the detailed description of the present application below, certain specific details are described in detail. Those skilled in the art can fully understand the present application without the description of these details. To avoid obscuring the essence of the present application, well-known methods, processes, procedures, components, and circuits are not described in detail.
[0090] Furthermore, persons of ordinary skill in the art will appreciate that the figures provided herein are for illustration purposes only and are not necessarily drawn to scale.
[0091] Unless the context clearly requires otherwise, words like "include," "comprising," and the like throughout this application should be construed as including, rather than exclusive or exhaustive; that is, as meaning "including but not limited to."
[0092] In the description of this application, it should be understood that the terms "first", "second", etc. are used for descriptive purposes only and cannot be understood as indicating or implying relative importance. In addition, in the description of this application, unless otherwise specified, "multiple" means two or more. In addition, the solutions described in this specification and the embodiments, if involving the processing of personal information, will be processed on the premise of having a legal basis (such as obtaining the consent of the subject of personal information, or being necessary for the performance of the contract, etc.), and will only be processed within the scope of the regulations or agreements. The user's refusal to process personal information other than the necessary information required for basic functions will not affect the user's use of basic functions.
[0093] In any office scenario, every employee (i.e., the person responsible for handling tasks) has tasks to handle. When an employee leaves their job, tasks related to them need to be promptly processed. Off-duty can mean an employee is unable to handle tasks for an extended period of time, such as leaving, taking a vacation, or being transferred. The aforementioned office scenario can be an enterprise, and accordingly, the employees in the office scenario can be enterprise employees.
[0094] Currently, in related technologies, tasks related to departing employees are generally reassigned by the task manager to the remaining employees, who then take over the tasks. These tasks can be approval tasks, development tasks, or any other applicable work tasks.
[0095] However, this approach relies heavily on managers or current employees being familiar with the work of off-duty employees. If a manager or current employee misses a task, it can be delayed, reducing the timeliness of task processing. Therefore, effectively improving the timeliness of task processing is an urgent issue.
[0096] In order to solve the above problems, an embodiment of the present application provides a task processing method, which can send reminders to employees who are in a pre-leave state and automatically transfer the unprocessed pending tasks of employees who have left their jobs, so that all tasks can be processed in a timely manner, thereby effectively improving the timeliness of task processing. Specifically, the task processing method of the embodiment of the present application can be applied to electronic devices, and the electronic devices can be terminal devices or servers. The terminal devices can be smart phones, tablet computers, or personal computers (PCs), etc. The server can be a single server, a server cluster configured in a distributed manner, or a cloud server.
[0097] Specifically, such as Figure 1 As shown, the task processing method of the embodiment of the present application may include the following steps:
[0098] In step S110, the on-duty status of each target object is queried.
[0099] Wherein, the target object is an employee of an enterprise or other arbitrary service unit, and the on-the-job status of the target object may include at least a pre-leave status and an already-leave status. Leaving the job may represent a state in which the service employee is unable to handle tasks for a long time due to leaving the job, taking a vacation, or transferring to another job. It is understandable that the on-the-job status of the target object may also include a still-on-the-job status. Specifically, the pre-leave status is used to represent a target object that has submitted a leave application but has not officially left the job. That is to say, the target object still needs to process pending tasks in the pre-leave status. At this time, the embodiment of the present application may set the status of the pre-leave object to the pre-leave status and store it in a system database (such as a system message queue or system database of a human resources system). The already-leave status is used to represent a target object that has officially left the job. The target object in the already-leave status does not need to process pending tasks. At this time, the embodiment of the present application may set the status of the already-leave object to the already-leave status and store it in a system database.
[0100] It should be noted that the embodiment of the present application can set a reasonable off-duty time threshold to determine whether the employee who has left his job is a newly-left employee. If the official off-duty time of the employee who has left his job is less than or equal to the off-duty time threshold, the embodiment of the present application can determine the status of the employee as a newly-left object. For example, the embodiment of the present application can set the off-duty time threshold to 1 day. If the official off-duty time of the employee who has left his job is less than or equal to 1 day, it indicates that the current moment is the first day of the off-duty of the employee who has left his job. At this time, the embodiment of the present application can determine the status of the employee as a newly-left object. It should also be noted that the off-duty time threshold of the embodiment of the present application is not limited to 1 day. It can also be 2 days or 3 days. By setting a longer off-duty time threshold, the embodiment of the present application can further adapt to situations where the employee is unable to work for a long time, such as rest days or holidays, thereby improving the flexibility of the system.
[0101] In step S120 , in response to detecting a pre-leave object in a pre-leave state, task processing reminder information is sent to the pre-leave object.
[0102] Among them, the task processing reminder information can be used to remind the pre-leave object to promptly process the pending task, thereby ensuring that the pending task is processed in a timely manner. The embodiment of the present application can traverse the status of each target object in the system. If a pre-leave object is detected in the pre-leave state, the embodiment of the present application can send a task processing reminder information to the target object (i.e., the pre-leave object) to prompt the pre-leave object to promptly process the pending task.
[0103] In an optional embodiment, the embodiment of the present application can send a task processing reminder message to the pre-office subject every predetermined period to prevent the pre-office subject from missing pending tasks. The predetermined period can be 1 day, 2 days, or 3 days, etc. The embodiment of the present application can send a task processing reminder message to the pre-office subject every predetermined period such as 1 day, 2 days, or 3 days to prevent the pre-office subject from missing a single reminder, thereby further improving the timeliness and efficiency of task processing.
[0104] In addition, if the embodiment of the present application detects that there is no corresponding pending task for the pre-leave object, the embodiment of the present application can stop sending task processing reminder information to the pre-leave object until the pre-leave object receives a new pending task.
[0105] In an optional implementation, for the process of querying whether there is a pre-leave object in the target object, such as Figure 2 As shown, the above step S110 may specifically include the following steps:
[0106] In step S111, a list of pre-leave objects is obtained.
[0107] The pre-leave object list is used to store the pre-leave status of pre-leave objects. Whenever a new pre-leave object appears, the embodiment of the present application can store the status of the pre-leave object in the pre-leave object list. Correspondingly, whenever a pre-leave object officially leaves its post, the embodiment of the present application can remove the status of the officially leaving pre-leave object from the pre-leave object list.
[0108] In step S112, the list of pre-leave objects is traversed to search for pre-leave objects in each target object.
[0109] Among them, the query results corresponding to the list of pre-leave objects may include whether a pre-leave object exists or not. The query result of whether a pre-leave object exists may further include information such as the name and number of the pre-leave object and whether there are pending tasks. The embodiment of the present application can send task processing reminder information to the pre-leave object based on this information.
[0110] In addition, the embodiment of the present application can set a reasonable query time. For example, the above query time can be 9:00 am every weekday or 10:00 am every weekday, etc. Whenever the query time is reached, the embodiment of the present application can obtain and traverse the list of pre-office objects to determine whether the target object includes the pre-office object.
[0111] In step S130 , in response to detecting that a resigned object is in a resigned state and that there are unprocessed pending tasks under the resigned object, the pending tasks of the resigned object are transferred according to a preset transfer process.
[0112] Among them, the handover process is used to hand over pending tasks (pending tasks that need to be handed over are also called pending tasks). The embodiment of the present application can pre-configure one or more handover processes, and when a departing object is detected in an off-duty state, the unprocessed pending tasks of the departing object are automatically handed over according to the pre-set handover process, which can avoid missing pending tasks and improve the timeliness of task processing.
[0113] The embodiment of the present application can determine whether there are pre-leave objects and already-leave objects by querying the on-the-job status of the target object. If a pre-leave object is detected, the embodiment of the present application can send a task processing reminder to the pre-leave object. If a already-leave object is detected and there are unprocessed pending tasks under the already-leave object, the embodiment of the present application can transfer the pending tasks of the already-leave object according to a pre-set transfer process. In this way, the embodiment of the present application can avoid the problem of pending tasks being missed, so that all tasks can be processed in a timely manner, effectively improving the timeliness of task processing, that is, improving the efficiency of task processing.
[0114] In an optional implementation, for the process of querying whether there is a resigned object in the target object, such as Figure 3 As shown, the above step S110 may specifically include the following steps:
[0115] In step S113, a list of objects that have left their posts is obtained.
[0116] The list of resigned objects is used to store the resigned status of resigned objects. Whenever a new resigned object appears, the embodiment of the present application can store the status of the resigned object in the resigned object list. Accordingly, whenever a resigned object meets certain conditions (for example, the resigned object's time away from work is greater than a preset threshold such as 1 month, 6 months, or 1 year), the embodiment of the present application can remove the resigned object that meets the conditions from the resigned object list.
[0117] In step S114, the list of resigned objects is traversed to search for resigned objects in each target object.
[0118] Among them, the query results corresponding to the list of resigned objects may include the existence of resigned objects and the non-existence of resigned objects. The query result of the existence of resigned objects may further include information such as the name and number of the resigned objects and whether there are pending tasks. The embodiment of the present application can transfer the unprocessed pending tasks of the resigned objects based on this information and the pre-set transfer process.
[0119] In addition, the embodiment of the present application can set a reasonable query time. For example, the above query time can be 9:00 am every weekday or 10:00 am every weekday, etc. Whenever the query time is reached, the embodiment of the present application can obtain and traverse the list of off-duty objects to determine whether the target object includes the off-duty object.
[0120] In an optional implementation, the off-duty status of the embodiment of the present application may include a new off-duty status, wherein the new off-duty object in the new off-duty status is a target object whose formal off-duty duration is less than or equal to the off-duty time threshold.
[0121] Furthermore, the above step S130 may be performed as follows: in response to detecting a new off-duty object in a new off-duty state and having unprocessed pending tasks under the new off-duty object, transferring the pending tasks of the new off-duty object according to a preset transfer process.
[0122] That is to say, the newly-left object is a part of the already-left object. The embodiment of the present application can set a reasonable leaving time threshold to determine whether the already-left object belongs to the newly-left object. If the formal leaving time of the already-left object is less than or equal to the leaving time threshold, the embodiment of the present application can determine the state of the target object as the newly-left state, and transfer the pending tasks of the newly-left object according to the pre-set handover process. For example, the embodiment of the present application can set the leaving time threshold to 1 day. If the formal leaving time of the already-left object is less than or equal to 1 day, it indicates that the current moment is the first day of the already-left object's leaving. At this time, the embodiment of the present application can determine the state of the target object as the newly-left state, and transfer the pending tasks of the newly-left object according to the pre-set handover process.
[0123] By determining the new off-duty object by the off-duty time threshold, the embodiment of the present application can effectively reduce the amount of information query, thereby improving the efficiency of task processing.
[0124] It should also be noted that the off-duty time threshold of the embodiment of the present application is not limited to 1 day, it can also be 2 days or 3 days, etc. By setting a longer off-duty time threshold, the embodiment of the present application can further adapt to situations where the office is unable to work for a long time such as weekends or holidays, thereby improving system flexibility.
[0125] In an optional implementation, for the process of querying whether there is a new leaving object in the target object, such as Figure 4 As shown, the above step S110 may specifically include the following steps:
[0126] In step S115, a list of new off-duty objects is obtained.
[0127] The new off-duty object list is used to store the new off-duty status of the new off-duty object. Whenever a new off-duty object appears, the embodiment of the present application can store the status of the new off-duty object in the new off-duty object list. Accordingly, whenever a new off-duty object meets certain conditions (for example, the off-duty time of the new off-duty object is greater than the above-mentioned off-duty time threshold), the embodiment of the present application can remove the new off-duty object that meets the conditions from the new off-duty object list.
[0128] It should be noted that the aforementioned list of newly-resigned objects may be a sublist of the list of already-resigned objects, a separate list, or the list of already-resigned objects itself. If the list of newly-resigned objects and the list of already-resigned objects are the same list, then when querying whether the target objects include the newly-resigned objects, embodiments of the present application may filter by the departure time threshold to determine whether the target objects include the newly-resigned objects.
[0129] In step S116, the list of newly resigned objects is traversed to search for newly resigned objects in each target object.
[0130] Among them, the query results corresponding to the list of resigned objects may include the existence of resigned objects and the non-existence of resigned objects. The query result of the existence of resigned objects may further include information such as the name and number of the resigned objects and whether there are pending tasks. The embodiment of the present application can transfer the unprocessed pending tasks of the resigned objects based on this information and the pre-set transfer process.
[0131] In addition, the embodiment of the present application can set a reasonable query time. For example, the above query time can be 9:00 am every weekday or 10:00 am every weekday, etc. Whenever the query time is reached, the embodiment of the present application can obtain and traverse the list of new off-duty objects to determine whether the target object includes the new off-duty object.
[0132] In conjunction with the process of querying whether the target object includes a pre-leave object, a left object and a new left object in the embodiment of the present application, in an optional embodiment, the embodiment of the present application can merge the pre-leave object list, the left object list and the new left object list into a merged list. Wherein, the merged list can be used to store the status of the pre-leave object, the left object and the new left object, and whenever there is a new pre-leave object, the left object or the new left object, the embodiment of the present application can store the status of the pre-leave object, the left object or the new left object to the merged list. Accordingly, whenever there is a pre-leave object, the left object or the new left object to meet the removal condition (such as the pre-leave object formally leaves the post, or the leaving time of the left object is greater than a preset threshold, or the leaving time of the new leaving object is greater than the above-mentioned leaving time threshold), the embodiment of the present application can remove the state of the target object that meets the removal condition from the merged list.
[0133] In an optional implementation, for newly received pending tasks for employees who have officially left their jobs (ie, those who have left their jobs), such as Figure 5 As shown, the embodiment of the present application may further include the following steps:
[0134] In step S210, a new task is obtained.
[0135] The newly created task can be a task created locally or a task received from outside.
[0136] In an optional embodiment, as Figure 6 As shown, for the process of acquiring a new task, step S210 may include the following steps:
[0137] In step S211, the received new task is written into the system message queue.
[0138] The system message queue may be a queue for receiving all tasks, and the system may be any applicable system such as a human resources system.
[0139] In step S212, a new task is obtained from the system message queue.
[0140] Through the system message queue, the embodiment of the present application can uniformly manage new tasks, thereby improving the efficiency of task processing.
[0141] In step S220, the on-the-job status of the target object corresponding to the newly created task is queried.
[0142] In step S230 , in response to detecting that the target object corresponding to the newly created task is off-duty, the newly created task is handed over according to a preset handover process.
[0143] Among them, the handover process can also be used to hand over newly created tasks to be processed (that is, newly created tasks in the embodiment of the present application). The embodiment of the present application can pre-configure one or more handover processes, and when it is detected that an off-duty object receives a newly created task, the newly created task is automatically handed over according to the pre-set handover process. This can not only avoid missing newly created tasks, but also improve the timeliness of task processing.
[0144] In an optional implementation, with respect to the handover process in each of the above implementations, the handover process pre-set in the embodiment of the present application may include one or more of the following combinations:
[0145] Transfer process 1: transfer the task to be transferred to the superior processing object of the corresponding target object.
[0146] Among them, the tasks to be transferred include unprocessed tasks of the objects that have left their posts (including newly left posts), as well as newly created tasks corresponding to the objects that have left their posts. The superior processing object can be the direct superior of the corresponding target object, or it can be the indirect superior of the target object. Through the transfer process 1, the embodiment of the present application can promptly and quickly hand over the tasks to be transferred to the superior processing object of the corresponding target object for processing, which can avoid missing the tasks to be transferred and improve the timeliness of task processing.
[0147] Handover process 2: sending an assignment task to the superior processing object corresponding to the target object of the task to be handed over, so that the superior processing object assigns the task to be handed over.
[0148] Through the transfer process 2, the embodiment of the present application can promptly and quickly assign the tasks to be transferred to the superior processing object of the corresponding target object, so that the appropriate on-the-job objects (i.e., on-the-job employees) can handle the tasks to be transferred in a timely manner, which can not only avoid missing the tasks to be transferred, but also improve the timeliness of task processing.
[0149] Handover process 3: Send the tasks to be handed over to the task allocation queue and hand over the tasks to be handed over according to the task allocation queue.
[0150] The task allocation queue may be a queue dedicated to receiving tasks to be transferred. After the task allocation queue receives the task to be transferred, the embodiment of the present application may transfer the task to be transferred according to a pre-configured transfer method. The pre-configured transfer method may be customized by relevant associated personnel. In other words, the embodiment of the present application may flexibly configure the transfer method of the task to be transferred through transfer process 3, thereby improving the flexibility of task processing.
[0151] In an optional embodiment, as Figure 7 As shown, the above-mentioned handover process 3 may specifically include the following steps:
[0152] In step S310 , the task type of each task to be transferred in the task allocation queue is determined.
[0153] Among them, the task type of the task to be transferred may include approval task, development task or other types. By determining the task type, the embodiment of the present application can determine the target object related to the task to be transferred, thereby quickly determining the employee who can handle the task to be transferred and improving the efficiency of task processing.
[0154] In step S320, the transfer object corresponding to each task to be transferred is determined according to the preset association relationship between the task type and the target object.
[0155] Among them, a single task type can establish a preset association relationship with one target object, or it can establish a preset association relationship with multiple target objects. When a task type corresponds to multiple target objects, the embodiment of the present application can determine the transfer object responsible for processing the task to be transferred from each target object based on the priority or ranking of each target object.
[0156] In step S330, the task to be transferred is transferred to the transferee.
[0157] The embodiment of the present application can determine the task type of each task to be transferred in the task allocation queue, and quickly assign the tasks to be transferred to the transfer object according to the preset association relationship, which can not only avoid missing tasks to be transferred, but also improve the timeliness of task processing.
[0158] In an optional implementation, the above-mentioned handover process 3 may also be performed as follows: each task to be handed over in the task allocation queue is handed over to a predetermined object.
[0159] The predetermined object may be an object responsible for uniformly processing the tasks to be transferred, or an object responsible for redistributing the tasks to be transferred, or any other suitable object.
[0160] It should be noted that, for the handover process in the embodiment of the present application, in addition to the above-mentioned handover processes 1-3, the embodiment of the present application can also set any other applicable handover process (for example, ignoring the currently unhanded tasks to be handed over).
[0161] For example, Figure 8 As shown, the embodiment of the present application can build a task processing system 81 based on the Activiti engine. The task processing system 81 may include a management background 811 and a platform application 812. The management background 811 may include a process modeling module 8111, an extension configuration module 8112, and a basic configuration module 8113. The platform application 812 may include a pre-leave object component 8121, a new leave object component 8122, and a left object component 8123. Among them, the Activiti engine is an open source workflow engine that can extract the business processes in the business system (that is, the tasks in the embodiment of the present application) and represent them as a standardized process model, and execute the corresponding business processes according to the process model.
[0162] Specifically, in the embodiment of the present application, the process modeling module 8111 can be used to design and deploy the above-mentioned process model. The extension configuration module 8112 can be used to configure various custom extended attributes of the process model. Specifically, the task processing method of the embodiment of the present application can be configured through the extension configuration module 8112. The basic configuration module 8113 can be used to configure various basic information and data. Specifically, the system message queue and task assignment queue of the embodiment of the present application can be configured through the basic configuration module 8113.
[0163] In addition, the pre-office object component 8121, the new off-duty object component 8122 and the already-office object component 8123 of the embodiment of the present application can be used to execute the task processing method to achieve the purpose of prompting the pre-office object to promptly process the pending tasks, handing over the pending tasks under the new off-duty object (or the already-official object), and handing over the newly received pending tasks of the already-official object. This can avoid the problem of tasks being missed, so that all tasks can be processed in a timely manner, effectively improving the timeliness of task processing, that is, improving the efficiency of task processing.
[0164] The following will take the human resources system as an example to illustrate the task processing method of the embodiment of the present application.
[0165] like Figure 9 As shown, for the pre-leave object, the embodiment of the present application can perform the following steps:
[0166] In step S91, the human resources system interface is called to query the list of pre-leave objects.
[0167] After obtaining the list of pre-leave objects, the embodiment of the present application may traverse the list of pre-leave objects to determine whether the list includes the pre-leave object and whether there are any pending tasks under the pre-leave object.
[0168] In step S92, it is determined whether there is a pre-leave object in the pre-leave object list. If there is a pre-leave object in the pre-leave object list, step S93 is executed, otherwise the process ends.
[0169] In step S93, it is determined whether there is any pending task for the pre-leave object. If there is any pending task for the pre-leave object, step S94 is executed, otherwise the process ends.
[0170] In step S94, task processing reminder information is sent to the pre-leave object.
[0171] Among them, the task processing reminder information can be used to remind the pre-leave object to handle the pending tasks in a timely manner, thereby ensuring that the pending tasks are handled in a timely manner.
[0172] like Figure 10 As shown, for a newly-retired object, the embodiment of the present application may perform the following steps:
[0173] In step S101, the human resources system interface is called to query the list of new off-duty objects.
[0174] After obtaining the list of new off-duty objects, the embodiment of the present application may traverse the list of new off-duty objects to determine whether the list includes the new off-duty object and whether there are any pending tasks under the new off-duty object.
[0175] In step S102, it is determined whether there is a new leaving object in the new leaving object list. If there is a new leaving object in the new leaving object list, step S103 is executed, otherwise the process ends.
[0176] In step S103, it is determined whether there is any pending task for the newly-off-duty object. If there is any pending task for the newly-off-duty object, step S104 is executed, otherwise the process ends.
[0177] In step S104, the handover process of the newly-leaving object is searched and matched.
[0178] Among them, the handover process pre-configured in the embodiment of the present application may include handover processes 1-3 and other handover processes (for example, ignoring the tasks to be handed over that are not currently handed over). Specifically, handover process 1 can hand over the task to be handed over to the superior processing object of the corresponding target object. Handover process 2 can send an assigned task to the superior processing object so that the superior processing object assigns the task to be handed over. Handover process 3 can send the task to be handed over to the task allocation queue and hand over the task to be handed over according to the task allocation queue.
[0179] like Figure 11 As shown, for the off-duty object, the embodiment of the present application can perform the following steps:
[0180] In step S111 , the received new task is written into the system message queue.
[0181] In step S112, a new task is obtained from the system message queue.
[0182] New tasks can be created locally or received from outside. The system message queue can be used as a queue to receive all tasks.
[0183] In step S113, the human resources system interface is called to query the target object corresponding to the newly created task.
[0184] In step S114, it is determined whether the target object is a resigned object. If the target object is a resigned object, step S115 is executed, otherwise the process ends.
[0185] In step S115, the handover process of the person who has left his post is searched and matched.
[0186] Among them, the handover process pre-configured in the embodiment of the present application may include handover processes 1-3 and other handover processes (for example, ignoring the tasks to be handed over that are not currently handed over). Specifically, handover process 1 can hand over the task to be handed over to the superior processing object of the corresponding target object. Handover process 2 can send an assigned task to the superior processing object so that the superior processing object assigns the task to be handed over. Handover process 3 can send the task to be handed over to the task allocation queue and hand over the task to be handed over according to the task allocation queue.
[0187] Therefore, the embodiment of the present application can avoid the problem of missed tasks, so that all tasks can be processed in a timely manner, effectively improving the timeliness of task processing, that is, improving the efficiency of task processing.
[0188] Based on the same technical concept, the embodiment of the present application also provides a task processing device, such as Figure 12 As shown, the device includes: an on-the-job status query module 121, a task processing module for pre-off-the-job objects 122, and a task processing module for already-off-the-job objects 123.
[0189] The on-the-job status query module 121 is configured to query the on-the-job status of each target object.
[0190] The pre-leave object task processing module 122 is configured to execute, in response to detecting a pre-leave object in a pre-leave state, sending task processing reminder information to the pre-leave object.
[0191] The task processing module 123 for the resigned object is configured to execute, in response to detecting that the resigned object is in the resigned state and there are unprocessed pending tasks under the resigned object, transfer the pending tasks of the resigned object according to a preset transfer process.
[0192] In some embodiments, the apparatus further comprises:
[0193] The task acquisition module is configured to execute and acquire newly created tasks.
[0194] The newly created task query module is configured to query the on-the-job status of the target object corresponding to the newly created task.
[0195] The newly created task handover module is configured to execute, in response to detecting that the target object corresponding to the newly created task is in the off-duty state, handover the newly created task according to a preset handover process.
[0196] In some embodiments, the task acquisition module is specifically configured to perform:
[0197] The received new task is written into the system message queue.
[0198] The newly created task is obtained from the system message queue.
[0199] In some embodiments, the on-duty status query module 121 is specifically configured to execute:
[0200] Get the list of pre-leave objects.
[0201] The list of pre-leave objects is traversed to query the pre-leave objects in each target object.
[0202] In some embodiments, the on-duty status query module 121 is specifically configured to execute:
[0203] Get the list of objects that have left their jobs.
[0204] The list of resigned objects is traversed to search for the resigned objects in each target object.
[0205] In some embodiments, the off-duty state includes a new off-duty state, and the newly off-duty object in the new off-duty state is a target object whose formal off-duty duration is less than or equal to an off-duty time threshold.
[0206] The task processing module 123 for the object that has left the job is specifically configured to execute:
[0207] In response to detecting a new off-duty object in a new off-duty state, and there being unprocessed pending tasks under the new off-duty object, the pending tasks of the new off-duty object are transferred according to a preset transfer process.
[0208] In some embodiments, the on-duty status query module 121 is specifically configured to execute:
[0209] Get the list of newly departed objects.
[0210] The newly resigned object list is traversed to query the newly resigned object in each target object.
[0211] In some embodiments, the pre-set handover process includes one or more of the following combinations:
[0212] Transfer the task to be transferred to the superior processing object of the corresponding target object.
[0213] Sending an assignment task to a superior processing object corresponding to a target object of the task to be transferred, so that the superior processing object assigns the task to be transferred.
[0214] The task to be transferred is sent to a task allocation queue, and the task to be transferred is transferred according to the task allocation queue.
[0215] In some embodiments, transferring the task to be transferred according to the task allocation queue includes:
[0216] Determine the task type of each task to be transferred in the task allocation queue.
[0217] According to the preset association relationship between the task type and the target object, the transfer object corresponding to each of the tasks to be transferred is determined.
[0218] The task to be transferred is transferred to the transfer object.
[0219] In some embodiments, transferring the task to be transferred according to the task allocation queue includes:
[0220] Each of the tasks to be transferred in the task allocation queue is transferred to a predetermined object.
[0221] The embodiment of the present application can determine whether there are pre-leave objects and already-leave objects by querying the on-the-job status of the target object. If a pre-leave object is detected, the embodiment of the present application can send a task processing reminder to the pre-leave object. If a already-leave object is detected and there are unprocessed pending tasks under the already-leave object, the embodiment of the present application can transfer the pending tasks of the already-leave object according to a pre-set transfer process. In this way, the embodiment of the present application can avoid the problem of pending tasks being missed, so that all tasks can be processed in a timely manner, effectively improving the timeliness of task processing, that is, improving the efficiency of task processing.
[0222] Figure 13Schematic diagram of an electronic device according to an embodiment of the present application. Figure 13 As shown, Figure 13 The electronic device shown is a general address query device, which includes a general computer hardware structure, which includes at least a processor 131 and a memory 132. The processor 131 and the memory 132 are connected via a bus 133. The memory 132 is suitable for storing instructions or programs executable by the processor 131. The processor 131 can be an independent microprocessor or a collection of one or more microprocessors. Thus, the processor 131 executes the instructions stored in the memory 132, thereby executing the method flow of the embodiment of the present application as described above to process data and control other devices. The bus 133 connects the above-mentioned multiple components together, and at the same time connects the above-mentioned components to the display controller 134 and the display device and the input / output (I / O) device 135. The input / output (I / O) device 135 can be a mouse, keyboard, modem, network interface, touch input device, somatosensory input device, printer, and other devices known in the art. Typically, the input / output device 135 is connected to the system via an input / output (I / O) controller 136.
[0223] It will be understood by those skilled in the art that the embodiments of the present application may be provided as methods, devices (equipment), or computer program products. Therefore, the present application may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present application may take the form of a computer program product implemented on one or more computer-readable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0224] The present application is described with reference to flowcharts of methods, apparatuses (devices), and computer program products according to embodiments of the present application. It should be understood that each process in the flowcharts can be implemented by computer program instructions.
[0225] These computer program instructions may be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device that implements the process Figure 1 A function specified in a process or multiple processes.
[0226] These computer program instructions can also be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce the instructions for implementing the process Figure 1 A device that specifies functions in a process or multiple processes.
[0227] Another embodiment of the present application relates to a non-volatile storage medium for storing a computer-readable program, wherein the computer-readable program is used to enable a computer to execute part or all of the above method embodiments.
[0228] That is, those skilled in the art will understand that all or part of the steps in the above-mentioned embodiments can be implemented by specifying relevant hardware through a program, which is stored in a storage medium and includes a number of instructions for causing a device (which may be a single-chip microcomputer, chip, etc.) or a processor to execute all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage medium includes: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc., various media that can store program code.
[0229] Another embodiment of the present application relates to a computer program product, including a computer program / instruction, which can implement some or all of the above method embodiments when executed by a processor.
[0230] That is, those skilled in the art can understand that the embodiments of the present application can specify relevant hardware (including the processor itself) by executing a computer program product (computer program / instructions) through a processor, thereby implementing all or part of the steps in the above-mentioned embodiment method.
[0231] The foregoing is merely a preferred embodiment of the present application and is not intended to limit the present application. Persons skilled in the art will readily appreciate that various modifications and variations are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present application are intended to be within the scope of protection of the present application.
Claims
1. A task processing method, characterized in that: The method comprises: Query the on-the-job status of each target object; In response to detecting a pre-leave object in a pre-leave state, sending task processing reminder information to the pre-leave object; In response to detecting that a resigned object is in a resigned state and that there are unprocessed pending tasks under the resigned object, the pending tasks of the resigned object are transferred according to a preset transfer process.
2. The method according to claim 1, characterized in that The method further comprises: Get the new task; Query the on-the-job status of the target object corresponding to the newly created task; In response to detecting that the target object corresponding to the newly created task is in an off-duty state, the newly created task is handed over according to a preset handover process.
3. The method according to claim 2, characterized in that The acquiring of the new task includes: Writing the received newly created task into the system message queue; The newly created task is obtained from the system message queue.
4. The method according to claim 1, wherein The query of the on-the-job status of each target object includes: Get the list of pre-leave objects; The list of pre-leave objects is traversed to query the pre-leave objects in each target object.
5. The method according to claim 1, wherein The query of the on-the-job status of each target object includes: Get the list of objects that have left their jobs; The list of resigned objects is traversed to search for the resigned objects in each target object.
6. The method according to claim 1, characterized in that The off-duty status includes a new off-duty status, and the new off-duty object in the new off-duty status is a target object whose formal off-duty time is less than or equal to the off-duty time threshold; In response to detecting that a departed object is in a departed state and there are unprocessed pending tasks under the departed object, transferring the pending tasks of the departed object according to a preset transfer process includes: In response to detecting a new off-duty object in a new off-duty state, and there being unprocessed pending tasks under the new off-duty object, the pending tasks of the new off-duty object are transferred according to a preset transfer process.
7. The method according to claim 6, characterized in that The query of the on-the-job status of each target object includes: Get the list of newly resigned objects; The newly resigned object list is traversed to query the newly resigned object in each target object.
8. The method according to any one of claims 1 to 7, characterized in that The pre-set handover process includes one or more of the following combinations: Transfer the task to be transferred to the superior processing object of the corresponding target object; Sending an assignment task to a superior processing object corresponding to a target object of the task to be transferred, so that the superior processing object assigns the task to be transferred; The task to be transferred is sent to a task allocation queue, and the task to be transferred is transferred according to the task allocation queue.
9. The method according to claim 8, characterized in that Transferring the task to be transferred according to the task allocation queue includes: Determine the task type of each task to be transferred in the task allocation queue; Determining the transfer object corresponding to each of the tasks to be transferred according to the preset association relationship between the task type and the target object; The task to be transferred is transferred to the transfer object.
10. The method according to claim 8, characterized in that Transferring the task to be transferred according to the task allocation queue includes: Each of the tasks to be transferred in the task allocation queue is transferred to a predetermined object.
11. A task processing device, characterized in that: The device comprises: The on-the-job status query module is configured to query the on-the-job status of each target object; a pre-leave object task processing module configured to execute, in response to detecting a pre-leave object in a pre-leave state, sending task processing reminder information to the pre-leave object; The task processing module for the resigned object is configured to execute a response to detecting that the resigned object is in the resigned state and there are unprocessed pending tasks under the resigned object, and transfer the pending tasks of the resigned object according to a pre-set transfer process.
12. An electronic device comprising a memory and a processor, characterized in that: The memory is configured to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method according to any one of claims 1 to 10.
13. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 10 is implemented.
14. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the method according to any one of claims 1 to 10 is implemented.