Mingle Card: 5949
We initially released an alpha version of auto-upload. Everything worked as we expected. However, Pioneer raised a new use-case.
Their users are offline and make a 100 ticket item upload packet.
The user gets out a hotspot and connects his tablet. His only purpose in doing this is to upload his ticket.
Because of the nature of auto-upload, the upload takes 7 or 8 minutes when it used to only require the user to be online for 30 seconds.
Other customers love the auto-upload.
Proposed solution
Continue with auto-sync as is
If the user has been offline and auto-sync detects that it is now online:
If the upload queue is very small, then continue with normal auto-sync
If the upload queue is greater than X items, then create the normal pre-sync audit log and then call an executeAnonymous to let SFDC process the packet.
Problems/Questions
This means some errors will be in the audit log and some will be in the error queue.
We could write a trigger to periodically add an audit log entry if there are unprocessed errors in the new error queue
When the upload queue is large and we upload using the old style, when do we clear the event store? Does this cause any problems with the user still using the app?
Can we write a single web app like Packet Viewer to handle both error queues?
Test Plan
Stories
{{ table query: SELECT Number, Name, Owner, Status, 'Story Points' WHERE Type = Story and Feature = THIS CARD ORDER BY Status }}
Mingle Card: 5949 We initially released an alpha version of auto-upload. Everything worked as we expected. However, Pioneer raised a new use-case.
Other customers love the auto-upload.
Proposed solution
Problems/Questions
Test Plan
Stories
{{ table query: SELECT Number, Name, Owner, Status, 'Story Points' WHERE Type = Story and Feature = THIS CARD ORDER BY Status }}