The core element of synchronization management are the sets of rules. They define how the app synchronizes, depending on time, network connection and data volume. In this way, for example, synchronization can be limited in the case of low transmission speeds (2G/3G) or a limited data volume for mobile data usage. Different sets of rules can be created, which identify themselves by their code. This code is stored in the Anveo user. They can either be generally valid, or specifically defined for background and manual synchronization.
To further refine the rules, time windows can be defined in which synchronization is restricted. In addition, process control can be used to define pages in which synchronization is suppressed. This prevents half-finished work processes from being transferred to Microsoft Dynamics.
Rules and regulations
The behavior of the app during synchronization can be controlled via rule sets. Different devices can be used to react to different parameters. These are described below.
Rulesets differ in type between “All”, “Manual” and “Background synchronization”. For each ruleset code, either the “All” type or a combination of the “Manual” and “Background” types can be defined.
If no set of rules is stored for a user or a synchronization type, a full synchronization is always performed. A background synchronization does not take place then.
There are 5 different synchronization behaviors whose scope is as follows in ascending order:
- No synchronization
- Send only
- Send only and calculate delta
- Send and receive only
- Full synchronization
If different behaviors are possible for a synchronization, the behavior with the smallest scope is always used.
Dependence on network connection
A specific behavior can be defined for each of 5 different types of network connections. If no specific behavior is stored, a full synchronization is performed. This is defined via the following options:
- 2G Behavior
- 3G Behavior
- 4G behavior
- WIFI behavior
- LAN behavior
Dependence on time windows
Time windows can be used to set up time periods for deviating synchronization behavior. (see “Time windows”).
In addition, it is possible to specify a minimum time interval in the “Min. minutes since full synchronization” field. If this value is not reached, the synchronization behavior is downgraded to “Send only”.
Process control makes it possible to avoid the synchronization of half-finished data captures. For this purpose, pages that are used during an acquisition process are locked for synchronization. “( Process control )
Dependence on data volume
In order to limit the synchronization time on the mobile device, the “Min. open data for send only” field can be used to specify the amount of data above which the synchronization behavior is limited to “Send only and calculate delta”. The data created on the server will then be received in subsequent synchronizations.
In rulesets of the “All” type, it is possible to set up a background synchronization. This is deactivated by default for the “Active” type, and activated for the “Background” type.
If background sync is enabled, the interval between two background syncs can be specified in seconds in the “Background Sync Interval” field.
In order for the background synchronization to be executed, the action code “ANV_OOM:AUTO_SYNC” must be stored in the OnOpenMenu script.
Time windows are assigned to a specific set of rules. For example, staggered synchronization times can be implemented for different user (groups).
At peak times or fixed maintenance times, synchronization can be restricted or completely prohibited.
Each time window contains a start and end time, as well as a synchronization behavior to be used for this period. The time period must not extend beyond the date boundary.
Process control makes it possible to avoid the synchronization of half-finished data captures. For this purpose, pages that are used during an acquisition process are locked for synchronization.