Kofax Ascen 7.0 Release Script - Manual (Page 38)

Ascent® 7.0 Release Script for IBM DB2 Content Manager Enterprise 8.3/8.4 Release Notes
32 Kofax, Inc.
MIME Types Must Exist in Content Manager
When releasing an eDocument with a MIME type that does not exist on the Content Manager
server, an error similar to the following will occur and the eDocument will be rejected.
(SPRs 28153 and 28252)
Method '~' of object '~' failed.
Workaround: Add the MIME-compliant application that you need to your DB2 Content Manager
system (for instance, you will need to install the Microsoft Excel software to open XLS MIME
types). Once the applicable MIME types exist in Content Manager, you can unreject the document
and re-release it.
Note To release eDocuments, the MIME types for the eDocuments must be in lowercase letters on
your DB2 Content Manager system. Contact your Content Manager administrator for more
information about adding MIME types.
User–Defined Ranges for Document Attribute Values
Range checking is not performed in all cases at release setup or release for Ascent Values linked to
document attributes for which user-defined ranges have been specified in Content Manager. At
release, if an Ascent Value falls outside of the valid range for a document attribute, the following
will occur.
For Long/Short Integer Data Types (SPR 00009828):
„
Long or Short integer values that fall outside of the range specified in Content Manager
will retain their values and will be released into Content Manager. No warning or error
message will be generated.
For CHAR and VARCHAR Data Types (SPR 00009736):
„
VARCHAR values with lengths that are less than the minimum allowed length will be
released into Content Manager. No warning or error message will be generated.
„
CHAR and VARCHAR values with lengths that exceed the maximum allowed length will
generate the following error message at release:
The size of the attribute < attribute name > specified < attribute size > is greater
than the size < maximum length > specified in the item type definition.
Workaround: If this problem occurs, adjust your values so that they fall within the allowed length
or range, and then re-release the batch. If this is not possible, delete the batch in error in Batch
Manager. When linking Ascent Values to Content Manager document attributes during release
setup, make certain that you know the valid ranges for values. Then, only link Ascent Values that
are valid for the attributes.