Groups of tasks

• Group (field CODGRP)

A task group permits the bringing together of several tasks that should be executed in order, one after the other.

• Description (field ZDES)

Title associated to the previous code.

• Active (field ENAFLG)

Select this check box to activate the current record.

The data and setup of disabled records is kept, but they cannot be used on other records (documents, settings, etc.) or for mass processing by recalling the record code.

Authorizations granted for a given function can prohibit the creation of an active record. In this case, this check box is deactivated by default. It can only be modified by an authorized user or using a signature Workflow.

For accounting batch tasks, you cannot change the active status of a recurring task from this function. To do so, you must use the Journal status monitor function (VALPCE).

• Module (field MODULE)

Select a module for the setup.

Use this field to specify if the screen has to be created in the folder database. This is the case when the module linked to the screen is active on the folder.

• Authorization level (field NIVEAU)

The level will be compared with the access level of each user who attempts to launch this task. It will be refused if the user level is insufficient.

• Hourly constraints (field HOR)

The time constraint code is used to identify the time slots during which the task groups can be launched.

• Proceed if error (field CNTERR)

When it is checked, this box is used to ignore an error in a batch task in order to:

• launch the following task when performing several tasks
• Re-perform the task when it is launched in a repetitive way with a given frequency.

If it is not checked, in case of an error in a task, the following tasks will be "Aborted".
The errors that can interrupt a task are the following:

• - GOK variable different from 1: usually indicates that there is an update transaction error in the database update.
• GERRBATCH variable superior to 100: this variable, that can be setup in the processing that performs the task, is used by the developer to distinguish minor from major errors.
• GERREUR variable different from 0: in some processings, this variable is set in an error management sub-program generated by the "Onerrgo" instruction. In this case this is an exception returned by the engine (for example: non-existent variable or division by zero)

• Sequence (field SEQ)

• Task code (field CODTAC)

A "batch" task is a program that can be executed by the server periodically or at the request of a user.