DirectConnect couldn't be simpler to use, but there are some tips and tricks that can be leveraged to optimize the end user experience: - Setup searches to identify documents waiting indexing in GlobalSearch. If the Archive has an Entered By System Field, it will automatically be populated with the name "DirectConnect Import". Setup a search with a Static Search Prompt to automatically identify documents saved by DirectConnect. You can extended that search to only include results where key index criteria is empty to narrow results even further.
- In GlobalSearch, setup email notifications on an Archive to alert others there is work to perform. If you are licensed for GlobalAction, notifications and alerts can be very dynamic and include escalation rules to ensure all documents are processed in a timely manner.
- Applications or capture devices that "job build" (making changes to files directly in a destination folder) can create situations where files get imported before they are ready. DirectConnect will not process a file that is in use. If your capture process results in partial or incomplete files getting picked, you may need to implement an idle wait time to be sure files are finished be written to before being imported. Idle wait settings require a manual configuration file change.
- In the DirectConnect running directory, open the file DirectConnectService.exe.config in any text editor.
- In the appSettings section of the file, you will need to add a setting with a key of IdleWait and a value representing the number of milliseconds to wait after a file's last modified time has been updated.
- The stock configuration file includes an IdleWait entry that is commented out (the setting is wrapped with <!-- -->). Removing the comment characters will allow you to reuse this line in the file.
|