
Thank you for choosing ScannerVision as your document capture solution.
ScannerVision is an advanced document processing solution which enables you to capture documents from various sources, process them, and then store them in any of a large number of destinations. Capture sources include, but are not limited to:
- Local folders or network shares (also known as “Hot folder”)
- Multi-functional devices of various brands
- FTP
- eMail boxes
- Windows Desktop (aivika)
- Mobile devices (aivika mobile)
Integration with third party document management systems is achieved through connectors, which are 32 bit Windows DLLs (Dynamic Link Libraries) or .NET assemblies that are loaded by ScannerVision. If a connector does not exist already to upload documents to a desired location, one can be developed. Alternatively, the PowerSharp connector, which supports C# or PowerShell scripting, can be used to write a script to perform the upload.
ScannerVision provides powerful metadata support. Metadata is data that provides information about the documents processed by ScannerVision and can come from various sources. Some metadata is generated by the ScannerVision Processing Server as it processes documents. Metadata can also be captured by users as they scan documents at the MFP or at their workstation, or it can be obtained from the document itself through barcode reading and/or various OCR functions such as Magnetic Ink Character Recognition (MICR), Optical Mark Recognition (OMR), and full-document and zonal Optical Character Recognition (OCR).
ScannerVision allows you to apply conditional logic to determine which connectors to execute under certain circumstances or where to route documents. This means that ScannerVision can make intelligent decisions on what metadata to use or where documents should be stored based on the conditions you specify.
This help manual will guide you through the process of configuring your ScannerVision workflows, called templates. Please read through the manual from start to finish. Some of the concepts will only become clear once you have implemented them in a template. We encourage you to configure test templates as you work through the manual and to try out the features and functions covered by the topic you are reading.