Skip to main content
Version: 8.2

Management of schedules, modules and help

Schedule management​

Access: Administration → Job management → All schedules

In AOS, you have a possibility to use batches (access: Application config → Batches). Batches can be triggered by schedules.

The Schedule menu can be found in the Administration menu. Launch scheduled actions via a Cron code.

With the help of a schedule, you can schedule processes at the application level. For example, ‘Increment holidays every month’.

caution

On revenue instances, the schedule service is disabled for security/data volume reasons.

The schedules can slow down the operation of the application.

  1. Open a schedule file.

  2. Active: tick the box to activate the schedule.

  3. Job: this field is very important. Select a job from the drop-down list. As a general rule, users will use the Batchjob job (com.axelor.apps.base.job.Batchjob). Why? Most of the time a schedule is used for batch (i.e. batch). However, some schedules are used for other reasons. For example, global tracking on objects.

  4. Cron: the cron is a recurrence generator. It is an international code that allows you to define recurrence schedules. By validating the cron, a periodicity will be generated.

info

Use a CronMaker to generate the final code.

  1. Service: the service (Batch part) appears when you select a Batchjob. There are several types of Service: Base / CRM / Accounting services. How is a service determined? In the batch section, you will find a batch (for example, an HR batch).

If you open the batch in question, you will find a code (for example, for the HR batch, it could be HT_MONTHLY_LEAVE). If you then open the schedule, you will find the same code. To associate a schedule with a batch, the code on the schedule must be identical to the code of the batch. This code will allow the batch to be launched automatically instead of doing it manually.

Module management​

Access: Administration → Module Management → All Modules

You will also find the menu that groups together all application modules with their current versions.

Depends on: if you open the module file, you will find the ‘Depends on’ field. This refers to the module's dependency on other elements. For example, you will not be able to download the Business Production part without first downloading the Supplychain module or the Sales module. This menu is for information purposes only.

Help management​

Access: Administration → Help management → View help/menu help

Help management in Axelor allows you to provide contextual help to users of the application.

There are two types of help in the application:

  • View help: it will add the help on the fields in an overloaded form view.

  • Menu help: it will add the help for the menus of the application.

In the ‘View help’ menu, you can add help to the fields. For example, on the Sales order, you can add help to the ‘Tax position’ field.

On the view help sheet, you will find:

  1. Model: for example, com.axelor.apps.sale.dlb.SaleOrder.

  2. Field: for example, fiscalPosition.

  3. Type: for example, tooltip. You can also select ‘Substitute missing’ or ‘Online’.

  4. View: for example, sale-order-form.

  5. Language: for example, French.

  6. Help: in the dedicated space, enter the information concerning the help.

info

Consequently, when you open the file for an order, you will see that the ‘Tax position’ field has a tooltip.

Consequently, you will find help for the user when viewing a sale order form. Remember to select a menu on which you want the help to appear.