Kofax DOKuStar Validation - Manual (Page 9)

DOKuStar Validation for Ascent Capture Page • 5
Files
Yet, I didn’t mention one important thing: Where does all the code go?
In most development environments, you have some file handling functionality, like File...Open/Close menus or
something similar to that. The VBA studio is different here: When you look around in the studio, you will not find
anything like it. So: Where is the code stored?
The answer is simple: It all goes into one file on the Ascent Capture Server. For each stage of DOKuStar Validation,
a subdirectory of the server directory …
\Ascent\AdminDB is created, named DokuStarValidation ,
DokuStarValidation_2 , etc.. In these directories, the scripting files are stored, named like the batch classes,
with an extension .vps :
In this example, there are two batch classes named TaxForms and TwoTypes .
All code always goes to this single file, no matter how many Modules, Class Modules or User Forms you added.
As you can see in the picture above, there is also a file named like the batch class with an extension .vpj . This is the
“Validation Project File”. It is generated automatically from the Ascent Capture batch class definition and contains
the knowledge about document classes, field names etc. needed by DOKuStar Validation. It is generated
automatically whenever:
- a batch class is published,
- Validation Scripting is called from the Administration module.
Usually, you don’t have to care about this Validation Project File.
When you developed your scripting code on one PC and you want to transfer it to another one (e.g. to the Ascent
Capture installation at a customer’s site), just copy the scripting file (
.vps ) . The only thing you have to make sure
additionally is that the Ascent Capture batch class definition is the same, so it is best to export it into a .cab and
import it again on the target PC (see the Ascent Capture documentation for details).