Import Failure Feedback Email Is Vague/Needs More Detail
Problem: If "opted into", the Import Feedback email notification does not give any details as to why a file may have failed.
If the error is with the file structure itself (most commonly a missing or stray quote), giving the message recipient details as to what the issue was and what line it was on would greatly speed up the troubleshooting process.
Currently, the failure message reads as "Your student data import to AcademicWorks failed. For additional information, please contact our Support Team at 888-376-4252 extension 2." with the time stamp listed afterward.
This doesn't give the recipient any context as to why the file may have failed. They then need to reach out to their support (or more frequently — implementation) contact to have them read the import log found in the Support portal. This lapsed time between calls/emails/tickets isn't ideal, as an import file failure does need to be addressed pretty quickly.
While the entirety of the import log wouldn't need to be included in the feedback email, the main error line should be.
"2016-07-14T15:27:48.527-05:00 [ERROR] CSV::MalformedCSVError Missing or stray quote in line 3329", for example.
This would allow the admin to quickly and easily troubleshoot from their end and reload a new, edited file.
Impact/Why: Giving admins more detail as to why a file may have failed will give them the ability to quickly fix it on their own and ensure a new, successful file is promptly loaded without having to wait for a call to be returned or ticket to be answered.
User story: As an administrator, if my import file fails, I need detail as to why it failed so I can fix it. By signing up for the import feedback email in the first place, I'm expecting helpful details. A simple "Failed" message and prompt to contact someone at AcademicWorks is information I can see within the system and doesn't help me to solve the issue.
Note: I do know that files can occasionally "time out" and fail not due to an error in the file structure. In that case, I think the current failure message is appropriate.
-
Guest
- Jul 14 2016
- Shipped
| Employee Name | Brandon Spiller, Brooke Butler, MIlad Alzeerah |
| Client Name "shard name" | pepperdine, winona, sfsu |
| User | IT Admin |
| Functional Unit | Communications, Imports |
Related Enhancements
Brown University would like to see this happen as well
admins at SFASU have requested this, as well.
deborah armstrong (SA) and kai markowitz (IT admin) at pepperdine would also like this.