Indicates objects that are independent.

An IndependentObject represents an EngineObject that has its own independent identity. Contrast this with a DependentObject, which is an EngineObject that can only exist within the scope of another object. (An example of this dependency is ContentElement; content elements are scoped to a particular Document object and cannot exist independently.) An IndependentObject can be retrieved from the server with a call to InstantiatingScope.FetchObject or Factory.<classname>.FetchInstance, whereas a DependentObject can only be fetched as a property of an IndependentObject.

An IndependentObject always has an ObjectReference, which can be obtained by calling GetObjectReference. An ObjectReference provides identity information for the object.

When calling the Refresh methods, note that the behavior differs from that of fetch-related methods (FetchProperty and FetchProperties). The fetch-related methods retrieve the object and merge retrieved property information into the current contents of the property cache. The Refresh methods retrieve the object and replace the current contents of the property cache with the retrieved property information.

Public Interface IIndependentObject _
	Implements IEngineObject, ICloneable

public interface IIndependentObject : IEngineObject, 
	ICloneable

public interface class IIndependentObject : IEngineObject, 
	ICloneable

FileNet.Api.Core.IIndependentObject = function();
FileNet.Api.Core.IIndependentObject.createInterface('FileNet.Api.Core.IIndependentObject');