New option to allow for more split out 'silos' in which to check for duplicate emails, to support business models where same email is explicitly sent to multiple business areas for multiple work items
Last updated
Was this helpful?
As part of day-to-day processing in Email systems and integration with other systems, it is possible for errors to result in duplicate emails. To combat this Enate provides built-in capabilities to deduplicate received emails. Let’s take a look at the details for this.
As a core principle, Enate will generate or update 1 Work Item per received Email after deduplication. To guard against accidental creation of multiple work items caused by duplicate incoming emails, Enate checks for such duplicates and deduplicates them so that only one work item is created. This is how Enate is set up as standard, and is termed ‘Global Level deduplication’.
Global Level Deduplication (default) – where emails deduplication logic is run globally on all emails, and any mails considered duplicate are always de-duped.
However in some business operations, it is possible that the same exact email will be explicitly forwarded into two different parts of the business, with the intention of creating two different work items in Enate. In order to allow this, Enate has now introduced a new feature to allow this deduplication scope to be at a 'per email connector' level:
Per-Connector Level Deduplication – where emails are deduped if received into the same individual Email Connector, but are not deduped if the two mails are sent into two separate Email Connectors in Enate. In Per-Connector mode, Enate will only search for existing Emails that have been received to the same Email Connector as configured in Enate.
For a more detailed discussion of Email Deduplication, including likely Email Server behaviour and the impact on work item creation in Enate, check out the section in the main help articles.
