Offline mode

Offline mode is available for Entreprise module.

Introduction

Here are the key points to remember when the internet connection is active:

1. Connection: this is a mandatory setting. Offline data retrieval takes place through the configuration.

2. Application use: data retrieval takes place directly from the ERP and functional actions are sent directly to the ERP.

caution

Data retrieval: however, if the connection is lost, data retrieval is possible. Data retrieval takes place using data from storage, if available. Otherwise, no results will be displayed.

Functional action: the request will be put on hold in parallel with changes to the storage data, if possible.

3. Queue synchronization: this involves sending the requests on hold in order to the ERP during connection recovery. In the event of a conflict, the ERP takes precedence. If the connection is lost again, the request returns to the queue and synchronization is interrupted.

4. Data synchronization: this involves updating the storage following synchronization of the queue.

Configuration

Access: Application config → Apps management → Axelor Mobile Offline, configure

Open Axelor Mobile Offline. Fill in the following information:

1. Enable offline mode: check the box if you want to enable offline mode.

2. Default time to reload: specify the default reload time (open the “Configuration for getting data to mobile app section”). This is the time between two data reloads in the storage. By default, the time is 24 hours.

3. Offline meta models: add offline templates. This is the setting for the data to be synchronized in order to use the application in offline mode. This setting is essential to ensure that offline mode works properly on the mobile application.

4. Enable auto synchronization: check this box if you want to enable the option (open the “Configuration for sending data from mobile app” section). This option enables automatic data synchronization as soon as the user regains a connection. If this option is disabled, synchronization must be initiated manually by the user.

5. Default time to timeout: enter the timeout in seconds before the synchronization request fails.

Data retrieval

In the “Offline meta models” table, select a template or add a new one. A new window with the settings to be entered will open.

1. Meta model: select the meta model to retrieve.

2. Fields: here, define the fields of the template to retrieve. All referenced required fields must also be filled in. It is necessary to include both the fields to be displayed and those used in the filters to ensure correct evaluation of the application's requests. To retrieve all fields of the object without specifying the fields of related objects, simply use the * character.

3. Concerned roles: this refers to the limitation of data to a group of roles. By default, if nothing has been entered, this configuration applies to all users.

4. Time to reload: defines the time interval between two reloads of data in local storage. By default, the value of this field is inherited from the global configuration. During retrieval, an expiration date is calculated based on this interval. Once this date has passed, synchronization is automatically triggered as soon as the application regains an internet connection.

5. Rule: the JPQL rule for filtering the data to be retrieved.

6. Parameters: here you will find the parameters of the JPQL rule with Groovy elements.

Synchronization

On the mobile application, open the settings (User profile → gear icon). Open the query log.

1. View pending queries: clicking this button opens the Query Log. From this log, you can delete a query.

2. Manual synchronization of pending queries: click the icon at the top right to start manual synchronization of pending queries.

3. Manually synchronize saved data: click the icon in the upper right corner to start manually synchronizing saved data.

4. Retry: Click the button next to a request to retry requests that have failed.