reitermb
commented
7 months ago We should check back in on the state of the relevant loading times here—if possible by querying data from prod?
What the real-world timing is looking like will inform whether this work is still a useful TDP enhancement
Description:
Future state: Data files that will take more than 10 seconds to parse, validate and process
Related User Stories:
As a Data Analyst, I would like to upload my data files and be confident that they have been validated and submitted successfully to ACF.
Notes Consider that the parsing and peak user base - Guessing it will be waiting between 30 seconds - 1 minute?
Stages: Needs More Work
For Andrew: QQ: Is the loading state considered inactivity and if for some crazy reason it hits 20 minutes of loading the user would run into the inactivity modal? 20 minutes of inactivity you get the modal about inactivity…
Depending on technical factors we may need multiple treatments to handle varying upload times. We only want to use a spinner for very fast uploads (e.g. ideally a second or two and less than 10 seconds). Percent/time remaining indicators are needed if we're going to make users wait longer than that. For some secondary research: https://www.nngroup.com/articles/progress-indicators/
Success message may need to change to reflect pending state while a bunch of stuff on our end happens
https://www.figma.com/file/irgQPLTrajxCXNiYBTEnMV/TDP-Mockups-For-Feedback?node-id=4447%3A220&t=C5RO5wkY9XBsqkUc-1 — early idea about a loading dialog state
https://www.figma.com/file/irgQPLTrajxCXNiYBTEnMV/TDP-Mockups-For-Feedback?node-id=4124%3A0&t=C5RO5wkY9XBsqkUc-1 — some of the error cases here may need to be surfaced in more of an error report format than an inline file input error format (system processes need time)
AC:
Tasks:
Supporting Documentation: Figma