MSG Versioning Implications for NetDocuments/Symphony OCR

There are four different levels of versioning available for NetDocuments Symphony OCR users, and the type of versioning you choose will determine the behavior that Symphony OCR uses.   The levels and how they work with .msg files are listed below:

1. Do not create versions - when this is set, Symphony OCR will not create new versions when processing a document with the exception of .msg files.  NetDocuments requires that version 1 of emails not be overwritten. Therefore, even when Symphony OCR is set to "Do not create versions" , it will create a Version 2 of email files.  If there are multiple attachments to the email, Symphony OCR will only create a Version 2 (not any additional versions) as it processes multiple attachments.
   
2. Create versions for all documents -when this is set, Symphony OCR will create new versions for all documents it processes regardless of the file type / extension.  Therefore, if there are multiple attachments to the email, Symphony OCR will create a separate version for each email attachment. (If there are 10 email attachments, there will be 10 versions created)
3. Create versions for pdf documents only — when this is set, Symphony OCR will create new versions for all PDF documents.  NetDocuments requires that version 1 of emails not be overwritten.  Therefore, even when Symphony OCR is set to "Create versions for pdf documents only", it will create a Version 2 of email files.  If there are multiple attachments to the email, Symphony OCR will only create a Version 2 (not any additional versions) as it processes multiple attachments.  This behavior for .msg files is the same as "Do not create versions".
   
4. Create versions for non-pdf documents only — when this is set, Symphony OCR will create new versions of .tif and .msg files.   Therefore, if there are multiple attachments to the email, Symphony OCR will create a separate version for each email attachment. (If there are 10 email attachments, there will be 10 versions created)

TIF Versioning Implications for NetDocuments/Symphony OCR

Let's discuss the behavior with versioning for .tif files and the four applicable settings:

1. Do not create versions — when this is set, Symphony OCR will not create new versions when processing a document.  The .tif file is converted to .pdf when processed, but no new version is created. 
2. Create versions for all documents — when this is set, Symphony OCR will create a new version for all documents it processes regardless of the file type / extension.  Therefore,  the .tif file is converted to .pdf and saved as a new version, v1 remains a .tif file.
   
3. Create versions for pdf documents only -when this is set, Symphony OCR will create new versions for all PDF documents only.  Symphony OCR will not create a new document for .tif files
4. Create versions for non-pdf documents only — when this is set, Symphony OCR will create new versions of .tif and .msg files but not create versions for .pdf files.