File name considerations, Duplicate file names – Kofax Ascen 7.5 Release Script for FileNet Content Manager 4.5 User Manual
Page 20
![background image](/manuals/658221/20/background.png)
Ascent® 7.5 Release Script for FileNet Content Manager 4.5 Release Notes
14
Kofax, Inc.
If the content element is specified to be a multipage image type or Kofax PDF image
type, then the content element is combined with other images (if any) to form one
content element. The content element is released with the appropriate file extension as
specified by the image type. However, the content element uses the Ascent Capture file
naming scheme, which is the {Document ID}.
If the document is released with the SupportsOriginalFileName property set to FALSE,
each content element contained within the document is released with the file name
assigned by Ascent Capture
.
Notice that when the INF setting or the Ascent Capture Release module is not set, the release
script will not use the File Name Retention feature. In addition, OCR full text files and Kofax PDF
documents released from Ascent Capture do not use the File Name Retention feature, regardless
of the configuration.
Note
The SupportsOriginalFileName property is not case-sensitive.
File Name Considerations
If the Ascent Capture File Name Retention feature is enabled, problems may develop when a new
input file has the same name as a pre-existing file.
When releasing new input files with the File Name Retention feature enabled, the Ascent Capture
Release module checks the batch to see if pre-existing image files (including eDocuments) have
the same name as the new input file. Each document in the batch is checked to avoid duplicate file
names. If a match is found, the new input file is rejected and the following error message may
display:
A duplicate file name was encountered: <
FileName
>.
The rejected document will be routed to the Ascent Capture Quality Control module.
Duplicate File Names
The following case scenarios explain how a new image file may have the same name as a
pre-existing file when the Ascent Capture File Name Retention feature is enabled.
Case 1
When pages in an image file have been scanned, the file is named with a sequential number
that is assigned by Ascent Capture. However, if the document already contains an imported
file that used a similar file naming scheme (for example, 1.tif or 2.tif), the new scanned image
file may match the name of the imported file.
To illustrate, let’s say that you scanned the following pages into a document:
1.tif
2.tif
3.tif
4.tif
5.tif
The document already contains the following imported files:
1.tif
2.tif
3.tif