At present if a record is downloaded to the Servicemax application and then the record is updated within Salesforce so that it no longer meets the download criteria, the only means to remove said record from the device is to purge data. This must be done manually or the purge data must be scheduled to run every X hours. However in the real world, with a large work force completing multiple jobs per day, trying to get said workforce to remember to purge data on a regular basis is logistically impossible. In addition, with so many jobs having to be completed, scheduling a purge data could very well cause disruption during a user's day.
It therefore make much more sense to include the purge data within the data sync. This way the application is downloading/updating those records which meet the download criteria and is automatically removing those records that don't. Since the application is already performing a data sync throughout the day as a user completes work orders, this process would ensure that data on the device is as up to date as possible. On top of this it ensures that a user has clarity on what jobs they need to complete, as well as what stock is available to them.
What is the underlying problem do you intend to solve with this idea?
Records that no longer meet the download criteria remain on a device until they are purged.
How is the problem being addressed today, if at all?
There is no means to rectify this other than to manually trigger or schedule purge data.