Kofax Ascen 7.0 Release Script - Manual (Page 8)

Ascent® 7.0 Release Script for XML Release Notes
4 Kofax, Inc.
Features
This section contains information about features provided with the Ascent 7.0 Release Script for
XML.
Ascent Capture Values/Custom XML Elements and Document Fields
The Ascent 7.0 Release Script for XML provides an easy-to-use interface for linking Ascent Values
to Custom XML elements, document fields, and folder fields. Examples of Ascent Values include
Document index fields, Folder index fields, Batch fields, Ascent Capture Values, and Text
Constants.
The maximum length for any Ascent Value is 254 characters. If the value contains invalid
characters, the invalid characters will be automatically replaced at release with escape sequences
that are legal for XML. However, the escape sequences will also be counted as characters. The total
length of the characters entered, including escape sequences, can be no more than the maximum
length.
Refer to Invalid Characters and Escape Sequences on page 10 for more information.
Ascent Capture Value {Document GUID}
The Ascent Capture Value {Document GUID} is a new value that can be used for index fields and
release values. This Ascent Capture value is a type of document ID that is unique across the
central site and all remote sites that comprise of an Ascent Capture installation. The Document
GUID is the concatenation of the Batch GUID and the document ID number. For example, a Batch
GUID of {D3C58EE2-5627-443b-BBFA-EE7A5790482A} and a document ID of 123 will yield
{D3C58EE2-5627-443b-BBFA-EE7A5790482A} 123 as the Document GUID.
Release to XML Files
When releasing batches from Ascent Capture, the Ascent 7.0 Release Script for XML releases:
„
Images, OCR full text files, Adobe PDF documents, and/or eDocuments are released to
directories that you specify.
„
A standard XML file that contains the following batch information:
„
Standard Ascent Capture document data (index fields), batch information (batch
fields), and paths to the released files
„
Custom XML elements that you define, which can contain batch-level information that
is intrinsic to your back end system (optional)
„
Batch status information that indicates whether all documents in a batch were
successfully released
„
Document Type Definition (DTD) file that defines the elements and attributes in the XML
file
Once the document/batch data and file information for a batch is released to an XML file, the
XML file can be transformed (if necessary) into other XML formats or otherwise imported into
your back end system with an application that you provide.