Revised Warranty Upload Process

Background
The warranty upload process is designed to upload a list of changes to the pricing of warranties, which is an export from Cat. The current process uploads the file through a browser, and continually checks if the file has finished uploading. Once finished, The list of excepted is then managed.

Problem:
At times it hangs. At other times it times out for a long number fo possible reasons. The only other way to manage this is manually, which is both time and resource impacting. By fixing this, the Dealer Admin can get the changes in as a self-serve effort.

Proposed Solution:

Rebuild this a true multi-part asynchronous operation.

Upload - Upload the file through the the application. Once uploaded, they can check the status in the application (see 4 below), or they can wait foe the email to be sent to them (see 2 below)
Job - The application uploads the file as an overnight job. This job makes the changes requested, except for Exceptions that require manual intervention.
Email notification - Once the job is completed, the person uploading is sent an email to notify them of the completion. The email also contains a link where they are taken directly yo a web page within the application where they can view the status and review exceptions.
3.a. - For consideration - the admin should also be get email notification?
Upload list/history report - Within the application is a list of all of the warranties that have been uploaded since the launch of this feature, where they can see:
1. The complete list of all uploads, date, etc.
2. For each upload they can see:
  1. Who uploaded the file
  2. What file was uploaded
  3. The date it was uploaded
  4. A status. - With the possibility of cancelling if the status is still pending
  5. A link specific to the the uploaded file's exceptions to manage those exceptions.
Exception report Management - For files that have not 100% successfully uploaded, the exceptions are listed in the exception report management screen specific to the upload. The exceptions also have the methods to resolve the exception using much of the same exception management UX we use today.
1. List of missing models
2. If you want to add a model then then add it, then re-upload the file for the models that were added. SO, if you were missing 3 models, then you could just upload a change for those 3.
3. In the case where there are exceptions. they'll be able to edit the missing models.
4. Once changed the job will re-run again with the modifications ad selected.
5. If a new
** Future consideration - different project- the ability to delete model by model