The Administration Module
Kofax Capture Administrator's Guide
folder class. With this method, there is no need to manually sort your documents before
scanning them. Documents with the same index field value can be scanned in any order,
and auto-foldering places them all in the same folder.
If a match is found, then the document is placed in the folder and becomes the last
document in that folder. If more than one folder matches, then the last matching folder
(the one at the end of the hierarchy in the batch ordering) is used. All matching uses a
case-insensitive string comparison. For example, “cat” and “CaT” are treated as a match.
Note that “01” and “1” do not match since a string comparison (rather than numeric) is
used, irrespective of the field type.
If a matching folder is not found, then a new folder is created. In this case, the folder
class is the one specified in the folder creation rule. After the new folder is created, the
document is moved into that folder.
Once a folder has been created, the folder index field is set to the value of the
corresponding document index field. The confidence of the folder index field is set to the
same value as that of the document index field. At this point, the values of all other folder
index fields are blank, and their confidence values are zero. Blank folder index fields may
not appear blank during validation if the Validation module applies a default value.
Use this method to organize your documents into logical folder groups within Kofax
Capture. In order for your export connector and document management software to
make use of this structure, you need to configure the Kofax Capture foldering rules so
that the resulting folder hierarchy can be recognized by them. For example, the folder
name property in an export connector should typically be set to equal the value of the
corresponding folder index field in Kofax Capture.
There are three variations on this method of auto-foldering.
▪ unique (null as value): If you select this method, a blank document index field creates
an “unnamed” folder and places the document in that folder. All the documents with
blank index fields end up in the same folder.
▪ unique (null as wildcard character): If you select this method, a blank document index
field matches any existing folders with the appropriate folder class, irrespective of the
value. If there is more than one matching folder, then the last one is used.
▪ unique (null as error): If you select this method, a blank document index field results
in an error, and puts the batch into an error state.
2 Create When Value is Not Null
This method (also referred to as “not blank”) is best used in cases in which the sequence
of documents is used to determine folder grouping, instead of the unique value of an
With this method, if the document index field value is blank, then the document is
moved to the most recently created folder. If no folder has been created by this algorithm,
but a folder already exists, then the last existing folder is used, regardless of the folder
class. If the document index field value is not blank, then a new folder is created, whether
or not the index field value matches that of an existing folder.
The key concept with this method is that a folder is created when any non-blank value
is recognized, even if it is the same value repeatedly. You may find this useful in cases
in which “special” documents are inserted in the batch to flag the beginning of a new
folder. For instance, a particular document may have a patch code that always indicates
the creation of a new folder. It is the sequence of these documents, not the value, that
identifies the folder grouping.
However, if no folders exist, and a document with a blank index field is processed, the
document is rejected with the following note: