System and method for uploading and verifying a document
A computer implemented method may allow for the upload and verification of a document. In one aspect, the method may receive a file at a data server associated with an insurance company event and determine if the file contains a computer security threat. The method may also determine if the file is supported and convert the file wherein the converted file is supported. The method may further flag the converted file for association with an insurance company event and transmit the converted file to a permanent storage server.
1. A computer implemented method comprising:
receiving, at a data server, a file uploaded from a client device, wherein the file is associated with an insurance company event;
determining, by a malware module of the data server, whether the file contains a computer security threat;
removing, by the malware module of the data server, the computer security threat from the file when it is determined that the file contains a computer security threat;
determining, by a conversion module of the data server, whether the file is supported;
converting, by the conversion module of the data server, the file into a converted file when it is determined that the file is not supported, wherein the converted file is supported;
flagging the converted file for association with an insurance company event; and
transmitting, by a hardware processor, the converted file to a permanent storage server.
2. The computer implemented method of claim 1 , further comprising:
transmitting the converted file to the client device for a verification from the client device that the converted file can be uploaded; and
receiving the verification from the client device that the converted file can be uploaded.
3. The computer implemented method of claim 2 , further comprising:
transmitting a status notification for viewing on the display of the client device, wherein the status notification visually represents the progress of the file upload.
4. The computer implemented method of claim 2 , further comprising:
displaying a suggestion that the user try to upload a different file when the verification is not received from the client device.
5. The computer implemented method of claim 1 , further comprising:
transmitting the user credentials; and
determining whether the file is uploaded by a trusted user.
6. The computer implemented method of claim 1 , wherein flagging the converted file for association with an insurance company event further comprises:
presenting the user with a selection of several insurance company events; and
flagging the converted file for association with the insurance company event selected by the user.
7. A computer device comprising:
one or more hardware processors; and
one or more memories coupled to the one or more hardware processors;
wherein the one or more memories include non-transitory computer executable instructions stored therein that, when executed by the one or more hardware processors, cause the one or more hardware processors to:
receive, at a data server, a file uploaded from a client device, wherein the file is associated with an insurance company event;
determine, by a malware module of the data server, whether the file contains a computer security threat;
remove, by the malware module of the data server, the computer security threat from the file when it is determined that the file contains a computer security threat;
determine, by a conversion module of the data server, whether the file is supported;
convert, by the conversion module of the data server, the file into a converted file when it is determined that the file is not supported, wherein the converted file is supported;
flag the converted file for association with an insurance company event; and
transmit the converted file to a permanent storage server.
8. The computer device of claim 7 , wherein the non-transitory computer executable instructions further cause the one or more hardware processors to:
transmit the converted file to the client device for a verification from the client device that the converted file can be uploaded; and
receive the verification from the client device that the converted file can be uploaded.
9. The computer device of claim 8 , wherein the non-transitory computer executable instructions further cause the one or more hardware processors to:
transmit a status notification for viewing on the display of the client device, wherein the status notification visually represents the progress of the file upload.
10. The computer device of claim 8 , wherein the non-transitory computer executable instructions further cause the one or more hardware processors to:
display a suggestion that the user try to upload a different file when the verification is not received from the client device.
11. The computer device of claim 7 , wherein the non-transitory computer executable instructions further cause the one or more hardware processors to:
transmit the user credentials; and
determine whether the file is uploaded by a trusted user.
12. The computer device of claim 7 , wherein the non-transitory computer executable instructions further cause the one or more hardware processors to:
present the user with a selection of several insurance company events; and
flag the converted file for association with the insurance company event selected by the user.
13. The non-transitory computer readable medium of claim 11 , wherein the instructions when executed on the one or more hardware processors further cause the one or more processors to:
transmit the user credentials; and
determine whether the file is uploaded by a trusted user.
14. The non-transitory computer readable medium of claim 11 , wherein the instructions when executed on the one or more processors further cause the one or more hardware processors to:
present the user with a selection of several insurance company events; and
flag the converted file for association with the insurance company event selected by the user.
15. A non-transitory computer readable medium with instructions stored thereon, the instructions executed by one or more hardware processors cause the one or more hardware processors to implement a method, the method comprising:
receiving, at a data server, a file uploaded from a client device, wherein the file is associated with an insurance company event;
determining, by a malware module of the data server, whether the file contains a computer security threat;
removing, by the malware module of the data server, the computer security threat from the file when it is determined that the file contains malicious code;
determining, by a conversion module of the data server, whether the file is supported;
converting, by the conversion module of the data server, the file into a converted file when it is determined that the file is not supported, wherein the converted file is supported;
flagging the converted file for association with an insurance company event; and
transmitting the converted file to a permanent storage server.
16. The non-transitory computer readable medium of claim 15 , wherein the instructions when executed on the one or more hardware processors further cause the one or more hardware processors to:
transmit the converted file to the client device for a verification from the client device that the converted file can be uploaded; and
receive the verification from the client device that the converted file can be uploaded.
17. The non-transitory computer readable medium of claim 16 , wherein the instructions when executed on the one or more hardware processors further cause the one or more hardware processors to:
transmit a status notification for viewing on the display of the client device, wherein the status notification visually represents the progress of the file upload.
18. The non-transitory computer readable medium of claim 16 , wherein the instructions when executed on the one or more hardware processors further cause the one or more hardware processors to:
display a suggestion that the user try to upload a different file when the verification is not received from the client device.