You can extend Content Engine functionality
with your own server-based action handlers, implemented in either Java™ or JavaScript. You create action handlers
by implementing the following Java interfaces
in the
com.filenet.api.engine package:
- EventActionHandler. An implementation of this
interface executes as part of a subscription, when a subscribed
system or custom event is fired. An event handler can run
synchronously or asynchronously, depending on how the execution
mode is set on the Subscription object. For
a workflow subscription, an event handler can only run asynchronously.
- DocumentLifecycleActionHandler. An implementation
of this interface executes as part of a lifecycle policy attached
to a document or document class, when a document state is changed.
Document states are user-defined. A lifecycle action handler
runs synchronously.
- DocumentClassifier. An implementation of this
interface automatically classifies a
new document based on its MIME type. A document classifier
runs asynchronously.
- ChangePreprocessor. An implementation of this
interface is associated with a class definition. When
an instance of the class is created or updated, the change
preprocessor executes synchronously.
For action handler implementation guidelines, see Restrictions and Best Practices.