A group of tasks is a list of batch tasks that are:

  • launched at the same time (either by submission of the group or by recurring task)
  • executed sequentially in time (each task is executed once the previous task is complete) with a log file created for each.
  • linked on the condition that the previous task is completed without error.

You define them by simply placing a list of tasks in a grid.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

A group of tasks is defined from a single section where you enter the tasks to be launched and some general information (module, time constraint, execution minimum level).

Block number 1

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 with the previous code.

Characteristics

Active (field ENAFLG)

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.
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)
Execution tag (field RTTAG)

Grid Tasks

Sequence (field SEQ)

Use this field to specify the order in which you want to run the tasks of the group. These fields allow you to run the tasks of a group in a series or in parallel.


Example of parallel tasks:

Sequence Task code
10 Tâche1
10 Tâche2
20 Tâche3
20 Tâche4

Example of tasks in series:

Sequence Task code
10 Tâche1
20 Tâche2
30 Tâche3
40 Tâche4

The Sequence fields must be entered.
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.
Execution tag (field RTTAGTAC)

Specific actions

Copy

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Incorrect task code

The task could not be launched via a recurring task (it is a task that could not be standardized for use in Web mode: tasks of this type have no function associated with them).

Tables used

SEEREFERTTO Refer to documentation Implementation