EWS

• User name: domain\user

  Shared mailbox: mailbox

• User name: user@domain.com

  Shared mailbox: mailbox

• User name: user@domain.com

  Shared mailbox: mailbox@domain.com

Where, domain is the domain name, user is the user having impersonation rights, and mailbox is the name of the shared mailbox to access. The mailbox can be a user's mailbox or a service account's mailbox.

This option is only available if Keep message on server is selected.

• Multiple instance: Allow multiple connections to a single mailbox, without risking duplicate imports.

• Single instance(Default): Poll this mailbox with only one message connector. If you use single instance and run multiple connections in parallel, it might cause TotalAgility to import a message multiple times.

Select one of the following for authentication with the EWS mailbox:

• Local (Default) : Enter the User name and Password.

• External: Enter the secret name for the user name and password stored in the configured external storage in the User name secret and Password secret fields respectively.

To avoid timeout for messages with longer processing time, increase the timeout value. Maximum allowed value is 86400 seconds (24 hours.)

• Attachments

• Attachments first and body

• Body first and attachments (Default)

• None

• Only body

• Exclude message header (Default)

• Include message header of email

• Include message header of email and embedded email(s): Additionally, select the Body option for the Handle body of nested emails as a field in the Document conversion tab of Message Connector Configuration.

Allows you to set conditions to skip specific files for import. For example, to skip the import of .png files that are less than 10 bytes, do the following:

1. Click .
2. In the File extension text box, enter the file extension as .png.
3. Select an Operator as Less than. (Available options are: Less than and Greater than).
4. Specify the Size in bytes as 10. Use the increment  or decrement  buttons to specify the file size.
5. Click Add.

Only the .png files that are less than 10 bytes are skipped. Files greater than or equal to 10 bytes are imported.

To edit the skip import details: Select the record to edit, click , make the required changes, and then click Ok.

To delete the skip import details: Select the record to delete, click , and then click Yes.

Allows you to set a specific file extension for import. For example, to import .png files, do the following:

1. Click .
2. In the File extension text box, enter the file extension as .png.
3. Click Add.

To edit the allowed import details: Select the record to edit, click , make the required changes, and then click Ok.

To delete the allowed import details: Select the record to delete, click , and then click Yes.

The available file types are:

Normalizes non-PDF eDocuments (MS Office documents) to PDF/A. (Default: Clear)

Configure the following.

Converts the PDF documents to the ISO-standardized PDF/A format, specialized for the digital preservation of electronic documents. (Default: Clear). Configure the following.

Allows conversion of XFA forms to PDF documents. (Default: Clear)

Ensure the following:

• Install the Adobe Experience Manager output service and ensure that the web service interface is available.
• Configure the Adobe Experience Manager credentials in the Kofax Message Connector configuration.

Import the unprocessed document if there is any exception during the normalization process of a document. (Default: Clear).

A document with error information is generated and the original document is appended to this document.

Name of the Scan/VRS profile.

To extract the text from PDF, select one of the following options:

• All text (Default): Extracts both visible and invisible text.
• Automatic: Extracts only visible text. If the results are empty, then extracts by including invisible text in the results.
• Ignore all text layer: Extracts PDF through OCR. The PDF text layer is ignored.
• Visible text only: Extracts only visible texts.

The characters required as word separators. Default characters are: "/", ":", "(", ")", "-" and "#".

When processing the PDF text, strings of text containing these characters are treated as separate words. For example, "1234/56" is treated as three separate words, "1234", "/", and "56".

Save page PDF data

If selected, saves the metadata which could be used later to render or add back the metadata. (Default: Clear)

Select one of the following options:

• Do not map XML fields to TotalAgility fields: The XML file fields are not mapped to the TotalAgility fields.

• Map XML fields to TotalAgility fields and allow fields mismatch:

  TotalAgility imports the XML file and maps the TotalAgility fields to XML file fields. If there is any difference in the fields specified in the XML file, TotalAgility will still import the file and display the errors in the Message Connector.

• Map XML fields to TotalAgility fields and reject on mismatch:

  TotalAgility imports the XML file and maps the TotalAgility fields to XML file fields. If there is any difference in the fields specified in the XML file, TotalAgility rejects the XML file.

• Document: Imports a Kofax XML containing reference to a multi-page TIFF file.

• Page (Default): Imports Kofax XML containing reference to a single page TIFF file.

Creates a document from the XML content. (Default: Clear).

Additionally, on the Process list, select the process which contains the Document conversion activity with the required XML rendering configuration. By default, you can only map the XML content to the XML process variable.

The email addresses of the recipients to whom you want to send the notification. You can use an inline value, server variable, and metadata.

The email addresses of the recipients to whom you want to send a copy of the notification. You can use an inline value, server variable, and metadata.

The email addresses of the recipients to whom you want to send a blind copy (the email address of the recipient is not shown to other recipients in the list) of the notification. You can use an inline value, server variable, and metadata.

The email address of the sender. You can use an inline value, server variable, and metadata.

The subject of the email notification. You can use an inline value, server variable, and metadata.

• Text: Supports only plain text. Any images, font colors, or tables are not displayed or not displayed as expected.
• HTML: Supports images, tables, and font formats.

The message included in the email notification. You can use an inline value, server variable, and metadata.

Sends a notification to the originator (sender). The sender receives a copy of the email notification if this option is selected. (Default: Clear)

Attaches the original message (in EML format) to the notification mail. (Default: Clear)

Removes attachments from the original email. (Default: Clear)

Archive folder

Path of a local folder (such as C:\Archive) or a network folder to store the successfully imported documents.

Supported formats for successfully imported documents are:

• File: Archives the message body in a text file and all attachments in separate files.

• EML: Archives the message body and the attachments as a single EML file.

• XML: Archive the message metadata in an XML file (custom Kofax format).

The name of the subfolder and prefix for the archived files. You can also add predefined Fields (metadata) as subfolder names and filename prefixes. The value of these metadata is populated at the time of saving the archived files. If you do not add the "\" character in the field, all the fields are appended to the archived file names. For example, if you add {OK}\{Process-ID}, the files are stored in the OK folder with the process ID appended to the filename.

The following fields are available:

Path of a local folder (such as C:\Archive) or a network folder to store the partially imported documents.

Format

• File: Archives the message body in a text file and all attachments in separate files.

• EML: Archives the message body and the attachments as a single EML file.

• XML: Archives the message metadata in an XML file (custom Kofax format).

The name of the subfolder and prefix for the archived files. You can also add predefined Fields (metadata) as subfolder names and filename prefixes. The value of these metadata is populated at the time of saving the archived files. If you do not add the "\" character in the field, all the fields are appended to the archived file names. For example, if you add {PARTIAL}\{Process-ID}, the files are stored in the PARTIAL folder with process ID appended to the filename.

The following fields are available:

Archive folder

Path of a local folder (such as C:\Archive) or a network folder to store the failed/rejected documents.

• File: Archives the message body in a text file and all attachments in separate files.

• EML: Archives the message body and the attachments as a single EML file.

• XML: Archive the message metadata in an XML file (custom Kofax format).

The name of the subfolder and prefix for the archived files. You can also add predefined Fields (metadata) as subfolder names and filename prefixes. The value of these metadata is populated at the time of saving the archived files. If you do not add the "\" character in the field, all the fields are appended to the archived file names. For example, if you add {REJECTED}\{Process-ID}, the files are stored in the REJECTED folder with process ID appended to the filename.

The following fields are available:

Create new job (default)

1. On the Process list, select a process or case.

   If the selected process or case map has any initialization variables, the parameters appear under Initialization variables.

   For rejected/failed or partially imported documents, only the metadata of the documents is passed to the relevant processes. When configuring such process maps, you can then map the metadata. Additionally, in case of rejected/failed documents, the original content of an EML is added as a document to the Job.

2. To map the parameters to the initialization variables, on the Mapping list of the initialization variable, select a dynamic value or click  and enter a static value.

Create new case

1. On the Case list, select a case map.

   If the selected case map has any initialization variables, the parameters appear under Initialization variables.

2. Select an Expression type:

   • Regular: Enter an expression to extract the case reference from a subject in the Case ref field.

   • XSL: Enter an XML expression to extract the case reference from the XML data in the Case reference field.

   • None (default): Automatically uses the job ID as the case reference.

3. Map the parameters to the initialization variables, using a dynamic or static value.

Create job in case

1. On the Process list, select a process, case, or case fragment.

   If the selected process, case, or case fragment has any initialization variables, the parameters appear under Initialization variables.

2. Select an Expression type:

   • Regular (default): Enter an expression to extract the case reference from a subject in the Case reference field.

   • XSL: Enter an XML expression to extract the case reference from the XML data in the Case reference field.

3. Map the parameters to the initialization variables, using a dynamic or static value.