Tongda OA develops a program for automatically Transferring monitoring workflow timeout

Tongda OA develops a program for automatically Transferring monitoring workflow timeout (image and text)

There were countless workflows in the past, and the previous initiators were anxious, but they were helpless and had to wait. I hope there was a program to transfer the work for this guy who never handled it, how comfortable and easy it is.

In the actual process of using a workflow, it is often the case that the handler is on a business trip or cannot be handled in a timely manner due to other reasons, resulting in poor operation of the entire workflow, the Administrator is helpless with the workflows that have been transferred to someone, and there is no way to worry about instant rights. The system clearly has a place where you can set the timeout time. However, this time is only a reminder of timeout and does not help you transfer the program out for handling. If the program times out, it will be automatically transferred to the next step! Yes, this program does this. In this article, the monitoring workflow timed out and the automatic transfer program can complete this function. You no longer have to worry about the workflow.

Here, let this program provide you with an image:

Step 3 is the step for monitoring. You need to add the timeout receiving step in the next step of monitoring. After the timeout, the program is automatically transferred to Step 5, during normal handling, you cannot go to this step. The path identified by the Red Arrow is the path controlled by the program.

You can monitor and set multiple steps in the process, and process any step programs that meet the timeout conditions.

Set the timeout duration for the steps to be monitored. Set the timeout duration to 1 hour first. In the "Monitor" section below, select and save to monitor and transfer this step.

The program calculates the work time directly according to the work time. The work time is not included, and the weekend time is also removed. The implementation of this setting is the actual work time, which is more convincing.

This is a time-out transfer step, with a note above.

When the timeout process is transferred in, the program sends a message to the recipient of the timeout step through the system food reminder function. Click "details" in the message ", the workflow will be opened directly for processing.

The record in the process step is automatically completed by the program, so there is only the end time and there is no start time. In the 2013 enhanced version, the two times are basically the same.

The time data in this figure does not match the above settings. Here, we only use the demo instructions.

The monitor program that runs silently in the background is displayed at the end. The running monitoring status and history information are displayed directly when the program is running. You can set the monitoring cycle by yourself. The testing cycle can be set to 1 minute. At this time, the monitoring cycle will be stopped after the specified (initially set to 50 times. During server deployment, you can set to run once a day. Otherwise, excessive monitoring may also affect the server.

The steps for transferring in and out are marked separately in the remarks column of the database data table, so that the administrator can search and verify the data;