The following table lists the types derived from IContainable .
Derived Types
Type | Description |
---|---|
ICodeModule | Represents a user-implemented Java event handler that executes when an To create an Note:
object must be of type , not . If you attempt to save an object with an type in the content element list, the object will throw an exception.
, such as by updating the event handler content, then you must set the new version to the CodeModule property of any -based object for which the new version is intended.To instantiate an As an alternative to representing a Java event handler as an For cache configuration considerations, see the applicable code module-related properties in the See also the Javadocs for the following interfaces: |
IXMLPropertyMappingScript | Represents the definition of a subclass for defining XML property mapping scripts. The Content Engine XML Classifier uses XML property mapping scripts to populate document object properties with values based on data extracted from an XML document’s content. Administrators build mapping scripts that associate XML tags in the incoming document to properties, thus enabling the automatic classification of any XML document. An object, in addition to having all of the capabilities of a object, provides a container for user-authored XSL scripts for transforming XML documents of a specified type. The script contains instructions for extracting content from source XML documents of the type identified by the property in order to map it onto property values for the properties associated with the target document class identified by the property. |
ICustomObject | Represents a general interface that can be subclassed. A object has no inherent semantics, but is independently securable and can be persisted to an object store. A does not carry content, is not versionable, and does not support lifecycle functionality. The |
IDocument | Represents a single version of a document stored in an object store. In addition to being versionable, a object can be subclassed and can carry content, which is stored in one or more content elements. Each content element represents content data, which can either be local to an object store (represented by a object) or external to an object store and therefore outside the control of the Content Engine server (represented by a object). In addition, a object can be associated with a document lifecycle policy. A document lifecycle policy defines a set of valid lifecycle states for a document, controls the transition of those states, and specifies the actions to be taken when a document's lifecycle state changes. |
IFolder | Represents a container that can hold other subclasses, but cannot have content data of its own. Although objects and their subclasses can be referentially contained, they are the only Containable subclass that can be directly contained (in a ). All other subclasses are referentially contained using the or classes. Note: Folders that are referentially contained cannot participate in hierarchy index searches. The container hierarchy is a one-to-many relationship: a folder can have many child folders, but a child folder can have only one parent folder. At the top of the container hierarchy is an automatically-created root folder. Use Folders are not versionable. |
IWorkflowDefinition | Represents a workflow definition, an XML document of class "WorkflowDefinition" that is stored in a Content Engine object store. A workflow definition describes the instructions, paths, and queues available to a workflow, and acts as a processing template that the Process Engine uses each time the workflow runs. Workflow definition documents are versionable, containable, and can have a lifecycle associated with them. The To create a new After you create a workflow definition, you link it to an object that implements the To return all of the workflow subscription objects associated with this You can instantiate a
|
IPublishStyleTemplate | Represents the style template that defines how a source document will be transformed. A style template serves as a template for a particular kind of transformation and is tied to a specific publishing event handler on a specific object store. (Note that a publishing event handler can have more than one style template associated with it.) Information in the style template can be whatever is meaningful to the publishing event handler. For example, the style template might include an XML-based description of the transformation to be done for this style template, an ID of another document that contains a more detailed template, or a URL for publishing to an external location. A style template also specifies a list of input formats (MIME types) supported for the style template, the output format (MIME type) generated when the style template is applied, and, optionally, passwords used by PDF renditions. A publish style template associated with the HTML publishing event handler does not specify any additional transformation options beyond the basic ones (title, description, input formats, output format, and provider ID). In addition to the basic transformation options (as mentioned above for the HTML publishing event handler), a publish style template associated with the PDF publishing event handler optionally specifies the user and master PDF passwords, as well as other PDF security and watermark settings (stored as XML in the TransformationOptions property). |
IPublishTemplate | Represents a template for publishing a document. A publish template is an XML document that contains information used to automate the selection of options for a publishing request. For example, it contains the properties and security to apply to the destination document, and instructions for republishing a document, such as whether to version the existing destination document or replace it. Also, a publish template's StyleTemplate property might reference a object, which describes how the document is to be transformed. Because |