This section offers a friendly interface to configure certain items of the application, according to the needs of the business, susceptible to be configured by the administrator of the tool.
The administrator will be able to make configurations of the tool in the following 5 options detailed below:
Application Maintenance
In this option, the administrator displays the following information:
| Fields | Description |
|---|---|
| Days to keep old records in database: | Number of days that historical records are retained for: Commands- Locations- Consumption logs -Device event logs. After the configured days have elapsed, the records will be moved to historical tables in the database. |
| Days to delete previous records in the database: | Number of days of old records to be retained in Historical Tables before being definitively eliminated. |
Tracking Settings
In this section the administrator will be able to modify the default settings (defaults) for the 3 tracking levels. When the tracking command is sent to a device according to accuracy, it reports according to the settings made in this section.
In this option, the administrator displays the following information:
| Fields | Description |
|---|---|
| Number of Tracking Logs: | The maximum number of logs that a device can send in a single invocation to the location reporting service, exposed by the server. |
| Distance in meters High precision: | Maximum distance in meters before reporting location in high tracking accuracy. |
| Time, seconds, high precision: | Maximum time elapsed before reporting location in high tracking accuracy. |
| Distance in meters medium accuracy: | Maximum distance in meters before reporting location in average tracking accuracy. |
| Time, seconds, average accuracy: | Maximum time elapsed before reporting location in average tracking accuracy. |
| Distance in meters Low accuracy: | Maximum distance in meters before reporting location in low tracking accuracy. |
| Time, seconds, low accuracy: | Maximum time elapsed before reporting location in low tracking accuracy |
Metric
This section presents configurations that control the collection of metric data by devices to the server.
In this option, the administrator displays the following information:
| Fields | Description |
|---|---|
| Enable Metrics Collection: | Enable/Disable globally if mobile devices can report metrics statistics. |
| Start time for metrics and productivity calculation: | Starting time on the day when devices will start reporting metric data. |
| End time of calculation of metrics and productivity: | The final time on the day when devices will stop reporting metrics data. |
| Frequency of Metric Reporting by Devices: | An interval of time with which devices will send a metric update report to the server. |
| Send metrics command in linking: | Determines if at the time of linking a device the sending of metrics of the device in question will be activated by default. |
Remote Support
In this section you will be able to configure the options for remote control sessions to devices. The administrator should check or uncheck the boxes as required and click Apply. The actions are described below according to the configuration made:
| Fields | Description |
|---|---|
| Request confirmation on mobile device before signing in: | Checking this box will prompt the user of the device to confirm that it will be launched. |
| Request a password on your mobile device before logging in: | When you check this box, a 6-digit numerical code will be generated on the device when you log in that will have to be typed correctly in the console to effectively start the session. |
⚐ Note Android 15 or higher devices:
- The system displays the user to select whether to view the full screen or only a single application in the session.
- Kiosk configuration: If the device is in configuration kiosk shows all the installed applications, in this case the user must select the applications that are configured in the kiosk environment; If the user selects an application that is not configured in kiosk, the session is closed, due to the restrictions configured from the policy