You can define a rule to specify whether content is federated or moved.
About this task
A move content operation is applied differently depending on the state of the document.
- New
- The document is not federated. A move content operation that is applied to a document in this
state causes the document to be federated and the content to be moved.
- Existing with federated content
- The document is federated and the content is in the source repository. A move content operation
that is applied to a document in this state causes the document properties to be updated and the
content to be moved.
- Existing with moved content
- The document is federated and the content was already moved to a local Content Platform Engine object store. The move content step is ignored but the
property updates continue if necessary. The latter case is rare because move content causes the
source version to be deleted so that it does not appear in future import requests.
Procedure
To specify the content behavior:
- In the Federation Administration application, select the Rule Builder
tab.
- Select the FileNet® P8 target object store that is the
destination for the content.
- Select the FileNet P8 target folder that is the destination
for the content. To prevent the content from being filed in a specific folder, select the
Do not file option.
- Select a content operation.
- If you selected Move as the content operation, select a destination
storage area. Some storage areas have a default retention period that is associated with them. For
these storage areas, the default retention period is displayed with the selected storage area so
that Content Federation Service administrators can avoid unintentionally moving content to a storage
area with retention periods that are not appropriate for the content.