Recurring Task Management

• Recurring task code (field CODABT)

It identifies the recurring task code.

• Title (field NOMABT)

Title associated to the previous code.

• Folder (field DOSSIER)

It defines the name of the folder in which the request will be launched (the current folder code is proposed by default).

• User code (field USER)

It defines the code of the user under whose identity the task will be launched (the code of the current user is proposed by default).

• Password (field PASSE)

When the folder or task to be executed is not the current one, or if the user does not correspond to the current user code, it is necessary to enter the corresponding password in order to identify oneself.

• Group (field GRP)

It defines a group of tasks to be launched.

• Task code (field TACHE)

It defines the code of the task that will be launched automatically by the batch server.

• Active (field ENAFLG)

This check box is used to activate or deactivate the current record without losing its content.

A deactivated record cannot be used (by calling its code) in other records (documents, setups, etc.) or during mass processings.

The authorizations for a given function can prohibit the creation of an active record. In this case, the box is cleared by default and it can only be modified by an authorized user or via a signature circuit defined by Workflow.

• Last execution (field DJOUR)

When the recurring task has already generated task executions, this field makes it possible to know the last execution date.

• Periodicity (field PERIO)

This field defines the task execution frequency.

If the period is monthly, it is possible to indicate one day of the month (date in the month ranging between 1 and 31) and/or check the end of month box. If the period is weekly, it is necessary to check one or more days of the week.

• Excluded days (field CAL)

This calendar code makes it possible to exclude some days for the execution of the recurring tasks.

• field JOUR

The days of the week selected for the execution of a weekly task are mentioned here.

• Days of the month (field QUANT)

It is possible to specify, in the case of a monthly recurring task, from one to five days (plus possibly the end of the month via the corresponding box) in order to define the days of the month when the request will be launched.

• Month end (field FDM)

In case of monthly recurring tasks, this box is used to release the execution of the task on the last day of each month (if such a date has not been excluded by the calendar code).

• Start time (field HDEB)

It is used to limit the execution of a frequency defined task between two hours.

• End time (field HFIN)

• Frequency (min) (field FRQ)

When a task must be executed in a repetitive way, a start and end time are defined, along with an execution frequency expressed in minutes. This frequency enables the task to be relaunched automatically.

• One single query (field ONE)

This box can be checked if the recurring task is frequency defined.

If it is checked, a single request is launched every day in order to execute the requested process, and as soon as the process is completed, the task is put on hold for the number of minutes defined by the frequency, then the execution is resumed until the end time is exceeded. The request is then displayed in the In process report for the whole execution interval.

This ensures that the request is always stored in the memory once it will have been launched, which can be detrimental to other tasks if the maximum number of tasks launched simultaneously has been reached.

• Purge (field EPUR)

This box can only be checked for a frequency recurring task. In this case, no record of the successive executions of the task is kept in the request management function. Only the request under progress and the previous one are kept in the corresponding table.

• Proceed if error (field CNTERR)

• Time (field HEURE)

In case of a not frequency defined task, it is possible to launch this task at three different times in one day, as mentioned here.

• Forced execution (field FORCE)

This flag can only be checked if fixed execution times are indicated for a recurring task. It ensures the creation of the execution request even if if the time is exceeded at the moment when the batch server processes the recurring tasks of the day.

For instance, if a task is planned for 07:00, 10:00 and 15:00, but the batch server starts in the morning at 08:00:

• if the box is checked, 3 execution requests will be created (at 07:00, 10:00 and 15:00). The execution request dating from 07:00 will be executed or not depending on the server parameters (it is possible to specify a maximum execution delay in the server parameters). In any case, a line will have be planned for 07:00.
• If the box is not checked, only the two execution requests later than the current time will be created.

• Date field (field DATZON)

• Base date (field DATDEP)

• Increment (field DATNBR)

• Time unit (field DATJRS)

• Formula (field DATFRM)