Therefore™ Content Connector

The Therefore™ Content Connector is used to automatically save information to Therefore™.  It can monitor input folders, mailboxes or third party services such as eSignature integrations. Using an indexing profile, it can extract index data and then save a document or case to Therefore™. Regardless of what is monitored, the following components are always required:

1. Indexing Profile
   This defines what should be saved to Therefore™ and where the index data should come from.

   1. What should be saved to Therefore™:
      - The document itself;
      - Another document;
      - An empty document (form);
      - A new case.

   2. What should source the index data:
      - PDF, XML, Text and CSV files;
      - An existing Therefore™ document;
      - The file name;
      - A combination of the above.

2. Therefore™ Content Connector profile
   This defines what should be monitored and which profile should be used to process incoming files.

   1. What should be monitored:
      - Input folder;
      - Mailbox;
      - Signature Monitoring.

The following apply to using the Therefore™ Content Connector with Therefore™ Online: Documents are uploaded to the Therefore™ Content Connector using an FTP connection. Connection details and credentials are provided by Therefore Corporation when a Content Connector license is activated on a Therefore™ Online system. Each tenant is restricted to one FTP account to use for uploading files to the Therefore™ Content Connector.

Right-clicking on the Therefore™ Content Connector object opens a context menu. A double-click opens the Therefore™ Content Connector administrator.

Settings
This opens the Settings dialog, see below for further details.

Security
View and edit role-based access for anything below this node.

Therefore™ Content Connector Settings

Content Connector Schedule
The daily start and end times during which the processing sequence will run automatically. By default these are set to run all the time.

Blocksize for database insert
The maximum number of documents to be inserted into the Therefore™ database in a single transaction.

Month names
This can be used when custom month names occur in the documents to be imported. For example if the month names have been abbreviated to Jan. instead of January. Then edit the name of the months in this list.  These will then be used to correctly convert captured dates.

Content Connector Events
Four settings are possible for each event.

Do not log: no log data is recorded.
Log success: log data is only recorded when the event is successful.
Log failure: log data is only recorded when the event fails.
Log always: log data is always recorded

Event	Description
Service Startup/Shutdown	Log when the Therefore™ Import  service starts or stops.
File or e-mail processing	Logs when a spoolfile is saved to Therefore™.

Archive
Frequency of log file creation can be defined based on time or size.

Every Day: the log file is archived everyday at the specified time.
Every Week: the log file is archived once a week on the specified weekday and time.
Every Month: the log file is archived on the first day of each month.
On Size: the log file is archived as soon as the specified size is exceeded.

Most of these settings as the same as in the previous two tabs. However, if the Therefore™ Content Connector service is running on a different machine to the Therefore™ Server, then this needs to be specified in the setting Content Connector Server.

Therefore™ On-premise systems require a DCOM connection the for Therefore Content Connector. DCOM Configuration

Server

This object is only visible in Therefore™ installations with a Therefore™ Content Connector license and with multiple server licenses. By expanding this object the user can access the Content Connector Input Folders and Mailbox Monitoring profiles for each of the Therefore™ servers. For the more general case of a single server system, the Input Folders and Mailbox Monitoring objects are listed directly under the Therefore™ Content Connector object.