Import constraints
An import into a Content Manager applies certain rules concerning checked-out items, items in workflow, items in a Bundle, secure items, BluePrint structures, and root items.
- Checked-out items
-
You cannot overwrite a checked-out item in Content Manager with an item you import. For best results, make sure that all items involved in an import are checked in before and while you perform an import.
- Items in workflow
-
You cannot import an item into Content Manager if the item exists and is in workflow on the Content Manager, not even if the item is assigned to the user who is performing the import. If you configure the import process to prompt the end user, it does halt the import to allow you to finish workflow on the item and try again. For best results, make sure that all items involved in an import are not in workflow when you perform the import.
- Items in a Bundle
-
When importing a Bundle, you also import all items in that Bundle. This may include items that had never been checked in on the export system. During import, such an item is assigned a version number 1, unless importing the item immediately triggers a Workflow Process on the import Content Manager instance.
- Secure items
-
Import items that exist on the destination Content Manager and that the user has no write access to cannot be imported. If you configure the import process to prompt the end user, it does halt the import process to allow you to change security settings and try again. For best results, make sure that the user has write access to all items that the import will want to update when performing the import.
Note that when an item is imported that has a BluePrint parent item, the user needs no access at all to the parent item, not even read access.
- Items that are invalid against their Schema
-
If you import an item without its dependent Schema or Schemas, it may be the case that the item is invalid against the Schema on the target Content Manager. You can configure the import to perform any or all of a number of synchronization operations to attempt to make the item conform to the target Schema or Schemas.
- Root items
-
A number of assumptions are made automatically about where to map certain root elements, regardless of what names they have.
If these root elements are present on the destination Content Manager, they are mapped from their export locations to their import locations automatically. The imported items get the names of the corresponding items on the import Content Manager.
This procedure applies to the following items:
- the root Folder of a Publication (called "Building Blocks" by default)
- the root Structure Group
To map one of these items to a different location, edit the mapping table.
- Business Process Types
-
Business Process Types have one or more associated Target Types (the exact number equals the number of Purposes of the Topology Type of the Business Process Type). These Target Types are recreated on the target system automatically when you import the Business Process Type. But there are some requirements on the target system to ensure a successful transfer:
- To successfully import a Business Process Type, a Topology Type with the same ID and Purposes must exist on the source system and on the target system.
- If the security settings of your Target Type(s) refer to a specific User or Users (rather than a specific Group), then, to ensure the same security settings on the target system, you must configure the User(s) manually on the target system.