Some tasks are default, i.e. are automatically configured on the platform and cannot be registered in the scheduler. To learn about them, go to Platform ❙ Default tasks.

Required information:

Description
Description of the task scheduling.

Type
Type of task to be scheduled. Available types:

• Document expiration: used when there is a need to find out whether documents have already expired, if so, the documents will expire after a document expiration task is performed.
• Request expiration: used when there is a need to check whether the expiration date for a request has already passed. If there are tasks to expire, a notification is sent to the employees that have been configured to receive the expiration notification for that process.
• Task expiration: used when there is a need to notify users that the deadline for a workflow process activity is about to expire. If there are tasks to expire, a notification is sent to the users that have been configured to receive the expiration notification in that process.

MORE SETTINGS
Notify only on-the-job: Allows you to configure the receipt of notifications only during working hours, according to the already configured working hours.

• Delayed tasks: used when there is a need to find out whether the deadline for a workflow process activity has already expired; if there are any late tasks, a notification is sent to the users who have been configured to receive delay notifications in that process.

MORE SETTINGS
Notify only on-the-job: Allows you to configure the receipt of notifications only during working hours, according to the already configured working hours.

• Automatic flow: used to register an alternative flow in the workflow process so that, when a user does not perform a task within the deadline set, the request is automatically transferred to the alternative flow.
• Document indexation: used to index documents that have not yet been indexed.

MORE SETTINGS
Start by documents: How to start document indexation. Available options: Oldest or Newest.

• Recalculate volume: used to recalculate the physical size of the registered volumes. Attention: for a proper quota control, carrying out this task is mandatory.
• Compress finished requests: used to compress the form records linked to finished processes. After finishing the process, only the latest version of the form records are saved since the previous versions are deleted to enhance the performance of the platform.
• Convert documents (internal viewer): used to convert files from a given folder to ones in PDF format in the stipulated period so that they can be viewed internally from the internal viewer that uses the Open Office engine. If the company uses the new document viewer, this scheduling does not apply.

MORE SETTINGS
Conversion type: Type of document conversion to be performed. Available options: All or Non-converted ones only.
Start by documents: How to start document indexation. Available options: Oldest or Newest.

• Clear document temporary files: used to remove temporary files generated by TOTVS Fluig Platform in the "temp" folder of the operating system in the stipulated period. This procedure also occurs when the platform server is stopped; however, once the scheduling is configured, you can reduce the length of time to delete the files, even with the platform up and running, in order to free up disk space on the server.
• Clearing notifications: used to delete all the notifications of all users of the company - except for those that require an action by the user, such as requests to join communities, for example - according to the defined periodicity.
• Metrics monitor: used to send an alert notification to administrators when some runtime internal metric of components and routines exceeds the time set as borderline acceptable. The limit is set in milliseconds.

MORE SETTINGS
Limit: Limit runtime of the components from which an alert notification is sent.

• Dataset synchronization: used to configure the synchronization frequency for the selected dataset. The purpose of dataset synchronization is to reduce the number of accesses to data services provided by products external to the platform. For more details on synchronization, see our Dataset Synchronization technical documentation.

MORE SETTINGS
Dataset: Dataset for which the task scheduling synchronization will be created. 

• Quota calculation for zeroed folders: Used in cases when folder quota control is active, to check for folders without quota calculation and perform the calculation.
• Empty recycle bin: used to permanently delete items in the recycle bin.

MORE SETTINGS
Delete documents sent to the recycle bin for more than: Number of days in which items must remain in the recycle bin before being deleted by the scheduled task.

Run only after
Time from which the task should be performed.

Frequency
Frequency at which the task should be performed. Available options:

• Daily: in this option you can configure whether the task is performed one or more times a day, or even if they are performed with an interval of days. It is possible to configure it in four ways:

- every "X" minutes: in this option, the frequency will be according to the interval of minutes specified. Note: the minutes should be divisible by 60 (1, 2, 3, 4, 5, 6, 10, 12, 15, 20 and 30) and it is only possible to configure the time in the standard time field; the minutes cannot be configured.

- every "X" hours: in this option, the frequency will be according to the hours specified.

- every "X" days: in this option, the task will be performed according to the days specified and at the standard time entered.

- all days of the week: in this option, the task will be performed all days of the week at the standard time entered. Note: the frequency calculation is based on the standard time entered. By entering 00:00, the next valid frequency after the current time will be calculated.

• Monthly: in this option, you can configure whether the task will be performed on a specific date of the month. It is possible to configure it in two ways:

- every day "X" of each month: in this option, the task will be carried out on the specified day of each month and at the standard time entered.

- on a day of one week: in this option, the task will be carried out on a specific day of one of the weeks of the month, and at the standard time entered.

When clicking Run, the task will be performed manually at the current time and later it will be performed as usual, as configured on the scheduler.

Even if manually performed, the tasks keep following their configuration rules. For example, in the tasks “Clear all notifications” and “Clear read notifications”, the platform will run the command to clear the notifications as previously defined on the Platform ❙ Notification settings screen.