EPMDocuments
This section describes some limitations related to EPMDocuments and the behavior related to exporting and importing EPMDocuments as checked out.
Attribute Limitations
Because the attributes of CAD documents are tightly related to content files, there are limitations on which attributes can change outside the workgroup manager clients. The following import actions are not supported for CAD documents:
• Creating a new object with new identities
• Substituting for an existing object
• Ignoring an object
Mapping rules enable you to change any attribute specified in an import or export XML file. When you are working with CAD documents, only the following attributes should be changed by mapping rules:
• name
• number
• CADName
• description
• folderpath
• versionInfo
• lifecycleInfo
• teamIdentity
When you are importing CAD documents, do not use mapping rules to change the following attributes:
• ownerApplication
• authoringApplication
• epmDocType
• epmDocSubType
• extentsValid
• contentItem
• iba
Do not use mapping rules to change any attributes on other EPM link objects, including:
• EPMMemberLink
• EPMReferenceLink
• EPMVariantLink
• EPMContainedIn
• EPMDescribesLink
• EPMBuildLinksRule
• EPMBuildHistory
EPMDocuments as Checked Out
When you export or import EPMDocuments as checked out, they are located in a workspace whose name is the name of the import JAR file without its extension. For example, if the JAR file abc.jar includes EPMDocuments that were exported as checked out, they are located in the workspace abc. If you import abc.jar, the EPMDocuments are checked out to the workspace abc. If the workspace does not already exist, it is automatically generated.