Overview
The following is a brief step by step guide in how to determine if document scans within the application are reaching the destination that the ASR document polling services can deposit them to. Depending on the client setup the images may be sent to an email or an imaging folder, for the imaging provider to then in turn retrieve.
Document Hub in Drive Axle
If the driver or user has indicated they have scanned a document within the application, a record of this scan will have occurred within the Drive Axle Document Hub.
Login Drive Axle and navigate to the Document Hub: https://secure.driveaxleapp.com/documents/search to use the search option for the scanned document. You can search by the user’s name, user ID, order, or load number.
Document History
The following SQL query can be run to verify that scans for a particular load made it to the Document History table. For example, if searching for document scans where the“LoadNumber” is “91”, the query to search this would look something like the following:
SELECT TOP(100) *
FROM ELEOS.[DocumentHistory] H
WHERE H.[LoadNumber] = ‘91’ ORDER BY H.[UploadedAt] DESC
The document scans for this load number in question should be returned in descending order from the Document History table with the “UploadAt” column being a valid datetime. The “Pending” column represents whether the document has been processed or not with 1 indicating it’s waiting in queue and 0 indicating that it has been completed. The “Retries” column should return between 0 and 9. This value indicates the number of times the document has been attempted for reprocessing. Typically indicating a transient error or failure when the value is above 0. After attempting 10 times, the intergation will no longer attempt to retry on a single document.
Using the results seen in the example above you can further see fields on document scans that indicate what processing was done for that document along with fields on the form submitted with the document scan. If you look for a column called “DocumentId” and copy the value from your first result you can query the subsequent ELEOS.DocumentFields table to see these indicators of processing done on the document scan. The query to search for fields on this first result set that has a “DocumentId” of “244992825” would look something like the following:
SELECT TOP(100) *
FROM ELEOS.[DocumentFields] F
WHERE F.[DocumentId] = ‘244992825’
The results of this will show the fields of the form that was associated with the document scan along with other added fields indicating what kind of processing occurred for the document. These added fields that indicate processing that occurred can be “AzureUpload” if the document was uploaded to an Azure file share, “BoxUpload” if the document was uploaded to a Box storage location, “EbeImported” if the document was imported by EBE, “FileSaved” if the document was saved to imaging folder, and “EmailSent” if the document was emailed to a configured address which is the case for the example highlighted below. Please note that these are not indicative of successful processing. These only convey that processing is fully completed against a document for a specific processor.
Document scans that occur from an action of type “Document Scan” will only be present in the ELEOS.DocumentHistory and ELEOS.DocumentFields tables. This configuration is made and displayed in the Eleos App Manager on the action itself as shown in the example below.
Message History
For inline document scans, the scanning of the document is done during the completion of the form and occurs on forms that contain a “Form Scan” field type and that are launched from a “New Message” action type such as the example configured in the Eleos App Manager shown below.
Because these scans are completed inline on the forms themselves, information on these specific types of document scans can be found audited within the standard ELEOS.DocumentHistory and ELEOS.DocumentFields tables and within ELEOS.MessageHistory and ELEOS.MessageFields tables too. For example, if searching for the most recent inline scans, coming from an identifiable Form Code (Ex. “TEST-INLINE-DOC-SCAN”), we can query to search for the most recent of these in the Eleos.MessageHistory table which would look something like the following:
SELECT TOP(100) *
FROM ELEOS.[MessageHistory] H
WHERE H.[FormCode] = ‘TEST-INLINE-DOC-SCAN’ ORDER BY H.[ComposedAt] DESC
The first result in your result set is the most recent message from an inline document scan and we can use information on that first result to even further see what was submitted for all other fields on that form.
If you look for a column called “MessageId” and copy the value from your first result you can query the subsequent ELEOS.MessageFields table to see form fields submitted with the inline document scan, this is useful for seeing things like email related fields to help determine what email an inline scan went to. The query to search for fields on this first result set that has a “MessageId” of “6313” would look something like the following:
SELECT TOP(100) *
FROM ELEOS.[MessageFields] F
WHERE F.[MessageId] = ‘6313’
The results of this will show the name of the field from the form and the value that was either prefilled or entered by the user during submission. Other useful info specific to an inline scan includes the hub URL, download URL, and status of the scan. 
Sendgrid Confirmation
If document scans are deposited to an internal email inbox, ASR Solutions can check the SendGrid activity feed for that email to confirm that delivery was successful. Successful sends using this method show as follows:
Imaging Folders
If scans are being deposited to an imaging folder on the client server, then confirmation of successful scans can be validated by navigating to the imaging folder in question. ASR does not have a way to determine if scans are retrieved from the staging folder, as that is up to the Imaging Provider to confirm.