Represents a static relationship between two Containable
subclasses: a container and a containee. The object-valued Head
and Tail
properties express the relationship. The tail always references a Folder
(the container), while the head references the containee: another Containable
subclass (such as another Folder
, a CustomObject
, or a Document
). When the head is a Document
object, it represents a specific document version.
The following tables list the members exposed by IReferentialContainmentRelationship.
Public Properties
|
Name |
Description |
|
ContainmentName
|
The name of the contained object. For a DynamicReferentialContainmentRelationship or ReferentialContainmentRelationship object, this is the name of the head object in the relationship. The default value is supplied as follows: If both the Name and MimeType property of the Head object are present and not zero length, the default value is Name.MimeType (where the MimeType value is a normalized representation). If the MimeType property value is not present, the default is the Name value of the Head object. If the Name value is not found; the Id value of the Head object is used. The following characters are not allowed: - asterisk
- forward slash
- backslash
- colon
- question mark
- double quote
- less than
- greater than
- pipe
Note |
---|
If AutoUniqueName.AUTO_UNIQUE is set when the document is filed, the server attempts to make this containment name unique. |
For an Event object generated from the IFileEvent and IUnfileEvent event classes, the value of this property is the name of the Containable object added or removed. |
Top
Public Methods
|
Name |
Description |
|
ChangeClass
|
Changes the class of a Content Engine object. The new class must already exist and both it and the original class must be subclasses of the same base class. The ChangeClass method does not modify the security for an object, even if the object's current security is derived from the default security for its source class. For the object's user-defined properties, the following rules apply: - Any user-defined properties that exist in the new class but not in the original class are set to the default value defined by the new class (or to
null if there is no default defined). - Any user-defined properties that exist in both the original and the new class that are writable and have the same value (including
null ) as the default value defined in the original class will be set to the default value defined by the new class. However, any user-defined property that has had its value modified from the default value will retain that modified value in the new class. - Any user-defined properties whose definitions exist in the original class but not in the new class will no longer exist on the object when its class is changed.
When the class of a document object is changed, the default document lifecycle policy of the new class will only be applied to the document object's DocumentLifecyclePolicy property if both of the following scenarios occur: - The document has no current lifecycle policy.
- The document is either a reservation object, or is the current version object and is not reserved.
|
Top
See Also