Content Connector Use Cases

The following page covers several examples of use cases for the Therefore™ Content Connector.

Monitoring an Input Folder

  1. Under Therefore™ Content Connector node, right-click on Input Folder and then select 'New'.

  2. Define the folder and then the job that should be used to process files in this input folder. Give this input folder an intuitive name e.g. Invoices and select Add to define new job. A job consists of an indexing profile together with other settings that can be defined depending on the situation. In this case the input folders should be used for other profiles too and hence a filter can be defined to only process documents with a certain file name.

    Note:

    • When using an input folder in Therefore™ Online, it's not necessary to enter the full FTP file path. Only enter the name of the folder to which the document will be uploaded.

    • For text and XML files a display form can be defined.

    • If required, the storage format can be changed. For PDF formats, it is possible to sign and timestamp the documents.

    • For text files, for example, with line feed variations a preprocessor can be defined.

  3. Now the Therefore™ Content Connector will automatically process documents placed into this folder based on the configured polling interval and schedule settings. To confirm everything is working, the process can be run manually. Open the Therefore™ Console, click 'Window' and then 'Content Connector View'. Under Content Connector click 'Stop' and then 'Start Scheduler'. The new input folder should now be listed and any documents in the folder should be processed correctly. If all successful, open the test document(s) using Therefore™ Navigator as a final check.

Signature Monitoring

The Therefore™ Content Connector can be used to monitor documents sent to eSignature providers, and save these back into Therefore™ once they are signed.

  1. The first step is to create an indexing profile to configure where the signed document should be saved and what kind of data should be extracted.

  2. Next, create a new Signature Monitoring profile. Go to Integrations > Therefore™ Content Connector and right-clicking on the 'Signature monitoring' node. Select 'New'.

  3. Select your eSignature provider from the drop-down list on the opened dialog and give the profile an intuitive name. Click 'Add' to add new jobs.

  4. Select the indexing profile that should be applied from the drop-down list and specify the content that should be downloaded.

    Note:

    The 'Context' field should match the content of the context field in the respective Send for Signing workflow task to match documents with the specified indexing profile. Anything can be entered in these two fields but the name of the category that is assigned in the eSignature workflow, the workflow name, or the workflow task name are recommended.

  5. Now, the Therefore™ Content Connector will check for documents based on the configured polling interval and schedule settings. These are then checked against the context values. If a document with a configured context value is found, it is retrieved and processed using the corresponding indexing profile. To check that everything is working, the process can be run manually. Open the Therefore™ Console, click 'Window' and then 'Content Connector View - <yourtenant>'.

  6. Select 'Content Connector' in the main menu. Click 'Stop' and then 'Start Scheduler'. Any signed documents should then be automatically processed. If all is successful, open the test document(s) using the Therefore™ Navigator as a final check.

Saving Cloud Storage

The Therefore™ Content Connector can be used to monitor and download documents from cloud storage devices. See the our page on Cloud Storage configuration:

Using Cloud Storage