Solutions
Microsoft Document Imaging Solutions Checklist
When evaluating document imaging solutions, there are several key issues/questions to consider, especially when the solution is going into a Microsoft environment.
Use the checklist below to ensure the solution you choose works best for your work environment.
| Microsoft SharePoint Integration: |
Product X |
Product Y |
| Are SharePoint workflows supported by enforcing metadata requirements for rules-based processing? |
|
|
| Are changes to the underlying SharePoint site structure reflected dynamically at the point of capture? |
|
|
| Are audit trails maintained? |
|
|
| Are there no components required on the server? |
|
|
| Are hosted environments supported as seamlessly as server-based environments? |
|
|
| Microsoft Exchange/Outlook Integration: |
Product X |
Product Y |
| Does the solution support MSFT mail options? (Copy of sent message stored in Sent Items folder, Access to Global Address Books and Personal Contacts, etc.) |
|
|
| Does the solution leverage the Exchange server's ability to store a single instance of an attachment delivered to mulitple recipients? |
|
|
| Is the solution scalable? |
|
|
| Are hosted environments supported as seamlessly as server-based environments? |
|
|
| Microsoft SQL Server & Microsoft Access: |
Product X |
Product Y |
| Can the solution integrate with legacy / home-grown applications? |
|
|
| Can the solution validate index data at the scanning device? |
|
|
| Does the solution store file pointers and metadata values to the database? |
|
|
| Microsoft Security: |
Product X |
Product Y |
| Does the solution have dynamic integration with Active Directory? |
|
|
| Does the solution utilize Base DN? |
|
|
| Does the solution support SSL communication? |
|
|
| Does the solution utilize the same cryptography utilized by MSFT (Kerberos)? |
|
|
| Microsoft Architecture: |
Product X |
Product Y |
| Are products end-of-lifed only when MSFT ceases support for the particular OS utilized? |
|
|
| Does the product offer a wizard-based installer? |
|
|
| Does the solution adhere to standard MSFT platform architecture? |
|
|
| Does the solution leverage .NET security? |
|
|
