A workflow task reminder method based on reminder interval verification and dual-channel status write-back

Abstract

The present application relates to the technical field of enterprise process management and message control, and provides a process task urging method based on urging interval verification and double-channel state write-back, comprising: after receiving an urging request, querying the latest urging record according to the process instance identifier in the urging request, and judging whether to allow this urging based on the interval between the current time and the latest urging time; when the urging is allowed, obtaining the process task information according to the task identifier in the urging request, generating a process title and urging content according to the business type of the process task, and creating an urging record; respectively calling a first message channel and a second message channel to send the urging message, and writing back the sending states of the first message channel and the second message channel to the urging record respectively. The present application can reduce message noise, improve business identification efficiency, improve touch reliability and full-process traceability.

Description

Technical Field

[0001] This invention relates to the field of enterprise process management and message control technology, and in particular to a process task reminder method based on reminder interval verification and dual-channel status write-back. Background Technology

[0002] In daily business processes, approval tasks often cause bottlenecks in the workflow due to the failure of those responsible for them to process them in a timely manner. Therefore, a follow-up mechanism has become an important means of ensuring efficient workflow. An effective, controllable, and traceable follow-up system is both practically necessary and widely applicable in improving approval response speed and reducing the risk of business interruption.

[0003] Existing reminder methods typically involve users directly triggering reminder messages on the page, with the system only responsible for calling a specific message interface to send the message. This lack of effective control over repeated reminders for the same process within a short period is problematic. Due to the lack of reminder frequency control, repeated clicks by users or multiple reminders from multiple people on the same task can easily lead to multiple identical reminders being sent to the same person within a short time, creating message noise and negatively impacting user experience. Furthermore, reminder content often only includes a process instance or task number, lacking business type and document title, making it difficult for the person handling the task to quickly identify the specific business context of the pending matter, thus reducing processing efficiency. In addition, in existing solutions, the sending results of portal messages and instant messaging messages are usually recorded together, making it impossible to independently determine which channel failed, hindering problem localization and message reach analysis. Moreover, the lack of a systematic reminder record makes it difficult to trace the reminder time, the person reminding, the recipient, and the sending status of each channel, failing to provide data support for subsequent statistics and optimization.

[0004] Chinese patent CN113780968A discloses a task execution method. This method generates a reminder configuration task based on the node reminder configuration when a pending task is generated and inserts it into a local message table. The task engine then periodically scans this table to schedule the generation of timed reminder tasks, thereby asynchronously decoupling the generation of pending tasks and the execution of reminders. This solution only addresses the asynchronous scheduling and decoupling of reminder tasks. Chinese patent CN117151614A discloses a method that divides pending processes into different reminder levels based on a comparison between the process flow time and a preset timeline. It then dynamically sets the monitoring time interval and reminder instructions based on the reminder level, and cyclically corrects the reminder strategy based on feedback instructions. This solution only addresses the problem of reminder level division based on the degree of overdueness and the dynamic adjustment of monitoring frequency. Both of these methods lack an interval verification mechanism for repeated reminders within a short period of time for instances of the same process, fail to generate business-oriented reminder content including business type and document title, and do not achieve independent dual-channel sending and independent write-back and recording of their respective sending statuses.

[0005] Therefore, how to provide a process task reminder method that can control the reminder frequency at the granularity of process instances and tasks, and independently record the sending status across multiple message channels, has become an urgent technical problem to be solved. Summary of the Invention

[0006] In view of this, in order to overcome the shortcomings of the prior art, the present invention aims to provide a process task reminder method based on reminder interval verification and dual-channel status write-back.

[0007] This invention provides a method for expediting workflow tasks based on expediting interval verification and dual-channel status write-back, the method comprising:

[0008] After receiving the reminder request, query the most recent reminder record based on the process instance identifier in the reminder request, and determine whether to allow the reminder based on the interval between the current time and the most recent reminder time.

[0009] When expediting is allowed, process task information is obtained based on the task identifier in the expediting request. The business type of the process task generates a process title and expediting content, and an expediting record is created.

[0010] Send reminder messages through the first and second message channels respectively, and write back the sending status of the first and second message channels to the reminder record respectively.

[0011] Optionally, the process task reminder method of the present invention based on reminder interval verification and dual-channel status write-back determines whether to allow the current reminder in the following manner:

[0012] Based on the process instance identifier, query the most recent expedited record corresponding to the process instance in the expedited record table. If no record is found, expediting is allowed.

[0013] If found, calculate the minute difference between the current time and the most recent reminder time, and compare the minute difference with the preset reminder interval threshold.

[0014] When the minute difference is less than the preset reminder interval threshold, the remaining waiting time is generated and the reminder is blocked; otherwise, the reminder is allowed.

[0015] Optionally, the process task reminder method based on reminder interval verification and dual-channel status write-back of the present invention generates the remaining waiting time in the following manner: calculate the difference between the preset reminder interval threshold and the current minute difference, and return the difference as the remaining waiting time to the caller to prompt the caller that it is allowed to initiate a reminder request again after the remaining waiting time has elapsed.

[0016] Optionally, the process task reminder method of the present invention based on reminder interval verification and dual-channel status write-back generates process titles and reminder content and creates reminder records in the following manner:

[0017] Parse the set of reminder recipient identifiers in the reminder request, obtain process task information based on task identifiers and extract business process type identifiers, and call the business processor factory to obtain the corresponding business processor.

[0018] The business processor reads business document data to obtain the business name and business number. The process title is generated by combining the business name and business number. If the business name and business number cannot be obtained, the title passed in from the front end or the default title is used.

[0019] Read the pre-configured reminder template, and replace the reminder person name placeholder and process title placeholder in the reminder template with the actual values ​​to generate the reminder content;

[0020] Create a reminder record and write it to the reminder record table. The reminder record should include at least the process instance identifier, task identifier, reminder information, reminder recipient information, reminder content, reminder time, and dual-channel status field. The initial status of both dual-channel status fields should be set to not sent.

[0021] Optionally, in the process task reminder method of the present invention based on reminder interval verification and dual-channel status write-back, the set of reminder recipients is a set containing multiple user identifiers, and reminder messages are sent to each user in the set.

[0022] Optionally, the process task reminder method of the present invention based on reminder interval verification and dual-channel status write-back terminates the reminder if the set of reminder recipient identifiers is empty.

[0023] Optionally, in the process task reminder method based on reminder interval verification and dual-channel status write-back of the present invention, the first message channel is a portal message channel and the second message channel is an instant messaging message channel. The two channels are configured with independent channel switches. The unactivated channel does not perform a sending operation and keeps its corresponding status field in the unsent state. The failure of sending in one channel does not affect the sending execution of the other channel.

[0024] Optionally, the process task reminder method based on reminder interval verification and dual-channel status write-back of the present invention sends reminder messages by calling the first message channel and the second message channel respectively in the following manner: read the first message channel switch and the second message channel switch configured by the system; for the channel that is turned on, call the corresponding channel interface to send reminder messages according to each reminder recipient in the reminder recipient identifier set, and count the number of successes and failures of each channel.

[0025] Optionally, the process task reminder method based on reminder interval verification and dual-channel status write-back of the present invention writes back the sending status of the first message channel and the second message channel to the reminder record in the following manner: the sending result status of the first message channel is independently written into the first channel status field of the reminder record, and the sending result status of the second message channel is independently written into the second channel status field of the reminder record, wherein the two status fields are independent of each other and do not overwrite each other.

[0026] Optionally, the process task reminder method of the present invention based on reminder interval verification and dual-channel status write-back includes three states for the sending result: success, failure, or not sent. The state of not sent corresponds to the corresponding channel switch being closed or no sending operation being performed.

[0027] The workflow task reminder method based on reminder interval verification and dual-channel status write-back of the present invention has the following beneficial technical effects:

[0028] By implementing a process instance-level reminder interval verification mechanism, repeated reminders and message noise within a short period of time are effectively avoided. The dynamic generation of process titles containing business type and document title by the business processor significantly improves the identification efficiency of the handler and the approval response speed. The dual-channel independent sending and status independent write-back mechanism improves the message delivery probability and enables channel-level failure location. At the same time, the structured reminder record table completely saves the reminder person, the reminder recipient, the reminder content, the reminder time, and the dual-channel sending status, thereby optimizing reminder frequency control, message content availability, delivery reliability, and full-process traceability. Attached Figure Description

[0029] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0030] Figure 1 This is a flowchart illustrating a process task reminder method based on reminder interval verification and dual-channel status write-back according to an exemplary embodiment of the present invention.

[0031] Figure 2 This is a schematic diagram illustrating the process of determining whether to allow a current reminder in a process task reminder method based on reminder interval verification and dual-channel status write-back according to an exemplary embodiment of the present invention.

[0032] Figure 3 A flowchart illustrating the process of generating process titles and reminder content and creating reminder records according to the process task reminder method based on reminder interval verification and dual-channel status write-back according to an exemplary embodiment of the present invention.

[0033] Figure 4 This is a flowchart illustrating the process of sending reminder messages according to an exemplary embodiment of the present invention, which is a process task reminder method based on reminder interval verification and dual-channel status write-back. Detailed Implementation

[0034] The embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0035] It should be noted that, in the absence of conflict, the following embodiments and features can be combined with each other; and, based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0036] It should be noted that various aspects of embodiments within the scope of the appended claims are described below. It will be apparent that the aspects described herein can be embodied in a wide variety of forms, and any particular structure and / or function described herein is merely illustrative. Based on this disclosure, those skilled in the art will understand that one aspect described herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement the device and / or practice the method. Additionally, this device and / or method can be implemented using structures and / or functionalities other than one or more of the aspects set forth herein.

[0037] An exemplary embodiment of the present invention provides a process task reminder method based on reminder interval verification and dual-channel status write-back. Figure 1 This is a flowchart illustrating a process task reminder method based on reminder interval verification and dual-channel status write-back according to an exemplary embodiment of the present invention, as shown below. Figure 1 As shown, in this embodiment, the method of the present invention is implemented in the following manner:

[0038] First, after receiving the reminder request, the system queries the most recent reminder record based on the process instance identifier in the reminder request, and determines whether to allow the reminder based on the interval between the current time and the most recent reminder time.

[0039] Figure 2 This is a schematic diagram illustrating the process of determining whether to allow a current reminder based on reminder interval verification and dual-channel status write-back according to an exemplary embodiment of the present invention. Figure 2 As shown, in this embodiment, the decision on whether to allow the current follow-up is made in the following manner:

[0040] The system queries the reminder record table based on the process instance identifier to find the most recent reminder record corresponding to that process instance. If no record is found, the reminder is allowed. If a record is found, the difference in minutes between the current time and the most recent reminder time is calculated and compared with a preset reminder interval threshold. If the difference in minutes is less than the preset reminder interval threshold, a remaining waiting time is generated and the reminder is blocked; otherwise, the reminder is allowed. This embodiment controls the reminder frequency for the same process instance by querying the most recent reminder record based on the process instance identifier and comparing the minute difference with a preset reminder interval threshold. This effectively avoids message noise caused by repeated reminders within a short period. Simultaneously, generating a remaining waiting time when the reminder is blocked provides the caller with a clear indication of when to request a follow-up reminder, improving the controllability of the reminder mechanism and the user experience.

[0041] It should be noted that in this embodiment, the remaining waiting time is generated as follows: the difference between the preset reminder interval threshold and the current minute difference is calculated, and this difference is returned to the caller as the remaining waiting time. This serves as a reminder to the caller that the reminder request can be initiated again after the remaining waiting time has elapsed. This ensures that blocked reminder requests receive clear feedback on the waiting time, allowing the front-end page or the caller to reasonably schedule the timing of initiating reminders again, reducing invalid duplicate requests, and minimizing the waste of system resources.

[0042] Then, when expediting is allowed, the process task information is obtained based on the task identifier in the expediting request. The process task's business type generates the process title and expediting content, and an expediting record is created.

[0043] In the project implementation, the `checkCanRemind` method of the process reminder service queries the most recent reminder record and reads the `intervalMinutes` configuration item; if the configuration is empty, the default interval value is used. Reminder records are queried using the process instance identifier index, enabling a quick determination of whether reminders are allowed.

[0044] Figure 3 A schematic diagram illustrating the process of generating process titles and reminder content and creating reminder records according to the process task reminder method based on reminder interval verification and dual-channel status write-back according to an exemplary embodiment of the present invention is shown below. Figure 3 As shown, in this embodiment, the process title and reminder content are generated and reminder records are created in the following manner:

[0045] The process parses the set of recipient identifiers in the reminder request, obtains the process task information based on the task identifier, extracts the business process type identifier, and calls the business processor factory to obtain the corresponding business processor. It then reads business document data through the business processor to obtain the business name and business number, prioritizing the combination of business name and business number to generate the process title. If the business name and business number cannot be obtained, it uses the title passed in from the front end or a default title. It reads the pre-configured reminder template, replacing the reminder recipient name placeholder and process title placeholder in the template with actual values ​​to generate the reminder content. Finally, it creates a reminder record and writes it to the reminder record table. The reminder record must at least include the process instance identifier, task identifier, reminder recipient information, recipient information, reminder content, reminder time, and a dual-channel status field. The initial status of both dual-channel status fields is set to "not sent".

[0046] This embodiment retrieves the corresponding business processor by calling the business processor factory and generates a process title based on the business name and business number. This allows the reminder content to carry specific business context, enabling the handler to quickly identify the business type and document information of the pending item without additional queries, significantly improving the usability of reminder messages and approval efficiency. Simultaneously, by creating reminder records with dual-channel status fields and setting the initial status to "not sent," it lays the foundation for independent write-back of subsequent channel statuses and full-process traceability of reminder actions. In this embodiment, the business processor factory dynamically retrieves the corresponding business processor based on the business type of the process task, thereby achieving differentiated processing for different business processes (such as contract approval, procurement approval, invoicing approval, etc.).

[0047] In this embodiment, the set of reminder recipient identifiers is a collection containing multiple user identifiers. Reminder messages are sent to each user in the set individually, enabling batch reminder processing for scenarios with multiple recipients. This eliminates the need for multiple reminder requests from the front-end or the calling party, simplifying the interface call logic and improving reminder processing efficiency. In practical applications, if the set of reminder recipient identifiers is empty, the reminder process is terminated, avoiding unnecessary subsequent queries, content generation, and message sending operations due to invalid requests, thus saving system processing resources.

[0048] In the engineering implementation, the process expediting service reads task information through task identifiers, calls WorkflowHandlerFactory to obtain the corresponding business processor, and then generates process titles through message data, such as contract registration, contract borrowing, or other business process titles.

[0049] Finally, the first and second message channels are invoked to send reminder messages, and the sending status of the first and second message channels is written back to the reminder record.

[0050] In this embodiment, the first message channel is a portal message channel, and the second message channel is an instant messaging message channel. Each channel is configured with an independent channel switch. A channel that is not activated does not perform a sending operation and maintains its corresponding status field as "not sent." The failure of one channel to send data does not affect the sending execution of the other channel. This embodiment achieves flexible channel-level control, allowing the system to selectively activate or deactivate a channel according to actual business needs. The failure of one channel to send data does not affect the sending execution of the other channel, improving the overall success rate of message delivery. Simultaneously, the unactivated channel maintains its status field as "not sent," avoiding confusion in status records.

[0051] Figure 4 This is a flowchart illustrating the process of sending reminder messages according to an exemplary embodiment of the present invention, which describes a process task reminder method based on reminder interval verification and dual-channel status write-back. Figure 4 As shown, in this embodiment, the first message channel and the second message channel are called to send reminder messages in the following manner: the first message channel switch and the second message channel switch configured by the system are read. For the channel that is turned on, the corresponding channel interface is called to send reminder messages for each person in the reminder person identifier set. The number of successes and failures of each channel are counted. The overall sending status of the corresponding channel is determined based on the statistical results of the number of successes and failures.

[0052] As an optional example, this embodiment writes the sending status of the first and second message channels back to the reminder record in the following manner: the sending result status of the first message channel is independently written to the first channel status field of the reminder record, and the sending result status of the second message channel is independently written to the second channel status field of the reminder record. The two status fields are independent of each other and do not overwrite each other. This embodiment achieves refined recording of the sending status of the two channels, enabling the reminder record to fully reflect the sending results of each channel, which facilitates subsequent channel-level failure cause analysis and message delivery troubleshooting.

[0053] In practical applications, the transmission result status includes three states: success, failure, or no transmission. The no transmission status corresponds to the corresponding channel switch being closed or no transmission operation being performed.

[0054] The method in this embodiment is applicable to task expediting scenarios in enterprise process management systems, such as contract approval, procurement approval, invoicing approval, or payment approval processes.

[0055] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods of various embodiments or some parts of embodiments.

[0056] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A workflow task reminder method based on reminder interval verification and dual-channel status write-back, characterized in that, The method includes: After receiving the reminder request, query the most recent reminder record based on the process instance identifier in the reminder request, and determine whether to allow the reminder based on the interval between the current time and the most recent reminder time. When expediting is allowed, process task information is obtained based on the task identifier in the expediting request. The business type of the process task generates a process title and expediting content, and an expediting record is created. Send reminder messages through the first and second message channels respectively, and write back the sending status of the first and second message channels to the reminder record respectively.

2. The workflow task reminder method based on reminder interval verification and dual-channel status write-back according to claim 1, characterized in that, Determine whether to grant this follow-up request using the following methods: Based on the process instance identifier, query the most recent expedited record corresponding to the process instance in the expedited record table. If no record is found, expediting is allowed. If found, calculate the minute difference between the current time and the most recent reminder time, and compare the minute difference with the preset reminder interval threshold. When the minute difference is less than the preset reminder interval threshold, the remaining waiting time is generated and the reminder is blocked; otherwise, the reminder is allowed.

3. The workflow task reminder method based on reminder interval verification and dual-channel status write-back according to claim 2, characterized in that, The remaining waiting time is generated as follows: the difference between the preset reminder interval threshold and the current minute is calculated, and this difference is returned to the caller as the remaining waiting time, which is used to prompt the caller that it is allowed to initiate a reminder request again after the remaining waiting time has elapsed.

4. The process task reminder method based on reminder interval verification and dual-channel status write-back according to claim 1, characterized in that, Generate process titles and reminder details, and create reminder records as follows: Parse the set of reminder recipient identifiers in the reminder request, obtain process task information based on task identifiers and extract business process type identifiers, and call the business processor factory to obtain the corresponding business processor. The business processor reads business document data to obtain the business name and business number. The process title is generated by combining the business name and business number. If the business name and business number cannot be obtained, the title passed in from the front end or the default title is used. Read the pre-configured reminder template, and replace the reminder person name placeholder and process title placeholder in the reminder template with the actual values ​​to generate the reminder content; Create a reminder record and write it to the reminder record table. The reminder record should include at least the process instance identifier, task identifier, reminder information, reminder recipient information, reminder content, reminder time, and dual-channel status field. The initial status of both dual-channel status fields should be set to not sent.

5. The workflow task reminder method based on reminder interval verification and dual-channel status write-back according to claim 4, characterized in that, The set of reminder recipient identifiers is a set containing multiple user identifiers, and reminder messages are sent to each user in the set.

6. The workflow task reminder method based on reminder interval verification and dual-channel status write-back according to claim 4, characterized in that, If the set of reminder recipients is empty, the reminder process will be terminated.

7. The workflow task reminder method based on reminder interval verification and dual-channel status write-back according to claim 1, characterized in that, The first message channel is the portal message channel, and the second message channel is the instant messaging message channel. The two channels are configured with independent channel switches. The unactivated channel will not perform a sending operation and will keep its corresponding status field in the "not sent" state. The failure of sending on one channel will not affect the sending execution on the other channel.

8. The workflow task reminder method based on reminder interval verification and dual-channel status write-back according to claim 1, characterized in that, The first and second message channels are invoked to send reminder messages in the following manner: Read the first and second message channel switches configured in the system. For channels that are enabled, the corresponding channel interface is invoked to send reminder messages for each person in the reminder recipient identifier set, and the number of successes and failures for each channel is counted.

9. The workflow task reminder method based on reminder interval verification and dual-channel status write-back according to claim 1, characterized in that, Write back the sending status of the first message channel and the second message channel to the reminder record in the following manner: Write the sending result status of the first message channel independently to the first channel status field of the reminder record, and write the sending result status of the second message channel independently to the second channel status field of the reminder record. The two status fields are independent of each other and do not overwrite each other.

10. The workflow task reminder method based on reminder interval verification and dual-channel status write-back according to claim 9, characterized in that, The transmission result status includes three states: success, failure, or no transmission. The no transmission status corresponds to the corresponding channel switch being closed or no transmission operation being performed.

Images