Periodically (and in the background) download changes from back office to FieldFX Mobile (if the user has connectivity).
It is assumed that the default interval for triggering a download will be 15 minutes.
Acceptance Criteria
The polling interval should be driven from a custom setting
Users should be able to navigate and use the app while automated download is pending
While using Mobile, changes made from back office (for example, new job assignments, new tickets, new price books etc) will become available for use within Mobile
It is not expected that new content from back office to appear in real-time. New content and modified values should appear after significant application events, such as page navigation.
If the application is closed during an automatic download, the automatic download should resume when the application is reopened
If connectivity is lost during an automatic download, the automatic download should initially retry, then abort if connectivity is not restored. The automatic download will be retried after the interval period (if connectivity is restored).
Automatic downloads should NEVER cause data to be lost (due to an incomplete download)
If the automated download fails for any reason (including dropped connectivity or expired auth token), it should be visible to the user from any screen that a problem occurred to the user can remedy the situation if necessary.
Content removed from back office should not cause the app to fail (for example, the user shouldn’t be stuck looking at an infinite spinner). If content is removed from the sync during usage of that content, then the user should be redirected to a “Content unavailable” screen. For example, while viewing a job, it the job assignment is removed, or the job is deleted, actions the user takes from the job screen such as editing the job, changing it’s status or creating a ticket should either succeed (if the job was previously loaded in memory), or should cause a navigation to the “Content unavailable” screen.
If a user’s authentication token has expired, it is expected that the automatic download will not continue (no changes from back office will become available in Mobile). No attempt will be made to redirect the user to the login screen during the automated download.
When on the sync screen, it should be clear if a download is currently in progress.
Sync diagnostics information for automated downloads should be available from the sync screen (as per manual downloads)
It is NOT necessary to block logout during automatic downloads
Automatic downloads should be disabled during the process of logging out
Automatic downloads will not trigger when the application is closed. This feature may be added later in conjunction with and enhanced feature set, such as a configurable download schedule (to limit unnecessary API calls), or push-based download triggers.
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 }}
githubbob42
commented
5 years ago
Mingle Card: 5135 Narrative
See feature card #5126
Periodically (and in the background) download changes from back office to FieldFX Mobile (if the user has connectivity).
It is assumed that the default interval for triggering a download will be 15 minutes.
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