Specify output locations. Specify and validate naming of output folders and documents
Output Root
Specify the folder that can be used as shared location for reports and exceptions. Though it does not have to be used as a root folder, it is convenient to have all Barcode Director produced documents in a known location. If used in file/folder name it is identified by the <OutputRoot> macro.
The field can be edited, or use the down arrow to specify predefined location macros:
Default Folder - sets value to <MyDocuments>\BarcodeDirector\<SessionID>
Select Folder - use the Windows dialog box to select specific folder
Project File Folder - sets the value to <ProjFolder>. Replaced at runtime by the folder in which Project File is located.
Session ID - appends <SessionID> macro, which is replaced by the Session ID value at runtime.
Exceptions
Specify the folder that holds the exception files from the sessions. The default value is <OutputRoot>\Exceptions\. Its name can be edited via the Folder Name Editor dialog.
Document File
File Name
To specify the location of output documents click the Edit button to open the File Name editor dialog. Typically the name specification contains Macros to be replaced at runtime by the actual session and barcode data
Delete Document ID (separator) pages
If checked, input pages with the barcode, used to name the document,
are excluded from output
document.
For example, if the
cover pages are created solely for batch separation and are not
intended to be part of the final document delivery, check this
box to remove them
Delete Folder ID (separator) pages
If checked, input pages with barcode used to name output folders are excluded from output document.
Delete Blank Pages
If checked, removes pages considered blank. Duplex scanning creates many blank pages in the input file, and it may be desirable to remove these blank backside images from the final document.
Exceptions Processing
Specify the processing rules for Documents mode exceptions. Click on the links below to see how exceptions are processed and recommendations how to avoid these exceptions.
No Document ID exception
This exception is raised when program can not create the name of the output document file. Typical situations where this happens are:
The program fails to find the expected one or more pages with barcodes that would allow it to construct an output file name. See the No Document ID for recommendations how avoid it.
Two or more barcodes, with different values, satisfy the validation rules, consequently, the program cannot construct a unique Document ID. See Multiple Document ID for recommendations how avoid it.
Specify the action of Barcode Director:
Store Exception pages in Exceptions Folder. The offending page is copied to the exception folder.
Store Exception pages in last Document Folder. The offending page is copied to the folder which contains the last output document.
Duplicate Document ID exception
See Duplicate Document ID for recommendations how avoid it.
Specify the action of Barcode Director if the output document file the same name file already exists:
Append to existing file. Append the offending page to the existing file. Applicable only to TIFF and PDF output.
Create unique file name. A string with the format _NNNN_ is inserted in file name before the extension. For example sample.tif becomes sample._0001_.tif
Report No-Document ID exception. The exception is generated and recorded in the XML Results, and the offending pages are copied to the Exception folder.
Overwrite (only for testing). The new file overwrites the existing file, which will cause the loss of the previously stored data.
Invalid Characters exception
The barcode contains characters that cannot be used in a file name. They may be binary characters or characters not allowed in file names, such as: *?<>. See Invalid character in Document ID for recommendations how avoid it.
Specify how Barcode Director should construct the output file name if such characters are encountered at runtime:
Skip. the invalid character is removed from barcode value
Replace with: The invalid character is replaced by the character from the field to the right
Report exception. The exception is generated and recorded in XML Results, and the offending page is copied to the Exception folder.
Exception file naming
Typically an exception affects several sequential pages. The
format of the output file name is: filename.PN-M.ext
Where:
N
- the first page number
that generated an exception
in input file filename.ext
M - the last
page number that generated an exception
in input file filename.ext
For example if input document sample.tif has 5 pages and a barcode is present on page 4. Under the Separation profile no Document ID is identified for pages 1, 2, and 3. Therefore, pages 1, 2, and 3 are copied into exception file sample.P1-3.tif