Export an Assembly to a Virtual Document
Exporting an assembly to a virtual document enables you to generate a virtual document you can use in a submission publishing tool.
Due to the nature of DMS repository virtual documents, you can unintentionally convert a document to a virtual document, change the structure of an existing virtual document, or check in a checked-out document by exporting an assembly as a virtual document.
- Assigning children to an assigned document in and then exporting the assembly as a virtual document forces to convert the assigned document into a virtual document.
- If the assigned document was already a virtual document, is forced to change the virtual document so it reflects the assembly hierarchy.
- If the assigned document was checked out, is forced to check the assigned document back in to convert it to a virtual document, or to change its virtual document structure.
Before you export an assembly containing assigned documents that have children, you should evaluate the effects of converting those documents to virtual documents or changing the structure of the assigned virtual document. This is generally applicable; it is not specific to InSight and applies equally when working with virtual documents through any means.
When you export an assembly to a virtual document:
- You can export only from the root level. You cannot export from the folder, leaf or document levels.
- Each time you export an assembly to a virtual document, a new virtual document is created; you cannot re-export to an existing virtual document.
- If a document in the assembly is a child of another document, the parent document is converted to a virtual document.
- The virtual document name in the DMS repository must be unique.
- The assembly name cannot contain characters that are illegal on the file system (slashes, asterisks, etc.).
- A new folder is created in the destination folder you choose and is assigned the following name: <User-Defined Virtual Document Name> Supporting Documents.
- A new DMS repository object is added for each assembly element that is not already in the DMS (that is, root, folders, leaf elements, document placeholders, and file system documents). These new objects are placed in the supporting documents folder.
- For the assembly root, folders, leaf elements and document placeholders, the object in the virtual document is a no-content object.
- Any bound document that is already checked out is checked back in during the export.
- For each document that links to content in a different repository, a link to that content object is created in the Supporting Documents folder.
- For each document in the target export repository, the existing DMS objects are linked to the virtual document.
- For documents that link to content in the file system, a new object is created as a no-content object.
- The document type you specify is applied to all new objects created in the DMS.
The assembly version bindings are mapped to the virtual document as follows:
- If the assembly has version number binding, the virtual document bindings are set to the same number.
- If the assembly binding is version status binding, the virtual document binding defaults to the version label Current.
- If the assembly binding is version label binding, the virtual document bindings are the same.
- Currently the export will fail if there are any documents set to MISSING_VERSION (no binding).