FileHold Quick Portal Integration is designed to allow customers to embed the FileHold library section of our web client interface - as is - into their intranet portal. This is accomplished while retaining header section of the customers existing portal interface allowing users to access documents in the FileHold library while still being able to navigate to other sections of their portal. This Quick Portal integration is in contrast to lower level integration where a customized portal page is making document get or put web method calls to the FileHold server directly using FileHold API Web Services.

For more detail information on Quick Portal integration and requirements see below. Use the following link to learn more about how to setup Quick Portal Integration.

FileHold Requirements

The Quick Portal integration requires FileHold server version 7.2 or higher. The customer must have also purchased FileHold Guest Account User optional module. Unlike regular user accounts, more than one user can access the FileHold library at the same time using a guest account username and password. This ability for a single user account to support more than one session is required when automatically authenticating users in a portal situation (see below for more details). Use the following link for more information on the FileHold guest user accounts and other optional modules.

Quick Portal Integration In Detail

The FileHold web client consists panes (see below screenshot)

Header pane- containing the FileHold banner, user account information and logout button.
Tree pane- containing the tree control allowing users to navigate the FileHold Library
Body pane- depending on the view specified by the user the body pane contains folder view, search results view, metadata pane etc.
Footer pane- this very narrow pane shows the FileHold logo in the bottom right corner.

The FileHold Quick Portal Integration allows customers to replace or customize the header pane to make it appear and function like their existing intranet navigation toolbar. For example, if your existing portal page had a header section with buttons for 'Home', 'Sitemap' and 'More' sections an additional button could be added for 'Documents' (see below screenshot).

Users accessing the portal would then be able to click on the 'documents' button to be be automatically authenticated to the FileHold library as a pre-defined guest account user. On click panes 2, 3 and 4 from the FileHold would appear in the body section of the page beneath the header. Since users are authenticated as the guest account user they are authorized to have read only access to the sections of the library as set by their rights in the library.

NOTE: When configured, the Quick Portal Integration will essentially allow users to logon to the FileHold Web Client via 2 separate URL's.
When the FileHold web client is opened from the default …/WebClient URL, it displays the regular FileHold login page allowing users to logon with their username and password. Once authenticated the standard FileHold header pane will appear along with the standard Tree, Body and Footer panes. If user access FileHold from the …/WebClientPortal URL, the custom header pane will appear and the user will be automatically logged on according to the settings described below and displays a custom header control.