How To Guide

Recurring Task Management

Introduction
Using this function, you may define recurring tasks, which allows regular launching
by the batch server:
Batch Tasks
Batch Task Sequences
These recurring tasks trigger regular execution with a monthly (define the days of
the month), or weekly frequency (define the days of the week).
Recurring batch tasks are handled on a single tab. A batch task is characterized by
a code that will be used to call it and by a certain number of technical characteristics
defining the processes to be launched. A batch task may be:
Sage Program (process)
Report (printout)
System task defined by a script file (shell script under UNIX or Windows script)
A recurring batch task is defined either by a function or a process name. The fact
that the Function field is assigned means that the function can be launched in Web
mode as well as in Windows client/server mode: The parameter and profile
(authorized sites, among other things) passing conditions are processed via this
function code.
A batch process may need parameters entered dynamically with each task
submission in a dialog screen. You will also be able to call this screen if the task is
launched directly. The development standardization of the batch tasks processes
call to a parameter entry screen and resends the corresponding values for the
execution, either directly (if the task is launched directly), or in a deferred way.
Other characteristics of the batch tasks:
Timeout Length (in minutes), i.e., a time limit at the end of which the task can be stopped
if it is still running.
Related Module
The minimum authorization level the user requires to launch the task.
Priority (parameter depending on the system and transmitted to the system when
launching the task).
Three flags allowing you to launch the task in single user mode; authorize the entry of a
folder code different from the current folder when you launch the task; send a message to
the user warning them when the task has terminated.

August 2009 Sage Page 1 of 8

Procedure
Navigate via Usage>Batch Server>Recurring Task Management

August 2009 Sage Page 2 of 8

 The following screen appears. Note the Left List Box is populated with existing
Recurring Tasks.

Click the New Icon in the top right hand corner of the screen: -or-
Select an Existing Task you wish to change
Enter a Name and a Description for the Recurring Task

Select the Folder.

Select the User Code and Password (if necessary).
Select the Group (if necessary).
Select the Task Code you wish to run.

August 2009 Sage Page 3 of 8

 The Task Code is the Function or Report you wish to execute (i.e., MRP function).
You can find the function name by hovering over the function on the Menu with
your cursor.

August 2009 Sage Page 4 of 8

 You may also select from a list of values via the F12 key or r/c Select

Next, Select the Frequency at which you wish the Recurring Task to run.

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 tick the end of month box.
If the period is weekly, it is necessary to tick one or more days of the week.
If the frequency is nil, it is possible to launch the task at three different times in one
day.

August 2009 Sage Page 5 of 8

 You may also exclude days by entering a value in that field. In order to do this, you
must first set up a Batch Server Calendar via Parameters>Usage>Batch Server
Calendar.

The frequency expressed in minutes, makes it possible to start the task again in n
minutes after it has finished during a time interval. The requests can be removed
progressively if the purge box is ticked.

August 2009 Sage Page 6 of 8

Note: New to V5 is the Forced execution field
This flag can only be checked if fixed execution times are indicated for a recurring
task. It ensures the creation of the execution request even if the time is exceeded at
the moment when the batch server processes the recurring tasks of 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 the box is checked, 3 execution requests will be created (at
07:00, 10:00 and 15:00). The execution request dating from 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 planned for 07:00; if he box is not
checked, only the two execution requests later than the current time will be created.

Note: Also New to V5 is the Relative Date Block.

This Block allows you to more effectively set up your Recurring Task by:
Selecting a variable Base Date for the process

Creating a Time Increment for the Task to run again by Time Unit

Or by creating a custom Formula

When you have finished setting up the Recurring Task click the Create Button
on the bottom of the screen.
You are now ready to enter the Parameter Definitions for the Function or Report.

Click on the Parameters Definition Button on the bottom of the screen.

The Parameter Screen appears just as it would if you were running the Function or
Report normally.

August 2009 Sage Page 7 of 8

 Leave Blank

Enter the Parameters.

Note: The Requirement Cutoff Date MUST be left blank if you wish todays date to default each
day that it is run!

Click the OK Button once you have entered the Parameters.

Click the End Button

The Recurring Task will now run according to the schedule and parameters.

August 2009 Sage Page 8 of 8