IBM FileNet P8, Version 5.2            

Compound document data

Component relationship

Description Defines a hierarchical relationship between two documents as components in a compound document. One document is the designated parent component and the other is the designated child component.
Deployment Mechanism FileNet® Deployment Manager:
  1. Create deploy dataset
  2. Convert objects for import
  3. Analyze objects for import
  4. Import converted objects
Dependencies
  • The document referenced by the ParentComponent property.
  • The document referenced by the ChildComponent property, if not null
  • The version series, or any document version in that series, referenced by the ChildVersionSeries property, if not null
  • The URI document referenced by the URIValue property, if not null

See Common dependencies between objects.

Environment-specific data Any object exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information identifying users and groups. For more information, see Permission.

A component relationship of type URICR has a URIValue property that FileNet Deployment Manager does not convert. You must manually update any environment-specific data, such as a server name, in the property value.

Notes® The individual document components of a compound document do not depend on their component relationships to import successfully or to function as standalone documents.


Feedback

Last updated: October 2013
roadmap_ce_compound_docs.htm

© Copyright IBM Corporation 2014.
This information center is powered by Eclipse technology. (http://www.eclipse.org)