A batch job is a group of tasks that are submitted to an AOS instance for automatic processing.

The tasks in a batch job can run sequentially or simultaneously. In addition, you can create dependencies between tasks. This means that you can set up a different sequence of tasks depending on whether an earlier task succeeds or fails.

Batch jobs are run using the security credentials of the user who created the job.

Create a batch job

  1. Click > > .

  2. Press CTRL+N to create a new batch job.

  3. Enter a description for the batch job.

  4. In the field, enter the date and time when you want the batch job to run. If you do not enter a date and time, the current date and time will be entered for you.

  5. Press CTRL+S to save the job.

  6. To set up a recurring job, click the button and enter a range and pattern for the recurrence.

  7. To set up an alert for the batch job, click the button and select alert options.

    Note Note

    Alerts will always be sent if the option is set to . If this option is set to , alerts will be sent only if the job was unsuccessful. If this option is set to , alerts will not be sent.


Add a task to a batch job

  1. In the form, click the button.

  2. Press CTRL+N to create a new task.

  3. Enter a description for the batch task.

  4. In the field, select the company database where the task will run.

  5. In the field, select the process that you want the task to run. (Classes appear in the list only if the property CanGoBatchJournalis enabled.)

    Important Important

    Some classes are designated to run on the client. You can add client tasks to a batch job. However, you must run client tasks manually by using the form. For more information, see Run client and private tasks.


  6. If necessary, select a batch group for the task. Client tasks must belong to a batch group.

  7. Press CTRL+S to save the task.

  8. To make the selected task dependent on another task in the job, click in the grid and follow these steps.

    1. Press CTRL+N to create a new condition.

    2. Select the task ID of the parent task.

    3. Select the status that the parent task must reach before the dependent task can run.

    4. Press CTRL+S to save the condition.

    If you have entered more than one condition and if all conditions must be met before the dependent task can run, select a condition type of . Select a condition type of if the dependent task can run after any of the conditions are met.

  9. Choose how to handle task failures. To ignore the failure of a specific task, mark for that task. If this option is marked, the failure of the task will not cause the job to fail. You can also use the field to specify the number of times a task should be retried before it is considered failed.

See Also