FileHold WebServices API - integration with 3rd Party Applications
The main subsystems of FileHold communicate with each other via secure and fully authenticated web service calls. All FileHold application clients (including the FileHold Web Client, FileHold Desktop Application and FileHold MS Office Add-in) interact with the FileHold Server using the same web services and calls. These very same Web Services make up the FileHold Web Services API for integration of custom clients with the FileHold library. The web Service API allows: the integration of FileHold document management software functionality into other productivity applications. The API can be used to develop connectors to import documents and metadata into FileHold from other applications or give users the ability to retrieve data and documents from the FileHold Library through a custom Intranet portal.
The SOA architecture provides the ability to deploy web services on different servers for the ultimate in system scalability and performance management.
FileHold FastFind – 3rd Party integration Tool
Example #1: A user, who has had the FileHold FastFind feature installed, is working in a windows based accounting application such as simply accounting or QuickBooks and is displaying a customer invoice. The user would like to see the original contract, or other documentation, that is associated with that customers invoice. These documents may have been scanned or imaged and stored in the FileHold software. To see the invoice the user simply puts their curser on the Customer Name field (or just makes it the active field) and presses a designated “hot key” (i.e. F3). Upon pressing the hot key the customer name is transferred to the FileHold library search engine and all documents that have that customer name associated with them will be brought up in FileHold for review. The user can select the appropriate document and review it using the FileHold document viewer. To work with the document even further, the user can, open it in its native application for further work, or using “paperless office” best practices initiate a workflow and send that document to a colleague for approval.
Example #2: A customer is using a very popular Geographic Information System (GIS) such as ArcGIS. In this example the customer is looking at a creek on a map and wants to review all documents anyone has stored in either the GIS system or in the FileHold document management software relative to creeks. The following screenshots shows that the user has typed “creek” into the GIS search engine but instead of hitting the enter key and searching for creek within the GIS they simply press the F3 key and a search begins in the FileHold document repository.