Third-party software is copyrighted and licensed from Kofax's suppliers. This product includes
software developed by the Apache Software Foundation (http://www.apache.org/).
This product is protected by U.S. Patent No. 6,370,277.
THIS SOFTWARE CONTAINS CONFIDENTIAL INFORMATION AND TRADE SECRETS OF KOFAX,
INC. USE, DISCLOSURE OR REPRODUCTION IS PROHIBITED WITHOUT THE PRIOR EXPRESS
WRITTEN PERMISSION OF KOFAX, INC.
Kofax, the Kofax logo, Ascent Capture, the Ascent Capture logo, and Ascent are trademarks or
registered trademarks of Kofax, Inc. in the U.S. and other countries.
Hummingbird DM, DOCSFusion, and Hummingbird Records Management are registered trademarks
of Hummingbird Ltd.
Microsoft and Windows are registered trademarks of Microsoft Corporation.
All other product names and logos are trade and service marks of their respective companies.
U.S. Government Rights Commercial software. Government users are subject to the Kofax, Inc. standard
license agreement and applicable provisions of the FAR and its supplements.
You agree that you do not intend to and will not, directly or indirectly, export or transmit the Software
or related documentation and technical data to any country to which such export or transmission is
restricted by any applicable U.S. regulation or statute, without the prior written consent, if required, of
the Bureau of Export Administration of the U.S. Department of Commerce, or such other governmental
entity as may have jurisdiction over such export or transmission. You represent and warrant that you
are not located in, under the control of, or a national or resident of any such country.
DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE
DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY
INVALID.
System Requirements ...................................................................................................................................2
Hummingbird DM Server Support .....................................................................................................2
Hummingbird Records Management Support .................................................................................2
Client Operating System Support .......................................................................................................2
Administration and Release Workstations – Additional Requirements .......................................2
Features ..........................................................................................................................................................4
Ascent Capture Value {Document GUID} .........................................................................................4
Ascent Values / DM Index Fields .......................................................................................................4
Folder Support .......................................................................................................................................5
Release to Records Management System ...........................................................................................6
Online Help Available for Release Setup ...........................................................................................6
Image Support ........................................................................................................................................7
Kofax PDF Support ........................................................................................................................7
Adobe PDF Support .......................................................................................................................7
OCR Full Text Support ..................................................................................................................7
eDocument Support .......................................................................................................................7
Additional Information ................................................................................................................................8
Unsupported Ascent Capture Features ..............................................................................................8
File Name Retention .......................................................................................................................8
Access to Documents and Folders ......................................................................................................8
{Index Operator’s Station ID} Ascent Capture Values .....................................................................9
Context Menu Removed From the Folder Hierarchy ......................................................................9
Image Format Tab ................................................................................................................................28
General Settings Tab ...........................................................................................................................29
Publishing a Batch Class ............................................................................................................................30
Known Problems ........................................................................................................................................32
Using Duplicate User Names .....................................................................................................37
Releasing Documents With Multiple Release ..........................................................................37
Appendix A – Data Type Conversion .....................................................................................................38
Ascent Value Data Types ...................................................................................................................38
Text Constants ......................................................................................................................................38
Appendix B – Kofax Technical Support ..................................................................................................39
Kofax, Inc.v
Contents
viKofax, Inc.
Introduction
This document contains the release notes for Ascent 7.5 Release Script for Hummingbird DM,
which supports Hummingbird DM 6.0. This release script releases images, OCR full text files, PDF
documents, eDocuments, and index values from Ascent Capture into your DM repository.
Please read these notes carefully as they contain information not included in the Ascent Capture
Help or printed documentation.
Additional Documentation
These release notes are a supplement to the following:
Ascent Capture Advanced FeaturesGuide
Ascent Capture Release Notes
Getting Started with Ascent Capture guide
Installation Guide for Ascent Capture and Ascent Capture Internet Server
Learning Ascent Capture guide
Help provided from any of the Ascent Capture modules
Help provided with Ascent 7.5 Release Script for Hummingbird DM
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
For more information about Hummingbird DM or other Hummingbird products, contact your
Hummingbird representative or refer to the documentation that came with your Hummingbird
DM product.
Tip For additional information about Kofax products, visit our Web site at www.kofax.com and
go to the Technical Support pages. The Technical Support Web pages provide product-specific
information, such as current revision levels, the latest drivers and software patches, technical tips,
and a searchable knowledgebase. In addition, updates to product documentation (if any) are
available from these pages.
Kofax, Inc.1
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
System Requirements
Ascent 7.5 Release Script for Hummingbird DM requires the following components to be installed
prior to installing this release script.
Hummingbird DM Server Support
Ascent 7.5 Release Script for Hummingbird DM requires the following network server
components:
Hummingbird DM Server 6.0
Hummingbird DM Web Server 6.0
Hummingbird DM API 6.0
Hummingbird DM Extension API 6.0
Note This release script was tested against a Hummingbird DM Server 6.0.3 on a Windows 2003
Server (with Service Pack 1) and Microsoft SQL Server 2000 (with Service Pack 4).
Hummingbird Records Management Support
Ascent 7.5 Release Script for Hummingbird DM supports the following Hummingbird Records
Management systems:
Hummingbird Records Management Server 6.0
Client Operating System Support
Ascent 7.5 Release Script for Hummingbird DM supports the following client platforms:
Windows 2000 Professional with Service Pack 4
Windows 2000 Server with Service Pack 4
Windows Server 2003 with Service Pack 1 (Standard or Enterprise Edition)
Windows XP Professional with Service Pack 2
Note At the time of publishing these release notes, Ascent 7.5 Release Script for Hummingbird
DM was certified with the Service Packs listed above.
Administration and Release Workstations – Additional Requirements
The Ascent Capture Administration and Release workstations must have the following
components installed:
Ascent Capture 7.5 with Service Pack 1 or higher, Kofax Capture 8, or Kofax Capture 9
Hummingbird Windows Explorer DM Extension 6.0
2Kofax, Inc.
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Source Code
The source code for Ascent 7.5 Release Script for Hummingbird DM is provided and it is located
on the Ascent 7.5 Release Script for Hummingbird DM 6.0 installation CD in the
Hummingbird\DM6 folder. The source code can be opened, edited, and compiled in Visual
Basic 6.0 with Service Pack 6.
X To modify the release script
1Install the Hummingbird DM release script. Refer to Installing the Release Script on page 18
for the installation instructions. When you install the Hummingbird DM release script,
you will install the required components referenced in the source code.
2Open, make any desired modifications, and compile the Hummingbird DM source code
in Visual Basic.
3Copy the newly created DMRel6_v7.dll to the installation directory (for example,
C:\Program Files\Ascent\CAP\DMRel6_v7\DMRel6_v7.dll). When you are prompted
to replace the existing file, select “Yes.” You will need to repeat this procedure on each
Administration and Release workstation that will be using the Hummingbird DM release
script. You may want to make a copy of the file for backup purposes, and store the copy in
a safe location.
Note In order to successfully modify and compile the release script, development must occur on a
workstation with the appropriate versions of Ascent Capture, CAPTools, and the Hummingbird
DM release script previously installed. To use the modified release script, you must replace the
Hummingbird release script DMRel6_v7.dll with the modified version on the client workstation.
If you receive an access denied error, you will need to close the Administration module.
Refer to the documentation that came with your Hummingbird DM product and Visual Basic
documentation for assistance.
Kofax, Inc.3
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Features
This section contains information about features provided with Ascent 7.5 Release Script for
Hummingbird DM.
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 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.
Ascent Values / DM Index Fields
Ascent 7.5 Release Script for Hummingbird DM provides an easy-to-use interface for linking
Ascent Capture Ascent Values to DM index fields. Examples of Ascent Values include Document
index fields, Folder index fields, Batch fields, Ascent Capture Values, and Text Constants. The
names of “required” DM index fields are marked with an asterisk (*), giving you a visual indicator
that certain fields must be linked.
DM Custom Constants
Allowed values for DM index fields defined in a DM profile are available for selection from the
Ascent 7.5 Release Script for Hummingbird DM 6.0 — Release Setup dialog box. This allows you
to easily link DM custom constants to DM index fields.
Excluding DM Index Fields
If desired, you can exclude certain DM index fields from the list of fields to be linked during
release setup. You do this by creating the ACFusion.INI file in the Ascent root directory (for
example, C:\Program Files\Ascent).
Refer to Excluding DM Profile Attributes on page 11 for more information about excluding DM
index fields.
Security
Options available with the Hummingbird DM release script allow document access rights and
folder access rights to be defined for selected DM groups and users during release setup. One
example is that users can be granted access rights that allow the profile of a released document
and/or user-defined folder to be edited.
Refer to Access to Documents and Folders on page 8 for more information about security options.
4Kofax, Inc.
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Versioning Options
Ascent 7.5 Release Script for Hummingbird DM supports two methods for versioning documents:
Version using Document Number Instead of the Document Name: This is a feature that
allows you to version your documents using the Hummingbird DM document number.
The document number is created by Hummingbird DM. This feature is available on the
General Settings tab.
Version Document: This method allows you to version your documents using the
document name.
Note that if you select the “Version using the document number instead of the Document name”
option, the following options will be unavailable on the Document Settings tab:
Version document
Create exception document
Create new document
DM Libraries and Profiles
When setting up Ascent 7.5 Release Script for Hummingbird DM, you can easily select the DM
library and profile to use for releasing images. The Ascent 7.5 Release Script for Hummingbird
DM 6.0 – Release Setup dialog box honors access privileges defined for your Hummingbird DM
users, and makes accessible only those libraries and profiles allowed for the logged in user. The
Hummingbird DM release script supports all libraries, including default, remote, and
independent libraries.
Keywords
For profiles that contain keyword fields, the Hummingbird DM release script allows you to add
one or more keywords to a document. You can also control how new keywords are handled. For
example, you can create new keywords in the DM repository, or skip keywords not found in the
indexed document.
Duplicate Documents
Ascent 7.5 Release Script for Hummingbird DM offers three options for handling duplicate
documents. For example, you can specify that duplicate documents be:
Created as new major versions to existing documents
Created as exception documents, and given unique exception document names
Created as new documents with the same name as the existing documents
Folder Support
Ascent 7.5 Release Script for Hummingbird DM displays folders from a selected library in a
hierarchical tree view that provides an easy-to-use format for choosing the DM folder to select or
create at release time. From the Ascent 7.5 Release Script for Hummingbird DM 6.0 – Release
Setup dialog box, you can add, rename, and delete user-defined DM folders that have not yet been
created in the DM repository. Simply select an Ascent Value or specify a text constant to find or
create the DM folder.
Kofax, Inc.5
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Release to Records Management System
Ascent 7.5 Release Script for Hummingbird DM copies document images, OCR full text files, PDF
documents, eDocuments, and index values from Ascent Capture into your DM repository.
Optionally, you can release documents into your Hummingbird Records Management system.
For more information about releasing to Records Management, refer to the Help that is available
with the Ascent 7.5 Release Script for Hummingbird DM (Help keyword: Records Management).
Integrated Release Setup
Ascent 7.5 Release Script for Hummingbird DM provides an easy-to-use setup dialog box
available from the Ascent Capture Administration module. This dialog box allows you to specify
release settings at batch class setup time that control how documents are released into your DM
repository.
SecurityBoost Supported
Ascent 7.5 Release Script for Hummingbird DM supports the Ascent Capture SecurityBoost
feature. The SecurityBoost feature allows you to enhance Ascent Capture security for systems
using Windows XP and Windows 2000.
Refer to your Ascent Capture Help for more information about the SecurityBoost feature. (Ascent
Capture Help keyword: SecurityBoost > about)
Online Help Available for Release Setup
Ascent 7.5 Release Script for Hummingbird DM Help is installed with your release script. It is
available from the Administration module when you are setting up your release script. You can
click the Help button from the Ascent 7.5 Release Script for Hummingbird DM 6.0 — Release
Setup dialog box to display help information about release options.
6Kofax, Inc.
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Image Support
This release script supports the following file formats/compression formats:
Multipage TIFF with Group 3, Group 3/2D, and Group 4 Compression
Multipage TIFF with JPEG Compression
Multipage TIFF — Uncompressed
JPG with JPEG Compression
Kofax PDF
Adobe PDF from JPEG
Adobe PDF from TIFF
Kofax PDF Support
With Ascent 7.5 Release Script for Hummingbird DM, you can release Kofax PDF documents into
your Hummingbird DM repository. Kofax PDF is bundled with Ascent Capture and does not
require additional software implementation. Kofax PDF documents can be saved in the following
output types:
PDF Image Only
PDF Image + Text
Refer to Kofax PDF Options on page 15 for more information about Kofax PDF documents.
Adobe PDF Support
Ascent 7.5 Release Script for Hummingbird DM supports releasing Adobe PDF documents into
your Hummingbird DM repository. The software is provided by Adobe Acrobat Capture and is
not included with the Ascent Capture product. To release Adobe PDF documents, you must
install the Adobe® Acrobat Capture® 3.0 Clustered or Personal Edition software.
Refer to Adobe Acrobat Capture Options on page 16 for more information about Adobe PDF
documents.
OCR Full Text Support
With Ascent 7.5 Release Script for Hummingbird DM, you can release documents processed
through the Ascent Capture OCR Full Text module into your DM repository.
Refer to OCR Full Text Options on page 14 for more information about OCR full text files.
eDocument Support
With Ascent 7.5 Release Script for Hummingbird DM, you do not need to limit your batches to
image files. eDocuments are supported for release into your DM repository.
Kofax, Inc.7
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Additional Information
This section contains additional information about Ascent 7.5 Release Script for Hummingbird
DM.
Unsupported Ascent Capture Features
Ascent 7.5 Release Script for Hummingbird DM 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 “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 Hummingbird DM, 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 Hummingbird DM 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 DM attributes that support
Ascent Values. Notice that the DM 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.
Access to Documents and Folders
If you create documents and folders with no security settings at release setup, the documents and
folders will only be available for you to edit. This means that your released documents and userdefined folders are protected and can only be accessed by you. If you want certain DM groups and
users to have access to your documents and folders, you must use the Security Settings tab to
assign access privileges to your documents and folders.
For more information about the Security Settings tab, refer to the Help available with Ascent 7.5
Release Script for Hummingbird DM (Help keyword: Security Settings tab).
Warning If you create documents with no security settings and place it in a folder with security
settings, the documents will automatically inherit the permissions that you set for the folder.
8Kofax, Inc.
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
{Index Operator’s Station ID} Ascent Capture Values
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.
Context Menu Removed From the Folder Hierarchy
In Ascent 7.5 Release Script for Hummingbird DM, the context menu has been removed from the
folder hierarchy on the Folder Settings tab. This means that a context menu will no longer be
displayed when you right-click on any DM folder in the folder hierarchy to add, delete, or rename
a folder. To successfully add, delete, or rename a DM folder, use the Add Folder button, Delete
Folder button, or Rename Folder button on the Folder Settings tab.
Note that the right mouse button will now behave like the left mouse button. You can right-click
or left-click on a DM folder in the folder hierarchy to select the folder.
Refer to the Help available with the Ascent 7.5 Release Script for Hummingbird DM for more
information about adding, deleting, or renaming DM folders in the Folder Settings tab (Help
keyword: Folder Settings tab).
Hummingbird DM Projects
Ascent 7.5 Release Script for Hummingbird DM does not support projects. In addition, the release
script will not upgrade existing projects to folders during the upgrade process. Therefore, we
recommend that you use the Hummingbird DM Folder Conversion Utility provided by
Hummingbird that converts your projects into folders. The conversion utility will replace all your
projects with folders in the Hummingbird DM repository. For more information on the conversion
utility, refer to your Hummingbird DM Suite Installation Guide.
Due to a limitation with the Hummingbird DM Folder Conversion Utility, you will not be able to
directly view a document in the last converted folder in a hierarchy of converted folders.
(Hummingbird case number 375239; Kofax SPR 29388)
Hummingbird DM User Permissions
Ascent 7.5 Release Script for Hummingbird DM 6.0 – Release Setup dialog box honors access
permissions defined for your Hummingbird DM users, and makes accessible only those profiles
allowed for the logged in user. You can easily set the user profiles from the Permissions tab on the
Hummingbird Group Maintenance dialog box. We recommend that you set the following fields to
“Yes” for the user you specified at release setup to create and remove folders on the
Hummingbird DM server.
Can Create New Documents: allows the user to create documents
Can Create Folders: allows the user to create folders
Can Create/Remove Public Folders: allows the user to create and remove public folders.
For more information about the Hummingbird DM user permissions, refer to the documentation
that came with your Hummingbird DM product.
Kofax, Inc.9
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Application and Document Type Fields
When you are creating a user-defined folder for release, the Application and Document Type
folder profile attributes must be set to “FOLDER,” which is the default choice. If you attempt to
change this value, you will receive an error message at release and the value will be returned to
“FOLDER.”
Releasing to Records Management
If you are releasing to Records Management via Ascent 7.5 Release Script for Hummingbird DM,
make certain that you have the following items set in the link control when you want your
documents to be released into Records Management as records:
The Code field is set to a text constant containing the File Part Number (for
example, “2002/1(A)”)
Item Type field for released documents is set to “Document”
The Type field is set to “Keep”
The Document Type field is set to “RM”
To release to Records Management, check the “Mark document as a record for Records
Management” check box on the General Settings tab, and select a Records Management profile
form from the Profile drop-down list on the Document Settings tab. Then, leave the Item Type
unlinked.
Note If you specify an Item Type of Record, File, or Box, the following error will occur and release
will fail. “An error occurred while releasing the document <document name> to the Records
Management system. 9519.”
Search Criteria for Duplicate Folders
If the “Create new folder” option is selected on the Folder Settings tab, a new folder will be
created as long as Ascent 7.5 Release Script for Hummingbird DM does not find a duplicate folder.
The release script classifies a duplicate folder as an existing folder with the same name, same
profile, same public setting, and exists in the same parent (library or folder).
If a duplicate folder is found that satisfies the above criteria, then that folder is used for releasing
documents. The attributes for the duplicate folder are not updated and will not be used at release.
10Kofax, Inc.
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
DM Check Box Attributes Requires Numeric Values
The Hummingbird DM release script allows you to establish links between DM index fields and
Ascent Values. However, the DM check box data type only accepts numeric string values. You
must use “1” for a checked value and any other numeric string value for an unchecked value (for
example, “0” or “2”).
Note The numeric values must be in quotation marks.
Releasing to Localized Versions of Hummingbird DM
When you are releasing to German Hummingbird DM, Ascent 7.5 Release Script for
Hummingbird DM requires an INI file containing localized table names. If you are running a
standalone Ascent Capture system, you must create the INI file in the Ascent Capture root
directory (for example, C:\Program Files\Ascent) and name it “DMTables.INI.” If you have a
client/server Ascent Capture system, you must create the “DMTables.INI” file in the Ascent
Capture server directory (for example, C:\Program Files\AscentSS\AscentSV).
Note that the INI file must contain a section named “[Table Names]” followed by the localized
table names. The following information must be entered into the “DMTables.INI” file:
[Table Names] is the section name and each subsequent line refers to a localized table in
Hummingbird DM. The INI file name, section name, and table names are not case sensitive.
If you do not create the DMTables.INI file and attempt to login to the German Hummingbird DM
release script, login will fail with an error message similar to the following:
The retrieval query did not return results.
Warning The third table name (DOC_GROUPS_ENABLED) requires an underscore prior to the
localized prefix. The fourth table name (DOC_KEYWORD) may not require a localized prefix.
Notice that if you attempt to use the INI file on an English system, you will receive an error. This
happens because the table names expected by the Hummingbird DM release script do not match
the actual names on the Hummingbird DM server. You will receive the following error message
on the English system:
Runtime error. <
DM Server Name
>: <
DM Server Name
> Your search was unsuccessful.
Excluding DM Profile Attributes
The DM index fields defined for a profile will display in the DM Profile Attributes area on the
Document Settings tab and Folder Settings tab. If desired, you can prevent one or more of the DM
index fields from displaying in the list.
To do so, you must create a file named ACFusion.INI and store this file on the Ascent Capture
server’s installation folder (for example, C:\Program Files\AscentSS\AscentSV).
Kofax, Inc.11
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
X To create the ACFusion.INI file
1From Windows Explorer, select Program Files | Ascent.
2On the File menu, click New and then Text Document.
3Rename the file to ACFusion.INI.
4Right-click the ACFusion.INI file in the Ascent folder, and select “Open with” from the
context menu. Use any text editor to edit this file.
5Insert a section heading titled [Profile Display Names]. This section heading lists the
column names to exclude from display. Columns are derived from the SQL column
attributes.
6Add the desired column names. The DM profile fields for the column names that you list
will not display in the DM Profile Attributes area on the Document Settings tab and/or
Folder Settings tab.
7When you are finished, save the file.
Warning When you first log on to release setup, you will receive a warning message. The
warning message is “Cannot find the DM attribute <attribute> in the profile form <profile>. The
link will be removed.” Simply click OK to acknowledge the removal of the DM index field. Notice
that you will receive warning messages for each DM index field that you excluded.
Note If any required DM index fields are listed in the ACFusion.INI file, a warning message will
display at release setup time, and the required fields will display in the DM Profile Attributes
area. Consequently, you cannot hide required fields. As a result, Ascent Values can be linked to all
required DM index fields.
Each line listed under [Profile Display Names] specifies one column name to exclude, as follows:
Sequence number=Column name
Where:
Sequence number is a unique incrementing number that identifies the line in the [Profile
Display Names] section.
Column name is the name of the DM profile attribute as it is known in the DM repository.
A sample of an ACFusion.INI file is shown below. Note that each line under the section heading
must conform to the required format.
Note The list of excluded index fields is checked at release setup; it is not checked at release. All
linked index fields will be released. Changes to the list of excluded index fields after a batch class
is published will have no impact on existing batches.
12Kofax, Inc.
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Sharing Data Among Release Scripts
The Ascent Capture Release Script Information Interchange feature is useful when more than one
release script has been configured for a particular batch class and document class combination.
The sharing of information is accomplished by allowing the release script to pass information to
other release scripts. The Ascent Capture Value {Repository Document ID} is used to store and
retrieve the RepositoryDocumentID that will be used by the first invoked release script. Therefore,
the first release script that runs can set this value, and subsequent release scripts can read the same
value.
Notice that when you are passing the RepositoryDocumentID information to a different release
script, the release script must exist within the same document class using multiple release. In
addition, the release script that is passing the RepositoryDocumentID information must be placed
first in the list on the Release Scripts dialog box. For example:
Ascent 7.5 Hummingbird DM 6
Ascent Capture Text
Only the first release script can set the RepositoryDocumentID value. Subsequent release scripts
can only read this value.
Refer to your Ascent Capture Help for more information about configuring the
RepositoryDocumentID. You can display Ascent Capture Help from the Help menu available
from any Ascent Capture module. Alternatively, you can click Start | Programs | Ascent
Capture | Ascent Capture Help
Kofax, Inc.13
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
OCR Full Text Options
To release OCR full text files, you must enable Ascent Capture OCR full text processing in your
applicable document class and add the OCR Full Text module to your applicable batch class.
For details about how OCR full text files and non-image files are released to the DM repository,
refer to the Help available with Ascent 7.5 Release Script for Hummingbird DM (Help keyword:
File format combinations).
Note OCR full text files are displayed in the Attachments tab with a three-character label
matching the extension of the OCR document. For more information about attachment labels,
refer to the documentation that came with your Hummingbird product.
X To enable OCR full text processing for a document class
1From the Create Document Class dialog box or Document Class Properties dialog box,
select the OCR tab.
2Check the Enable OCR full text check box to enable OCR full text processing for the
document class.
3Click Apply to save your settings without closing the dialog box. Click OK to save your
settings and close the dialog box.
X To add the OCR Full Text module to a batch class
1From the Create Batch Class dialog box or Batch Class Properties dialog box, select the
Queues tab.
2Select OCR Full Text from the list of Available Queues, and click Add.
3Click Apply to save your settings without closing the dialog box. Click OK to save your
settings and close the dialog box.
For more information about OCR full text processing, refer to the Getting Started with Ascent Capture guide.
14Kofax, Inc.
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Kofax PDF Options
To release Kofax PDF documents, you must enable Ascent Capture Kofax PDF generation in your
applicable document class and add the Kofax PDF Generator module to your applicable batch
class.
For details about how Kofax PDF documents and non-image files are released to the DM
repository, refer to the Help available with Ascent 7.5 Release Script for Hummingbird DM (Help
keyword: File format combinations).
X To add the Kofax PDF Generator module to a batch class
1From the Create Batch Class dialog box or Batch Class Properties dialog box, select the
Queues tab.
2Select PDF Generator from the list of Available Queues, and click Add.
3Click Apply to save your settings without closing the dialog box. Click OK to save your
settings and close the dialog box.
X To enable Kofax PDF generation for a document class
1From the Create Document Class dialog box or Document Class Properties dialog box,
select the PDF tab.
2Check the Enable Kofax PDF generation check box to enable Kofax PDF processing for the
document class.
3Click Apply to save your settings without closing the dialog box. Click OK to save your
settings and close the dialog box.
For more information about the Kofax PDF Generator module, refer to the Getting Started with Ascent Capture guide.
Kofax, Inc.15
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Adobe Acrobat Capture Options
Ascent 7.5 Release Script for Hummingbird DM supports Adobe Acrobat Capture. This section
contains information related to using Adobe Acrobat Capture for your Adobe PDF documents.
For additional details about creating Adobe PDF documents, refer to your Adobe Acrobat Capture
documentation.
For details about how Adobe Acrobat Capture PDF documents and non-image files are released to
the DM repository, refer to the Help available with Ascent 7.5 Release Script for Hummingbird
DM (Help keyword: File format combinations).
Operating System Requirements for Ascent Capture
To release Adobe PDF documents, your Ascent Capture Administration and Release workstations
must be running on Windows XP or Windows 2000 computers. Windows 95, Windows 98,
Windows Me, and Windows NT are not supported operating systems for Ascent Capture.
Adobe Acrobat Capture and the Ascent Capture Release Workstation Installations
During the conversion process, communication must occur between Adobe Acrobat Capture and
the Ascent Capture Release module. However, due to timing conflicts, Adobe Acrobat Capture
and Ascent Capture cannot be run at the same time on a workstation. Therefore, Adobe Acrobat
Capture and Ascent Capture must be installed on separate workstations on the same LAN.
Releasing Adobe PDF Documents
To release in Adobe PDF format, you must install the appropriate Adobe Acrobat Capture
software. In addition, the release working directory must be available to the Ascent Capture
workstation where you are setting up the release script and the Adobe Acrobat Capture
workstation. One way to do this is to specify a UNC path for the Release directory. This can also
be done with a mapped drive, the drive letter and path must be the same on all workstations. If
you specify a local Release working directory, please note the following:
A folder with that name will be created on the Ascent Capture workstation, but it will not
be used.
The same path must already exist on the Adobe Acrobat Capture workstation.
Adobe PDF images will be placed in the folder on the Adobe Acrobat Capture workstation.
Workflow Steps
Adobe Acrobat Capture lets you create your own workflow or use one of the predefined
workflows. Note the following:
For complete image conversion for Formatted Text & Graphics or Searchable Image page content,
a basic Adobe Acrobat Capture workflow needs to contain at least four steps, in the following
order:
1Capture Image
2Bind Pages
3Export to PDF
4Store File (PDF)
16Kofax, Inc.
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
For complete image conversion for Image Only page content, the Adobe Acrobat Capture
workflow needs to be called “PDF Image Only” and contain at least three steps, in the following
order:
1Convert Image to PDF
2Combine PDFs
3Store File (PDF)
Note When creating workflows, do not include manual steps such as Quick Fix Page, Review
Document, and Zone Images. If you do, Adobe Acrobat Capture will stop running when it
encounters any of these steps and require manual processing by the user. This kind of workflow is
not suitable for Ascent Capture Release because it disrupts the automated process of releasing
Adobe PDF documents.
Multipage TIFFs
If you are releasing multipage TIFFs, you must use the Split Multipage TIF step in your Adobe
Acrobat Capture workflow.
Releasing from Multiple Ascent Capture Standalone Workstations
If you use multiple Ascent Capture standalone workstations and one Adobe Acrobat Capture hub,
you must create unique Adobe Acrobat Capture “workflows” and “watched folders” for each
Ascent Capture standalone workstation. This is because Adobe Acrobat Capture uses Ascent
Capture document IDs for its document naming scheme. Since standalone Ascent Capture
document IDs may not be unique, the document names could conflict in Adobe Acrobat Capture
and cause the release process to fail.
Re-releasing Documents in Error
If an Adobe Acrobat Capture error occurs during the release process, you must clear your Adobe
Acrobat Capture finished documents and cancel any hung documents before re-releasing the
same documents in Ascent Capture.
Invalid Watched Folders
If you attempt to release documents to an invalid Adobe Acrobat Capture watched folder, the
documents will be rejected. To cancel the release, click Cancel on the Ascent Capture PDF Release
dialog box displayed at the Release workstation. The Cancel button will automatically cancel the
Adobe Acrobat Capture documents.
Kofax, Inc.17
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Installing the Release Script
You can install Ascent 7.5 Release Script for Hummingbird DM on an Ascent Capture client
workstation or standalone workstation.
Important Note About Installation
To install Ascent 7.5 Release Script for Hummingbird DM you must have Windows administrator
privileges. If you do not have administrator privileges and install this release script, you may
receive error messages and several of the files may not install correctly.
Before you install Ascent 7.5 Release Script for Hummingbird DM, refer to System Requirements on
page 2 for information about installation requirements.
Installation Instructions
Use the following instructions to install Ascent 7.5 Release Script for Hummingbird DM.
X To install the release script
1Insert your Ascent 7.5 Release Script for Hummingbird DM 6.0 installation CD into your
CD drive.
2From your Windows task bar, select Start | Run, browse to the Hummingbird\DM6
folder on the CD, and run Setup.exe. The installation program will start.
3Follow the instructions on your screen to install the release script.
4When the installation is complete, a message will display that indicates the release script
was successfully installed.
Note Installing the release script automatically registers it with Ascent Capture.
5Repeat this procedure on all Administration and Release workstations that will use the
Hummingbird DM release script.
18Kofax, Inc.
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Replacing a Previous Version of the Release Script
Ascent 7.5 Release Script for Hummingbird DM does not support upgrading from previous
versions. If you attempt to upgrade, you may receive the following error message:
Error upgrading release script “Ascent 7.5 for Hummingbird DM 6.0” for batch class
“
<Batch Class Name>
When replacing a previous version of the Hummingbird DM release script, you will need to
uninstall your current version before you install version 7.5. In some cases, you may need to reenter your release setup settings. If you do, you may want to take notes on the release setup
settings defined for your current version of the release script before you install version 7.5. An
easy way to do this is to capture and save screen shots of the release setup settings.
X To replace a previous version of the release script
1Release any existing batches associated with your current version of the release script. See
Releasing Batches on page 31.
2Follow these substeps to take notes on the release setup settings for your current release
script.
a From the Administration module’s Definitions panel, select the Batch class tab and
right-click a document class associated with the current version of the Hummingbird
DM release script. (You may need to expand the batch class items.)
b From the context menu, select Release Scripts. The Release Scripts dialog box will
display.
c Select the Hummingbird DM release script form the left side of the dialog box and
click Setup. The Release Setup dialog box will display.
d Capture screen shots of each tab and save them so that you can easily re-create the
settings later. You can use the Windows Alt-Print Screen function or any screen
capture software.
e Click Cancel to close the Release Setup dialog box, and then click Close to close the
Release Scripts dialog box.
” and document class “<
Document Class Name>
.
3For information about uninstalling a release script, refer to Removing the Release Script on
page 21.
4For information about installing version 7.5 of the release script, refer to Installing the
Release Script on page 18.
Kofax, Inc.19
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Application Maintenance
This section describes how to repair and remove Ascent 7.5 Release Script for Hummingbird DM.
Users with full administrative privileges can:
Install the release script
Remove the release script (from Add or Remove Programs or Application Maintenance)
Repair the release script (from Application Maintenance)
Users with Power User privileges can repair the release script from Application Maintenance.
Figure 1. Application Maintenance Dialog Box
Repairing the Release Script
The Repair option replaces missing, renamed, or deleted files.
X To repair the release script
1Insert your Ascent 7.5 Release Script for Hummingbird DM 6.0 installation CD into your
CD drive.
2From your Windows task bar, select Start | Run, browse to the Hummingbird\DM6
folder on the CD, and run Setup.exe.
3Setup will detect an existing installation and the Application Maintenance dialog box will
display, as shown in Figure 1.
4From the Application Maintenance dialog box, ensure that the “Repair” option is selected
and click Next.
5Follow the instructions on the screen to repair the release script.
6When the repair is complete, a message will display that indicates the release script was
successfully installed.
20Kofax, Inc.
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Removing the Release Script
The Remove option will delete the release script.
X To remove the release script
1Insert your Ascent 7.5 Release Script for Hummingbird DM 6.0 installation CD into your
CD drive.
2From your Windows task bar, select Start | Run, browse to the Hummingbird\DM6
folder on the CD, and run Setup.exe.
3Setup will detect an existing installation and the Application Maintenance dialog box will
display, as shown in Refer to Figure 1 on page 20.
4From the Application Maintenance dialog box, select “Remove” and then click Next.
5Follow the instructions on the screen to delete the release script.
6When the uninstallation is complete, a message will display that indicates the release
script was successfully uninstalled.
Alternatively, you can use the Add or Remove Programs utility from the Windows Control Panel
to uninstall the Hummingbird DM release script.
Refer to your Microsoft documentation for more information about the Add or Remove Programs
utility.
Refer to Problems When Uninstalling the Release Script on page 33 for information about a known
problem.
Note After uninstalling, Ascent 7.5 Release Script for Hummingbird DM will continue to display
in the Release Script Manager, although it will not be functional. To remove the release script from
the list, you must go into every batch class and associated document class, select the applicable
release script from the Assigned Release Scripts list and click Remove. You must do this for every
instance of Ascent 7.5 Release Script for Hummingbird DM. After all references to the release
script are removed, you will be able to delete Ascent 7.5 Release Script for Hummingbird DM
from the Release Script Manager.
Kofax, Inc.21
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Logging on to the Release Script
Once you have associated a document class with a batch class in Ascent Capture, you may specify
the release script to use when releasing your images, OCR full text files, PDF documents,
eDocuments, and index data.
X To log on to the release script
1Start the Ascent Capture Administration module. The module’s main screen will display.
2Select the Batch class tab from the Definitions panel, and right-click the applicable
document class. (Expand the batch class item to select associated document classes.) A
context menu will display.
3From the context menu, select “Release Scripts.” The Release Scripts dialog box will
display.
Figure 2. Release Scripts Dialog Box
4The Release Scripts dialog box lists all available release scripts. Available release scripts
are those that are registered with Ascent Capture. From the Release Scripts dialog box,
select the “Ascent 7.5 for Hummingbird DM 6.0” release script and click Add. The DM
Login Information dialog box will display, as shown in Refer to Figure 3 on page 23.
5Enter your DM library name, user name, and password. This information will be used to
log on to DM.
Note The Hummingbird DM release script does not accept empty or NULL passwords. If
you attempt to log on to DM without a password you will receive an error.
(SPR 00011363)
22Kofax, Inc.
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Figure 3. DM Login Information Dialog Box
The Library Name combo box lists the default primary library and all available remote
and independent libraries. If this is the first time you are logging on to the Hummingbird
DM release script, then this setting defaults to the primary library. Notice that the library
name you choose will display in the title bar of the Ascent 7.5 Release Script for
Hummingbird DM 6.0 — Release Setup dialog box, as shown in Refer to Figure 4 on
page 24.
Note The login information will be saved and used during release.
6To prompt for a user ID and password if the release script is not able to log in to DM at
release time, select the “If unable to log in during release, prompt for valid login
information” check box.
If selected and there is a problem logging on to DM during release, the DM Login
Information dialog box will display and the library name will be disabled. The user
may then enter valid login data and click OK. However, if the user clicks Cancel, the
release will fail and the batch will be routed to the Ascent Capture Quality Control
module.
If not selected and problems occur when logging on to the Hummingbird DM release
script, the DM Login Information dialog box will not display during release. Release
will fail and the batch will be routed to the Ascent Capture Quality Control module.
Note Do not select this feature if you plan to run the Ascent Capture Release module as a
service or if you plan to run the Release module during off-hours. The DM Login
Information dialog box requires a user response, which interferes with the automated
nature of running the Release module as a service or without operator attention.
7Click OK. The Ascent 7.5 Release Script for Hummingbird DM 6.0 — Release Setup dialog
box will display, as shown in Refer to Figure 4 on page 24.
Kofax, Inc.23
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
8Refer to the next section, Setting Up the Release Script, for information about the set up
options.
24Kofax, Inc.
Setting Up the Release Script
The following sections describe the setup options available with the Ascent 7.5 Release Script for
Hummingbird DM.
Note For more details about the setup options, refer to the Help available from Ascent 7.5 Release
Script for Hummingbird DM 6.0 — Release Setup dialog box.
Document Settings Tab
This tab allows you to select from a list of available DM profile attributes, and link Ascent Values
to DM index fields.
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Figure 5. Document Settings Tab
Kofax, Inc.25
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Folder Settings Tab
This tab allows you to specify or create a DM folder location for your released documents. At
release, the released documents will be linked to the selected folder.
Figure 6. Folder Settings Tab
26Kofax, Inc.
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Security Settings Tab
The options on this tab allow you to specify which DM groups and users will have access to the
released documents and/or user-defined folders. In addition, you can specify the profile access
rights for the selected DM groups and users.
Figure 7. Security Settings Tab
Kofax, Inc.27
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Image Format Tab
This tab allows you to specify the desired image formats for releasing your images. You can
specify a primary format and a secondary format. If Adobe PDF is selected as an image format, the
PDF Settings on this tab will become available for selection.
Figure 8. Image Format Tab
28Kofax, Inc.
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
General Settings Tab
This tab allows you to specify a temporary storage location to be used at release time, and specify
whether to skip the first page of each document at release. You may want to skip the first page if
you are using standalone separator sheets to separate your documents, and you do not want to
release scanned images of the separator sheets. In addition, you can specify whether the released
document will be released directly to the DM Records Management system, publish new
documents to the library, enable content searching, and version a document using the document
number.
Figure 9. General Settings Tab
Kofax, Inc.29
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Publishing a Batch Class
After you select all your batch class settings, you must publish your batch class before you can use
it. The publishing process checks the integrity of the settings in your batch class, and makes the
batch class available for use. If problems are found with any of the settings, error and warning
messages will display along with recommended actions for fixing the problems.
If you ever decide to edit your batch class, you must publish your batch class again before your
changes can be used. Your changes will not be applied to batches created before the new
publication date.
X To publish a batch class
1Start the Ascent Capture Administration module. The module’s main screen will display.
2Select the Batch class tab from the Definitions panel, and right-click the applicable batch
class. A context menu will display.
3From the context menu, select “Publish.” The Publish dialog box will display.
4From the Publish dialog box, select your batch class and click Publish. Ascent Capture
will check all your batch class settings and display the results in the Results box.
a If no problems are detected, the message “Publishing successful” will display.
b If problems are detected, warning/error messages will display along with the
recommended actions to resolve the problems. Perform the recommended actions, and
then try to publish the batch class again.
5Run some sample batches through the system to test the operation of the release script.
After successfully publishing, you can create batches based on your batch class. As your batches
flow through your Ascent Capture system, they will be routed from module to module. The
modules that are used to process a batch, and the order that processing occurs, are specified as
part of the batch class definition for the batch.
Refer to the Ascent Capture Help for more information about batch classes (Ascent Capture Help
keyword: Batch classes > about).
30Kofax, Inc.
Releasing Batches
With Ascent 7.5 Release Script for Hummingbird DM, the Ascent Capture Release module will
process batches based on the settings of the associated batch classes. The Release module is
responsible for releasing documents, as well as index data using the attributes defined during
release setup.
The Ascent Capture Release module usually runs as an unattended module on a Windows
workstation, periodically polling the Release module for available batches. The Release module
may be configured to run during off-hours to avoid any impact to the throughput of Ascent
Capture and/or the network system. To start the Release module, select
Start | Programs | Ascent Capture | Release. All batches queued for release will be released after
initiation of the Release module.
Note Refer to your Ascent Capture Help for more information about configuring the Release
module (Ascent Capture Help keyword: Release module > about). You can display Ascent Capture
Help from the Help menu available from any Ascent Capture module. Alternatively, you can click
Start | Programs | Ascent Capture | Ascent Capture Help.
X To release a batch
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
1Start the Ascent Capture Release module. The module’s main screen will display. Any
batches waiting to be released will be processed.
2Once your batch is released, it will be removed from Ascent Capture. If any documents or
pages are rejected, the batch will be routed to the Ascent Capture Quality Control module.
3When you want to exit the Release module, select Batch | Exit from the Release module’s
menu bar.
Kofax, Inc.31
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Known Problems
This section contains information about known problems with Ascent 7.5 Release Script for
Hummingbird DM.
FOLDER_PROF Folder Profile
This release script does not support specifying a folder profile type other than FOLDER_PROF.
Note that if you attempt to use any other folder profile from the Profile drop-down list on the
Folder Settings tab, it will create duplicate folder names for every document released in the batch.
(SPR 00026499)
Workaround: Use only FOLDER_PROF as the folder profile type.
Public Folder and File Plan Locations are Not Supported
This release script does not support releasing documents to the “Public Folder” or “File Plan”
locations. If you attempt to select the “Public Folder” or “File Plan” location in the Browse dialog
box from the Folder Settings tab, the release will fail and the batch will be routed to the Ascent
Capture Quality Control module. (SPR 00026649)
ITEM_TYPE Custom Constant is Not Supported
This release script does not support the ITEM_TYPE custom constant. If you attempt to select the
custom constant in the Document Settings tab, the release will fail with the following error
message. (SPR 00026496)
Not all required values are supplied: FILE_SERIES_NAME.
DM Profile Attributes
Certain DM profile attributes have “Document Name” and “Name” as the index fields. If this
occurs, simply associate the same Ascent Value to the “Document Name” and “Name” index
fields. (SPR 00026619)
Note that this behavior occurs in the following DM profile attributes:
If you are installing Ascent 7.5 Release Script for Hummingbird DM on a Windows XP
Professional workstation and you specify a mapped drive, you will receive the following error
message. (SPR 31250)
32Kofax, Inc.
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Error 1904. Module <
your support personnel.
mapped drive
> failed to register. HRESULT –2147467259. Contact
Workaround: The error message is incorrect and can simply be ignored. Click the Ignore button
and the release script will successfully install and register the release script.
If you click the Abort button, the installation will end. If you click the Retry button, you will
receive the above error message again.
Problems When Uninstalling the Release Script
If you click the Cancel button while you are uninstalling the release script, all the release script
original files will remain properly installed on the system. However, depending on the point
during the uninstallation that the Cancel button is clicked, the release script may be un-registered.
In such a case, once you attempt to log on to the release script, login will fail. (SPR 31221)
Workaround: If this problem occurs, run Repair. Refer to Repairing the Release Script on page 20
for more information. Alternatively, you can re-register the release script in the Release Script
Manager.
Uninstalling the DMRel Folder
Uninstall does not remove the DMRel folder when using Add or Remove Programs utility. If you
want to completely uninstall the DMRel folder from your workstation, you must manually delete
the folder. (SPR 28017)
Blank Passwords are Not Supported
The Hummingbird DM release script does not support using a blank or NULL password when
logging on to the release script. You will receive the following error message when you attempt to
log on to the release script. (SPR 00011363)
The release script could not log you on. Please make sure that your library name, user
name, and password are correct. In addition, make sure that the Caps Lock is not
accidentally turned on.
Deleting the Last Remaining Folder from the Hummingbird DM Server
The release script does not allow you to delete the last remaining folder in the folder hierarchy
from the Folder Settings tab. Therefore, if you delete this folder from the Hummingbird DM
server, you will receive a warning message when you return to release setup. Although this folder
has been deleted from the Hummingbird DM server, the folder name will still appear in the folder
hierarchy in release setup. In addition, the Browse button will be disabled since there are no
existing folders on the Hummingbird DM server. (SPR 30356)
Workaround: Replace or recreate the deleted folder on the Hummingbird DM server. Another
option is to recreate the release script settings.
Duplicate “Billable” Attributes in the LAWPROF Profile
If you have generated new libraries based on the Hummingbird “Legal” template, you will
automatically have a “LAWPROF” profile that may be specified in the Document Settings tab and
Folder Settings tab. This profile has a duplicate “Billable” attribute, which is a hidden object and is
Kofax, Inc.33
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
not displayed in the normal design view. This minor problem has been reported to Hummingbird
and will likely be resolved in a future Hummingbird DM Patch. (SPR 00011020)
If this presents a problem, your DM system administrator can use the DM Designer application to
resolve the problem. To view the hidden profile attributes, click “Show Hidden Objects” from the
Edit menu. Then, remove the duplicate “Billable” attribute and save the profile. Notice that it may
be necessary to refresh the Hummingbird DM server and DM client before the update displays in
the Hummingbird DM release script.
eDocument Name Not Preserved at Release
Ascent Capture releases eDocuments as attachments. This means that the original file name of the
eDocument is renamed and displayed in Hummingbird DM as a 3-digit hexadecimal number.
Note that the original eDocument file extension is retained and used in the final name.
Images, PDF Documents, and eDocuments Display in Versions Tab
Primary images, secondary images, PDF documents, and eDocuments submitted to
Hummingbird DM will display in the Versions tab when viewed via Windows Explorer DM
Extension. The images, PDF documents, and eDocuments receive a unique hexadecimal number
as a version label, as shown in Figure 10. This is a visual limitation of the Hummingbird DM API
since the attachment name begins with numeric characters rather than alphabetical characters.
(Hummingbird case number 348736; Kofax SPR 26091)
Workaround: You can use Windows Explorer DM Extension to view the images, PDF documents,
and eDocuments, as they will display as attachments. The Comments area displays the original
file name and the version to which the image, PDF document, or eDocument is linked.
Figure 10. Select a Version to Edit Dialog Box
“Error 75 – Path/File Access” Error
An “Error 75 – Path/File access” error will occur if you try to release hidden files. (SPR 28969)
Workaround: Remove the hidden files from the batch.
34Kofax, Inc.
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Select a Version to Publish Dialog Box Displays During Release
If you have enabled the “Publish new documents to the library” check box on the General Settings
tab and release, the “Select a Version to Publish” dialog box will display as shown in Figure 13.
This dialog box will display each time a document is to be published, and you will need to click
the OK button each time this dialog box is displayed. Therefore, if you are releasing ten
documents, this dialog box will display ten times. (Hummingbird case number 377909; Kofax
SPRs 29874 and 30665)
Figure 11. Select a Version To Publish Dialog Box
Workaround: If this occurs, your DM system administrator can adjust the Group Versions
settings on the Hummingbird DM server by setting the “Always Display Version Selection List”
drop-down list box to “No.”
Adobe Acrobat Capture Error
If you are running the Release module as a service and have specified a mapped drive for your
Adobe configuration (hub, watched folder, and release working directory), the release will fail
with the following error message.
Acrobat Capture workflow does not exist.
Workaround: Specify a UNC path for your Adobe hub, Adobe watched folder, and Adobe release
working directory.
Releasing Versions of Documents With OCR Attachments
If you enable the “If Document Exists – Version document” option on the Document Settings tab
and release a document with an OCR full text attachment, the document will fail with the
following error message. (Hummingbird case number 684801; Kofax SPRs 29709 and 31107)
Kofax, Inc.35
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
{Release Error Script #1 (Hummingbird DM) [9530 The attachment “TXT” cannot be
versioned for the document <
documentname
>. (9530)}
Workaround: None. The Hummingbird DM API does not allow versioning of documents with an
OCR full text attachment.
Possible Memory Leak When Releasing Documents
When releasing a large number of documents to an existing folder, you may experience a possible
memory leak. In this case, you will notice that the system performance will be considerably
slower. The problem is more evident on a system where system resources are low. (Hummingbird
case number 384571; Kofax SPR 31312)
Workaround: If you experience low virtual memory, shut down the workstation and restart it.
Visit the Hummingbird Web site at www.hummingbird.com or contact your Hummingbird
representative.
OCR Full Text Files Saved With TIF Extension
When releasing to Records Management via this release script, Hummingbird will automatically
save all released images with a “.TIF” file extension. This means that Hummingbird will not save
your OCR full text files with the expected “.TXT” file extension. Instead, the DM repository will
actually store the OCR full text file as a text file with a “.TIF” extension. (Hummingbird case
number 384591; Kofax SPR 31210)
Workaround: None. This is the default behavior of Hummingbird DM. OCR full text files are
searchable in the DM repository.
Customizing a Hummingbird Profile Form
When customizing a Hummingbird profile form, you must add the FULLTEXT attribute to the
form. When the FULLTEXT attribute is set, the Hummingbird DM server will index documents. If
you do not add this attribute to the Hummingbird profile, the release will fail with the following
error message. (SPR 30769)
[-2147221032 NYPSSVR3: You have supplied an invali d property value.: =
FULLTEXT:X9748\CLIENT ID\X8809 = 1\1\ (-2147 221032)
Workaround: Add the FULLTEXT attribute to the Hummingbird profile form. Notice that this
attribute is normally labeled “Enable Content Searching” in the DEF_PROF profile.
Releasing Kofax PDF With TIFF Files
When releasing Kofax PDF as the primary image file and multipage TIFF as the secondary image
file from an Integrated Development Environment (IDE), the release will occur successfully.
However, you will receive the following error message after the Release module closes.
(SPR 00017358)
Release.exe — Application Error.
Workaround: You can do one of the following:
Run from an installed version of the Hummingbird DM release script
Scan or import JPEG images instead of TIFF
36Kofax, Inc.
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Multiple Release Problems
The following sections describe a couple of known multiple release problems.
Using Duplicate User Names
If you attempt to run multiple DM release scripts from one workstation using different user
names, the release script will use the login properties from the last logged in user. (SPR 00011500)
Releasing Documents With Multiple Release
If you run multiple DM release scripts from one workstation and release documents to folders, the
first document will always release to the correct folder in each release script. However, the
remaining documents will not release to the correct specified folder. The folder that released last
will receive all the remaining documents. (SPR 00011607)
For illustration, let’s say that you are releasing the following:
Release ScriptFolderDocuments
RS1Existing AdocA1
docA2
docA3
RS2Existing BdocB1
docB2
docB3
RS3Existing CdocC1
docC2
docC3
When you run multiple DM release scripts and release documents to folders, the following will
occur:
Release ScriptFolderDocuments
RS1Existing AdocA1
RS2Existing BdocB1
RS3Existing CdocA2
docA3
docB2
docB3
docC1
docC2
docC3
Workaround: Release the batches in the release script order.
Kofax, Inc.37
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Appendix A – Data Type Conversion
The tables in this appendix map Ascent Capture data types to Hummingbird DM data types, and
indicate which combinations are valid.
Refer to your Ascent Capture Help for more information about Ascent Capture data types (Ascent
Capture Help keyword: Data types). You can display Ascent Capture Help from the Help menu
available from any Ascent Capture module. Alternatively, you can click
Start | Programs | Ascent Capture | Ascent Capture Help.
Ascent Value Data Types
When Ascent Value fields are copied to DM profile attributes their data types are converted to DM
data types. The following table contains the conversion between the Ascent Value fields and the
DM profile attributes.
Table 1. Data Type Compatibility
Ascent Value
Data Types
DM
Text
DM
Boolean
DM
Number
DM Date
CHAR
DATE
DECIMAL
DOUBLE
FLOAT
INTEGER
NUMERIC
REAL
SMALLINT
TIME
VARCHAR
3
33
33
33
33
333
33
33
333
33
3
Text Constants
The following table lists the supported Hummingbird DM data types for Ascent Capture text
constants.
Table 2. Text Constants
Ascent
Capture Text
Constants
DM
Text
DM
Boolean
DM
Number
DM Date
Text
Constants
38Kofax, Inc.
3333
Ascent® 7.5 Release Script for Hummingbird DM 6.0 Release Notes
Appendix B – Kofax Technical Support
For additional technical information about Kofax products, visit the Kofax Web site at
www.kofax.com and select an appropriate option from the Support menu. The Kofax Support
pages provide product-specific information, such as current revision levels, the latest drivers and
software patches, online documentation and user manuals, updates to product release notes (if
any), technical tips, and an extensive searchable knowledgebase.
The Kofax Web site also contains information that describes support options for Kofax products.
Please review the site for details about the available support options.
If you are a certified representative from an authorized company, and need to contact Kofax
Technical Support, please have the following information available:
Ascent Capture software version
The Hummingbird DM release script version
Operating system and Service Pack version
Network and client configuration
Copies of your error log files
Information about your release script
Kofax, Inc.39
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.