Document Binding
When you create an assembly, you choose a default document binding. The documents you assign to the assembly assume the specified document binding.
For example, if you set your document binding to a status of approved, Ennov InSight clearly indicates when the assigned documents are in or out of compliance with that rule.
Keep in mind the following about document binding:
- When you apply a document binding to all children, it is not applied to child documents that reference a branched version and that are set to 'Bind to Version'. In this case, after you navigate through any messages, the selected binding is applied to documents up to, but not including, the document that references the branched version. You can apply the version binding to documents individually, or you can select a more granular range that does not include the branched document versions.
- When you create an assembly from a virtual document or when you assign a virtual document to an assembly, no warning is displayed if the virtual document contains binding rules that are not defined in Ennov InSight by the administrator.
- Including the same document in an assembly twice when one of the documents is bound to a non-existent status (such as Approved) produces the inclusion of this document as a bound document in an exported virtual document.
- Binding cannot be removed after it is applied. However, it can be modified by using the Apply Binding to All Children option.
- Binding can be applied to DMS documents only, and does not apply to file system documents.
- Your options for applying binding rules are controlled by the configuration of Ennov InSight Data Administration, your DMS, and your permissions in the system.