Owner's manual

DOKuStar Validation for Ascent Capture Page • 95
Test the Scripting Code
Something about this topic has already been said in the first chapter, this chapter discusses some more details.
It is important to understand that each Ascent Capture Batch Class that uses DOKuStar Validation has a Validation
Project assigned to it. Each project in turn has its scripting code.
Whenever a batch is opened in DOKuStar Validation, the following things happen:
- The scripting code of the batches’ batch class is loaded.
- The project is loaded (which leads to the
Application_OnProjectLoaded event in the scripting code).
- The data for the batch is loaded (which leads to the
Data_OnDataImported event in the scripting code).
When the operator closes or suspends the batch:
- The data are exported (which leads to the
Data_OnExported event in the scripting code) and unloaded.
- The project is closed (which leads to the
Application_OnProjectClosed event in the scripting code).
- The scripting code is unloaded.
This is the normal course on the validation clients. However, things are slightly different when you start DOKuStar
Validation from the Ascent Capture Administration Module: