Disable combined Upload & Submit step in ORA
I discovered this behavior while trying to repro a different bug.
Create an ORA with optional file uploads and text response.
Click "Choose Files" and select a file that will cause an upload error. Example: A file named tęšt-fïłê.jpg will raise an error when being uploaded.
Put in a description, but don't click "Upload Files", click "Submit your response and move to the next step".
Click yes on all JS alerts.
An error banner will appear when attempting to upload files, but just wait
Your submission will be created, but the file you uploaded will not appear, showing you as having an effectively blank submission. (clarification: your submission will contain info for the file, but since it was not uploaded, it won’t show up anywhere.)
Proposed Fix (AC):
The submission should wait for the upload. If the upload fails, we should not proceed with the submission.
Separate the Submit/Upload behavior into 2 discrete steps, as proposed by :
Staging file(s) (user has clicked Choose files… and selected files but are awaiting description/upload) should disable the submit button.
After a student clicks Upload, a successful upload re-enables the submit button (if all required sections are complete).
After a failed/partial failed upload, [open discussion for what we want to do here]
Remove the “shortcut” where clicking the Submit button while a file has been staged uploads the file before submitting.
Update alert text/messaging/documentation with new behavior
Steps to Reproduce
Reason for Variance
User Impact Summary
Changed title from Error handling around combined upload/submit allows effectively empty submissions
Outstanding question for and , on a failed file upload should we:
automatically disable the submit button until successful re-upload
argument: I wanted to upload a file, why would it make sense to be able to submit without it and end up with a partial submission?
workaround: student reloads page, if the submission doesn’t require files or they don’t want to add the one that fails, they can still submit
fall back to existing validation
argument: as long as a submission does not require files, or at least one file successfully uploaded, don’t block the student from submitting
It was where I found it, though, this was my first thought as to the cause of that ticket
It actually /isn’t/ the cause of that ticket. In this case, the submission is created with the file info for the nonexistant file. In that ticket, the submission was completely blank.