- (Administrator) Batch Types (Developer) Batch Types ( (Distributed) for Document Definitions (Standalone) for specific batch types);
- (Administrator) Projects (Developer) Projects (for all batch types in the project except for those for which event handlers have been set up in batch type properties).
- (Administrator) Document Definitions (Developer) Document Definitions (for documents of the current type).
Batch events
After batch created Before batch delete Before batch parameter change After page added Before page delete After document created Before document delete Before pages move After batch opened Before batch close Batch integrity checkDocument events for batch types
These event handlers are set up in a batch’s properties or in a batch type’s properties. Before document parameter change After document state changed After export completed Before matchingDocument event for the current batch type
These event handlers are set up in a Document Definition’s properties. Before document parameter change After document state changed After document rules are checked Event handlers for fields can also be set up in a Document Definition’s properties (see below).Field events
Field verification requestIf the same event handler is set up for batch types and the current document type, the event handler for the document will be executed first, followed by the event handler for batch types.
Storing procedures in global modules
Storing procedures in global modules
We recommend adding procedures that you plan to use in sever event handlers to a global module. To do this, select Events from the drop-down list on the toolbar of the script editor.Note: Global modules are not available for event handlers in the Document Definition editor.
Adding external assemblies
Adding external assemblies
If a script or a global module is using methods from an external assembly, you can add this external assembly on the .NET References tab of the properties dialog of an object (a batch type, a project or a Document Definition).
