Recurring Task Management

It identifies the recurring task code.

Title associated with the previous code.

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

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).

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.

It defines a group of tasks to be launched.

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

Select this check box to activate the current record.

Disabled records keep their content and setup but cannot be used by recalling their code:

• On other records such as documents and settings
• On mass processes

The authorizations for a given function can prohibit the creation of an active record. In this case, the check box is disabled by default. It can only be modified by an authorized user or through a signature workflow.

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

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.

Enter a calendar code to exclude specific days from the execution of recurring tasks.

Select the day or days of the week to run a task the same day or days each week.

For accounting tasks: If the MULBATCH – Multi-instance batch task parameter (CPT chapter, ACC group) is set to , you can enter a unique value for each recurring task.

If you selected Monthly, you can indicate one day of the month, ranging between 1 and 31, and/or select the Month end check box.

For accounting tasks: If the MULBATCH – Multi-instance batch task parameter (CPT chapter, ACC group) is set to , you can enter a unique value for each recurring task.

If you selected Monthly, select this check box to run the task on the last day of each month unless the date is excluded by the calendar code.

For accounting tasks: If the MULBATCH – Multi-instance batch task parameter (CPT chapter, ACC group) is set to , you can enter a unique value for each recurring task.

Enter start and end times to limit running the task to between that time range.

For accounting tasks: If the MULBATCH – Multi-instance batch task parameter (CPT chapter, ACC group) is set to , you can enter a unique value for each recurring task.

Enter the number of minutes between multiple iterations of a task. For example, if the first run does not process all the No. of records set, the task runs again after the number of minutes entered here.

For accounting tasks: If the MULBATCH – Multi-instance batch task parameter (CPT chapter, ACC group) is set to , you can enter a unique value for each recurring task.

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.

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

If this check box is selected, a recurring task is launched again even if there is an error.
Errors that can interrupt a task:
- GOK variable different from 1: This usually indicates that there is an update transaction error in the database update.
- GERRBATCH variable less than 100: This variable can be set in the process that executes the task.
- GERREUR variable different than 0: In some processes, this variable is set in an error management sub-program generated by the Onerrgo instruction.

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.

This check box can only be selected if fixed execution times are indicated for a recurring task. It ensures that the execution request is created, even if if the time is exceeded at the moment when the batch server processes the recurring tasks for 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 selected, 3 execution requests are created (at 07:00, 10:00 and 15:00). The execution request starting at 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 been planned for 07:00.
• If not selected, only the two execution requests later than the current time will be created.

Used to enter the screen zone name to initialize.
It is possible to specify the screen abbreviation if the task's parameter entry box uses several screens.

Used to enter the reference date for the calculation.

Number to add to (or withdraw from) the reference date.
This number corresponds to the chosen unit (day, week, month)

Time unit

Used to enter a formula that will be applied in the parameter entry environment of the batch task reccuring journal entry: open tables, global variables, user variables, etc...