A job is a set of actions to be performed on a predefined schedule. A job can be command execution, sending reports by e-mail, changing access to units, etc.
To configure jobs, open the Jobs panel choosing a corresponding name in the top panel or clicking on the necessary item in the main menu customizer. Here you can see the list of all jobs created, information on their state, and the button to create a new job.
In the list, jobs are sorted by name. Use the dynamic filter to save your time when looking for a certain job. Input job name or its part into the search box and observe the results. The other way to filter jobs can be used if you have access to more than one resource. Then, on the dropdown list, choose a resource to display only jobs belonging to it.
Direct a mouse pointer over a job to view details in the tooltip: job type, parameters, schedule, last execution time (whether successful or not), resource (if there is access to several), and other parameters depending on job configuration. In columns on the right, you can see job state (on/off), the number of executions already made, and the number of maximum executions allowed.
In the panel, the following icons and buttons are used:
|Job type||Different kinds of jobs are marked with special icons in the first column: — command execution; — sending report by e-mail; — sending information about fuel by e-mail or SMS; — access management; — job on engine hours counting; — job on mileage counting; — job on GPRS traffic counting.|
|Clicking on job state sign at the header of the table, you can enable/disable all jobs at once (if you have access rights on them). Enable or disable a certain job.|
|The first (left) column shows how many successful executions there were; the second (right) column shows maximum executions allowed.|
|Buttons to view and/or alter job properties (depending on your access).|
|Create a new job on the basis of this one.|
|Delete selected job.|
Note. If a job belongs to some resource to which you do not have access rights to Create, edit, and delete jobs, then some kind of actions towards this job, such as enable/disable, edit or delete will be unavailable.
To make manipulations with jobs, you should have at least one resource with the access right Create, edit, and delete jobs.
To create a new job, press the New button. In the dialog choose job type:
Then follow instructions in the dialog. For any type, you have to select units to apply this job to and set the basic parameters like activation time and schedule. For each type of job, adjust also individual parameters described below.
Access required: Use unit in jobs, notifications, routes, retranslators (resource's creator where the job belongs is supposed to have this access to units to assign then this job).
Dialog of choosing units for a job or notification consists of the units currently displayed in the work list of the Monitoring panel.
If you see no units, press the 'Display all' button . If it does not help, it means there is not enough access to any of units.
You can switch between units and groups by clicking the switch-button / . If a unit group have been selected, then the action is applied to all the units the group contains on the moment of action implementation. The list of current units you can find in a group's tooltip.
Mark units/groups to apply a job/notification to. Put the flag in the header of the table to select all items.
Please note that if there are more than a hundred units on this page, their icons are not displayed.
While editing a job or notification, this page contains units selected for the job (they are checked) and units displayed on the work list at the moment. You can add more units for the action or remove some. However, only unit with Use unit in jobs… flag can be displayed here. If a job or notification that you are editing contains units to which you have not enough rights, you will be warned about it and in case you save the job/notification, those units will be lost.
These parameters are adjusted in the last page of the dialog:
Name: It is used in the list of jobs or as mail topic if the job is to send some information by e-mail.
Description: Job description is optional. Is can appear in job's tooltip.
Execution schedule: Use one of two ways to set job's schedule:
(1) Periodic execution — each N hours and/or minutes. (2) On schedule. Execution time is set in 24-hour format hours:minutes or just hours. If you need to indicate several points in time, separate them with spaces. Example:
In this case, the job will be executed at 8 AM and 10 PM daily (if other conditions concerning execution days are not set on the Time Limitation tab).
Activation time: Date and time when the job will be activated.
Maximum executions: Enter the number of job executions after which the job will be automatically disabled. If you leave this field empty, the job will be executed endlessly until you delete it or disable manually.
Enabled: This check box indicated whether the job is on or off. When creating a job, enable this check box to activate the job just after creation. If this check box is not marked, the job will appear on the list anyway, and you can activate it later.
Time limitation: In the right part of the dialog one can define time limitations by days, months, time, etc. For instance, the job can be assigned to a unit just on weekdays and within working hours from 9 AM to 6 PM. Or you may want to reset traffic counter once a month on the first day of the month. To do this, select the day 1.
Job name and schedule are required fields, other parameters are optional.
While creating a job of this type, choose a command to be executed from the given list. The list consists of all commands that are configured in selected units (if you have Execute commands rights to these units).
Not all of selected units may be able to execute a chosen command, and it is seen from the indicator:
Restrictions can be placed due to access rights or device type used.
For some commands, you should set additional parameters like input/output number, online report interval, etc. More about executing commands…
Attention! When the time comes to execute a command as a job, all kinds of rights are checked beforehand. The user who is a creator of a resource where the job belongs should have the following access flags to unit: 'Execute commands' and the set of flags specified in properties of this command.
This job is aimed to change users' access rights automatically, for example, if you want to give someone demo access for several days or restrict access to working hours.
To configure this job, select users and assign them new access. On the list, there are only users to which you have access Manage user's access rights.
Check necessary users on the left and indicate access flags on the right. You can set flags, remove flags, or leave them untouched.
Attention! This type of job can be performed successfully only if at the moment of its execution necessary rights are OK. The user who is a creator of the resource where the job belongs should have unit ACL flag 'Manage access to this item'.
This job can be used to automatically generate and send reports about units' activity to your e-mail(s).
Choose report template, file format(s) and parameters. Specify time interval — for previous … minutes/days/weeks/months/years. In the Recipients section enter e-mail address(es) where to send reports. More about parameters of report export…
In the list of report templates, only those that belong to the same resource as the job are displayed. Depending on template type, you choose appropriate objects for report generation in the next page of the dialog — units, groups, users, drivers, routes, resources, or retranslators. To apply the job for those objects, you should have a special access to them — Query messages or reports (besides, units are taken here from the work list of the Monitoring panel).
Only compressed files of reports can be sent as a job. Subject for the e-mail is taken from the name of job, and the repository itself derives its name from the report template name plus data (yyyy-mm-dd). After you have received a letter with a report, extract files to some folder and open them with appropriate applications depending on file formats.
Note. If in your company the workday sometimes finished after midnight (because some vehicles may arrive late at night), then you can adjust the parameters for the daily report in the following way. Select report interval 'for previous 24 hours' and set job activation time at 4 AM. Then the report will be automatically generated every day at 4 AM. It will contain data for the last day, and the trips finished after midnight will not be divided into two parts.
You can get information about fuel (fillings, thefts, fuel level) by e-mail or SMS according to predefined schedule. This information is given in liters only.
To detect fuel fillings and thefts, the appropriate unit settings are used (see Unit Properties ⇒ Fuel Consumption).
Additional parameters to configure this report are:
Note. Information about fuel filling and thefts is sent only in case if any has been detected. Information about fuel level is given in any case.
<copy> Unit Name x a/b/c </copy> where
For example, SMS message
Iveco_1501 1 66/-/- 2 100/-/10
means that according to the first sensor the unit Iveco_1501 has 66 lt of fuel, and no fillings and thefts were detected; according to the second sensor (fuel in the second tank, for example) fuel level is 100 lt, no fillings were found, and 10 lt theft was detected.
Dashes may mean one of the following:
Note. Whether fuel volume will be sent in liters or gallons, depends on resource settings (where the job belongs) and not on units' settings.
Counters of three types are used in WBC Fleet tracking system: counters of GPRS traffic, mileage, and engine hours. They can be set up in unit properties.
Jobs about counters allow you to automate accounting of mileage, engine hours, and GPRS traffic.
This kind of job can help you to fulfill control over mileage counter automatically, according to schedule. With this job you can store mileage counter value in unit history, reset mileage counter, set a new value for it, save its value as parameter in data message.
To set a new value or to reset the counter, choose the option Set new value for mileage counter and input the desired value below. The counter will obtain this value each time when the job is executed. Depending on resource settings, different measurement systems can be used.
Set the flag Store counter value as parameter of unit data message to save the counter value as parameter in data message. Later on it can be used to get initial and final mileage for trips. It is recommended to store the counter while the unit is parked, for example, once a day at night time.
The option Store counter value in unit event history can be used to store current mileage counter value. It is especially recommended if according to the job properties, the counter has to be reset or altered.
This is analogue of the previous type of job but it is applied to engine hours sensors.
If you store engine hours sensor as parameter in data message, you can use this parameter to create engine hours sensor on its basis.
Attention! This types of job can be performed successfully only if at the moment of its execution all necessary rights are OK. The user who is a creator of the resource where the job belongs should have unit ACL flag 'Edit counters'.
Counters' values (traffic, mileage, engine hours) are stored in unit history as registered events, which is needed for creating reports – Events or Chronology. When counter values are stored as parameters, it means new data messages are added to unit database. Those messages bear data message type, and mileage and engine hours are displayed there in meters or feet (depending on unit's properties) and seconds correspondingly.
This job is aimed to:
For example, you can assign to reset the traffic counter once a month and register each reset with the current value in unit history.
Indicate the status of the option Store counter value in unit history. If the option is activated, each reset is registered in the system, and then you can generate a report on events or report on traffic to see traffic consumption. If the option is not activated, resets are not registered anywhere.
The option Reset GPRS traffic counter is to set the counter to 0 each time when the job is performed.