Design Adjustment/Receive/Issue behavior while offline
Description
Assumptions
Physical inventory is accessed rarely (like once a month). Filling the PI is a lengthy process (can take more than a day). If the user doesn’t have immediate access there (needs to wait a couple of minutes) that’s probably fine.
There could be situations where we need immediate access to PI as well!
Issue/Receive/Adjustments are accessed frequently (could be several times a day). Filling the data on those screens is quick (usually just one line). The user needs instant access there (no matter if they are online or offline).
We need to consider the following aspects:
We could consider having information about pending offline actions in the header
whether adjustments are synchronized automatically or not
Yes, the attempt to synchronize them is made as soon as the user is online again
It could be confusing that those actions are automatically synchronized
whether to change the button name from Submit to Save
The button name is changed, but not to save. See the mockups for design details
how to inform users about not sent adjustments
An error message is displayed on SoH page and issue/receive/adjusttments - see mock-ups for details
what happens when the request fails (e.g. a product is out of stock)
An error message is displayed on SoH page and issue/receive/adjusttments - see mock-ups for details
We should add more information about failed validations - let the user know what went wrong
Consider allowing to retry the failed actions somehow
There should be a global page where I see those problems and can act upon them
The approach should be announced on forum or Product Committee.
Mockups: https://agoiba.axshare.com
Activity
Could you assist us with answering how it would be best to inform the user about adjustments that were not correctly synchronized with the server?
I have linked the mockups in the ticket description https://agoiba.axshare.com . Mockups contain:
Offline notifications on the Stock on Hand page
Offline notifications on Issue page - the same pattern should be used for offline notifications for Receive and Adjustments pages.
Error notifications on the Stock on Hand page.
Error notification on the Issue page - the same pattern should be used for offline notifications for Receive and Adjustments pages.
Offline success flag on the Stock on Hand page that should display always when the user submits receive, issue or adjustment in offline mode.
Submit the offline button that should replace the standard submit button whenever a user tries to submit an issue, receive or adjustment while being offline.
Please let me know if you need anything else
Thanks, ! I’ll present on the Product Committee and let you know.
I noted the feedbacks in the ticket. Most importantly we should consider two things:
Add global information about pending offline actions that will be synchronized when I go online (and while I’m online and they are still synchronizing)
Add more granular management of the error notifications and allow the user to act upon them (retry or re-submit perhaps?); it would be also good to let the user know what went wrong exactly - maybe we can capture the coming error
Can you help us come up with an approach that will cover those cases?
Assignee
Reporter
Labels
Story Points
Time tracking
Time remaining
Sprint
Priority
