When performing an incremental sync, mobile today will re-query all the system metadata, transaction data and reference data for changes since the user’s last sync.
To reduce sync times and lower the number of API calls necessary for syncing, we should allow for metadata, transaction data and reference data to be updated independently from each other. This feature will be referred to below as “granular downloads”.
Acceptance Criteria
Granular _downloads _an advanced feature. It should NOT be given the same level of emphasis as the Sync and Upload features in Mobile, but should instead be available as an advanced option.
There should be no impact on the original sync, which should always complete a sync of metadata, transaction data and reference data
There should be no impact to sync upload
_There should be no calls to download metadata when performing a granular _download of either transaction data or reference data. Cached metadata should be used to drive the queries.
It is expected that the sync will fail if the columns or object types are removed from back office, or permissions are revoked. In this scenario, the user should be notified as such, so they can choose to update their metadata manually.
Sync diagnostic information should be available from the sync screen for granulardownload
It is not necessary to lock the logout option while performing a granular download
Analysis
Related Stories
Tasks
{{ table query: SELECT Number, Name, Owner, 'Task Status' WHERE Type = Task and Story = THIS CARD ORDER BY Status }}
Defects
{{ table query: SELECT Number, Name, Owner, 'Status' WHERE Type = Defect and 'Related Story' = THIS CARD }}
Mingle Card: 5136 Narrative
See feature card #5126
When performing an incremental sync, mobile today will re-query all the system metadata, transaction data and reference data for changes since the user’s last sync.
To reduce sync times and lower the number of API calls necessary for syncing, we should allow for metadata, transaction data and reference data to be updated independently from each other. This feature will be referred to below as “granular downloads”.
Acceptance Criteria
Analysis
Related Stories
Tasks
{{ table query: SELECT Number, Name, Owner, 'Task Status' WHERE Type = Task and Story = THIS CARD ORDER BY Status }}
Defects
{{ table query: SELECT Number, Name, Owner, 'Status' WHERE Type = Defect and 'Related Story' = THIS CARD }}
Test Plan