Our team was tasked with refactoring a COBOL-written script that gave the tariff admin user the functionality to update multiple tariff records at once by uploading a flat data file.
Mockups & Prototyping:
Project & Task Management:
White-boarding some modal options. Our SMEs requested a confirmation dialog to appear between the file upload and actual data persistence as a means of allowing the user to cancel the batch process should they suspect an error.
Working through the logic behind the scenes. Having three layers of validation rules (frontend, file content, and database values), we had to figure out at what point it would be simplest to implement the feature while still being able to relay useful information to the user.
Playing around with some ideas and what would be required to implement it. Some of the server-side validations take awhile to complete. A visual indication of the status would help the user know that the website didn't freeze and that something is in fact happening.
Figuring out the wording for a button that allows the user to download a log file of all errors. On click, the file would download directly to their computer.
This is a mockup given to a developer to demonstrate a message to be displayed after data validations but before database persistence along with annotations on expected interaction outcomes.
Another mockup to communicate with the developer that the button's display is conditional and based on the error output.