During processing, we sometimes run across data that is incompatible with our system, or is otherwise damaged and results in un reviewable documents. To counter act this, we sometimes make adjustments so that the data can still be stored, and presented to you in the most accurate way possible. Below is a list of changes we may make during processing.
Native File Changes
Paths too long or with invalid characters
If your file is stored in a location with a path that is too long to be saved, or contains characters that are invalid such as emoji's, or items from the list below, the system will generate a hash code based on various metadata from the document, and assign that as the folder path or file name depending on the original error.
Illegal characters in attachment file names
If an email attachment has an illegal character in the filename, it will be replaced with an underscore (_). Once illegal characters have been replaced, we check for duplicate naming conflicts. If a conflict is found we take the base name and extension, with consecutive periods removed, and attempt to add “-001”, “-002", etc... until no conflicts are detected.
Output PDF Changes
When the system processes spreadsheet files, the output PDF will auto fit rows and columns, and un-hide any rows, columns, work sheets, or cells that were hidden from view.
Extra long emails.
Emails ranging 50+ pages can be hard to read sometimes. These files have specially coded tags that show where a new indent should start, but with very long emails these new indents start happening after individual letters. This can turn a long email chain into several hundred pages of 1 letter lines, which isn't really reviewable. What we'll do is analyze and remove these indent tags for the PDF view, so that responses show up in a readable way no matter the length of the email chain.
/ (forward slash)
? (question mark)
^ (caret or circumflex)
$ (dollar sign)
! (exclamation mark)
` (grave or grave accent)
< (less than)
> (greater than)