Work order reminding method, electronic equipment, storage medium and program product

Abstract

The invention provides a work order reminding method, electronic equipment, a readable storage medium and a computer program product. The work order reminding method comprises the steps of determining a current task node of an unfinished work order in response to updating of a previous task node of the unfinished work order; in response to the fact that the current task node is not an end node, generating a work order assessment task corresponding to the uncompleted work order at the current task node, and determining an assessment cut-off moment of the work order assessment task; polling the respective assessment cut-off time of each work order assessment task, and determining the work order assessment task of which the time difference between the assessment cut-off time and the polled time of the work order assessment task is within the reminding time range as a to-be-reminded task; and generating a reminding notification corresponding to the to-be-reminded task, and sending the reminding notification to the target reminding object corresponding to the to-be-reminded task.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technologies, and particularly to a work order reminder method, an electronic device, a storage medium, and a program product. Background Art

[0002] In current after-sales services, the progress of after-sales work orders is usually followed up only when customer feedback is received. There are many task nodes involved in after-sales work orders, and it is usually necessary to manually check one by one to find the current task node of the work order, and then remind the relevant person in charge of the corresponding task node. The process is very cumbersome and the efficiency is low. Summary of the Invention

[0003] The present disclosure provides a work order reminder method, an electronic device, a storage medium, and a program product.

[0004] According to one aspect of the present disclosure, there is provided a work order reminder method, including:

[0005] In response to an update of the previous task node of an unfinished work order, determining the current task node of the unfinished work order;

[0006] In response to the current task node not being an end node, generating a work order assessment task corresponding to the current task node of the unfinished work order, and determining the assessment deadline of the work order assessment task;

[0007] Polling the assessment deadlines of each of the work order assessment tasks, and determining the work order assessment tasks whose time difference between the assessment deadline and the polled time of the work order assessment task is within the reminder time range as the tasks to be reminded;

[0008] Generating a reminder notification corresponding to the task to be reminded, and sending the reminder notification to the target reminder object corresponding to the task to be reminded.

[0009] According to the work order reminder method of at least one embodiment of the present disclosure, determining the assessment deadline of the work order assessment task includes:

[0010] Obtaining the creation time of the unfinished work order and the assessment duration corresponding to the current task node;

[0011] In response to the creation time of the unfinished work order not being within the working period, determining the start time of the next day's working period as the corrected creation time of the unfinished work order;

[0012] Based on the corrected creation time and the assessment duration corresponding to the current task node, determining the assessment deadline of the work order assessment task.

[0013] The work order reminder method according to at least one embodiment of the present disclosure for determining the assessment deadline of the work order assessment task includes:

[0014] Obtain the creation time of the unfinished work order and the assessment duration corresponding to the current task node;

[0015] Based on the creation time of the unfinished work order and the assessment duration corresponding to the current task node, determine the theoretical assessment deadline of the work order assessment task;

[0016] In response to the theoretical assessment deadline of the work order assessment task not being within the working period, determine the difference between the theoretical assessment deadline and the end time of the working period as the supplementary assessment duration;

[0017] Based on the start time of the working period of the next day and the supplementary assessment duration, determine the compensated assessment deadline as the actual assessment deadline of the work order assessment task.

[0018] According to the work order reminder method of at least one embodiment of the present disclosure, the reminder time range includes a first range and a second range, and the tasks to be reminded include early reminder tasks and overdue reminder tasks; determining the work order assessment tasks whose time difference between the assessment deadline and the polled time of the work order assessment task is within the reminder time range as the tasks to be reminded includes:

[0019] In response to the assessment deadline being later than the polled time of the work order assessment task and the time difference between the assessment deadline and the polled time of the work order assessment task being within the first range, determine the work order assessment task as the early reminder task;

[0020] In response to the assessment deadline being earlier than the polled time of the work order assessment task and the time difference between the assessment deadline and the polled time of the work order assessment task being within the second range, determine the work order assessment task as the overdue reminder task.

[0021] The work order reminder method according to at least one embodiment of the present disclosure further includes:

[0022] In response to the reminder notice corresponding to the early reminder task having been generated, add the work order assessment task corresponding to the early reminder task to the invalid task library;

[0023] In response to the unfinished work order corresponding to the early reminder task not being updated at the task node where the assessment deadline is located, remove the work order assessment task corresponding to the early reminder task from the invalid task library;

[0024] Among them, the work order assessment task in the failure task library is configured to: block the polling at the assessment deadline.

[0025] According to the work order reminder method of at least one embodiment of the present disclosure, the reminder time range further includes a third range, the minimum value of the third range is greater than or equal to the maximum value of the second range, and the task to be reminded further includes a re-timeout reminder task.

[0026] According to the work order reminder method of at least one embodiment of the present disclosure, determining the work order assessment task with the time difference between the assessment deadline and the polled time of the work order assessment task within the time range as the task to be reminded further includes:

[0027] In response to the assessment deadline being earlier than the polled time of the work order assessment task, and the time difference between the assessment deadline and the polled time of the work order assessment task being within the third range, determining the work order assessment task as the re-timeout reminder task.

[0028] According to the work order reminder method of at least one embodiment of the present disclosure, it further includes:

[0029] In response to the reminder notification corresponding to the timeout reminder task being generated, adding the work order assessment task corresponding to the timeout reminder task to the failure task library;

[0030] Based on the assessment deadline and the minimum value of the third range, determining the re-timeout moment of the work order assessment task corresponding to the timeout reminder task;

[0031] In response to the unfinished work order corresponding to the timeout reminder task not being updated at the task node where the re-timeout moment is located, removing the work order assessment task corresponding to the timeout reminder task from the failure task library;

[0032] In response to the reminder notification corresponding to the re-timeout reminder task being generated, adding the work order assessment task corresponding to the re-timeout reminder task to the failure task library;

[0033] Among them, the work order assessment task in the failure task library is configured to: block the polling at the assessment deadline.

[0034] According to the work order reminder method of at least one embodiment of the present disclosure, it further includes:

[0035] In response to the update of the current task node, adding the work order assessment task to the failure task library;

[0036] Among them, the work order assessment task in the failure task library is configured to: block the polling at the assessment deadline.

[0037] The work order reminder method according to at least one embodiment of the present disclosure further includes:

[0038] In response to the active reminder request for the unfinished work order, generating an active reminder notice for the unfinished work order;

[0039] Querying the subordinate sub-work orders corresponding to the unfinished work order and increasing the cumulative value of the number of active reminder requests for the unfinished work order and each of its corresponding subordinate sub-work orders by one;

[0040] Counting the cumulative value of the number of active reminder requests for the unfinished work order and determining the active reminder weight of the unfinished work order based on the cumulative value of the number of active reminder requests;

[0041] Polling the active reminder weights of each of the unfinished work orders, and sending the active reminder notice of the unfinished work order to the target reminder objects corresponding to the unfinished work order with the highest active reminder weight and each of the subordinate sub-work orders corresponding to the unfinished work order.

[0042] The work order reminder method according to at least one embodiment of the present disclosure further includes:

[0043] In response to the active reminder weight of the unfinished work order being greater than the weight threshold, adding an urgent label to the active reminder notice of the unfinished work order.

[0044] According to another aspect of the present disclosure, there is provided an electronic device, including: a memory storing execution instructions; and a processor that executes the execution instructions stored in the memory, so that the processor executes the work order reminder method according to any one of the embodiments of the present disclosure.

[0045] According to still another aspect of the present disclosure, there is provided a readable storage medium storing execution instructions, and the execution instructions are used to implement the work order reminder method according to any one of the embodiments of the present disclosure when executed by a processor.

[0046] According to yet another aspect of the present disclosure, there is provided a computer program product including a computer program, and the computer program implements the work order reminder method according to any one of the embodiments of the present disclosure when executed by a processor. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] The drawings illustrate exemplary embodiments of the present disclosure and, together with the description thereof, are used to explain the principles of the present disclosure. These drawings are included to provide a further understanding of the present disclosure and are included in this specification and form a part of this specification.

[0048] Figure 1 It is a flowchart of the work order reminder method according to an embodiment of the present disclosure.

[0049] Figure 2 It is a schematic process diagram of a work order reminder method according to an embodiment of the present disclosure.

[0050] Figure 3 It is a schematic flowchart of a work order reminder method according to an embodiment of the present disclosure.

[0051] Figure 4 It is a schematic flowchart of a work order reminder method according to an embodiment of the present disclosure.

[0052] Figure 5 It is a schematic flowchart of a work order reminder method according to an embodiment of the present disclosure.

[0053] Figure 6 It is a schematic flowchart of a work order reminder method according to an embodiment of the present disclosure.

[0054] Figure 7 It is a schematic process diagram of a work order reminder method according to an embodiment of the present disclosure.

[0055] Figure 8 It is a schematic flowchart of a work order reminder method according to an embodiment of the present disclosure.

[0056] Figure 9 It is a schematic flowchart of a work order reminder method according to an embodiment of the present disclosure.

[0057] Figure 10 It is a schematic flowchart of a work order reminder method according to an embodiment of the present disclosure.

[0058] Figure 11 It is a schematic flowchart of a work order reminder method according to an embodiment of the present disclosure.

[0059] Figure 12 It is a schematic flowchart of a work order reminder method according to an embodiment of the present disclosure.

[0060] Figure 13 It is a schematic block diagram of the structure of a work order reminder device according to an embodiment of the present disclosure.

[0061] Figure 14 It is a schematic block diagram of the structure of an electronic device according to an embodiment of the present disclosure. Detailed implementation manners

[0062] The present disclosure will be further described in detail below with reference to the accompanying drawings and examples. It can be understood that the specific examples described herein are only for explaining the relevant content and do not limit the present disclosure. Additionally, it should be noted that for the sake of convenience of description, only parts related to the present disclosure are shown in the drawings.

[0063] It should be noted that, without conflict, the embodiments in the present disclosure and the features in the embodiments can be combined with each other. The technical solutions of the present disclosure will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0064] In the after-sales service scenario of an online platform, the online platform usually creates an after-sales work order according to the specific after-sales service content and dispatches it to the relevant person in charge for processing. Currently, usually when the customer requesting after-sales service actively urges the order, the customer service of the online platform queries the node progress of the work order being urged, and then feeds back the urging requirement to the relevant person in charge. The process is cumbersome and inefficient.

[0065] An embodiment of the present disclosure provides a work order reminder method, which can be executed by an electronic device such as a server. The work order reminder method provided by the present disclosure can be applied to an online platform built on the server, such as an online platform in the decoration field, and is mainly used to remind the work orders generated by the online platform. The work order reminder method provided by the present disclosure is not limited to reminding the work orders generated by after-sales service, but can also be used to remind the work orders generated by any other service of the online platform, such as the quotation work order before sales, etc., and no limitation is made here.

[0066] Figure 1 FIG. shows the overall flowchart of the work order reminder method M10 according to an embodiment of the present disclosure. As Figure 1 shown, the method includes steps S11 to S17. The following takes the work order reminder method M10 applied to remind the work orders generated by the after-sales service of the online platform as an example for description.

[0067] Specifically, Figure 1 the method shown includes:

[0068] S11. In response to the update of the previous task node of the unfinished work order, determine the current task node of the unfinished work order.

[0069] Among them, the task nodes involved in a work order can include a start node, an end node, and the nodes corresponding to one or more specific tasks. An unfinished work order refers to a work order that still has unfinished tasks, and it can be determined whether the work order is an unfinished work order based on whether the work order is at the end node.

[0070] For example, a maintenance work order sequentially includes a pickup node, a dispatching node, a reservation node, a home visit node, and an end node in order. When the tasks involved in the reservation node of the maintenance work order are completed, the task node of the maintenance work order will be updated to the home visit node. At this time, if there are still tasks at the home visit node of the maintenance work order that have not been completed, then this maintenance work order is called an unfinished work order. When the tasks involved in the home visit node of the maintenance work order are completed, the task node of the maintenance work order will be updated to the end node, indicating that all tasks involved in the maintenance work order have been processed. At this time, this maintenance work order is called a completed work order.

[0071] In one example, an unfinished work order has corresponding task handlers at different task nodes, who are responsible for handling the relevant tasks of that task node. In the case where the relevant tasks involved in a task node have been processed, the task handler of that task node uploads the certificate that the tasks have been processed to the online platform. The online platform determines whether the relevant tasks of that task node have been processed based on the uploaded certificate. When it is determined that the relevant tasks of that task node have been processed, the online platform updates the current task node of the unfinished work order corresponding to the certificate to the next task node, so as to advance the task progress of the unfinished work order.

[0072] S13. In response to the current task node not being the end node, generate a work order assessment task corresponding to the unfinished work order at the current task node, and determine the assessment deadline of the work order assessment task.

[0073] Among them, the work order assessment task corresponding to the task node is used to specify the specific assessment rules configured for that task node, such as parameters such as the task content, task qualification criteria, and task time limit of that task node. Among them, the task time limit represents the task completion time restricted by that task node. If the task handler completes the tasks of that task node within the task time limit, it is considered that the assessment is completed; otherwise, it is considered that the assessment is overdue. The system background of the online platform can count the completion assessment situation and assessment overdue situation of the task handling tasks to be used for evaluating the performance of that task handler.

[0074] The assessment deadline of the work order assessment task represents the latest completion time of that work order assessment task. If the work order assessment task is completed after the assessment deadline, it is considered that the assessment is overdue.

[0075] In one example, the assessment deadline of the work order assessment task can be calculated based on the creation time of the work order assessment task and the task time limit in the work order assessment task. For example, the task node of a maintenance work order is updated to the home visit node at 10:00, and a work order assessment task corresponding to the home visit node is created, denoted as the home visit maintenance task. Among them, the task time limit configured for the home visit maintenance task is 180 minutes, then the assessment deadline of the home visit maintenance task of this maintenance work order can be determined to be 13:00.

[0076] In yet another example, the task time limit in the work order assessment task is used to limit the time difference between the assessment deadline of the work order assessment task and the creation time of the work order. In this case, the assessment deadline of the work order assessment task can be calculated based on the creation time of the work order and the task time limit in the work order assessment task. For example, if the creation time of a maintenance work order is 9:00, the task time limit for the appointment node of this maintenance work order stipulates that the maintenance appointment task needs to be completed within 180 minutes after the creation of the work order, and the task time limit for the on-site node of this maintenance work order stipulates that the on-site maintenance task needs to be completed within 240 minutes after the creation of the work order, then it can be determined that the assessment deadline for the maintenance appointment task of this maintenance work order is 12:00, and the assessment deadline for the on-site maintenance task is 13:00.

[0077] S15. Poll the assessment deadlines of each work order assessment task respectively, and determine the work order assessment tasks whose time difference between the assessment deadline and the poll time of the work order assessment task is within the reminder time range as the tasks to be reminded.

[0078] In one example, the system background of the online platform maintains a work order assessment task list, and the work order assessment task list includes one or more active work order assessment tasks. The active work order assessment tasks represent the work order assessment tasks that are not completed or not reminded. When performing work order reminders, the system of the online platform scans the assessment deadlines of each work order assessment task in the work order assessment task list at a certain polling frequency, and calculates the time difference (hereinafter referred to as the deadline time difference) between the scanned assessment deadline and the current time (i.e., the time when the work order assessment task is polled / scanned). If the deadline time difference is within the preset reminder time range, then the work order assessment task corresponding to this deadline time difference is determined as the task to be reminded, indicating that the task processing task for reminding this work order assessment task needs to perform task processing in a timely manner. In this way, the work order can be automatically, timely, and accurately reminded of messages, and the specific reminder task nodes and corresponding work order assessment tasks can be traced. Furthermore, by adjusting the preset polling frequency and reminder time range, the trigger conditions and trigger timing of message reminders can be flexibly configured.

[0079] Among them, the absolute value of the deadline time difference is taken to avoid introducing negative numbers for comparison calculations.

[0080] For example, if the preset polling frequency is to scan once every 2 minutes, the system of the online platform scans each work order assessment task in the work order assessment task list every 2 minutes. Assume that the moment when the system of the online platform scans the work order assessment task list is 10:20, the preset reminder time range is [0, 20] minutes, and the work order assessment tasks in the work order assessment task list include the first task, the second task, and the third task, and their corresponding assessment deadline times are 10:10, 10:30, and 10:50 respectively. In this case, the time difference corresponding to the first task is 10 minutes, the time difference corresponding to the second task is 10 minutes, and the time difference corresponding to the third task is 30 minutes. Therefore, the first task and the second task are determined as tasks to be reminded. Further, noting that the assessment deadline time of the first task is earlier than the current moment, and the assessment deadline time of the second task is later than the current moment, when generating the reminder copy for the first task and the second task respectively, it can be generated based on the early reminder copy and the overdue reminder copy respectively, so as to give an early reminder and an overdue reminder to the first task and the second task respectively.

[0081] S17. Generate a reminder notice corresponding to the task to be reminded, and send the reminder notice to the target reminder object corresponding to the task to be reminded.

[0082] Among them, the target reminder object corresponding to the task to be reminded refers to the device or software used by the target reminder person, such as the mobile phone, computer, work app used by the target reminder person, etc. The target reminder person may include relevant personnel such as the task handler corresponding to the task to be reminded, the task responsible person (such as the superior of the task handler), etc. For example, a door-to-door repair task is determined as a task to be reminded, and the corresponding reminder notice includes an audio notice and a text notice. The audio notice is sent to the specific repair person by making a phone call or leaving a voicemail, and the text notice is sent to the work app of the superior of the repair person.

[0083] In an example, the text notice can be generated by splicing the specific target reminder object and the assessment deadline time based on the preset notice copy template of the task node where the task to be reminded is located. The audio notice can be obtained by converting the already generated text notice into audio by calling a text-to-speech model. For example, text-to-speech models such as ElevenLabs, XTTS, and Deepgram can be called to achieve this.

[0084] In summary, the embodiments of the present disclosure can obtain the due time of the work order assessment task corresponding to the task node where each unfinished work order is currently located, and poll these due times to calculate the time difference from the current time to determine whether a reminder is needed, so as to determine the tasks to be reminded and perform corresponding reminders. In this way, the reminder of the work order can be realized automatically, accurately and timely, so as to speed up the work order flow and shorten the residence time of the work order. Among them, in the scenario of work order reminder where the work order reminder method of the embodiments of the present disclosure is applied to an online platform, the system background of the online platform can record data such as previous reminder operations, work orders affected by the reminder, task nodes affected by the reminder, and target reminder objects affected by the reminder, etc., to ensure the traceability of the data related to the work order reminder. In this way, the data related to the work order reminder can also be used for the performance calculation of the work order.

[0085] Please refer to Figure 2 , Figure 2 which is a schematic diagram of the application scenario of the work order reminder method of some embodiments of the present disclosure.

[0086] In Figure 2 the illustrated application scenario is a work order reminder scenario for a maintenance work order on an online platform. The task nodes involved in the maintenance work order sequentially include a start node, a dispatching node, a response node, a door-to-door node, and an end node. When the maintenance work order is updated from the start node to the dispatching node, in response to the update of its task node, it is determined that the current task node of the maintenance work order is the dispatching node, and a work order assessment task corresponding to the dispatching node (denoted as the dispatching assessment task) is generated, and the due time of the dispatching assessment task is determined. If the dispatching assessment task is completed before the reminder is triggered, the task node of the maintenance work order will be updated to the next task node (i.e., the response node), and at the same time, the dispatching assessment task will be invalidated to avoid reminding the tasks that have been completed. If the due time difference corresponding to the dispatching assessment task is within the preset reminder time range when the due time of the dispatching assessment task is polled, the reminder operation of the dispatching assessment task will be triggered. At this time, the dispatching assessment task is determined as the task to be reminded, and then a reminder notice corresponding to the dispatching assessment task is generated, and the reminder notice is sent to the target reminder object corresponding to the dispatching assessment task, such as sent to the work app of the customer manager responsible for dispatching. The work order reminder processes of the response node and the door-to-door node are similar to that of the dispatching node, and will not be listed one by one.

[0087] Regarding step S13, in some embodiments of the present disclosure, it may include steps S131 to S133 as Figure 3 shown.

[0088] S131. Obtain the creation time of the unfinished work order and the assessment duration corresponding to the current task node.

[0089] Among them, the assessment duration is the task completion time limit set based on the rules of task nodes. Completing the task processing of a task node within the assessment duration is regarded as implicitly completing the task. Otherwise, if the task processing of a task node is not completed within the assessment duration, it is regarded as a task timeout.

[0090] In one example, different task nodes can be configured with different assessment durations. For example, the task processing of the order assignment task node is relatively simple, and its assessment duration can be configured to 30 minutes. The task processing of the on-site repair task node is relatively complex, and its assessment duration can be configured to 60 minutes.

[0091] In one example, when a work order on an online platform is created, the timestamp at the creation moment is retained and recorded as the creation timestamp. In this way, the creation moment of an unfinished work order can be determined based on its creation timestamp.

[0092] S132: In response to the creation moment of the unfinished work order not being within the working period, determine the start moment of the next day's working period as the corrected creation moment of the unfinished work order.

[0093] Among them, the working period refers to the working period of the business personnel responsible for processing work orders. For example, for an unfinished work order related to after-sales service, its working period refers to the working period of after-sales business personnel. If the creation moment of an unfinished work order is not within the working period, it may cause the business personnel who handle complex work orders to process tasks during non-working hours to complete them on time. Such an assessment method is not flexible and practical. Based on this, when determining the assessment deadline of a work order assessment task, if the creation moment of the unfinished work order corresponding to the work order assessment task is not within the working period, then determine the start moment of the next day's working period as the corrected creation moment of the unfinished work order. For example, when determining the assessment deadline of the corresponding work order assessment task based on the corrected creation moment of the unfinished work order, it can be ensured that the assessment deadline of this work order assessment task falls within the working period of the next day. Thus, the reminder of this unfinished work order can be carried out during the working period, avoiding the assessment or reminder of work orders during non-working hours and disturbing business personnel.

[0094] S133: Determine the assessment deadline of the work order assessment task based on the corrected creation moment and the assessment duration corresponding to the current task node.

[0095] In one example, after a work order is created, each task node involved in the work order except the start node and the end node can be obtained, as well as the assessment duration corresponding to each task node. Then, the assessment deadline of each task node can be calculated in sequence according to the order of the task nodes, and used as the assessment deadline of the work order assessment task at that task node. For example, the creation time of the work order is 9:00, and the task nodes involved in the work order include the first task node, the second task node, and the third task node. Among them, the assessment duration corresponding to the first task node is 30 minutes, the assessment duration corresponding to the second task node is 40 minutes, and the assessment duration corresponding to the third task node is 50 minutes. Based on this, the assessment deadline of the work order assessment task at the first task node can be determined as 9:30 based on the creation time of the work order and the assessment duration corresponding to the first task node. Then, combined with the assessment duration corresponding to the second task node, the assessment deadline of the work order assessment task at the second task node can be further determined as 10:10. Finally, combined with the assessment duration corresponding to the third task node, the assessment deadline of the work order assessment task at the third task node can be further determined as 11:00. That is to say, based on the creation time of the work order and the assessment duration corresponding to each task node, the assessment deadline of the work order assessment task at each task node can be determined. On this basis, when the creation time of the unfinished work order is not within the working period, the start time of the next day's working period is determined as the corrected creation time of the unfinished work order. Then, based on the corrected creation time and the assessment duration corresponding to each task node, the assessment deadline of the work order assessment task of the unfinished work order at each task node can be determined.

[0096] In summary, based on steps S131 to S133, when the creation time of the unfinished work order is not within the working period, the creation time of the unfinished work order can be flexibly re-determined as the start time of the next day's working period, denoted as the corrected creation time, so as to determine the assessment deadline of the work order assessment task of the unfinished work order based on the corrected creation time, enabling the assessment and reminder of the unfinished work order to be carried out during the working period.

[0097] In some embodiments of the present disclosure, it may include steps S134 to S137 as Figure 3 shown.

[0098] S134. Obtain the creation time of the unfinished work order and the assessment duration corresponding to the current task node

[0099] Step S134 can be basically the same as step S131 above and will not be elaborated here.

[0100] S135. Determine the theoretical assessment deadline of the work order assessment task based on the creation time of the unfinished work order and the assessment duration corresponding to the current task node.

[0101] In one example, based on the creation time of the unfinished work order and the assessment duration of each task node of the unfinished work order except for the start node and the end node, the theoretical assessment deadline of the work order assessment task of the unfinished work order at each task node can be determined. Among them, the assessment deadline corresponding to the first task node except for the start node can be obtained by adding the assessment duration of this task node to the creation time of the unfinished work order. The theoretical assessment deadline corresponding to each subsequent task node can be obtained by adding the assessment durations of each task node up to the current task node to the creation time of the unfinished work order. For example, the creation time of the work order is 9:00, and the task nodes involved in this work order include the first task node, the second task node, and the third task node. Among them, the assessment duration corresponding to the first task node is 30 minutes, the assessment duration corresponding to the second task node is 40 minutes, and the assessment duration corresponding to the third task node is 50 minutes. Then, the theoretical assessment deadline of the work order assessment task of the unfinished work order at the third task node is obtained by adding 30 minutes, 40 minutes, and 50 minutes respectively to 9:00, and the theoretical assessment deadline is 11:00.

[0102] S136. In response to the fact that the theoretical assessment deadline of the work order assessment task is not within the working period, determine the difference between the theoretical assessment deadline and the end time of the working period as the supplementary assessment duration.

[0103] The previously described step S132 is to handle the situation where the creation time of the unfinished work order is in a non-working period. Generally, if the creation time of the work order is the start time of the working period, then basically the assessment deadline corresponding to the last task node of this work order except for the end node can be earlier than the end time of the working period. Therefore, for the situation where the creation time of the unfinished work order is in a non-working period, by re-determining the creation time of this unfinished work order as the start time of the working period of the next day, the assessment and reminder of this unfinished work order can be carried out within the working period.

[0104] Compared with step S132, step S136 mainly deals with the situation where the theoretical assessment deadline of the work order assessment task is not within the working hours, and has nothing to do with the creation time of the unfinished work order. If the theoretical assessment deadline of the work order assessment task is not within the working hours, it is possible that the theoretical reminder time corresponding to the unfinished work order of this work order assessment task appears in the non-working hours, which may cause interference to business personnel during non-working hours, or the reminder cannot be triggered normally because the theoretical reminder time appears in the non-working hours. Based on this, step S136 determines an actual assessment deadline within the working hours on the basis of the theoretical assessment deadline by determining the supplementary assessment duration, so as to ensure that the assessment and reminder of the unfinished work order are carried out during the working hours.

[0105] Among them, the supplementary assessment duration refers to the remaining assessment duration of the current task node at the end of the working hours of the day. Since the working hours of the day have ended and the tasks of this task node cannot be continued to be processed on the same day, the remaining assessment duration of this task node on the same day can be adjusted to the next day for supplementary payment, so as to avoid the assessment deadline corresponding to the task node falling into the non-working hours on the basis of ensuring that the assessment duration of the task node remains unchanged.

[0106] S137. Determine the post-compensation assessment deadline based on the start time of the working hours of the next day and the supplementary assessment duration as the actual assessment deadline of the work order assessment task.

[0107] For example, the working hours of both the current day and the next day are from 9:00 to 18:00. The theoretical assessment deadline of a work order assessment task of an unfinished work order at a certain task node is 18:30. Then the supplementary assessment duration corresponding to this work order assessment task is 30 minutes. 30 minutes of supplementary assessment duration can be added to the start time of 9:00 of the working hours of the next day to obtain the post-compensation assessment deadline of this work order assessment task at this task node as 9:30 of the next day, so as to obtain the actual assessment deadline of this work order assessment task as 9:30 of the next day.

[0108] To sum up, based on steps S134 to S137, when the theoretical assessment deadline of the work order assessment task is not within the working hours, by determining the remaining assessment duration of the current day as the supplementary assessment duration and settling it during the working hours of the next day, the actual assessment deadline of the work order assessment task can fall within the working hours, so as to ensure that the assessment and reminder of the unfinished work order are carried out during the working hours.

[0109] Regarding step S15, in some embodiments of the present disclosure, the reminder time range includes a first range and a second range, and the tasks to be reminded include early reminder tasks and timeout reminder tasks. Among them, an early reminder task refers to a reminder whose reminder action occurs before the assessment deadline, and a timeout reminder task refers to a reminder whose reminder action occurs after the assessment deadline. The first range and the second range are time ranges for determining early reminder tasks and timeout reminder tasks, respectively. Thus, the work order reminder method of the present disclosure can be applied to reminders before and after the assessment deadline of the work order assessment task, respectively.

[0110] Specifically, regarding step S15, in some embodiments of the present disclosure, it may include steps S151 to S152 as Figure 4 shown.

[0111] S151. In response to the assessment deadline being later than the polled time of the work order assessment task, and the time difference between the assessment deadline and the polled time of the work order assessment task being within the first range, determine the work order assessment task as an early reminder task.

[0112] For example, the first range is [0, 10] minutes. Suppose the assessment deadline of a certain work order assessment task is 10:30, and the work order assessment task is polled at 10:21. Then the assessment deadline of the work order assessment task is later than the polled time of the work order assessment task. At the same time, the time difference between the assessment deadline and the polled time of the work order assessment task is 9 minutes, which is within the first range. Then the work order assessment task is determined as an early reminder task, and a corresponding reminder notice is generated based on step S17 for reminder.

[0113] S152. In response to the assessment deadline being earlier than the polled time of the work order assessment task, and the time difference between the assessment deadline and the polled time of the work order assessment task being within the second range, determine the work order assessment task as a timeout reminder task.

[0114] For example, the second range is [30, 60] minutes. Suppose the assessment deadline of a work order assessment task is 10:30, and the work order assessment task is polled at 11:01. Then, the assessment deadline of the work order assessment task is earlier than the polling time of the work order assessment task. At the same time, the time difference between the assessment deadline and the polling time of the work order assessment task is 31 minutes, which is within the second range. Then, the work order assessment task is determined to be an overdue reminder task, and a corresponding reminder notice is generated based on step S17 for reminder. In this example, the second range is set to [30, 60] minutes, so that the overdue reminder is made only after the work order assessment task is overdue for 30 minutes, and no overdue reminder is made after the work order assessment task is overdue for 60 minutes. The smaller the minimum value of the second range, the earlier the theoretical earliest reminder time after the work order assessment task is overdue. The larger the maximum value of the second range, the later the theoretical latest reminder time after the work order assessment task is overdue, which can be flexibly set according to business requirements.

[0115] Regarding step S15, in some embodiments of the present disclosure, it may further include step S153 as Figure 5 shown.

[0116] S153. In response to the assessment deadline being earlier than the polling time of the work order assessment task, and the time difference between the assessment deadline and the polling time of the work order assessment task being within the third range, determine the work order assessment task as a re-overdue reminder task.

[0117] Wherein, the minimum value of the third range is greater than or equal to the maximum value of the second range.

[0118] For example, suppose the assessment deadline of a work order assessment task is 10:30, the second range is [30, 60] minutes, and the third range is [60, 90] minutes. If the work order assessment task is polled at 11:01, then the work order assessment task is determined to be an overdue reminder task, and a corresponding reminder notice is generated based on step S17 for reminder. If the work order assessment task is polled again at 11:31, then the work order assessment task is determined to be a re-overdue reminder task, and a corresponding reminder notice is generated based on step S17 for reminder. In this way, the overdue reminder or re-overdue reminder can be performed corresponding to different overdue durations, providing a diversified overdue assessment mechanism.

[0119] In some embodiments of the present disclosure, the work order reminder method M10 may further include step S19 as Figure 6 shown.

[0120] S19. Perform invalidation processing on the work order assessment task corresponding to the reminder task to be reminded that has been reminded.

[0121] Among them, failure handling means converting the work order assessment task in the effective state to the invalid state, so that it will not be polled by the reminder mechanism to avoid repeated reminders.

[0122] Specifically, regarding step S19, in some embodiments of the present disclosure, it may include steps S191 to S192 as Figure 7 shown.

[0123] S191. In response to the reminder notice corresponding to the early reminder task being generated, add the work order assessment task corresponding to the early reminder task to the failed task library.

[0124] Among them, the work order assessment tasks in the failed task library are configured to: block the polling of the assessment deadline. That is to say, when the reminder mechanism polls the assessment deadlines of each work order assessment task, the work order assessment tasks in the failed task library will not be polled, so that the work order assessment tasks in the failed task library cannot be determined as tasks to be reminded, to avoid repeated early reminders.

[0125] S192. In response to the task node where the unfinished work order corresponding to the early reminder task is located not being updated at the assessment deadline, remove the work order assessment task corresponding to the early reminder task from the failed task library.

[0126] If the task of the unfinished work order corresponding to the early reminder task is successfully completed at the current task node, the task node of the unfinished work order will be advanced to the next task node in sequence. On the contrary, if at the assessment deadline, the task node where the unfinished work order corresponding to the early reminder task is located has not been updated yet, it indicates that the task of the unfinished work order at the current task node has not been completed yet, that is, the work order assessment task to be reminded has not been completed yet. Based on this, it may still be necessary to remind the work order assessment task that has been early reminded again in the future. Therefore, it is necessary to restore the pollable state of this work order assessment task. In this case, step S192 restores the work order assessment task corresponding to the early reminder task to the pollable state, that is, restores its effective state, so that the work order assessment task that has been early reminded and has not been processed at the assessment deadline can be reminded again.

[0127] For example, the first range is [0, 10] minutes. Suppose the assessment deadline of a work order assessment task at the task assignment node is 10:30. If the work order assessment task is polled at 10:21, then the work order assessment task is determined as an early reminder task, and a corresponding reminder notice is generated based on step S17 for reminder. When the reminder notice has been generated, the work order assessment task corresponding to the early reminder task is added to the expired task library. In this way, the work order assessment task will be reminded at 10:21, and since 10:21, the work order assessment task will not be reminded again.

[0128] If the unfinished work order corresponding to the work order assessment task is still at the task assignment node at 10:30, it indicates that the task at the task assignment node has not been processed yet. Then, the work order assessment task corresponding to the unfinished work order at the task assignment node, that is, the work order assessment task corresponding to the early reminder task that has been reminded at the task assignment node of the unfinished work order, is removed from the expired task library. In this way, when the work order assessment task is polled and meets the condition of timeout reminder, it can be given a timeout reminder. That is, since 10:30, the work order assessment task can be reminded when the polling condition is met.

[0129] Correspondingly, if the unfinished work order corresponding to the work order assessment task has been updated from the task assignment node to the next task node at 10:30, it indicates that the task of the unfinished work order at the task assignment node has been processed and there is no need to remind the work order assessment task corresponding to the task assignment node anymore. Therefore, there is no need to remove the work order assessment task corresponding to the task assignment node from the task expired library.

[0130] Regarding step S19, in some embodiments of the present disclosure, it may further include steps S193 to S196 as Figure 8 shown.

[0131] S193. In response to the generation of the reminder notice corresponding to the timeout reminder task, add the work order assessment task corresponding to the timeout reminder task to the expired task library.

[0132] Step S193 is similar to step S191 described above. The difference is that the purpose of step S193 is to make the work order assessment task that has received a timeout reminder invalid and avoid repeated reminders of the work order assessment task that has received a timeout reminder, which will not be elaborated here.

[0133] S194. Determine the re-timeout moment of the work order assessment task corresponding to the timeout reminder task based on the assessment deadline and the minimum value of the third range.

[0134] Among them, the re-timeout moment represents the earliest theoretical moment for re-timeout reminder of the work order assessment task. The re-timeout moment can be obtained by adding the minimum value of the third range to the assessment deadline of the work order assessment task. For example, assume that the assessment deadline of a certain work order assessment task is 10:30, and the third range is [60, 90] minutes, then the re-timeout moment of this work order assessment task is 11:30.

[0135] S195. In response to that the task node where the unfinished work order corresponding to the timeout reminder task is located at the re-timeout moment has not been updated, remove the work order assessment task corresponding to the timeout reminder task from the invalid task library.

[0136] Step S195 is similar to step S192 described above. The difference is that the application scenario applicable to step S195 is the situation where the work order assessment task of the unfinished work order at the current task node has not been processed and completed after the timeout reminder reaches the re-timeout moment. In step S193, to avoid repeated reminders for the timeout reminder task, the work order assessment task corresponding to the timeout reminder task has been added to the invalid task library. In the application scenario applicable to step S195, it is necessary to perform a re-timeout reminder for the work order assessment task (timeout reminder task) that has already undergone a timeout reminder. Therefore, the work order assessment task corresponding to the timeout reminder task is removed from the invalid task library to restore it to the effective state that can be polled, so that it can be determined as a re-timeout reminder task when being polled to generate a corresponding reminder notice.

[0137] S196. In response to that the reminder notice corresponding to the re-timeout reminder task has been generated, add the work order assessment task corresponding to the re-timeout reminder task to the invalid task library.

[0138] Step S196 is similar to step S193 described above. The difference is that the purpose of step S196 is to invalidate the work order assessment task that has already undergone a re-timeout reminder to avoid repeated reminders for the work order assessment task that has already undergone a re-timeout reminder, which will not be elaborated here.

[0139] As an example, assume that the assessment deadline of a certain work order assessment task at the order assignment task node is 10:30, the second range is [30, 60] minutes, and the third range is [60, 90] minutes. If this work order assessment task is polled at 11:01, then this work order assessment task is determined as a timeout reminder task, and a corresponding reminder notice is generated based on step S17 for reminder, and the work order assessment task is added to the invalid task library when its corresponding reminder notice is generated. In this way, this work order assessment task will be reminded at 11:01, and since 11:01, this work order assessment task will not be reminded again.

[0140] If, at 11:30, the task node where the unfinished work order corresponding to this work order assessment task is located has not been updated and is still at the task node of dispatching the order, then remove this work order assessment task from the invalid task library. That is, starting from 11:30, this work order assessment task can be reminded when the polling condition is met.

[0141] Suppose this work order assessment task is polled again at 11:31. Then this work order assessment task is determined as a re-timeout reminder task, and a corresponding reminder notice is generated based on step S17 for reminder, and this work order assessment task is added to the invalid task library when the corresponding reminder notice is generated. In this way, this work order assessment task will be reminded at 11:31, and starting from 11:31, this work order assessment task will not be reminded again.

[0142] In summary, the invalidation mechanism of steps S191 to S196 ensures that the work order assessment task corresponding to an unfinished work order at the same task node receives at most 1 early reminder, 1 timeout reminder, and 1 re-timeout reminder by adding the work order assessment task to the invalid task library or removing it from the invalid task library, thus avoiding repeated reminders for the same reminder content / topic.

[0143] In some embodiments of the present disclosure, the work order reminder method M10 may further include step S14 as Figure 9 shown.

[0144] S14. In response to the update of the current task node, add the work order assessment task to the invalid task library.

[0145] If the current task node of the unfinished work order is updated, it indicates that the work order assessment task of the unfinished work order at the current task node has been processed and completed. Therefore, the work order assessment task at the current task node can be converted to an invalid state to avoid reminding the processed work order assessment task. Combining the previous records, the work order assessment task can be converted to an invalid state by adding it to the invalid task library, and it can be avoided from being polled by the polling mechanism and thus being reminded.

[0146] In some embodiments of the present disclosure, the work order reminder method M10 may further include step S18 as Figure 10 shown.

[0147] S18. In response to an active reminder request for the unfinished work order, send an active reminder notice to the target reminder object corresponding to the unfinished work order.

[0148] Specifically, regarding step S18, in some embodiments of the present disclosure, it may include steps S181 to S184 as Figure 11 shown.

[0149] S181. Generate an active reminder notice for the unfinished work order in response to an active reminder request for the unfinished work order.

[0150] Among them, the active reminder request can be a reminder request actively initiated by the client of the online platform or an active reminder request initiated by the internal staff of the online platform. For example, a user of the online platform initiates a reminder request for an unfinished after-sales work order, the superior department of the online platform initiates an active reminder request for the unfinished work order of the subordinate department, a salesman at a certain task node of the online platform initiates an active reminder request for the unfinished work order of the previous task node, and so on. These are not listed one by one here.

[0151] The active reminder request can be to remind of the work order assessment task at a certain task node of the unfinished work order, or it can be to remind of the overall unfinished work order without specifying a specific task node or work order assessment task. There is no limit here.

[0152] Among them, if the active reminder request specifies to remind of the work order assessment task at a certain task node of the unfinished work order, first judge whether the work order assessment task at the specified task node has been processed and completed. If it has not been processed and completed, generate the corresponding active reminder notice and send the active reminder notice to the target reminder object corresponding to the specified work order assessment task; if it has been processed and completed, return a processing result notice, which is used to inform the party requesting the active reminder that the specified work order assessment task has been processed and completed.

[0153] If the active reminder request does not specify a specific task node or work order assessment task, it is defaulted that the active reminder request is to remind of all ongoing work order assessment tasks of the unfinished work order. Based on this, the work order assessment task at the current task node where the unfinished work order is located when responding to the active reminder request can be determined as the active reminder task, generate the active reminder notice corresponding to the active reminder task, and send the active reminder notice to the target reminder object corresponding to the active reminder task. That is to say, in the case where the active reminder request does not specify a specific task node or work order assessment task, it is defaulted to actively remind of the ongoing work order assessment tasks of the unfinished work order.

[0154] S182. Query the subordinate sub-work orders corresponding to the unfinished work order and increase the cumulative value of the active reminder request times for the unfinished work order and each of its corresponding subordinate sub-work orders by one.

[0155] Among them, the cumulative value of the active reminder request times represents the number of times the work order has been actively reminded. Increasing the cumulative value of the active reminder request times for the unfinished work order and each of its corresponding subordinate sub-work orders by one represents that the unfinished work order and each of its corresponding subordinate sub-work orders have been actively reminded once.

[0156] The purpose of step S182 is, when an active reminder is issued for an unfinished work order and the unfinished work order is a parent work order including one or more subordinate sub-work orders, to query all the subordinate sub-work orders included therein, so as to issue reminders for the unfinished work order and all its corresponding subordinate sub-work orders together.

[0157] In some application scenarios, a work order includes an associated parent work order and subordinate sub-work orders subordinate to the parent work order. Among them, the parent work order is often a work order for upper-layer services, and the subordinate sub-work orders are often work orders for specific lower-layer services. For example, the parent work order is an after-sales work order involving maintenance services. This parent work order specifically designs three different maintenance services, and corresponding subordinate sub-work orders are created for each maintenance service. Among them, the target reminder objects corresponding to the parent work order and the subordinate sub-work orders can be the same or different objects. For example, the target reminder person corresponding to the parent work order is the after-sales manager, and the target reminder object is the equipment of the after-sales manager; the target reminder persons for the three different subordinate sub-work orders of this parent work order are respectively maintenance worker A, maintenance worker B, and maintenance worker C, and the target reminder objects are the equipment of maintenance worker A, maintenance worker B, and maintenance worker C respectively.

[0158] In one example, when creating a subordinate sub-work order, a parent-level label can be configured for the subordinate sub-work order, and the parent-level label is used to determine the parent work order corresponding to the subordinate sub-work order. When a reminder is issued for an unfinished work order, query whether there is a parent-level label corresponding to the unfinished work order, and the sub-work orders corresponding to the parent-level label of the unfinished work order can be determined as the subordinate sub-work orders corresponding to the unfinished work order.

[0159] S183. Statistically accumulate the number of active reminder requests for the unfinished work order, and determine the active reminder weight of the unfinished work order based on the accumulated value of the number of active reminder requests.

[0160] Among them, the active reminder weight of the unfinished work order is used to characterize the eagerness of the active reminder for the work order. The more the accumulated value of the number of active reminder requests for the unfinished work order, the higher the active reminder weight of the unfinished work order, which means that the active reminder for this unfinished work order is more urgent and it is more necessary to give a reminder notice preferentially. In one example, the accumulated value of the number of active reminder requests can be equivalently converted into the value of the active reminder weight. In other examples, other conversion methods can be configured. For example, a weighted coefficient of the task node is obtained based on the task node where the active reminder request acts, and then the value of the active reminder weight is obtained based on the product of the weighted coefficient and the accumulated value of the number of active reminder requests.

[0161] An unfinished work order may be a work order without a parent-child relationship, or it may be a parent work order or a child work order. If the unfinished work order is a subordinate child work order of a certain parent work order, when the unfinished work order itself is actively urged, the cumulative value of its active reminder request times will increase. At the same time, when the parent work order corresponding to the completed work order is urged, the cumulative value of its active reminder request times will also increase. As a result, the active reminder weight of the unfinished work order as a subordinate child work order is often higher than that of the unfinished work order as a parent work order, which is also more in line with the application scenario of regular reminder, that is, the reminder frequency for specific lower-level business personnel is higher than that for upper-level business personnel.

[0162] S184. Poll the active reminder weights of each unfinished work order, and send the active reminder notice of the unfinished work order to the target reminder object corresponding to the unfinished work order with the highest active reminder weight and each subordinate child work order corresponding to the unfinished work order.

[0163] In one example, the online platform maintains a reminder message queue and sends the active reminder notices in the reminder message queue in sequence. Among them, multiple active reminder notices in the reminder message queue are sorted in the order of the time when they are added to the reminder message queue by default. The active reminder notice can be added to the message reminder queue when it is generated and the target reminder object is determined. When the active reminder weight of any unfinished work order is updated, the update result is synchronized to the reminder message queue. After the reminder message queue synchronizes the update result, it polls the active reminder weights of the unfinished work orders corresponding to each active reminder notice in the reminder message queue, and sorts the active reminder notices corresponding to the unfinished work orders in descending order of the active reminder weight, so that the active reminder notice corresponding to the unfinished work order with a higher active reminder weight is sorted more forward, and the active reminder notice corresponding to the unfinished work order with the highest active reminder weight is sent after sorting. In this way, the active reminder notice corresponding to the unfinished work order with a higher active reminder weight can be sent preferentially.

[0164] Among them, when the active reminder notice corresponding to an unfinished work order is sent to the target reminder object corresponding to the unfinished work order, if the unfinished work order is a parent work order, the active reminder notice is also sent to the target reminder object corresponding to each subordinate child work order of the unfinished work order to ensure the integrity of the reminder.

[0165] Regarding step S18, in some embodiments of the present disclosure, it may further include step S185 as Figure 12 shown.

[0166] S185. In response to the active reminder weight of the unfinished work order being greater than the weight threshold, add an urgent label to the active reminder notice of the unfinished work order.

[0167] Among them, the urgent tag is a visually or auditorily perceivable identifier used to enable the target reminder personnel of the overdue order to quickly perceive the urgent processing requirement of the work order. For example, in the case where the proactive overdue order notification is a text notification, the urgent tag can be in the form of special characters, symbols, patterns, etc.; in the case where the proactive overdue order notification is an audio notification, the urgent tag can be specific audio content.

[0168] The proactive overdue order weight of an unfinished work order represents the cumulative number of times it has been proactively overdue ordered. Based on this, the weight threshold can be used to measure whether the number of times an unfinished work order has been proactively overdue ordered reaches the urgent level, serving as the basis for adding an urgent tag.

[0169] Based on any of the above embodiments, the present disclosure also provides a work order reminder device. Figure 13 It is a structural schematic block diagram of a work order reminder device according to an embodiment of the present disclosure.

[0170] As Figure 13 shown, the work order reminder device includes:

[0171] A node determination module 110, configured to determine the current task node of the unfinished work order in response to an update of the previous task node of the unfinished work order.

[0172] A work order assessment task generation module 120, configured to generate a work order assessment task corresponding to the current task node of the unfinished work order and determine the assessment deadline of the work order assessment task in response to the current task node not being an end node.

[0173] A polling module 130, configured to poll the assessment deadlines of each work order assessment task, and determine the work order assessment tasks with the time difference between the assessment deadline and the polled time of the work order assessment task within the reminder time range as the tasks to be reminded.

[0174] A reminder push module 140, configured to generate a reminder notification corresponding to the task to be reminded and send the reminder notification to the target reminder object corresponding to the task to be reminded.

[0175] The above work order reminder device can be computer software, and each of its modules can be a computer software module. The implementation processes of the functions and roles of each module in the above work order reminder device are specifically described in detail in the implementation processes of the corresponding steps in the above method, and will not be elaborated here.

[0176] The execution subject of the work order reminder method in the specific implementation manner of the present disclosure can be an electronic device such as a server.

[0177] Based on any of the above embodiments, the present disclosure also provides an electronic device, which can execute the work order reminder method of any of the above embodiments described in the present disclosure.

[0178] Figure 14 It is a schematic block diagram of the structure of the electronic device 1000 according to an embodiment of the present disclosure.

[0179] The hardware structure of the electronic device 1000 can be implemented using a bus architecture. The bus architecture can include any number of interconnected buses and bridges, depending on the specific application of the hardware and the overall design constraints. The bus 1100 connects various circuits including one or more processors 1200, a memory 1300, and / or hardware modules together. The bus 1100 can also connect various other circuits 1400 such as peripheral devices, voltage regulators, power management circuits, external antennas, etc.

[0180] The bus 1100 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Component (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of representation, only one connecting line is shown in this figure, but it does not mean that there is only one bus or one type of bus.

[0181] The present disclosure also provides a readable storage medium in which a computer program is stored. When the computer program is executed by a processor, it is used to implement the above method. The "readable storage medium" can be any device that can contain, store, communicate, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. More specific examples of the readable storage medium include the following: an electrical connection part (electronic device) having one or more wirings, 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 read-only memory (CDROM), etc.

[0182] The present disclosure also provides a computer program product. The method of the present disclosure can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed, the processes or functions of the present disclosure are executed in whole or in part.

[0183] Computer programs or instructions can be stored in a readable storage medium, or transmitted from one readable storage medium to another. For example, computer programs or instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired or wireless manner. The readable storage medium can be any available medium that can be accessed, or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium can be a volatile or non-volatile storage medium, or can include both volatile and non-volatile types of storage media.

[0184] Those skilled in the art should understand that the embodiments of the present disclosure can be provided as a method, system, or computer program product. Therefore, the present disclosure can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present disclosure can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memory, CD-ROM, optical memory, etc.) that contain computer-usable program code.

[0185] The present disclosure is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to the present disclosure. It should be understood that each flow and / or block in the flowchart and / or block diagram, as well as the combination of flows and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable work order reminder devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable work order reminder devices generate a device for implementing the functions specified in Figure 1 one or more of the processes or multiple processes and / or blocks Figure 1 one or more of the blocks or multiple blocks.

[0186] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable work order reminder device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including an instruction device that implements the functions specified in Figure 1 one or more of the processes or multiple processes and / or blocks Figure 1 one or more of the blocks or multiple blocks.

[0187] These computer program instructions can also be loaded onto a computer or other programmable work order reminder device, so that a series of operation steps are performed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide for implementing in the process Figure 1 a process or multiple processes and / or blocks Figure 1 the steps of the functions specified in a block or multiple blocks.

[0188] In the description of this specification, the description with reference to terms such as "one embodiment / way", "some embodiments / ways", "example", "specific example", or "some examples" means that the specific features, structures, or characteristics described in connection with the embodiment / way or example are included in at least one embodiment / way or example of the present disclosure. In this specification, the schematic expressions of the above terms do not necessarily refer to the same embodiment / way or example. Moreover, the specific features, structures, or characteristics described can be combined in a suitable manner in any one or more embodiments / ways or examples. In addition, without contradiction, those skilled in the art can combine and combine the different embodiments / ways or examples described in this specification and the features of different embodiments / ways or examples.

[0189] In addition, the terms "first" and "second" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first" and "second" can explicitly or implicitly include at least one of the features. In the description of the present disclosure, the meaning of "a plurality" is at least two, such as two, three, etc., unless otherwise specifically defined.

[0190] Those skilled in the art should understand that the above embodiments are only for clearly explaining the present disclosure and not for limiting the scope of the present disclosure. For those skilled in the art, other changes or variations can be made based on the above disclosure, and these changes or variations are still within the scope of the present disclosure.

Claims

1. A work order reminder method, characterized in that: include: In response to an update of a previous task node of an unfinished work order, determining a current task node of the unfinished work order; In response to the current task node not being an end node, generating a work order assessment task corresponding to the unfinished work order at the current task node, and determining an assessment deadline for the work order assessment task; Polling the respective assessment deadlines of the work order assessment tasks, and determining the work order assessment tasks whose time difference between the assessment deadline and the polled time of the work order assessment tasks is within the reminder time range as tasks to be reminded; as well as Generate a reminder notification corresponding to the task to be reminded, and send the reminder notification to the target reminder object corresponding to the task to be reminded.

2. The work order reminder method according to claim 1, characterized in that: Determining the assessment deadline of the work order assessment task includes: Obtain the creation time of the unfinished work order and the assessment duration corresponding to the current task node; In response to the creation time of the unfinished work order not being within the working time period, determining the start time of the working time period of the next day as the revised creation time of the unfinished work order; and The assessment deadline of the work order assessment task is determined based on the revised creation time and the assessment duration corresponding to the current task node.

3. The work order reminder method according to claim 1, characterized in that: Determining the assessment deadline of the work order assessment task includes: Obtain the creation time of the unfinished work order and the assessment duration corresponding to the current task node; Determine the theoretical assessment deadline of the work order assessment task based on the creation time of the unfinished work order and the assessment duration corresponding to the current task node; In response to the theoretical assessment deadline of the work order assessment task not being within the working time period, determining the difference between the theoretical assessment deadline and the end time of the working time period as the reissued assessment duration; and The compensation assessment deadline is determined based on the start time of the next day's working time period and the reissued assessment time as the actual assessment deadline of the work order assessment task.

4. The work order reminder method according to claim 1, characterized in that: The reminder time range includes a first range and a second range, and the tasks to be reminded include an advance reminder task and an overtime reminder task; determining the work order assessment task whose time difference between the assessment deadline and the polling time of the work order assessment task is within the reminder time range as the task to be reminded, includes: In response to the assessment deadline being later than the polling time of the work order assessment task, and the time difference between the assessment deadline and the polling time of the work order assessment task being within the first range, determining the work order assessment task as the advance reminder task; and In response to the assessment deadline being earlier than the polling time of the work order assessment task, and the time difference between the assessment deadline and the polling time of the work order assessment task is within the second range, the work order assessment task is determined as the timeout reminder task.

5. The work order reminder method according to claim 4, characterized in that: Also includes: In response to the reminder notification corresponding to the advance reminder task being generated, adding the work order assessment task corresponding to the advance reminder task to a failed task library; In response to the unfinished work order corresponding to the advance reminder task not being updated at the task node at the assessment deadline, removing the work order assessment task corresponding to the advance reminder task from the invalid task library; and The work order assessment task in the invalid task library is configured to shield the polling of the assessment deadline.

6. The work order reminder method according to claim 4, characterized in that: The reminder time range also includes a third range, the minimum value of the third range is greater than or equal to the maximum value of the second range, and the task to be reminded also includes a timeout reminder task; the work order assessment task whose time difference between the assessment deadline and the polling time of the work order assessment task is within the time range is determined as the task to be reminded, further comprising: In response to the assessment deadline being earlier than the polling time of the work order assessment task, and the time difference between the assessment deadline and the polling time of the work order assessment task being within the third range, determining the work order assessment task as the re-timeout reminder task; Optionally, it also includes: In response to the reminder notification corresponding to the timeout reminder task being generated, adding the work order assessment task corresponding to the timeout reminder task to a failed task library; Determining a re-timeout time of the work order assessment task corresponding to the timeout reminder task based on the assessment deadline time and the minimum value of the third range; In response to the unfinished work order corresponding to the timeout reminder task not being updated at the task node at the time of the re-timeout, removing the work order assessment task corresponding to the timeout reminder task from the invalid task library; and In response to the reminder notification corresponding to the re-timeout reminder task being generated, adding the work order assessment task corresponding to the re-timeout reminder task to a failed task library; The work order assessment task in the invalid task library is configured to shield the polling of the assessment deadline.

7. The work order reminder method according to claim 1, characterized in that: Also includes: In response to the current task node being updated, adding the work order assessment task to a failed task library; Wherein, the work order assessment task in the invalid task library is configured to: shield the polling of the assessment deadline; Optionally, it also includes: In response to the active order reminder request for the unfinished work order, generating an active order reminder notification for the unfinished work order; Query the subordinate sub-work orders corresponding to the unfinished work order, and increase the cumulative value of the number of active reminder requests for the unfinished work order and its corresponding subordinate sub-work orders by one; Counting the cumulative value of the number of active order reminder requests for the unfinished work order, and determining the active order reminder weight of the unfinished work order based on the cumulative value of the number of active order reminder requests; and Polling the active order urging weight of each of the unfinished work orders, and sending an active order urging notification of the unfinished work order to the target reminder object corresponding to the unfinished work order with the highest active order urging weight and each of the subordinate sub-work orders corresponding to the unfinished work order; Optionally, it also includes: In response to the active order urging weight of the unfinished work order being greater than a weight threshold, an expedited tag is added to the active order urging notification of the unfinished work order.

8. An electronic device, characterized in that: include: A memory storing execution instructions; as well as A processor, wherein the processor executes the execution instruction stored in the memory, so that the processor executes the work order reminder method according to any one of claims 1 to 7.

9. A readable storage medium, characterized in that: The readable storage medium stores execution instructions, which are used to implement the work order reminder method according to any one of claims 1 to 7 when executed by the processor.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the work order reminder method according to any one of claims 1 to 7 is implemented.

Images