Refer to documentation Implementation
Presentation
This screen is used to identify:
Close
Fields
The following fields are present on this tab :
Block number 1
| It defines the code for the folder in which the request must be launched. |
| It defines the code (and any password) of the user who has launched the request. |
|   |
Block number 2
| 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. |
|   |
| It defines the triggering day and time required for the request. |
|   |
| If thIS field is checked, a file containing the entered parameters for the request will be generated in the template file directory (batch server parameters) and the request will not be submitted to the server. The name of this file is composed of the task code followed by .mod. The file serves as a template for the creation of the .job files that permit the creation of the batch requests. |
Close
In addition to the generic error messages, the following messages can appear during the entry :
The task or the group of tasks to be launched is a level higher than the level of batch tasks that the user has the right to launch.
The function that the user wishes to launch is not authorized for this user (their function profile does not permit them to launch it whether directly or in batch mode).
The task to be launched is not active: the request could therefore not be launched.
The group of tasks to be launched is not active: the request could therefore not be launched.
Another user code has been entered and the associated password has not been entered correctly.