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

See also 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 Task1
10 Task2
20 Task3
20 Task4

Example of tasks in series:

Sequence Task code
10 Task1
20 Task2
30 Task3
40 Task4

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.
Description (field ZDES)
 
Group code (field GRP)
This field allows you to select a subgroup of tasks to be executed. The selected subgroup should be different from the parent group code.
Run after (field RUNAFTER)

This field provides the ability to execute a task or group run after a specific task or group. It allows for the following options:

  • At the end of all the previous sequences: Executes the task or group after all the sequences have been executed.

  • At the end of the previous sequence: Executes the task or group after the previous sequence has been executed.

  • At the end of the task: Execute the task or group after all the tasks have been executed.

  • At the end of the group: Execute the task or group after all tasks or groups have been executed.

If At the end of all the previous sequences or At the end of the previous sequences are chosen, the value of Task/Group code related to the Run after field is left empty and disabled.

When a Run after condition is set, make sure the sequence of the edited line is changed. The goal is to retrieve the sequence value of the selected Task/Group code and increment it by one. This ensure no tasks or groups exist between the target task or group and the task or group related to the Run after field.
Task/Group code (field RUNAFTERV)
Use this field to specify the task or group related to the Run after field.
Error condition (field ERRCND)

This field provides the ability to specify what happens to the execution of a task or a group when an error occurs. It allows for the following options:

  • Stop on error in previous sequences: Stops the execution of the task or group if an error occurs in any of the previous sequences.

  • Stop on error in the previous sequence: Stops the execution of the task or group if an error occurs in the previous sequence.

  • Stop on error in the task: Stops the execution of the task if an error occurs during its execution.

  • Stop on error in the group: Stops the execution of the task if an error occurs during the execution of any task within the group.

  • Always run: Continues the execution of the task no matter if any error occurs during its execution.

Note: If the check box Proceed if error is checked, set this field to Always run (enabled). Else, if the check box Proceed if error is unchecked, set this field to Stop on an error in previous sequence (disabled). This ensures no regression.
Task/Group code (field ERRCNDV)
Use this field to specify the task or group related to the Error condition field.
Run after (mn) (field RUNAFTTIM)
This field provides the ability to run a task or subgroup after a specific time. This field is specified in minutes. In the case of a subgroup, the specified time is added to the Run after the time of the tasks of the first sequence of the subgroup.
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).

Task code or group code not filled

Enter the task code or the group code.

Negative or "0" as part of the Sequence

The sequence cannot be equal to 0 or negative. Please enter a positive value.

Task code cannot exist multiple times with the same sequence

The task code cannot be selected multiple times with the same sequence.

Group code cannot exist multiple times with the same sequence

The group code cannot be selected multiple times with the same sequence.

The value of task code or group code cannot be used in the Run after or Error condition fields

Impossible to edit this field. It is used in the Task/Group code field.

Invalid tasks cannot be entered in the two Task/Group code columns.

No task/group code found.

Unable to change the seuqence due to the target line being used in the Runa fter field of another line.

This action will affect the sequence used in the Task/Group code field of line $1$.

The value of Group code must be different than the parent group code.

Please select a group other than the parent group.

A subgroup cannot contain more than one group.

Impossible to add a group that contains another group.

If a group is already in another group, a new subgroup cannot be added

Impossible to add a group that contains another group.

Sequence values cannot be repeated between lines of the field Task/Group code

Impossible to edit this field. It is used in the Task/Group code field.

Proceed if error check must be coherent with the Error condition field.

Impossible to clear this field. You need to choose the error condition Stop on error in previous sequences.

Group cannot be related to a recurring task when deactivated

The group is used in a recurring task. These will be deactivated in their next iteration: $1$.

Tables used

See also Refer to documentation Implementation