Represents a hold on an object of type ICmHoldable, preventing that object from being deleted for an indefinite period of time, until the hold is explicitly removed. Holds can be repeatedly applied and removed on an ad hoc basis during the object's lifecycle.

A hold is applied by associating a ICmHold object with a ICmHoldable object through an intermediate CmHoldRelationship object. Every hold in which a ICmHold object participates is reflected in the object's ICmHoldRelationships property. Deleting a ICmHold object results in a cascade delete of the set of ICmHoldRelationship objects referenced by the CmHoldRelationships property. Thus, the hold is removed from all of the ICmHoldable objects to which the hold previously applied.

Note: Deleting a ICmHold object that is referenced by a large number of ICmHoldRelationship objects can result in a database transaction failure. If you anticipate large-scale hold removals, configure the application server transaction timeout and transaction log space to accommodate the operation.

By default, only object store administrators have the right to create ICmHold instances. The initial default instance permissions for ICmHold grant full control to object store administrators and read-only access to general users.

See Hold Concepts

Public Interface ICmHold _
	Implements IRepositoryObject, IReplicable, ISubscribable, IIndependentlyPersistableObject,  _
	IIndependentObject, IEngineObject, ICloneable

public interface ICmHold : IRepositoryObject, 
	IReplicable, ISubscribable, IIndependentlyPersistableObject, IIndependentObject, IEngineObject, 
	ICloneable

public interface class ICmHold : IRepositoryObject, 
	IReplicable, ISubscribable, IIndependentlyPersistableObject, IIndependentObject, IEngineObject, 
	ICloneable

FileNet.Api.Admin.ICmHold = function();
FileNet.Api.Admin.ICmHold.createInterface('FileNet.Api.Admin.ICmHold');