Kofax Ascen 7.0 Release Script - Manual (Page 14)

Ascent® 7.0 Release Script for IBM DB2 Content Manager Enterprise 8.3/8.4 Release Notes
8 Kofax, Inc.
Additional Information
This section contains additional information about the Ascent 7.0 Release Script for IBM DB2
Content Manager Enterprise.
Unsupported Ascent Capture Features
Ascent 7.0 Release Script for IBM DB2 Content Manager Enterprise does not support the following
Ascent Capture feature.
File Name Retention
This release script does not support file name retention. Therefore, the original imported file name
will not be retained and the default numeric name will be used.
If you have enabled the “Use the original file name of image and eDocument files” check box in
the Ascent Capture Release Properties dialog box and you release a batch in Content Manager, the
release will fail with the following error message. (SPR 30293)
The specified file does not exist
.
In addition, if you set the “SupportsOriginalFileName” property to “True”
(SupportsOriginalFileName=True) in IBM DB2 Content Manager and you release a batch, the
release will fail with the same error message.
Refer to your Ascent Capture Help for more information about retention of file names (Ascent
Capture Help keyword: Release Properties dialog box).
Tip The Ascent Capture Value “{First Page Original File Name}” allows you to retain the original
file name for the first page of a document. This value can be linked to Content Manager attributes
that support Ascent Values. Notice that the Content Manager attribute type must be able to accept
all the characters that are part of the original file name and must not exceed the defined length or
release may fail.
{Index Operator’s Station ID} Ascent Capture Value
The Ascent Capture Value {Index Operator’s Station ID} has been deprecated, and replaced by
{Validation Operator’s Station ID}. It is strongly recommended that you use {Validation
Operator’s Station ID} instead.
eDocument Names Not Preserved at Release
Ascent Capture releases eDocuments in the same manner as images. This means that the original
name of the eDocument is modified and becomes a part of the image-naming scheme. Note,
however, that the original eDocument file extension is preserved and used in the final name.