There are two modes available for the mobile application in bpm’online: “online” and “offline”. You can select the mode in the [Mobile application operation mode] system setting.
Note
Regardless of the working mode, mobile devices only display data for which the users have access permissions.
Working in online mode
If you select the online working mode, there is no need to manually synchronize the application. Synchronization with the bpm'online server is performed automatically, in real time, i.e., if you add a task using the mobile application, the task will be immediately displayed in the main application and vice versa.
Note
To work properly in the “online” mode, you need a stable Internet connection to the bpm’online server.
Working in offline mode
In offline mode, the mobile application user should synchronize periodically with the main bpm’online application. Changes made to the mobile application are saved on the bpm'online server only after synchronizing with the main application. If there were any conflicts during synchronization,
To synchronize manually while in “offline” mode:
1.Tap the 
button and select [Settings].
2.On the opened page, tap the [Synchronization] button (Fig. 1).
Fig. 1 Running synchronization in the mobile application
As a result, the data from the main application will be displayed in the mobile application and the main application will display the records that were created using the mobile application.
Attention
If changes were made to the same record (for example, the duration of the activity) in both the desktop and the mobile application, then the conditions for saving these changes after synchronization depend on the order in which they were made. If the record was modified in the desktop application first, and then in the mobile application, the changes made in the mobile application will be saved during the synchronization. If changes in the main application are made during or after the synchronization, then they will be saved in the system.
Synchronization with the main application is performed by the OData protocol.
For example, there is a business process logic in the main application according to which if the opportunity advances to the next stage, an activity is automatically generated in the system. When the opportunity moves to such stage, the synchronization with the main application will be performed. The business logic of creating an activity will be handled on the main application, then the created activity will be displayed in the mobile application.
A user working in the “online“ mode will not notice this because the application will be working directly with the server. The new activity will appear in the mobile application immediately after the corresponding business process completes and without the need for manual synchronization. Users who work in the “offline” mode will need to run synchronization for the activity to be displayed.
The synchronization log is available only in the offline mode. The log displays the date of the last synchronization and any conflicts that occurred when records were last synchronized with the desktop application.
The [Log] tab includes a list of all found conflicts. Conflict details are specified for each record individually.
The [Pending changes] tab includes all data that were not yet exported to the desktop application during the last synchronization attempt.
Depending on the conflict, clicking the record in the log will display the following actions:
[Revert changes] - undo all changes and delete the record from the synchronization log. If triggered, the local copy of this record will be overwritten with a server copy. For example, your system administrator took away your rights to edit the account’s type. A conflict occurs once you edit the [Type] field and attempt to synchronize with the desktop application. To resolve this conflict, you can undo the changes and re-synchronize. A detailed example of a synchronization conflict due to insufficient rights is described in a separate article. Read more >>>
[Go to record] - opens the record edit page. For example, a field that could previously be left blank is now required. Creating a new account without populating this field will result in a conflict during the next synchronization attempt. To resolve this conflict, open the record edit page, populate the required field, and re-synchronize.
[Request access] - opens your preferred mobile mail client and creates a template of a request to provide the necessary access rights to complete the synchronization.
Note
To send requests to system administrators, please make sure that their correct email address is specified in the “Email for sending permission requests” system setting.
See also
