Synchronize Document Attributes
As the documents change in the DMS, synchronizing document attributes enables you to see the current DMS attributes in Ennov InSight.
Attributes that map to DMS values are indicated by 
on the
Document Attributes page.
When a DMS synchronization occurs, the following happen:
- The value for Last Repository Data Retrieval (on the Document Attributes page) is updated for the root, all folders, leaf elements, documents, and document placeholders.
- All calculated and mapped attributes (for example, assignment status and version numbers) are updated.
- Any other attributes for which you changed the values in Ennov InSight revert to their DMS attribute values.
Keep in mind the following:
- HTML text strings enclosed in angle brackets (< >) that map to Ennov InSight attributes do not appear in document attributes. HTML numeric strings map correctly.
- Running a DMS Synchronization on the root of a lifecycle working view performs a synchronization on documents from the previous sequence. Updates to documents from previous sequences do not become part of the current active view. Be aware, however, that if you synchronize the root and thereafter find unexpected attribute values on documents from previous sequences, you should check the same document in the current active view to determine the values of the document in the previous sequence.
- Running a DMS Synchronization from the Working View sends all previous sequences for Rendition & Extraction. Only documents for which there are no renditions and extractions are sent.
- Synchronizing large assemblies can slow the repository's performance and prevent other users from accessing it temporarily.
- Synchronization may be slower than expected if the DMS has limited space.
- Ennov InSight binds directly to specific versions of documents in a DMS repository. Because of this, Ennov InSight does not support the automatic or manual deletion of previous versions in a DMS. If you delete versions in your repository, Ennov InSight may generate an error when you attempt to synchronize to a version that no longer exists. You can avoid this by reassigning the document through the binding rule to a version that still exists.