3 Using Kofax Capture with Kofax Capture Export Connector - Oracle UCM

This section covers the following topics:

• "Working with Kofax Capture Batch Classes"

• "Customizing the Release Script"

• "Mapping Kofax Index Fields to CHECKIN Parameters"

• "Verifying Kofax Capture Installation"

3.1 Working with Kofax Capture Batch Classes

After you have completed the installation and configuration tasks, your Kofax Capture workstation has two published batch classes: ScannedDocsForOracleUCM and ScannedDocsForSOracleUCMParam.

Both batch classes (shown in the figure below) are set up to support the standard required Oracle Content Server check-in parameters. In addition, the batch class ScansForOracleUCMParameters illustrates how a batch class can be configured for optional Oracle Content Server parameters, such as Release Date, Expiration Date, and so forth.

Like all Kofax Capture batch classes, these Oracle Content Server batch classes are constructed using field types, index fields, form types, and document classes, which are described in the following sections.

Note: For more information about batch classes, view the Kofax Capture online help.

This section covers the following topics:

• "Folders"

• "Field Types"

• "Setting Up Field Types"

• "Document Classes"

• "Setting Up Document Class Index Fields"

• "Mapped Index Fields"

• "Form Types"

3.1.1 Folders

Folder classes define the properties of folders for a batch class. Batches are a collection of pages, documents, and folders that are organized into a hierarchy that you define. As with other elements of a batch class, you can create, edit, and delete folder classes.

In addition to organizing your documents within Kofax Capture, the real advantage to using folders comes after the documents have been released from Kofax Capture. If you ensure that the folder hierarchy in Kofax Capture matches (as closely as possible) the hierarchy used by your document management software, you can more easily import those documents into your third-party software.

Folders are created and filled with documents as the documents are processed through the Kofax Capture workflow. You can create folders manually (with batch editing), or you can allow them to be created automatically in accordance with rules you define. Likewise, you can place documents into folders manually or automatically.

Pages can be added to documents, and documents can be added to folders. Folders can be added to other folders (nesting) up to 32,000 levels. However, loose pages cannot be added to a folder (although you may have loose pages at the root level of your batch, they must be placed into a document before they are added to a folder).

3.1.2 Field Types

Installing and configuring the Kofax Capture release script sets up specific Kofax Capture field types, which are shown in the figure below. These field types are in turn used to define index fields in the sample document classes: ScannedDocsForOracleUCM and ScannedDocsForOracleUCMParam. When defining new index fields, you may use these field types, or create additional field types as needed. See "Setting Up Field Types".

3.1.3 Setting Up Field Types

To set up field types:

1. From Kofax Capture, open the Administration dialog, then select the Field Type tree view tab.

2. Right-click anywhere within the tab and select New Field Type.

   The Create Field Type dialog is displayed.

3. Click New.

4. Enter values in the fields provided.

   • On the General tab, Name and Data type are required; Description and Dictionary are optional. For Data type, Kofax Capture supports 11 ODBC-compliant types.

   • On the Values tab, you have the option of entering known values for the field type and specifying settings for Force match and Case sensitive.

5. Click OK when complete.

Note: For more information about field types, view the Kofax Capture online help.

3.1.4 Document Classes

Installing and configuring the Kofax Capture release script as described in Section 2.3, "Installing Kofax Capture Export Connector," and Section 2.4, "Configuring Kofax Capture," sets up the following sample Kofax Capture document classes:

• ScansForOracleUCM

• ScansForOracleUCMParameters

Each document class that is used with Kofax Capture includes the following:

• Index fields

• Attributes for the index fields

• At least one form type

Note: index fields that are defined for a document class are mapped to Oracle Content Server check-in parameters. See "Mapping Kofax Index Fields to CHECKIN Parameters" for more information.

3.1.5 Setting Up Document Class Index Fields

Use the following procedure to set up document class index fields.

1. From Kofax Capture, open the Administration dialog, then select the Document tree view tab.

2. Right-click a document class and select Properties.

   The Document Class Properties dialog is displayed. For examples of the dialogs for ScannedDocsForOracleUCM and ScannedDocsForOracleUCMParam, see "ScannedDocsForOracleUCM" and "ScannedDocsForOracleUCMParam".

3. Click New.

4. Enter the following information:

   • Name

     Enter a descriptive name.

   • Field Type

     Select the appropriate field type from the drop-down list.

   • Default

     If desired, enter a default value to populate the index field.

     Tech Tip: If the corresponding Oracle Content Server metadata field is required, entering a default value is recommended. Check-in will fail if a required metadata field does not contain a value.

   • Required

     Select True if the field must contain a value during validation.

     Tech Tip: If the corresponding Oracle Content Server metadata field is required, set this field to True.

   • Verify

     Set to False.

   • Hidden

     Set to False.

   • Sticky

     Set to False.

   • Total

     Set to False.

5. When you are done adding the index field, click Apply to continue or OK to exit.

3.1.6 Mapped Index Fields

This section covers the following topics:

• "ScannedDocsForOracleUCM"

• "ScannedDocsForOracleUCMParam"

3.1.6.1 ScannedDocsForOracleUCM

The ScannedDocsForOracleUCM document class includes "core" index fields that are mapped to Oracle Content Server standard required CHECKIN parameters.

Figure 3-1 Mapped Index Fields for ScannedDocsForOracleUCM Document Class

3.1.6.2 ScannedDocsForOracleUCMParam

The ScannedDocsForOracleUCMParam document class includes "core" index fields that are mapped to Oracle Content Server standard required check-in parameters, plus additional "example" index fields that could be mapped to Oracle Content Server optional check-in parameters using the CHECKIN Parameters Editor (see "Accessing CHECKIN Parameters Editor").

Figure 3-2 Mapped Index Fields for ScannedDocsForOracleUCMParam Document Class

Each of the Oracle Content Server document classes is configured with the index fields listed in the table below. The index fields that are defined for both document classes (Content ID, Type, Title, Author, and Security Group) are mapped to Oracle Content Server parameters that are required for successful check-in of documents to Oracle Content Server.

The additional index fields defined for ScannedDocsForOracleUCMParam are provided in the document class for illustration purposes only. They are examples of index fields that might hypothetically be mapped to Oracle Content Server parameters using the CHECKIN Parameters Editor.

ScannedDocsForOracleUCM Index Fields	ScannedDocsForOracleUCMParam Index Fields
Content ID	Content ID
Type	Type
Title	Title
Author	Author
Security Group	Security Group
N/A	Release Date
N/A	Release Time
N/A	Finished
N/A	LIDebug
N/A	Create Date
N/A	Create Time
N/A	Revision Label
N/A	Expiration Date
N/A	Expiration Time
N/A	Do Security Check

3.1.7 Form Types

Installing and configuring the Kofax Capture release script as described in chapters 1 and 2 sets up the two sample document classes with the form types shown in the figure below.

The form types (SimpleForm and SimpleFormParameters) are provided for the Oracle Content Server document classes because at least one form type must be defined for a document class. Since a form type defines a unique form, you will set up your own form types to meet the needs of your specific application.

Note: For more information about form types, view the Kofax Capture online help.

3.2 Customizing the Release Script

This section covers the following topics:

• "Accessing the Setup Dialogs"

• "Using the Index Storage Tab"

• "Setting Index Values"

• "Using the Document Storage Tab"

• "Using the Image Format Tab"

• "Specifying PDF Settings"

• "Setting File Type of Released Images"

• "Selecting Multipage TIFF Output File Types"

• "Selecting TIFF, JPG, or PCX Output File Types"

• "Selecting Adobe Acrobat Capture PDF Output File Types"

• "Specifying Adobe Acrobat Capture PDF Settings"

• "Using the Server Tab"

• "Setting URL, User Name, and Password"

• "Setting Primary/Alternate File Formats"

• "Setting Workflow Status"

• "Setting Options for Adobe Acrobat Capture PDF Files With Errors"

• "Accessing CHECKIN Parameters Editor"

3.2.1 Accessing the Setup Dialogs

Use the following procedure to access the setup dialogs for the Kofax Capture release script.

1. From Kofax Capture, open the Administration dialog, then select the Document tree view tab.

2. Expand a Oracle Content Server batch class, right-click its document class, and select Release Scripts.

   The Release Script dialog is displayed.

3. In the list of Assigned Release Scripts, highlight Kofax Capture Export Connector - Oracle UCM version, and click Setup.

   The Text Release Setup dialog is displayed. This dialog has the following tabs :

   • Index Storage Tab

     Used for index value settings.

   • Document Storage Tab

     Used for release directory and Acrobat Capture settings.

   • Image Format Tab

     Used for releases images as file type settings.

   • Server Tab

     Used for Oracle Content Server settings.

3.2.2 Using the Index Storage Tab

Use the Index Storage tab to set index values for the batch class. The Kofax Capture release script establishes assignments for the required information field items found in an initial Oracle Content Server installation. The values assigned to the index fields are supplied from the Validation module during Kofax Capture batch processing.

Note: You must add index fields to a document class before they are available to assign as index values in a customized release script. See "Setting Up Document Class Index Fields". By default, all index fields currently defined for the selected document class will be in the list of index values.

Note: For more detailed information about this tab, see "Index Storage Tab".

3.2.3 Setting Index Values

To set up index values:

1. Add the desired Index Field to document class properties. See "Setting Up Document Class Index Fields" or "Mapped Index Fields".

2. Navigate to the Index Storage tab of the Oracle Content Server Release Setup dialog.

3. Click Add.

   A blank index value is added to the end of the list of existing index values.

4. Click the context menu button to the right of the blank index value.

5. From the Index Fields menu option, select an index field.

6. Click Apply to continue or OK to exit the dialog.

Note: When selecting index values, do not choose Kofax Capture Values or Text Constant.

Note: If you want an index value to map to a Oracle Content Server optional check-in parameter, you must use the CHECKIN Parameter Editor to create the mapping. However, the following standard check-in parameters do not need to be mapped, because they are assigned automatically: Content ID Type Title Author Security Group Account (if enabled in Oracle Content Server)

3.2.4 Using the Document Storage Tab

Use the Document Storage tab to view or change the directory paths for released files and to set how Kofax Capture monitors the Acrobat Capture PDF conversion process.

Note: For more detailed information about this tab, see "Document Storage Tab".

3.2.5 Using the Image Format Tab

Use the Image Format tab to set the format (file type) of released images.

Note: For more detailed information about this tab, see "Image Format Tab".

3.2.6 Specifying PDF Settings

Use the Settings button to open the Adobe Acrobat Capture Settings dialog box where you can specify PDF settings.

Note: For more detailed information about this tab, see "Adobe Acrobat Capture Settings".

3.2.7 Setting File Type of Released Images

Kofax Capture supports releasing scanned images in a number of output file formats. The following image files are supported when using Kofax Capture:

• JPG - JPG Compression

• Multipage TIFF - CCITT Group 3

• Multipage TIFF - CCITT Group 3/2D

• Multipage TIFF - CCITT Group 4

• Multipage TIFF - JPEG Compression

• Multipage TIFF - Uncompressed

• PCX - PackBytes

• Adobe Acrobat Capture PDF (from JPEG)

• Adobe Acrobat Capture PDF (from Multipage TIFF)

• Adobe Acrobat Capture PDF (from PCX)

• Adobe Acrobat Capture PDF (from Single Page TIFF)

• TIFF - CCITT Group 3

• TIFF - CCITT Group 3/2D

• TIFF - CCITT Group 4

• TIFF - JPEG Compression

• TIFF - Uncompressed

3.2.8 Selecting Multipage TIFF Output File Types

Select a Multipage TIFF output file type when you have more than one TIFF image in a batch, and you would like to have all of those images bundled together and checked into the Oracle Content Server as one content item.

1. Navigate to the Image Format tab on the Oracle Content Server Release Setup dialog.

2. In the Release Images As Image file type drop-down list, click a Multipage TIFF Output File Type.

3.2.9 Selecting TIFF, JPG, or PCX Output File Types

Select a TIFF, JPG or PCX output file type if you want to check a file in one of those formats into Oracle Content Server as both the primary (native) and alternate (web viewable) file.

When you select TIFF, JPG or PCX, the first graphic in each batch is checked into Oracle Content Server. Because of this, you may want to use Multipage TIFF (see "Selecting Multipage TIFF Output File Types") if you have more than one graphic in a batch. Alternatively, you could ensure that each batch contains only one graphic.

1. Navigate to the Image Format tab on the Oracle Content Server Release Setup dialog.

2. In the Release Images As Image file type drop-down list, click a TIFF, JPG or PCX Output File Type.

3.2.10 Selecting Adobe Acrobat Capture PDF Output File Types

Select Adobe Acrobat Capture PDF as the output file type if you want to check a PDF file into Oracle Content Server as the primary (native) or alternate (web viewable) file.

Note: Selecting Adobe Acrobat Capture PDF as the output file type requires the use of Adobe Acrobat Capture. Before continuing with the following procedure, read through and complete "Configuring Adobe Acrobat Capture".

1. Navigate to the Image Format tab on the Oracle Content Server Release Setup dialog.

2. In the Release Images As Image file type drop-down list, click Adobe Acrobat PDF (from Multipage TIFF).

   The Settings button becomes available.

3.2.11 Specifying Adobe Acrobat Capture PDF Settings

When you choose to release images as Adobe Acrobat Capture PDF (from Multipage TIFF), you then use Settings button to specify Adobe Acrobat Capture workgroup hub, watched folder, workflow, and other settings.

1. On the Image Format tab of the Oracle Content Server Release Setup dialog, click Settings.

   
   

   Note: The Adobe Acrobat Capture PDF (from Multipage TIFF) setting will work with both single page and multiple-page TIFF files.

   
   

2. Select the location of the Adobe Acrobat Capture workgroup hub:

   1. Click the browse button next to the Workgroup Hub field.

   2. Navigate to the location of the Hub directory. For example:

      mapped drive/Program Files/Adobe/Adobe Acrobat Capture 3.0/Hub
      

   3. Click OK.

   Upon selection of a workgroup hub, the Dictionaries and Workflows drop-down lists will be populated with available options.

3. Select the location of the Adobe Acrobat Capture Watched Folder:

   1. Click the browse button next to the Watched Folder field.

   2. Navigate to the location of the Watch directory. For example:

      mapped drive/Program Files/Adobe/Adobe Acrobat Capture 3.0/Watch
      

   3. Click OK.

4. Select Formatted Text & Graphics from Page Content drop-down list.

5. If desired, select options for Language, PDF Document Settings, and Dictionaries.

6. Select StellentScans from Workflows drop-down list.

7. If desired, select options for Suspect Regions and Advanced Settings.

8. Click OK.

3.2.12 Using the Server Tab

The Server tab on the Oracle Content Server Release Setup dialog is used to specify settings for Oracle Content Server URL, user name, and password; to select options for workflow and primary/alternate file check in formats; and to access the CHECKIN parameters editor.

3.2.13 Setting URL, User Name, and Password

These settings were made during installation of Kofax Capture and may be changed using the fields provided on the Server tab if necessary.

3.2.14 Setting Primary/Alternate File Formats

Kofax Capture lets you control how your released files (as specified on the Document Storage Tab) are checked into Oracle Content Server.

There are two drop-down menus available-one for the primary file and one for the alternate file. Within each menu, you can choose: Image, Kofax PDF, Adobe Acrobat Capture PDF, or OCR full text. The Alternate file menu also includes a [None] option in case you do not want to check in an alternate file.

You can use the menus to, for example, select Image at the primary (native) file and Adobe Acrobat Capture PDF as the alternate (web-viewable) file.

Note: Oracle Content Server will not allow two files with the same file extension (such as .pdf) to be both the primary and alternate file.

Note: For information on using Adobe Acrobat Capture and checking in Adobe Acrobat Capture PDFs, see Appendix B, "Using Adobe Acrobat Capture".

3.2.15 Setting Workflow Status

The Kofax Capture release script enables you to initiate an existing workflow in Oracle Content Server when an item is released from Kofax Capture.

Note: The workflow setting on this dialog refers to a Oracle Content Server workflow, not an Adobe Acrobat Capture workflow.

Note: An active workflow must exist in Oracle Content Server before an item released from Kofax Capture can enter it.

1. Navigate to the Server tab on the Oracle Content Server Release Setup dialog.

2. Set the workflows status using the Allow Workflows check box.

   • Select the check box to enable initiation of workflows when content items are released from Kofax and checked into Oracle Content Server.

   • Clear the check box to disable initiation of workflows when content items are released from Kofax and checked into Oracle Content Server.

     
     

     Note: The Kofax Capture release script will initiate check in of a content item revision if the user specifies an existing content ID on the Validation dialog.

     
     

   • If the Allow Workflows check box is not selected, the revision will be checked in unconditionally.

   • If the Allow Workflows check box is selected, the content item identified by the user (on the Validation dialog) must be checked out of Oracle Content Server before Kofax Capture initiates check in. If the content item is not checked out, the check in will fail with an error message.

3.2.16 Setting Options for Adobe Acrobat Capture PDF Files With Errors

When an Adobe Acrobat Capture PDF file contains an error, you can stop it from being checked into Oracle Content Server so you can review it.

With the "Check In Adobe Acrobat Capture PDF with Errors" option, you can allow the check in of a PDF generated by Adobe Acrobat Capture that has any errors in the Adobe Acrobat Capture finished document log. In addition, you can choose to keep the PDF file, so it remains in the release directory where you can review it.

To set PDF error options:

1. Navigate to the Server tab on the Oracle Content Server Release Setup dialog.

2. Choose the PDF error checking option:

   • Leave the Check In Adobe Acrobat Capture PDF with Errors option unchecked to ensure that all PDF files containing errors are not checked into Oracle Content Server.

   • Check the Check In Adobe Acrobat Capture PDF with Errors option to check all PDF files into Oracle Content Server, even if they contain errors.

3. Determine if the files with errors remain or are deleted:

   • To keep the PDF files with errors in the release directory, select the Keep primary and alternate files in the release directory when the check in fails option, which is selected by default.

   • To delete PDF files with errors from the release directory, clear the Keep primary and alternate files in the release directory when the check in fails option.

   You may also want to use the Salvage PDF documents option, described Appendix C, "Setting Global Options".

3.2.17 Accessing CHECKIN Parameters Editor

When you want to map Kofax Capture index fields to Oracle Content Server CHECKIN parameters, you use the CHECKIN Parameters Editor, which is accessed using the following procedure.

1. Navigate to the Server tab on the Oracle Content Server Release Setup dialog.

2. Click the CHECKIN Service Parameters button.

   The CHECKIN Parameters Editor dialog is displayed.

Note: For information on how to create mappings, see "Mapping Kofax Index Fields to CHECKIN Parameters".

3.3 Mapping Kofax Index Fields to CHECKIN Parameters

When a Kofax Capture release script is used to check documents into Oracle Content Server, one of two Oracle Content Server IdcCommand services is used:

• The CHECKIN_ARCHIVE service is used if the Allow Workflows check box is selected on the Server tab of the Oracle Content Server Release Setup dialog . See "Setting Workflow Status".

• The CHECKIN_UNIVERSAL service is used if the Allow Workflows check box is not selected on the Server tab of the Oracle Content Server Release Setup dialog. See "Setting Workflow Status".

Each CHECKIN service specifies certain required parameters to successfully execute the content item check-in process. Other parameters may be specified but are not required.

Note: For more information on Oracle Content Server CHECKIN services and parameters, see the IdcCommand for Java Command Utility Reference Guide.

This section covers the following topics:

• "Setting Up Mappings for Required Parameters"

• "Setting Up Mappings for Optional Parameters"

• "Setting Up Date and Time Parameters"

• "Debugging Using LIDebug Parameter"

3.3.1 Setting Up Mappings for Required Parameters

When using Kofax Capture, it is necessary for Kofax Capture to have, at a minimum, index fields that correspond to the content information (metadata) fields that Oracle Content Server requires for content item check in. The following list of index fields must exist in the Kofax document class or the batch class.

• Content ID (unless auto-generation of Content IDs is enabled in Oracle Content Server)

• Type

• Title

• Author

• Security Group

• Account (if security accounts are enabled)

Note: Index fields must be named exactly as they are shown in the list above, so that the release script can recognize them as required fields and correctly format them for Oracle Content Server.

3.3.2 Setting Up Mappings for Optional Parameters

If you want to specify other check-in parameters, for example, release date, expiration date, and so forth, use the following procedure.

Note: You should have a solid understanding of Oracle Content Server CHECKIN services and parameters before proceeding to set up mappings. Invalid parameters will cause a batch to fail during release/check-in.

1. Set up index fields for the desired parameters. See "Setting Up Document Class Index Fields".

2. Set up index values for the Kofax Capture release script. See "Setting Index Values".

3. Open the CHECKIN Parameters Editor. See "Accessing CHECKIN Parameters Editor".

4. On the CHECKIN Parameters Editor dialog, click Add.

   The Parameter Detail dialog is displayed.

   
   

5. From the User Interface Name drop-down list, select the desired index field.

6. In the Oracle Content Server Parameter field, enter the name of the parameter.

   
   

   Note: Pay close attention to spelling and syntax when entering the parameter.

   
   

7. Click OK.

   The mapping will be displayed in the CHECKIN Parameters Editor list.

8. Add, edit, or delete mappings as desired.

9. When you are finished, click Save to exit and save your changes, or click Cancel to exit without saving your changes.

10. Click Yes to confirm the action.

11. Click OK to exit the Oracle Content Server Release Setup dialog.

12. Click Close to exit the Release Scripts dialog.

13. Publish the batch class so that your changes are in effect when you next use the batch class to import or scan documents.

3.3.3 Setting Up Date and Time Parameters

Oracle Content Server date fields include both the date and the time in one field. Kofax Capture uses separate fields for date and time. Use the following procedure to concatenate date and time into a single check-in parameter.

1. Set up an index field for the date field (for example, Release Date). Be sure to use the Date field type when defining the index field.

2. Set up an index field for the time field (for example, Release Time). Be sure to use the Time field type when defining the index field.

3. Use the CHECKIN Parameters Editor to map the date index field to the desired Oracle Content Server check-in parameter. For example, map Release Date to dInDate.

4. Use the CHECKIN Parameters Editor to map the time index field to the same Oracle Content Server check-in parameter. For example, map Release Time to dInDate.

3.3.4 Debugging Using LIDebug Parameter

If a mapping LIDebug:LIDebug is created, and if the value is set to TRUE during the validation step, the .hda data that is passed from Kofax Capture to Oracle Content Server will be displayed when the release script is run. This allows the user to verify that the correct data and parameters are being passed to the Oracle Content Server.

3.4 Verifying Kofax Capture Installation

Perform the following tasks to verify that Kofax Capture is installed and configured correctly.

• "Create a Batch"

• "Process Batch: Scan Queue"

• "Process Batch: Validation Queue"

• "Process Batch: Release Queue"

Note: Before proceeding, make sure that Oracle Content Server is running and that the Kofax dongle (hardware key) is in place.

3.4.1 Create a Batch

To create a batch:

1. On the Windows taskbar, click the Start button, then select Programs, then Kofax Capture, then Batch Manager.

2. Select File then New Batch.

3. In Batch class drop-down list, select ScansForOracleUCM.

4. Click Save.

5. Click Close.

   The new batch is displayed in the Batch Manager main dialog. The batch should be at the "Scan" queue and should show a "Ready" status.

3.4.2 Process Batch: Scan Queue

After creating the batch, perform the following steps from the Kofax Capture Batch Manager main dialog.

1. Select File then Process Batch.

   The Scan module is displayed.

2. Select Software Import from the drop-down list.

3. Select Scan then Start.

   The Import dialog is displayed.

4. Select a sample TIFF file, and click Open.

   A TIFF image is added to the batch contents.

5. Select Batch then Close.

6. Click Yes to confirm the action.

   In the Batch Manager main dialog, the batch should be at the Validation queue and should show a "Ready" status.

3.4.3 Process Batch: Validation Queue

After running the scan queue, perform the following steps from the Kofax Capture Batch Manager dialog.

1. Select File then Process Batch.

   The Validation module is displayed.

2. Enter the required Oracle Content Server Field Info values.

   Specify a Content ID if necessary, based on this information:

   • Use the default batch with the default Content ID: The content will be checked in with a unique suffix added to the Content ID Kofax0001.

   • Do not specify a Content ID (you can remove the default Content ID by changing the batch or by deleting the Content ID in the validation step): If Oracle Content Server is configured to automatically assign a Content ID, the content is checked in with this automatic ID. If Oracle Content Server is not configured to assign a Content ID, an error message is displayed during the release process.

   • Specify a Content ID: The content is checked into Oracle Content Server with the specified Content ID and without a unique suffix added. If a content item with the same Content ID is already checked in, the new document is checked in as a new revision of the existing content item.

3. Select Batch then Close.

4. If prompted, click Yes to save data before closing document.

   In the Batch Manager main dialog, the batch should be at the Release queue and should show a Ready status.

3.4.4 Process Batch: Release Queue

After running the validation queue, perform the following steps from the Kofax Capture Batch Manager dialog.

1. Select File then Process Batch.

   If the release queue runs without error, the TIFF image is checked into Oracle Content Server.

   If the release queue results in errors, check the error messages.

2. You may exit the Batch Manager module.