Destinations Tasks

Destinations tell Kofax Capture how it should handle documents received by Kofax Import Connector.

Use these tasks to add or edit destinations in Kofax Capture. For a destination, configure a set of parameters defining how messages should be imported to Kofax Capture, such as the message contents to import, the format, the batch class to use.

Use the following commands from the Destination Tasks menu of the KC Plug-In configuration window to manage destinations:

  • Add Destination: Click to create a new destination. The Destination configuration window opens.

  • Edit Destination: Select a destination in the table and click this button to edit it. The Destination configuration window opens.

  • Remove Destination: Select a destination in the table and click this button to delete it.

Following steps describe the general procedure for creating a destination. For detailed information related to specific fields, refer one of the following:

  1. Start KC Plug-In configuration. Do one of the following:
    • On a Kofax Capture Network Server remote site, start KC Plug-In from the KIC - Electronic Documents group in the Windows Start menu.

    • On other Kofax Capture installations, start Kofax Capture Administration and select Electronic Documents > Configuration.

  2. On the Destination Tasks menu, click Add Destination.
  3. On the Import settings tab, enter a Name of this destination. Optionally, add a description.
  4. Optional. Select an XML or EDI Type if you want to restrict the destination to that particular XML/EDI type, that is, only XML documents with matching namespace and root element are accepted by this destination.
    Note The default destination cannot have an XML/EDI type.
  5. Select Import content of this destination, that is, the parts of a document to be imported, and their order. Optionally, you can select to import the original content or the complete message as EML.
  6. Configure the Import Mode.
    • Select the content to convert (images versus non-image content), the format (TIFF, PDF) to convert to, and the scaling, resolution, and color of the converted image.

      • If you do not want to convert your documents, do the following:

        1. Clear both TIFF and PDF, and select one or more of the following options: Include original content, Include complete message as EML file, Include complete message as MSG file.

        2. Set Originals import mode to Import into Kofax Capture.

      • If a PDF to TIFF conversion results in a TIFF file larger than 4 GB, the Message Connector will return an error.

    • Select Message Rendering if you want to convert XML documents or metadata as images. See Render XML documents.

    • Enable VRS to preprocess incoming documents. This option is recommended for improving the quality of scanned images. See Configure VRS. You can also process PDF documents in VRS.

  7. On the Import mappings tab, select the batch class and document class. Optionally, select a folder class and form type.
    Note The selected batch class can be overwritten if you are importing XML documents that contain batch class information. If the batch class from the XML document does not exist in Kofax Capture, the following error message is displayed in the Message Connector storage: Batch class required for XmlAutoImport or generic Xml mapping does not exist.
  8. Optional. Map metadata of the imported document to Kofax Capture batch / folder / document fields. Do one of the following:
  9. Optional. On the Additional settings tab, configure custom scripts and error handling.
  10. Optional. On the Advanced Conversion and Import tab, configure advanced PDF settings.
  11. In Output PDF format, select the output format for normalized PDF files. (Default: PDF/A-1b)
    • In the Import settings tab, make sure that at least one option is selected for the Convert to field.

    • If the Normalize PDF documents to PDFA option is not selected, the incoming PDF files are not normalized to any of the selected format.

    • If the input PDF file format is not compatible to be converted to the required output format, the actual output format may be downgraded. For example, if the input file version is PDF 1.5 and if the Output PDF format field is set to PDF/A-1a, PDF/A-2a or PDF/A-3a, the output PDF format may be PDF/A-1b, PDF/A-2u or PDF/A-3u respectively. Following are some of the scenarios wherein the PDF/A compliance level may be downgraded:

      • If the input file contains text that is not extractable such as missing ToUnicode information, the output file compliance level is downgraded. For example, PDF/A-2u is downgraded to PDF/A-2b.
      • If logical structure (tagging) information is missing in the input file, the compliance level is downgraded to level B or U. For example, PDF/A-1a is downgraded to PDF/A-1b.

  12. Optional. On the Email Notification and Archiving tab, configure sending notifications to message originators and archiving of documents in a particular folder.
  13. Click OK to create the destination and restart the KC Plug-In service.
Note If you modify a batch class or form type used in an existing destination, the mappings might be lost. You have to map the fields again.