For the generic connector configuration options, click here.

Generic destination settings

Field/Button	Description
Name	The name of the destination.
Type	The type of the destination. The following destination types are available: Windows folder Novell Netware folder FTP folder Secure FTP WebDAV folder SMTP Message Database Destination List Connector

Folder location settings

Field/Button	Description
Folder location	Destination information for the scanned documents. For Windows or Novell folders, click the ... button and browse for an existing folder or create a new folder and select it. For an FTP folder or a Secure FTP, enter the FTP location, such as ftp://ftp01/scans. For a WebDAV folder, specify the root URL to a WebDAV folder, starting with either http:// or https://. Note that Quick Connect does not support long UNC paths, thus full path names are limited to 260 characters,
Secure connection (FTPS explicit)	Check this box to enable a secure connection. Only available for FTP folders.
Enable subfolder navigation	Enables users to select a subfolder at the device.
Root path	Only valid for Windows folders. Clicking the key icon before this textbox allows ShareScan to retrieve the root path data from Data Publishing. When the icon is highlighted, the name of the data published key defining root path must to be specified in the textbox (for example, a barcode name). The root path (a UNC path) is retrieved from this data published key during runtime. If the key icon is not highlighted, the root path has to be specified in the textbox manually. If the Data Publishing is used, subfolder routing and subfolder navigation works normally.
Maximum folder level	The number of subfolder levels users may navigate. The default is 3.
Subfolder routing...	This button displays a dialog which configures subfolder names where documents are stored. The text box under Folder Location specifies the root folder of the destination. A user can navigate subfolders underneath this root folder. If subfolder navigation is enabled at the device, Quick Connect creates subfolder underneath the user-specified folder and stores documents in the created folder. If subfolder navigation is disabled, Quick Connect creates a subfolder underneath the root folder and stores documents in the created folder. The location where documents are stored is: <Root folder>\<user navigated subfolders>\<subfolder to be created>\<document.pdf> The subfolder routing dialog consists of tree view and list view control. The tree view defines the hierarchy of subfolders while the list view defines folder naming rule for the selected subfolder. The text of tree node displays the names of field. Field names must be unique across subfolders. If a field is user modifiable, Quick Connect displays the Subfolders form at the device, between Folder Navigation and File Name form. Alphanumeric, Numeric, List and Database fields publish a DP key, so administrators can map document services DP keys to these fields to retrieve runtime value. You can turn Subfolder routing on for each destination in a destination list. However, the items you create under Subfolder routing are not published and therefore not accessible for the Data Publishing Mapper. If you want these to be published, add them to the Index file for the connector profile.

FTP settings

Only available for Secure FTP destination type.

Field/Button	Description
FTP type	FTP over SSL SSH FTP
Ssl mode	No security Implicit TLS or SSL Explicit TLS or SSL
Passive	Mark this checkbox for a passive FTP connection (the client initiates both connections to the server; this solves the problem of firewalls filtering the incoming data port connection to the client from the server)

Authentication settings

Field/Button	Description
Authentication type	Available for FTP folder, Secure FTP, WebDAV folder; the following options exist for each type: FTP folder: Windows, FTP, Netware Secure FTP: FTP WebDAV folder: Windows, WebDAV, Netware
Authenticate user	The options are: None: Sends scanned documents to the destination without requiring user authentication. The Manager requires write access to the destination. Logon As: All documents scanned and stored to this destination use the credentials that you enter in the User name and Password fields. The user is not required to log on at the device. Specify the domain/tree, user ID, and password to use for authentication. The specified account requires write access to the destination. Runtime: During each session at the device, prompts the user to provide logon credentials before storing the file. You specify the domain or tree (for Novell Netware folders) to use for authentication.
User ID	All Authentication types require a user name and password if Logon As is selected as the user authentication method.
Password	Specifies the password for the Logon as user.
Domain	Select either Logon as or RunTime authentication mode to enable this combo box. In Logon as mode, the combo box must specify the domain name for the Logon-as-user. In RunTime mode, the combo box specifies the default domain name which is initially displayed on the Logon form but this is optional.
Tree	Only available for Novell Netware folders; has the same function as the Domain combo box.

SMTP message destination settings

Field/Button	Description
Server	Specifies the SMTP server via name or IP address.
Port	Specifies the port number used. The default is 25.
Account	Sets the account to be used for authentication. The following options are available: Generic account - None Authentication Personal account - Windows Authentication Personal account - Netware Authentication Personal account - LDAP Authentication
Reply To:	Specifies the sender's email address. Available only for Generic account None Authentication.
Domain	Specifies the domain name used as initial value on the Logon form. Available only for Personal account - Windows Authentication.
Tree	Specifies the tree name used as initial value on the Logon form. Available only for Personal account - Netware Authentication.
LDAP settings	Displays the LDAP server settings dialog. Available only for Personal account - LDAP Authentication.
Cc sender:	Checking this box sends a copy of each message to the sender.
To listbox	Use the Add button to add the SMTP addresses of the recipients.
Subject	Set the subject of the message.

Database destination settings

For more information on database types and settings, see Database types and settings.

Field/Button	Description
DB type	The configured database types are displayed here. The available types are as follows: Microsoft Access Microsoft SQL Oracle
Data source	Displays the data source.
Catalog	Displays the catalog name, if supported.
Table	Displays the table name with schema, if applicable.
Document data (BLOB)	Displays the column name for the document's data (BLOB).
Document name	Displays the column name for the document name.
Document extension	Displays the column name for the document extension.
Configure	Displays a situation-based dialog. If the administrator is defining a new Database destination, clicking this button displays the Configure Data Source dialog to define database connection. If a defined database connection exists, the Select recent data source dialog with previously used connections is displayed, thus the administrator can reuse existing connection setting or go to Configure data source dialog via the New… button. If an existing connection setting is selected or new connection setting has defined, the connector displays the Map document destination dialog to define data mapping.

Note: 

Since Microsoft deprecated the Microsoft Jet 4.0 OLE DB Provider (https://msdn.microsoft.com/en-us/library/ms810810.aspx), and future Windows update may remove it from the system. Configuring a 'Microsoft Excel 97-2003' data source on machines without a Microsoft Jet 4.0 OLE DB Provider results in an error message. In case you still wish to use the old format .xls files, install 32 bit version of Microsoft Access Database Engine 2016 Redistributable (https://www.microsoft.com/en-us/download/details.aspx?id=54920) or later and configure Database type for Microsoft Excel 2007-2010 in the Configure data source dialog by selecting old format .xls files via setting the filter to All files (*.*) on the Windows File Open dialog.

Destination list settings

Field/Button

Description

Name Location, and Logon

Enables you to create a list of destinations to which the connector profile can send scanned documents. Clicking the Add button displays the Add destination to ... window, where you can set the attributes of the chosen destination. When you add a destination to the list, you specify the destination name, type, and location, as well as the authentication information. The New destination window then lists all the destinations.

 

Note:

To make sure that users have to log on, at most once, at the device, you cannot mix certain combinations of destination type and authentication in a destination list.

Example: 

If you add a Windows Folder or Novell Netware Folder destination that uses Runtime authentication, and then you add an FTP Folder destination, the Authenticate User combo box is shown without Runtime authentication mode.

Invalid options will not be available in the Authenticate User list.

 

Connector settings

This destination type represents another ShareScan workflow that receives its input from the output of this connector profile / destination.

By using the Connector destination type, it is possible to chain ShareScan workflows with the limitation that the second (3^rd, etc.) workflows in such a chain must be an Express workflow (i.e. not having any user interface / forms to display), similarly to the Watcher workflows.

For more details on Express workflows, see the Watcher.

To transfer document metadata between the original and the chained (connector destination) workflow, you can use the XML Index File fields: whichever metadata (data from Data Publishing, like barcode values, data provided by Database Lookup Extender etc.) item you want to use in the chained workflow, you simply need to specify it as a field the Index File of the connector profile using a Connector destination, and create a mapping in the Data Publishing Mapper.

The Connector destination type can also be used as an item in a Destination list. In this way, the same document(s) can be stored via multiple connectors.

The following scenarios details how to properly configure the QuickConnect Connector destination:

Make sure that the Connector destination type is available and the created profile results in a hidden watcher configuration:

1. Prerequisites
   1. Install ShareScan
   2. Load normal (non-watcher: dev, prodd, eval, nfr) ShareScan license
   3. Create / Set HKLM\SOFTWARE\Wow6432Node\Kofax\ShareScan\ShareScanAdmin\ShowHiddenCascadingWatchers to true
   4. Create a no-UI (aka Express) workflow with QuickConnect (profile is named as finaltarget in the example below)
   2. Create a folder on a local drive (e.g. ShareScanQC)
   3. Create a Windows folder destination (named as Output1 in the screenshot below) using the folder created in the previous step
   4. Make sure the is no user modifiable settings (e.g. document type) in the connector profile
   5. The icon of the connector profile will be grey, indicating the profile does not require any user input
      
   5. To be able to check the hidden watcher profiles, import a valid Watcher license as well. All the functionalities (of creating connector destinations) must also be available without a connector license.
2. Tests:
1. Create a new QuickConnect profile (e.g. by Save As... the default profile – named as ConnectorDest1 in the example below)
2. On the Destinations tab click the New button
3. The New destination dialog appears
   
4. There will be a Connector item in the drop-down list of the Type control.
5. If you select the Connector item, the dialog UI changes as follows: (If there is no Express profile to select, a warning is shown.
   
   If there is/are profiles(s) to select, they are included in the list.
   
6. Click OK – a warning appears:
   
7. If you click the Click to edit index field mappings of this destination link, the same warning appears.
8. Click the finaltarget radio button under the Quick Connect node (only the Express (no-UI) profiles should be listed in this dialog – all of the Express profiles should appear in this list, for any of the connectors having such type of profile)
9. If you click the Click to edit index field mappings of this destination link, the Data Publishing Mapper dialog appears (does not contain any items to edit yet, as there are some pre-requisites).
10. Click OK: a new destination shall appear on the Destinations tab, with the specified name, with the blue puzzle icon (representing the Connector destination)
11. Click the Save button for the profile saving.
12. Go to the Devices tab / Watching, right-click / Reload watchers: a watcher appears
13. A new entry is displayed, with the following name structure: <QC profile name>@<destination name> }- QuickConnect-<target express profile name>
    
    (This watcher is not be visible if the registry setting described in 1/c is not set, or set to false) Observe that the Rule has the name Rule - <GUID>, where the GUID is an automatically generated unique identifier of the connector destination
14. Click the newly created watcher entry, and check the Summary in the main panel of Administration Console
    
15. The Watch Folder entry will point to a folder under ...ShareScan\Cascading\<GUID>, where the GUID is a unique identifier of the connector destination. This GUID matches the GUID displayed for the Watcher Rule in m.)
16. Open Windows Explorer and check the folder shown in the Watcher Summary – it should be created by the creation of the Connector destination.
17. When the Rule is selected, click the Edit button in the Main panel - the Rule editor Wizard appears:
    
18. Observe that the Do not recreate PDF files checkbox and the Route to destination without processing radio buttons correspond to the checkbox on dialog 2.e
19. If the QC connector profile with the Connector destination is created with any/both of the checkboxes of 2.e having checked values, then the Do not recreate PDF files checkbox in the rule will be the same as the state of the corresponding checkbox of dialog 2.e; the Route to destination without processing radio button will be selected in the rule if the Route only checkbox was checked on dialog 2.e
20. The settings of the rule described in (s.) will correspond to the checkbox states of 2.e also if the connector profile / Connector destination is edited. FAIL
21. If the target Express profile is changed (while editing the connector destination), the change will be reflected in the watcher Rule. PASS
22. Testing if the DP mapper dialog is showing up only the relevant fields:
    1. Create an index field (on the Index File tab click Add etc.) (Do not save the connector profile at this point.
    2. Create a connector destination or edit an existing one
    3. Click the Click to edit index field mappings of this destination link. A message box pops up.
    4. If you click on No, the message box disappears and the DP mapper will not open. If you click Yes, the connector profile is saved, and then the DP mapper will open.
       
    5. The dropdown list of the Published Key column should contain only the field that is defined as an index field in the QC profile, having this connector destination. The name of the key will be Connector Destination.<name of the QC profile> . FAIL – the key is shown only when the QC profile was saved manually
    6. Connector keys in the DP mapper dialog are filtered to the available connector keys of the target connector – this is identical to the feature of the DP mapper when it is opened from the connector profile right-hand panel link.

Make sure that in Quick Connect connector, Connector destination type is available and the created profile results in a hidden watcher configuration in the Destination list:

1. Prerequisites: same as in the previous scenario
2. Tests:
   1. Similar to step 2.a of the previous scenario
   2. Similar to step 2.a of the previous scenario
   3. On the New destination dialog, select Destination list from the Type dropdown
      
   4. Click the Add button.
   5. From this point, creating the Connector destination is the same as in the previous scenario.
   6. When the destination dialog is confirmed with OK, the newly created destination list item appears in the list.
      
   7. The Summary panel below reflects the different settings of the Connector destination (Name, connector type, target profile name, Route only flag, PDF recreate flag) – a deselect / select is necessary to have these changes visible
   8. All the other test items from the previous scenario apply.

 

Field/Button	Description
Choose connector profile for processing	This list displays the configured Express connectors / profiles (i.e. the profiles with no UI runtime). If no connector / profile is available with Express setup, a warning message informs the user that the profile and corresponding services require Express mode. Note:  These profiles will not replicate in an AutoSync environment.
Route only	Mark this checkbox if you want to pass your files to their destinations without processing and/or transformation.
Do not recreate PDF files	Mark this checkbox to process incoming files as if they are all actual scans. When the Route only checkbox is marked, this checkbox is greyed out.
Click to edit index field mappings of this destination	Click this link to open the Data Publishing mapper tool with the published keys filtered for the keys derived from the index field of Quick Connect and the connector keys filtered to the destination Connector selected.

Setting a database as a destination enables you to configure a connector profile so that users at the device can scan and index documents and store them in the specified database. You can configure the profile to store the index information in a file, in the same database as the scanned document, or in a different database.

To set a database as a destination:

1. On the Configure tab, click New.

   The New destination window opens.

2. In the Name field, enter a name for the destination.
3. In the Type list, select Database.

4. Under Destination, click Configure.

   The Configure data source window opens.

5. Configure a new data source.
   1. Select the database type and specify the settings.
   2. Click Test connection.
   3. When the system displays the “Test succeeded” message, click OK twice.

   Or

   Configure an existing data source

   1. If the Select recent data source window opens, select the data source that you want to use.
   2. Click OK.

   The data source is the database where the scanned documents will be stored.

6. Depending from the purpose, the following windows are displayed:
   1. Map document destination for database destinations.
   2. Choose fields dialog for database fields
   3. Map index fields dialog for index files.
   4. Click OK. The New destination window displays the database settings.
   5. Click OK to save the settings. The Destinations list displays the name and summary information for the database destination you created.

Note: 

The Index file tab displays the mapped database column name in the Table Column in the Index File list view.

When you set a database as a destination, you can use the Map document destination feature to map the name and file extension of the scanned document to STRING fields in a table in the database. This enables you, or a database administrator, to create associations between the scanned document and any index information that the user enters on the Index screen for the document, wherever that index information is stored.

You can create a file name field or an index field that uses a database as the source of field values. Users at the device can then select from a list of available values for that field.

If the database administrator modifies, in a database, values that are associated with a Quick Connect field, users will have access to the changed values. You do not need to make any changes to the field in the Administration Console.

To use a database as the source of field values:

1. On the File name or the Index file tab, click New.

   The appropriate Field editor window opens (File name field editor or Index file field editor).

2. In the Name field, enter a name for the new field.
3. In the Type field, select Database as the type.
4. Check User modify if you want the user at the device to be able to alter this part of the file name.
5. Select the Required option if you want to require users at the device to specify a file name or index value.

6. Click Configure.

   If you have previously configured a data source, the Select recent data source window opens.

1. On the File name or the Index file tab, click New.

   The appropriate Field editor window opens (File name field editor or Index file field editor).

2. In the Name field, enter a name for the new field.
3. In the Type field, select Database as the type.
4. Check User modify if you want the user at the device to be able to alter this part of the file name.
5. Select the Required option if you want to require users at the device to specify a file name or index value.

6. Click Configure.

   If you have previously configured a data source, the Select recent data source window opens.

• To use an existing data source, select it and then click OK.

• If you do not want to use an existing data source, click New.

  The Configure data source window opens. Follow the instructions to configure a new data source.

• If you have not previously configured a data source, the Configure data source window opens. Follow the instructions for configuring a new data source.
• After selecting or configuring a data source, the Choose field window opens.
7. Select a table, select a column in the table, and then select the default file name or index value from the list of available values. The user at the device can accept the default value for the field or select a value from the list.

8. Click OK to return to the Field editor window.

   The window displays the settings you have configured.

9. Click OK to save the settings and return to the File name or Index file tab.

   The tab displays the name and summary information for the Database field you created.

You can define parameters, operators, and constant values via the Expression dialog. The parameters are published to the Data Mapping tool and mapped to published data from a document service. Document service publishes data as string and the connector converts the string to specific data type according to parameter type.

The file name generated at the eCopy-enabled device is composed of one or more fields. Note that if file name is not published by document service, Quick Connect uses its file naming rule even if you check Use Document Service file name.

To define file naming fields:

1. Select the File Name tab.
2. Click New.
3. Use the File name field editor to specify a name for the field and set the default values.
4. Click OK.

5. Repeat this procedure for each new file naming field.

   Or

   Select Use Document Service file name to use the file name configured for the Document Service.

6. Click the Save current profile button.

   The system saves your settings as part of the connector profile.

Note: 

If a scanned document already exists in a selected destination you are presented with a number of options.

Setting up an index file enables the user at the device to enter indexing information for the scanned document in one or more fields. Quick Connect writes the field names that you create on the Index file tab to an index file, and creates data mapping information between field names and database columns. The default values that you associate with each index field, or the values entered for the field by the user at the device are also stored in the index file or database table.

The information describes the content of the document, such as a case ID, a client name, or a document type. Quick Connect saves the index information with the scanned document. This option is useful with back-end applications that can process the scanned documents (image files) and index files in the destination folder.

To configure an index file:

1. Select the Index File tab.
2. Click New.
3. Use the Index Field Editor to define an index field and its default values.
4. Click OK.
5. Repeat this procedure for each new index field.
6. In the File format area, select the format of the index file.
7. If the Document splitting option is enabled on the Settings pane and you want to create a single index file, select Create single index file when Splitting is enabled.
8. If you want to duplicate unchanging index values, select Repeat unchanging index values.

9. Click the Save current profile button.

   The system saves your settings as part of the connector profile.

The index file has the same name as the scanned document, but has a different file extension. The available formats of the index file are:

• XML
• CSV (comma-separated value)
• TSV (tab-separated value)
• Database

Example: 

Click here to view file format examples:

CSV

filename,device,date,time,user-tag1<CRLF>

MyDocument.pdf,MEAP01,03052003,110534AM,value 1

TSV

filename<TAB>device<TAB>date<TAB>time<TAB>user-tag1<CRLF>

MyDocument.pdf<TAB>MEAP01<TAB>03052003<TAB>110534AM<TAB>value 1

XML

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<data>

<index id="filename">MyDocument.pdf</index>

<index id="device">MEAP01</index>

<index id="date">03052003</index>

<index id="time">110534AM</index>

<index id="user-tag1">value 1</index>

</data>

When the Document splitting option is enabled on the Settings pane, you can configure Quick Connect to create a single index file that records the index values entered at the device for all scan jobs of a batch.

• The connector uses the file name that you create on the File name tab to create a name for the index file. If you do not configure a file name, the connector uses the default file naming rule.

  If the file name includes the Batch number field, the connector sets the current batch number in that field; otherwise, the connector adds an underscore (_) to the batching number, as in “document-20070131_1.pdf”.

  If a file name already exists and the Create unique file name option is configured on the File name tab, the connector adds a period to the rolling number, as in document-20070131_1.1.pdf.

• Index fields are divided into three types. The type of index value determines the frequency of changes to index values:

• System: The index field retains the same index value when the user at the device starts a new scan job.

  Used with the following field type: Device Name.

• Scan Job: The index values in index fields of this type are the same for the entire scan job.

  Used with the following field types: Alphanumeric, Numeric, Date, Time, List, Authenticated user, Destination path, Database.

• Splitting job: A scan job can comprise multiple document splitting jobs. The index values in index fields of this type change for each document splitting job.

  Used with the following field types: File name, Number of pages, File size, and Batch-based index value.

• The Repeat unchanging index values option enables you to record the index values for a batch job each time the user enters the index values, even if the user at the device enters the same index values many times.
• If you do not select this option, the connector records the system- and scan job-dependent index values only once.
• Since batch job-dependent index values have different values based on the job, they will be recorded multiple times by default. However, if there is only a single batching job, the index values will be treated like system- and scan job-dependent values.
• If you select this option, batch job-dependent index values will be recorded in a different node (for an XML file) or a different row (for CSV and TSV files, and database tables). This does not apply when the connector is processing only one batch scanning job

This feature enables you to specify a database that will store index values entered at an eCopy-enabled device. You can map any type of Quick Connect index field to fields in an SQL, Access, or Oracle database. When a user enters values in mapped index fields, the connector profile stores the values in the associated database fields.

Note: 

The connector profile stores all mapped index values in the target database as STRING data, regardless of the type of index field.

If you store scanned documents in a database and you want to create a relationship between the database fields where the documents are stored and the database fields where the index values are stored, make sure that one of the mapped index fields is of the type “File name”. Index fields of type “File name” automatically use the file name of the scanned document that is stored in the database destination.

Example: 

Click here to see the example:

You configured a connector profile to scan insurance claims using the following file naming format:

eCopyClaims<Date><Time>

You configured the profile to store the scanned documents, named as shown below, in the target database:

eCopyClaims20060523123318.pdf

eCopyClaims20060523123319.pdf

eCopyClaims20060523123320.pdf

You created several Quick Connect index fields to capture account information and mapped them to fields in a database.

To associate the database record used to store the scanned documents with the database record used to store the scanned document’s index values, you must have an index field of type “File name” that captures the file name during scanning.

To map index fields to fields in a database:

1. Select the Index file tab, click New, and then define each index field that you want to map.

2. Under File format, select Database and then click Map Fields.

   The Configure data source window opens.

3. If you have not yet configured a data source, configure it now.

   To use the current data source, proceed to step 4.

   If you do not want to use the current data source, click Modify to select a different data source. When the Select recent data source window opens, click New and follow the instructions for configuring a new data source.

4. If you previously configured a data source, the Map index fields window opens, displaying the connection information.

5. Via Select table name, select a table.

6. Under Map fields, which displays the index fields you created, select the Quick Connect index field you want to map to a database field. You do not have to map all the Quick Connect fields.

   In the Database field column, which only displays fields of STRING data type, select the target field. The index values that the user at the device enters in the index fields will be stored in the database fields after the document is scanned.

7. Click OK to save the settings and return to the Index file tab.

If you have the eCopy Barcode Recognition Service, you can use batch-based index values. Batch-based indexing enables you to create index files with separate barcode values for each batch by assigning a base name (Publishing Name) to the position of the barcode.

All Publishing Names also have batch information available for Quick Connect to use. Note that only the first value found per Publishing Name is published for the session.

For example, a document is divided into two batches. It begins with a page that contains three barcodes and is split by another page that also contains three barcodes. On both pages the barcodes follow the same sequence but have different values:

Batch-based indexing example

The following diagram shows the four page document and how, after processing, the scanned document is stored with the correct index information.

To configure batch based indexing in Quick Connect:

1. Select the Index file or File name tab.

2. Click New.

   The relevant Field editor opens.

3. Enter the Data Publishing name to receive the Published Key from the service. You can specify any name to the Name field. The Name field provides descriptive information for you.
4. Select Batch-based index value as the Type, and click OK.
5. Follow steps 2 through 4 above for each value that you want to use.
6. Save the connector profile with the values.

When you configure a device and select this connector profile, you must then select the corresponding Service profile that you set up in the Barcode Recognition Service.

Quick Connect can read data published to a Data Publishing service by a connector. For example, a company can install a barcode recognition service and then use Quick Connect to access the barcode data that the service publishes.

The ShareScan administrator is responsible for the following tasks:

• Install and configure the Service on the same PC as the eCopy Manager. For more information see the Help topic for the Service in question.

• Work with the developer of the service, which may be available from eCopy or from a third party, to identify the data that the Service publishes and the names of the fields that will contain the published data. For example, assume that the document to be scanned contains barcodes. The service extracts data from the following barcode fields and publishes the data to a COM object:

  Barcode1, which contains a user name.

  Barcode2, which contains a date.

  Barcode3, which contains a company name.

  Barcode4, which contains a city.

• Define Quick Connect index fields that reflect the names of the fields containing the published data. Using the example, the administrator must define index fields named Barcode1, Barcode2, Barcode3, and Barcode4.
• Configure the Quick Connect index file.

When a user scans a document at an eCopy-enabled device, the Manager starts the installed Service. The Service creates the COM object and publishes data from the scanned document to the COM object. The Manager passes the COM object to Quick Connect, which searches the COM object for the configured field names. If Quick Connect finds a match, for example, if it finds a field named “Barcode1”, it reads the value in that field and writes the value over the default value in the “Barcode1” index field in the index file. Quick Connect then sends both the scanned image document and the index file to the target destination.