The synchronization process will sync any data that the user has access to that appears on pages in the offline navigation. Entities that do not appear in your offline pages will not be synchronized. The sync does detect reference selectors.
The synchronization does not take into account any database selection criteria on your pages, like in any listviews.
You could restrict the amount of data being synchronized by limiting the entity access. For example, when the inspection is completed, no longer allow the tablet user access to it by adding an XPath constraint to your entity access, specifying the inspection status.
Also make sure that users are only allowed their own inspections, assuming that is applicable for your app. Otherwise, all inspections from all users would be synchronized.
In other words, restrict access to the data being synchronized as much as possible using entity access.
As Marcel wrote, the current approach to limit the amount of data is indeed via entity access. We do want to make this more flexible/configurable. There are two main options:
- Create a separate domain model for the offline app so that only that data is synchronized
btw, regarding: "Syncing is done at startup automatically" This was the case before (7.8, don't remember the exact version). Now the data is only synchronized at startup after a model update.
Hi Danny, Marcel,
Thanks for your input! :) You definitely helped us!