To implement a script handler of an event, complete the following steps.

This event triggers when processing a document separation workflow step in Runtime Server. It appends a given workdoc after the last workdoc based on the append type.

This event triggers when a Verifier or Web Verifier user exits a batch in one of the following ways.

This event triggers when a user opens a batch.

This event allows you to implement a customer specific export of all extracted data. This provides the ability to implement a customer-specific export of all extracted data.

This event triggers when a batch opens for processing.

This event triggers when a Verifier or Web Verifier user places a document in the exception batch and the document moves out of the batch.

This event triggers after all defined classification methods are executed by the Cedar Project.

In general, this event triggers after the import.

The Runtime Server triggers this event after it finishes importing the batch. Use this event to set batch properties such as batch name and external group ID.

This event triggers after the OCR process.

This event triggers before any defined classification method executes by the Cedar project. During this event, it is possible to apply an existing name of a DocClass to the workdoc.

This event triggers between the PreClassify and PostClassify events that identify the beginning and end of the classification workflow step for a particular document. Using this event the custom script can clean-up and extend classification results before the final decision is made by the system and before the final classification matrix is built.

This event triggers before the import occurs.

This event triggers before the OCR process occurs.

The ProcessBatch event triggers when the Runtime Server instance begins processing during the custom processing workflow step.

This event triggers when the system extracts a document.

This event triggers before a batch closes after processing.

This event triggers when running security updates in Runtime Server.

This event triggers in Verifier in the following cases.

This event triggers in case of an exception in Verifier and Web Verifier.

This event triggers optionally in Designer before the Verifier form is loaded.

This event triggers each time before the focus inside the verification form changes. You can modify the focus change by modifying the pNewFieldIndex parameter. You can write a different field index into that parameter, which causes Verifier to change to a specific field instead of the originally selected field. The system triggers this event in Designer, if you set the Reason parameter to CdrBeforeFormLoaded, and if you enable the option in the Settings dialog box, on the Compatibility tab.

This event triggers if any of the configured actions in the Verifier Design Mode were caused by the user clicking a button or pressing any of the configured keyboard short cuts.

This event triggers after all defined analysis or evaluation methods execute by the Cedar DocClass. During this event, it is possible to examine and change the results of one or more fields of the document.

This event triggers before any defined analysis or evaluation method executes by the Cedar DocClass.

The PreVerifierTrain event is added to control SLW training in Verifier, Learnset Manager, and Designer.

Use the Validate event to perform validation on document level. At this point, the validation of all single fields executes. If one of the fields is still invalid, pValid is FALSE. During the Document_Validate event, it is possible to implement validation rules combining several fields. This may cause some fields to be invalid again. Do not make the document invalid if all fields are valid, because the Verifier needs an invalid field for focus control. If you want to keep the document invalid, always set at least one field to an invalid state.

After a document processed in self-learning Verifier has been checked whether it is supposed to be automatically trained for the local project, the Verifier has to trigger an event that adds a document to the local learnset.

This event triggers when a check box cell of the table is checked or unchecked by a user.

This event triggers each time the focus inside the verification table changes.

This event is used to reformat the content of a field, for example to unify a date or amount format or removing prefixes and suffixes. This event prepares the field data for validation.

Use this event to reformat the content of a field, for example to unify a date or amount format or to remove prefixes and suffixes.

This event triggers after the analysis step performs. It is possible to examine the list of all candidates and to add further candidates to the field.

This event triggers after the evaluation step performs. It is possible to examine the list of all candidates and to change their weights.

This event triggers before any defined analysis or evaluation method for this field executes by the Cedar DocClass.

This event triggers for the field where the smart indexing is defined. This field typically provides the key for the select statement.

This event triggers when a user clicks on one of the table header buttons. There are three different table header buttons: the Row Header, the Column Header, and the Table Header button.

Use this event to perform project specific validation rules. Use the pValid parameter to return the validation decision. If the parameter remains unchanged or if the event is not implemented, the document state gets valid if all fields are valid.

This event method triggers for each cell of the table. You can implement validation checks specific for a single cell.

Use this event to implement validation rules, which combine two or more cells of a row.

Use this event to implement a validation rule for the entire table.

The SCBCdrWKDOCLib object provides the following type definitions.

Cedar candidates are generated during the analysis step and are representing possible results of a field.

The SCBCdrDocPage object represents a single DocPage within a workdoc.

When importing a MSG file into a workdoc, the most important properties of the email are stored in the workdoc and available in the custom script through the "ISCBCdrEmailProperties" interface that can be queried from the SCBCdrWorkdoc interface.

This object contains the evaluated data to extract from the document.

This is a collection of all field objects contained in the current WorkDoc object.

A folder can represent an array of workdocs within a batch. A folder can contain one or more workdocs. During classification and extraction, you can access all workdocs of the same folder from within a script.

The Cedar table object represents a logical table in a document assigned to a Cedar field of a workdoc.

This object represents a TextBlock on a document. A TextBlock can contain one or more lines.

This object represents a textual word of a document.

The Cedar workdoc object stores all data of one document. The amount of data grows during the processing steps of OCR, classification and extraction.

The SCBCdrPROJLib object provides the following type definitions.

The Cedar Project object provides the following methods.

The Cedar Project object provides the following properties.

A Cedar DocClass object represents a single document class within a Cedar project class hierarchy.

This collection contains all defined DocClass objects of the Cedar project.

A Cedar FieldDef object represents the definition of a single FieldDef inside a Cedar DocClass

This collection contains all defined FieldDef objects of a single DocClass.

The Licensing Information Access object allows direct retrieval to the active licensing object. You can directly query any licensing component in a custom script.

The Cedar Settings object stores arbitrary strings for usage in script.

This is a global object at the project level. All script module events occurred at project level belong to this object.

Brainware Intelligent Capture provides a public interface "SCBCdrScriptAccess" for external access to the project and class level custom script pages. The interface can be queried from the main "SCBCdrProject" interface available in Brainware Intelligent Capture custom script. Using this interface it is possible to get, modify and dump project and class level scripts.

The SCBCdrSupExSettings object provides the following type definition.

The SCBCdrSupExSettings object provides the following methods.

The SCBCdrSupExSettings object provides the following property.

The SCBCdrSupplierExtractionEngine object provides the following method.

The SCBCdrParaCheckLib object provides the following type definition.

The SCBCdrParaCheckAnalysisSettings provides the following methods.

The SCBCdrParaCheckAnalysisSettings provides the following properties.

This is a collection of all vocabulary entry objects contained in the current ParaCheckSettings object.

The SCBCdrFormatEngine provides the following methods.

The SCBCdrFormatEngine provides the following property.

The SCBCdrFormatSettings object provides the following type definitions.

Use the following methods and properties to modify the list of format strings.

Use the following properties to specify the settings for each format string.

Use the following methods and properties to specify the general search settings.

Use the following properties to specify the settings for the search regions.

The SCBCdrBatchRoot object provides the following methods for batch administration.

The SCBCdrBatchRoot object provides the following properties for batch administration.

The SCBCdrStringComp object provides the following type definition.

The SCBCdrStringComp object provides the following methods.

The SCBCdrStringComp object provides the following properties.

The SCBCroImage object provides the following type definitions.

The component SCBCroImage provides methods and properties to load, modify, and save image files.

The component SCBCroViewer provides methods and properties to display various objects, such as images, text documents, annotations, or OCR and scanning results.

The SCBCroCiDocLib object provides the following type definition.

The component SCBCroCIDOC provides methods and properties to work with CI documents.

The component SCBCroCIDOCConv provides methods to convert a CI document to a text file or a Worktext.

The SCBCroProject object provides the following type definitions.

The component SCBCroProject provides methods and properties to work with projects.

The component SCBCroPage provides methods and properties to work with single pages.

The component SCBCroPages provides methods and properties to work with all contained page objects.

The component SCBCroZone provides methods and properties to work with zones.

The component SCBCroZones provides access to all contained zone objects.

The component SCBCroCollection provides methods and properties to work with collections.

The SCBCroWorktextLib object provides the following type definitions.

The SCBCroWorktext library provides methods and properties to modify the worktext object.

The DISTILLERVERIFIERCOMPLib provides the following type definition.

Use this interface to set specific verification form properties, as well as to set default properties for embedded elements, such as verification fields, labels, tables, and buttons.

This interface is used to identify verification properties specific for header fields’ validation elements, like drop down lists, check-boxes, and normal edit fields.

This interface is used to identify verification properties specific for table validation elements.

Use this interface to set verification properties specific for all custom buttons defined on a verification form.

This object is part of the Cedar Verifier Component Library. It enables the scripter to manipulate the verifier form labels.

The SCBCroPrint object provides the following type definitions.

The component SCBCroPrint provides methods and properties to configure the printing process.

The On Error statement enables you to handle runtime errors.

The ErrObject module provides methods and properties to identify and handle runtime errors using the Err object.

The following sample code sample shows how to use On Error Goto and the ErrObject.

The BIC architecture makes it important to be able to hide sensitive security information, such as database passwords stored in BIC or custom project configuration files.