When you review the content of imported documents, you might notice that some content elements do not contain the expected values.
The mapping features of FileNet® Deployment Manager are used to convert values that appear in the content of a document object that supports the conversion of environment-specific values. These environment-specific values can include service data in a workflow definition or object store references in a search template. After an import, review the imported documents in the destination environment to verify that the expected document object content appears in the documents. When you do this verification step, you might find that those converted values do not appear in the document.
In the Content Platform Engine, a document object represents a specific version of a document, with content stored as content elements. With the Content Platform Engine model of immutable content, the properties of a document object can be modified without creating a new version, but the content elements cannot. If the content is changed by using a method that does not create a new version of the document, a problem can occur.
One of the methods that can cause this problem to occur is the conversion process in FileNet Deployment Manager. The problem can occur when a document object with the same ID is reimported to a destination object store, but different mappings are used for the conversion operation that preceded the reimport action. If the import option Import Object ID is specified, and an imported document object exists in the destination object store with the same ID, the content of the imported document is unchanged by the import. This circumstance is true even if the conversion altered the document object content in the converted deployment data set.