Assembly Structure

When you build an assembly you create its structure. You can add the folders, leaf elements, documents, and document placeholders that make up the hierarchical content of the assembly.

As you add elements to the assembly tree, consider the following rules:

— An assembly can have major and minor divisions. The major and minor settings can be found on the Folder Elements in an assembly.

— You cannot add an element at the same level as the root.

— Documents you add to the assembly are saved as links to the document location in a repository or secure file system. No content is stored in Ennov InSight .

— An element you add is inserted as the last child of the selected element.

— You cannot add a leaf as a child of a leaf or as a child of another document.

— You cannot add a folder or a leaf as a child of a document or a document placeholder.

— To make an assigned document or document placeholder the child of another document or document placeholder, you must drag it from the document browse dialog box or promote or demote it.

— You cannot directly add an assigned document or document placeholder as a child of an assigned document or a document placeholder.

— When specifying the source location for a placeholder, do not end the source location with a backslash.

— You can only assign documents from one DMS at one time.

— To add multiple documents at the same time from the DMS browse window in Ennov InSight , do the following: - Shift+click adjacent documents to choose them. - Ctrl+click nonadjacent documents to choose them.

— When you add a specific version of a document to the assembly, the document binding rule for that document defaults to Bind to Version and the document's version number.

Ennov InSight Publisher 7.3

Modify Assembly Attributes

— When creating a new assembly, an error may occur if anything but the root is selected when previewing the assembly or template source.

Assembly Structure Table

The following guidelines may help you build an assembly.

Automatic Leaf Creation

You can create leaf elements automatically by dragging documents from the DMS browse window into an assembly folder or root node.

Based on the Create Leaf File attribute for an assembly, leaf creation behaves as follows when you add documents to the assembly.

When the Create Leaf Elements option is set to Yes and you drag documents to the root or a folder:

— A leaf element is added for each document.

— Each leaf element is created as the last child of the target element. — Each leaf has the same name as the corresponding document.

— Automatically, the Leaf Status for each leaf element is set to the default Leaf Status value configured in Data Administration.

— The Use Native File attribute of a new leaf is set to Yes if your system administrator configured the extension for the corresponding document to generate this attribute value. Your system administrator can configure the extension in the dms.nativeLeafExtension property in the insight.var file. You can extend the list by modifying the insight.var file. The following example shows the list of extensions that are set forEnnov

InSight by default. If additional extensions are needed, you must include the complete list of default extensions

(shown below) along with the additional file types you are adding when using the dms.nativeLeafExtension property in the Insight.var configuration file. Example:

dms.nativeLeafExtension=sas,xpt,xml,sc2,sct,sdq,sd2,ssd,ssp,stc,stx,sxs,s xx,sx,aml,dmn,imx,jmp,ecg

Ennov InSight Publisher 7.3 Assembly Structure

When the Create Leaf Element option is set to No and you drag a document to the root or a folder, you can expect the following behavior:

— A document you drag to an assigned document is added as the last child of that document.

— A document placeholder to which you drag a document becomes an assigned document. — A document you drag to the root or a folder becomes the last child of that element.

Regardless of whether leaf elements are created automatically: when you drag a document or documents to a leaf, they are assigned to that leaf and no additional leaf elements are created.

When a leaf element is created automatically during document assignment, the leaf is named with the document file name. The extension on the leaf file name is stripped and Ennov InSight later assigns the appropriate extension during publishing.

Reference Leaf Elements

A reference leaf element has the same life cycle requirements as a standard leaf element in the assembly. Both require a unique ID and life cycle management to track modified file information.

Reference leaf element features:

— A reference leaf element allows multiple leaf elements to point to a single piece of content or another leaf in either a current or submitted assembly.

— A reference leaf cannot point to another leaf in a standalone assembly.

— A reference leaf must include the application number, prefix and the sequence number.

— To reference an entity across assemblies, the target leaf must be included in a life cycle or supporting sequence. — A reference leaf element does not have the Leaf Status attribute.