Kofax Ascen 7.0 Release Script - Manual (Page 36)

Ascent® 7.0 Release Script for IBM DB2 Content Manager Enterprise 8.3/8.4 Release Notes
30 Kofax, Inc.
Known Problems
This section contains information about known problems with the Ascent 7.0 Release Script for
IBM DB2 Content Manager Enterprise.
Issues with CM Decimal Attribute
When setting the CM Decimal attribute in the DB2 Content Manager system, be aware that the
released value that expands beyond the working precision will simply be truncated. No error
message will be displayed. Therefore, if you set the CM Decimal attribute to two decimal places
and a value with three decimal places is released to the DB2 Content Manager system, the final
value will only have two decimal places. To illustrate, let’s say you release the following value to
the DB2 Content Manager system: 10.295. That value will display as 10.29 on the Content Manager
back end (assuming that the CM attribute was specified with only two decimal places).
(SPR 00025892)
Unexpected Behavior with Child Component Attributes
The Ascent Capture VARCHAR data type is not compatible with the Content Manager Long or
Short attribute; however, if you link a Content Manager Long or Short attribute of a child
component to an Ascent Capture VARCHAR data type, no error message is displayed at release
setup and release will not fail as expected. Any linked VARCHAR data values will not be released
into the Content Manager system. (SPR 00026048)
Note that this behavior is not exhibited at the root level. When you attempt to link the Content
Manager Long or Short attribute to an Ascent Capture VARCHAR data type, you will receive an
error message.
Workaround: Do not link a Content Manager Long or Short attribute to a VARCHAR data type.
Ascent Value {Document Count}
When the Ascent Capture Value {Document Count} is linked to the Content Manager
Char_Numeric attribute, release will not trim the value. The release will occur successfully;
however, the following message will display when the attribute is closed in Content Manager.
(SPR 00026002)
Value “1 “ for attribute Child1A/Char_Numeric (numeric string) has an invalid
character.
Workaround: Edit the value and remove the blank spaces.
Online Help Documentation – Ascent Value Data Types
The following Ascent Value data types are not documented correctly in the online Help system
that came with your product. The Data Type Compatibility online Help topic does not list the
correct information in the Ascent Capture Batch Fields and Index Fields table. (SPRs 00025909
and 00025939)
Note that Figure 11 on page 39 accurately portrays the supported Ascent Capture batch fields and
index fields for the Content Manager attributes.