Kofax DOKuStar Validation - Manual (Page 14)

DOKuStar Validation for Ascent Capture Page • 10
Relation to the Ascent Capture Definition
There are some relations between the document model and the Ascent Capture batch class definition.
Whenever a batch class is published, and also whenever DOKuStar Validation scripting is called from the
administration module, the document model is created from the Ascent Capture batch class definition. As stated in
the previous chapter, the Ascent Capture form types will become the document types in Validation’s document
model. Ascent “Document Classes” do not appear in Validation.
Furthermore, there is something called FieldClass in the document model. This corresponds to the Field Types
on the Ascent side – while the document models’ FieldType s are the Index Fields in Ascent Capture.
Before this gets too confusing, let us sum it up into a table:
Ascent Capture object… …corresponds to DOKuStar Validation object
Document Class ---
Form Type Document Type
Field Type Field Class
Index Field Field Type
When you define a field type in Ascent Capture, you give it a name, for example Varchar_100 . This will lead to
a FieldClass named alike, so you have a FieldClass Varchar_100 in the document model. An Ascent
index field of this type, named for example MyDescription , will result in a Validation FieldType
MyDescription , whose FieldClass is Varchar_100 .
In addition, there is always a FieldClass named TableField , which is used for all tables.
Note: The Field Class TextField , which existed in previous versions of DOKuStar Validation, is no longer used.
Ascent Capture Field Types are based on certain Data Types, like DATE , VARCHAR , etc.. These imply certain
restrictions to the data they can hold, e.g. a DATE field type can only hold valid dates, a VARCHAR has a
maximum number of characters, etc.. These data types are checked in the Validation automatically: When the user
tries to type something in that does not correspond to the data type, a message box is displayed: