eDOCS DM has the capability to store e-mail properties such as receiver, sender, carbon copy and date. It also captures and stores information about mail threads/ID to ensure the same mail is not saved more than once and that its relationship to other e-mails is retained within the repository.
But what if you have an installation where strong email integration has not been in place for an appropriate length of time, where some clients are missing registry mapping, or where the cc fi eld mapping was not added from the beginning? This can lead to email being stored in the repository with incomplete data, loosing quality, structure and security in your DM library.
Other common scenarios where the quality of your DM library can be affected include the receiver fi eld in the profi le card being too short, or when a user has imported emails to DM Explorer or through drag-and-drop but DM does not recognise the email format. As a result, important email-specific metadata fields can be lost.