Welcome to Kofax Capture Help > Administration > Batch Classes > Batch Class Import and Export - An Overview > Importing a Batch Class

Importing a Batch Class

  1. From the Administration module, on the Home tab, in the Batch Class group, click Import.
    The Open window appears.
  2. Browse to the folder where your .cab files are located.
    (Batch classes are exported as .cab files.)
  3. Select a .cab file and click Open.

    The Import/Export window appears. As soon as the Import/Export window appears, the .cab file is unpacked and prepared for import. The results of this process appear in the Unpacking results area on the window. When done, the Unpacking done. Completed message appears.

  4. When the message Unpacking done. Completed appears, click OK.

    The Import window appears.

  5. On the Import window, select the batch classes to import from the list of Available Batch Classes. Click the Add button to add them to the list of Selected Batch Classes.
    The list contains all the batch classes that were exported into the .cab file you unpacked.
  6. Select a Transfer Mode. You can choose one of the following:
    • Do not import duplicates: Does not overwrite duplicate batch class settings.
    • Save duplicates to new name: Saves duplicate batch class settings to a new name.
    • Replace duplicates with items imported: Overwrites duplicate batch class elements (such as index fields) with the ones you are importing.
  7. Click Import.
    Once the batch class is imported, it cannot be used until you publish it. In addition, you may need to recompile any custom scripts associated with the batch class.

    The Import/Export window lists the import results.

Importing Batch Classes that Export Index Data to a Database: In some cases, you may need to set up your export connectors again after you import batch classes. Consider this scenario: You import a batch class that was set up at another site. The export connector for the batch class uses field IDs to reference a back-end database, and the field IDs match the ones for the database at the other site. If the field IDs in your database do not match the field IDs from the other site, you are not able to export the index data. For this case, you do not get errors or warnings when you publish the imported batch class. However, you do get errors at export time. As a workaround, you should run a test batch through to export after you publish your imported batch classes. If problems occur at export time, set up the export connector again and republish the batch class.