The Include Options window allows you to control which object to include in an export manifest.
NOTE The use of Enterprise Manager or its related command-line tool to create an export manifest, or to export or import objects, is deprecated and it is recommended that you use FileNet Deployment Manager instead for these operations. For more information, see Exporting and importing.
Each time you add an object or object type to the export manifest, the Include Options window opens. Some objects might have associated objects (such as metadata or relationship objects) that you want to include in the export manifest. The Include Options window allows you to include some or all or none of the associated objects that an object is dependent on, without having to explicitly identify and add each associated object to the export manifest. For example, to export a folder and its contents, you can use the Include Options window to add the folder and its contents to the export manifest with one action; you do not have to individually add each object contained by the folder to the export manifest. However, if an export manifest or the target object store already contains those associated objects (through previous exports and imports), you do not need to include those associated objects again.
NOTES
Customized Includes
The following include options are also propagated to the included containees: Include relationships to containing folders, Include parent folders.
For a document, folder, or custom object, the export operation includes any user-defined class definitions associated with the object. It does not include FileNet system classes.
NOTE Class definitions that are created by FileNet P8 feature add-ons are not system classes and, therefore, are included if this option is selected.
For a class definition, the export operation includes the parent class hierarchy for the class definition.
If you are exporting both metadata and object instances with a single export manifest and do not want parent class hierarchies included in the exported data, you must manually modify the export manifest file. After saving the export manifest to a file, perform the following steps:
ClassDefinition
node, find the IncludeClasses
element.NOTES
For example, if exporting an annotation with this option cleared, only the GUID of the parent document is included, by using the Parent property on the annotation. With this option selected, the entire referenced object is also included, that is, the parent document itself (both its property values and its content). In addition, because include options are typically propagated, user-defined objects referenced by the parent document are also included in the data set, and so on, with user-defined objects referenced by other referenced objects.
Also adds the Security Folder and the permissions of any objects referenced in object-valued properties, if the SecurityProxyType properties of the referenced objects are set to FULL or INHERITANCE.
Adds the parent folder containment hierarchy (excluding the root folder) to ensure that objects are filed in the same folders on the target object store. This option applies only to folders. If this option is selected, the parent folder containment hierarchy is exported without containees, unless you explicitly add the contained objects to the export manifest.
Use this option directly on a folder to export all its parent folders, which allows the folder to be imported even if its parent folders do not currently exist at the destination.
If this object is applied to a containable object (document, custom object, or referentially contained folder), the parent folder containment hierarchy (excluding the root folder) is added only if the Include relationships to containing folders option is also selected.
Use this option on a document or custom object, along with the Include relationships to containing folders option, to export every folder that contains the object, and parents of all those folders. This allows the object to be filed in those folders even if the folders do not currently exist at the destination.
If the Include parent folders option is not selected and a containing folder does not exist at the destination, the following statements are true: