The synchronization rules contains the Entity for related to specific application and version. For an example if we take ServiceEngApp, 1.7. Each entity has a default delivery method and will select a batch entity "MobileClientSecurity".
For the above entity the default schedule is that it will sync for every 30 minutes interval.
The Batch schedule for the ServiceEngApp 1.7 is every 15 minutes.
Lets Imagine that the batch schedule ran at 12:00 (Batch-1) and MobileClientSecurity entity has been synced in this batch schedule. The next schedule will run on 12:15 (Batch-2). But during Batch-2 the MobileClientSecurity entity should not sync as its default interval is 30 mins. When the Batch-3 runs (at 12:30) then the delta of MobileClientSecurity will be synced.
The question I am having is that, how will the application will track that only some specific batch entities should be synced when it is executed ?( In above example, Batch-1 and Batch-3 will sync the delta of the specified entity but Batch-2 will not sync the delta of the specified entity)
Best answer by kathlk
I will try to answer the questions as below. Please let me know if you need further clarifications.
Next Sync Time: First I can clarify the timing. Each sync rule has their own frequency. Also the main Task Shedule has it’s own frequency. Final sync time for an entity is derived from both values. If you have high frequent syncing entity like ‘MobileClientSecurity’ then next sync time is actually a range like MIN value is equals to sync rule frequency and MAX is sync rule Frequency + Task Shedule Frequency. So MobileClientSecurity can sync range of every 30 or 45 min gap.
Background jobs: Native mobile only have a signal Task Shedule per App and it take care of all entities. That’s’ why we need to consider task scheduler’s frequency when calculates actual next sync time. This will be automatically calculates and shows in the ‘Synchronized Entities’ screen where you can see what’s the next estimated sync time of particular batch entity.
MobileClientSecurity: Data is fetched from the security cache. So Delta is not visible directly but data source is based on few tables in fndbas which holds security details.