Synchronization

The user can synchronize data in the Sync area of the control center.

The user can synchronize either:

  • All data (full synchronization), i. e. the data and the configuration, see Full Synchronization.
  • Only the data that has been changed since the last synchronization (incremental synchronization), see Incremental Synchronization.
  • Only the configuration (all the data from the designer database including resources), see Configuration Only.
  • Change the application's language.


Note: Data is not synchronized when the device switches to sleep mode, i. e. synchronization processes are interrupted (even if a full synchronization is being carried out). Therefore, Aurea software recommends to adjust the delay until the device switches to sleep mode accordingly.

You can use the following Web Configuration parameters to disable options:

Full Synchronization

The full synchronization transfers the data model, catalog values, the configuration, record data, configuration resource files, and documents as defined beforehand.

Note: Records deleted on the server are not transferred to the device (i.e. are not deleted on the device) unless a full synchronization is carried out.

Data is transferred in several requests that are sequentially processed:

  • At first, the data model, catalog and configuration data is transferred from the server to the client.
  • A request for each offline data set fetches the record data.
  • All configured resource files are transferred.
  • All document requests are sent to the Document Download Manager who downloads them asynchronously.

The application is blocked during synchronization, other actions cannot be carried out.

Data is fully synchronized when a user accesses the application for the first time. Afterwards, the user is reminded to fully synchronize data regularly. After a certain time period, users cannot access the application anymore without carrying out a full synchronization. You can define the interval, when a user must carry out a full synchronization with the following web configuration parameters:

If the application is terminated during the synchronization, the state is stored on the device. If the user logs in again, the synchronization continues.

Note: Records that are not included in the offline dataset are removed from the device when the next full synchronization is carried out, see Offline Record Set / Offline Data Set.

Incremental Synchronization

An incremental synchronization transfers all record and catalog data changed since the last synchronization (full or incremental). It is executed in one request, usually only takes seconds and can be carried out frequently.

You can define that data is incrementally synchronized at specific time intervals, see Sync.Config.

After synchronizing data is up-to-date, except:

  • Data downloaded with the application but not belonging to an existing record set.
  • Data that does not belong to an offline data set anymore because the rights definition or the record set itself was changed.
  • Data belonging to an offline data set after the rights definition was changed but the data itself was not changed. This data is only included in a full synchronization.
Note: Records that have been marked as deleted (DelCd. field) in the Aurea CRM database are also synchronized. However, physically deleted records are not considered. They are only removed from the device when carrying out a full synchronization.

Configuration Only

It is recommended to use this option only during the project development phase. Only the application's configuration data is transferred.

UpSync

The UpSync is started automatically when the application switches from offline to online mode and synchronizes only requests that were created while working offline.