Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
In this version of Enate we've focussed on making a wide range of number of smaller adjustments, enhancements and fixes throughout the system, mixed in with some useful new features which are detailed below:
In the AI space, we've added a couple of useful features to give you more control and precision on where and how you implement
You can now set your own Confidence Threshold for the Integrations you've switched on in Marketplace, allowing you to adjust the levels of work that Agents verify for any automated activity.
You can now opt specific Email Mailbox Connects out of Email Integrations you're running, letting you implement new AI technology while safeguarding specific work activities which you want to keep running as-is.
We've made a number of enhancements relating to how incoming emails are treated, to make sure
made changes to how emails with invalid addresses are treated, to allow more of them to be processed.
Added support for Wildcard Email Routes which let you process incoming emails where Enate has been Bcc'd.
changed how we identify if incoming emails have been sent out by your Enate system, to ensure mails sent from 3rd party systems which could be confused with those get processed.
Enate's Binary Storage is used for storing raw communications, communication attachments, files attached to work items, and files exported from Advanced Search views. Enate is always provisioned with the primary binary storage configured in an Enate Azure tenant. However, with the arrival of v2023.5, you've now got the option of switching where you store your Binary data to be one of your own Azure storage locations.
In addition to these enhancements we've added a large number of fixes to help improve and stabilise the use of certain recent features. You can check out this in the Release Notes section.
With the release of 2023.5 Enate is introducing improvements to how incoming emails are handled. The intention here is to handle any potential issues as well as possible, attempting to process whatever emails that can be. The most important changes that have been made refer to how Enate treats:
Emails recieved where one or more addresses are invalid (e.g. those involving Distribution Lists),
Emails received which have been BCC'd only to the Enate mailbox address, and
Emails sent into Enate with a 'from' addresse which this Enate instance itself uses to send emails out.
Previously in Enate, incoming emails that contained invalid email addresses did not meet the requirements to be processed, and were rejected by the Enate system. This can often occur if the email addresses contain Distribution lists, where the text name of the distribution list is supplied rather than the associated email addresses.
With version 2023.5 we've adjusted how such emails are handled, attempting to process them where we can, as follows:
If the email contains at least one valid email address which can be used for processing, we will process the mail, but will mark the invalid email address wherever it is displayed.
If ALL of the emails addresses which could potentialy be used for processing are invalid, the system will place the email in the 'Unprocessed emails' list, allowing agents to review and decide on how to proceed.
To help users identify which emails have come in with invalid email addresses, a notification will now be shown in Work Manager wherever that email is displayed, letting users know that it contains invalid address - and will then list all the invalid email addresses it contains.
Previously when Enate was Bcc'd in emails, upon arrival into Enate they would be directed to the Unprocessed emails list (due to not having a 'To' address value, the attribute which Enate uses for routing mails to create new Work Items).
To help reduce the ocurrences of such mails landing in 'Unprocessed emails' in this situation, Enate now supports the ability to configure Email Routes which essentially use the knowledge of which email addresses these mails come from to allow it to be processed. To help with this, you're now able to create Email Routes where the Routing Rules contain:
a '*' wildcard email address setting (i.e. the 'To' address of the incoming mail) along with
a known email address for the 'Sender List includes' (i.e. the 'From' address of the incoming mail).
This lets you set Enate to process emails coming in from a known email address even when Enate is only set as the bcc addresee. See details below for how to create these Email Routes.
Wildcard routes are created in the same way non-wildcard routes are created, via the 'Routes' page in the Email section of Builder. Simply click to create a new email route and fill in the email route pop-up information as required. To set this as a Wildcard Route to handle Bcc scenario, when filling out the Routing Rules information users should put a '*' wildcard asterisk as the 'Email Address', and then in the 'Sender List Includes' field, set the name of the known email address that such mails would be coming from. Multiple such addresses can be added to a single Route, with a ';' semicolon character between.
You should create as many such Wildcard Routes for a single Email Connector as there are different Work Item types you wish to be creating from that connector.
When ordering their email routes into a hierarchy, users should always ensure that non-wildcard routes appear above wildcard routes, with overall fallback routes appearing after the wildcard routes at the very bottom of the list.
Note: There are now a number of important rules to follow when including such Wildcard '*' Email Routes within your list of Email Routes, in order to ensure consistent creation of Work Items. See this section for a list of these rules.
We are making a change in how we analyse incoming emails to determine if they have come from this Enate instance. Until now, the system has used the 'From' address of incoming mails for determining if the mail has come from an address which the Enate system knows that it sends mails out from. The system then ignores such emails as it will have already been dealt with as it was being sent out - this helps reduce creation of duplicate work items. However in some circumstances, third party systems can send emails into Enate which also use those same email addresses as their 'From' - and this results in those emails not being processed by Enate. The new approach avoid this occuring, and such emails from third party systems will now process into Enate. Instead of using the 'From' address, Enate now uses the 'MessageID' of the incoming email to check if it has come from this system. Incoming emails which HAVE actually been sent out by this Enate instance will be identified correctly (and will be ignored), while mails coming from 3rd party systems which would previsouly have been ignored due to their From address will now be processed as desired.
Please note that since all of the above changes for Incoming emails involve processing more emails than previously, users may experience an increase in the volume of emails being seen in their system.
Binary storage is used for storing large files. At Enate, we employ it to store raw communications, communication attachments, files attached to work items, and files exported from Advanced Search views.
Enate is always provisioned with the primary binary storage configured in an Enate Azure tenant. You can see details of your Binary Storage locations in the 'Azure Binary Storage' section of the System Settings in Builder.
However, you can now if you wish choose to change where your binary data is stored, and switch this to be your own Azure tenant.
Important note: Changing your Binary storage location will not transfer your existing data to the new location. You should exercise extreme care when making this change, in order to avoid irrevocable loss of binary data. You should contact Enate's Customer Success team if you wish to make such a change, so the activity can be carried out with our team's advice.
To enable this feature of setting your own storage locations, you will need to perform activities outside Enate as well as within this section of Builder. You will need to do the following:
Create two Azure Storage Accounts in two separate Azure Regions within your Azure tenant. We recommend that one of these regions is Europe West to maximise performance.
Create an Azure App Registration that is granted access to these storage accounts.
Configure Enate to use these storage accounts rather than the Enate Default.
NOTE: If your organisation is not proficient at managing Azure storage then you should NOT adopt this option. Deletion or corruption of data in these storage accounts will result in immediate and irrevocable data loss.
To add a new Storage Location in Enate, click the '+' icon in the Azure Binary Storage section in Builder's system settings. This will show a popup where details of the new Storage location you have set up in Azure should be entered:
The general data asked for is as follows:
Important Note: Once you set the encryption key and key size here, they cannot be changes. You must ensure that you securely save the encryption key as it cannot be modified later.
In addition to these General settings, there is also information to fill in on the Azure details tab:
You can generate Certificates or upload an existing on by selecting the 'Authentication ith Certificate' option on the Azure details tab. This will bring up a further popup to allow you to generate or upload a certificate:
If you fill in the Subject here and click on Submit, a certificate will be generates and you will be given a Download link to allow you to download the public key certificate.
You should upload this Certificate in the Azure app registration 'certificate and secret' section.
Note: You need to make sure that you upload the certificate / create the secret in Azure App Registration before saving, as the configuration will not save until it can successfully test that all the information provided is correct.
Alternatively you can Upload an existing certificate if you have one.
Once you have entered all required information you can Test your connection and, once successfully tested, save it.
Once you have successfully created your own Azure storage locations and linked it to your Enate instance, yo can choose to set that location as your primary storage location. You will be met with a popup asking you to confirm your decision, and reminding you that your existing data will NOT be automatically transferred to the new location.
Access to being able to modify these settings should be tightly controlled. Access is managed via the 'Binary Storage' access option within Builder User Roles setup, under the 'Edit System Settings' section:
When dealing with storage locations and encryption keys for Binary data, there are a number of important points to keep in mind:
Only one single Binary Storage location can be active at one time.
You cannot be make any updates to or delete any Enate-managed Binary Storage.
The Encryption Key and Size cannot be changed after creating
While you can switch between binary storage configurations, this will NOT automatically migrate any of your existing data, so you must exercise extreme caution when choosing this option.
You can only delete a Storage location if that configuration has yet to ever be used (And you cannot do this at all with any Enate-managed storage locations).
Management of your Certificates / Secrets with regards to e.g. expiry of these is completely managed be you, and no management of these is provided by Enate.
To reiterate: If you are thinking of changing you Binary Storage location settings, we stringly recommend that you contact Enate's Customer Success team, so the activity can be carried out with our team's advice.
In v2023.5, Enate's Quickfind is being enhanced to allow users to be able to search for text strings which contain '.' decimal points. This is designed to make it easier for users to search using internal (i.e. non-Enate) reference numbers. Previously this '.' character was ignored.
Example:
Previously, if a user was searching for a reference number of '12345.12555', the search would have ignored the '.' character and searched for two separate strings either side of the dot marker.
Now, Quickfind will recognize this as a single search string and search for '12345.12345 in its entirety.
In the image above, a user has begun searching by typing '12345.12'. Quickfind has started bringing back results which contain 12345.12.
This enhancement will support numeric reference numbers which contain a '.' character up to 10 digits, e.g. NNNNN.NNNNN, and any variants of this with the '.' character anywhere within the string.
It should be noted that Quickfind does not support other digit separators such as commas, or multiple decimal points within a single string, for example '100.34.67'.
When creating an email route containing a wildcard route, there are some important rules that apply, to keep routing of incoming emails working consistently at runeimt. See the table below for a full list of rules regarding the use of working with Email Routes if wildcard (i.e. '*') email routes are involved.
Note: The system will show error messages when a user attempts an activity which may break these rules.
| Activity | Rule | Related API |
|---|---|---|
If a user attempts to move a route into an order that does not correspond with the required hierarchy, the route will return to where it was and a error message will be displayed.
Note: for a list of recent changes to Enate Marketplace integrations, see this section.
2023.5.9.0 is a Hotfix release for version 2023.5 of Enate that contains one bug fix which has been added since the release of the previous version. There are no new enhancements, features, breaking changes or additional breaking API changes in this release, and no additional known issues.
The change log contains a detailed list of the bug fixes in this version. There are no new features, enhancements and no new known issues. A downloadable copy of the Bug Fixes Change Log is available below.
2023.5.8.0 is a Hotfix release for version 2023.5 of Enate that contains one bug fix which has been added since the release of the previous version. There are no new enhancements, features, breaking changes or additional breaking API changes in this release, and no additional known issues.
The change log contains a detailed list of the bug fixes in this version. There are no new features, enhancements and no new known issues. A downloadable copy of the Bug Fixes Change Log is available below.
2023.5.7.0 is a Hotfix release for version 2023.5 of Enate that contains a bug fix and an enhancement that have been added since the release of the previous version. There are no new features, breaking changes or additional breaking API changes in this release, and no additional known issues.
The change log contains a detailed list of the bug fixes in this version. There are no new features, enhancements and no new known issues. A downloadable copy of the Bug Fixes Change Log is available below.
2023.5.6.0 is a Hotfix release for version 2023.5 of Enate that contains bug fixes that have been added since the release of the previous version. There are no new features, enhancements, breaking changes or additional breaking API changes in this release, and no additional known issues.
The change log contains a detailed list of the bug fixes in this version. There are no new features, enhancements and no new known issues. A downloadable copy of the Bug Fixes Change Log is available below.
2023.5.5.0 is a Hotfix release for version 2023.5 of Enate that contains bug fixes that have been added since the release of the previous version. There are no new features, enhancements, breaking changes or additional breaking API changes in this release, and no additional known issues.
The change log contains a detailed list of the bug fixes in this version. There are no new features, enhancements and no new known issues. A downloadable copy of the Bug Fixes Change Log is available below.
2023.5.3.0 is a HotFix release for version 2023.5 of Enate that contains a bug fixes that has been added since the release of the previous version, plus one Breaking API Change. There are no new features, enhancements, or further breaking changes in this release, and no additional known issues.
The change log contains a detailed list of the bug fixes in this version. There are no new features, enhancements and no new known issues. A downloadable copy of the Bug Fixes Change Log is available below.
Below is a copy of the breaking changes document for changes between 2023.5.0 and 2023.5.1 of Enate. It contains information about all the breaking changes within the Data Warehouse and Enate's APIs, and includes the validation codes for version 2023.5.1.
This is a downloadable copy of the API changes. It contains information about the API changes that have occurred between versions 2023.5.0 and 2023.5.1 of Enate.
2023.5.2.0 is the production release for version 2023.5 of Enate. It contains a number of new features, enhancements and bug fixes.
The change log contains a detailed list of the new features, enhancements, bug fixes and known issues in version 2023.5.2.0 of Enate. A downloadable copy of the New Features & Enhancements Change Log, the Bug Fixes Change Log and the Known Issues Change Log are available below.
This is a downloadable copy of the new features and enhancements in this version of Enate.
This is a downloadable copy of the bug fixes in this version of Enate.
This is a downloadable copy of the known issues in this version of Enate.
This is a downloadable copy of the API changes in Enate's 2023.5 release. It contains information about the API changes that have occurred between versions 2023.4 and 2023.5 of Enate.
This is a downloadable copy of the warehouse database data dictionary for all 2023.5 versions of Enate.
Below is a copy of the breaking changes document for version 2023.5.0 of Enate. It contains information about all the breaking changes within the Data Warehouse and Enate's APIs, and includes the validation codes for version 2023.5.0.
With the introduction of version 2023.5, Builder users will now have the ability to set the confidence levels for their Integrations (such as EnateAI's) in the General Settings section. This will give users a greater level of control and flexiility when implementing Integrations into their operations, letting them quickly and easily adjust Integrations confidence levels as needed to allow more of fewer Work Items to be passed via Agents for verification after AI has taken some action.
Within Builder, go to the General Settings page, then to the 'Integrations' section.
This section allows users to set the confidence Thresholds for all available Integrations which use them. level for:
Document Classification Integrations
Email Classifications Integrations
Document Extraction Integrations
Thank You Email Integrations
To set the confidence level users simply need to move the slider for the desired integration. The higher the confidence implies a greater degree of trust in the results of the integration, while a lower confidence level will see a greater degree of human involvement.
If users do not have a specific integration activated in the Enate Marketplace, there will be a 'Get This Integration' button displayed instead of the slider. Clicking on this button will take the user to the section of the Enate Marketplace where the Integration offerings for that confidence level option are.
For Integrations that do not work with Confidence Thresholds, no sliders are provided. Examples of this are Sentiment Analysis and Email Data Extraction Integrations.
These confidence threshold sliders control the threshold levels for ALL Integration patterns, no matter which technology provider has been enabled for it in Marketplace.
With the release of v2023.5, we're giving you more fine-tuning control over your Email Integrations. Specifically, you can now choose to disable any of your Email-related Integrations for specific Mailbox Connectors, so the technology doesn't run for any emails coming in to that specific mailbox. This more flexible steup lets you implement new AI technology while safeguarding specific work activities which you want to keep running as-is.
When an Email-related Integration is activated in the Enate Marketplace, it is automatically applied to all email connectors. However, in certain scenarios, users may only want certain Email integrations to apply to certain email connectors. To disable integrations for a specific connector users should go to the Connectors page in the Email section of Builder. There they will see a new column titled 'Integrations', which will show the total number of Integrations available, and the number of those which are switched on for that Connector, e.g. '3/4' will mean that 3 of the 4 email integrations are running.
Users must have the edit Email Connectors feature access granted in their User Role to be able to edit integrations for connectors.
To disable / re-enable integrations for a specific connector simply click on the relevant link in the 'Integrations' column box for the desired connector. This will bring up the 'Edit a Connector' pop-up, showing all activated Email integrations for that connector.
Toggle the settings on / off as desired to enable / disable an Integration. Please note the following:
Whenever a new email connector is created, ALL integrations that are active in Marketplace will automatically be activated for the new connector.
Whenever an Integration is enabled in Marketplace for a certain Email Integration pattern, e.g. 'Sentiment Analysis', it will be switched on for ALL Connectors. If an EmailAI pattern gets switched off in Marketplace and subsequently turned back on, it will be active in all connectors once again.
Email Integrations cannot be turned on for email connectors that are just for outgoing emails, since currently these integrations are only relevant for incoming emails. For these connector an 'NA' will be displayed in the 'Integrations' column.
| Item | Details |
|---|---|
| Item | Details |
|---|---|
Name
A Name for this Binary Storage Location
Description
A Description for this Binary Storage Location
Primary Endpoint
The first Azure storage location primary endpoint URL
Secondary Endpoint
The second Azure storage location primary endpoint URL
Container Name
The exact container name of first Azure storage account. NOTE: both the first and second storage account must have the same container name.
Key Size
This will be used to encrypt and decrypt binary data.
Encryption Key (plus Confirmation)
This secret key will be used to encrypt and decrypt binary data.
Tenant ID or Domain
Get this from the registered app 'Host Name' in the overview menu in Azure
Application ID
Get this from the registered app 'Application (client) ID' in the overview menu in Azure
Authentication with Certificate / with Client Secret
You can generate a secret in the Azure app registration certification and secret section, however Enate recommends using the Certificate approach here.
Updating an Email Route
Updating a NON-wildcard email route to a wildcard email route is now restricted.
Email Route - Update
Updating an Email Route
Updating a wildcard email route to a NON-wildcard email route is now restricted.
Email Route - Update
Creating or Updating an Email Route
The system does not allow using a wildcard address for the sender list when the route's email address is also a wildcard.
Email Route - Create Email Route - Update
Creating or Updating an Email Route
A wildcard route requires a sender list to be included.
Email Route - Create Email Route - Update
Ordering Multiple Routes
When using a wildcard, a strict routing order exists: 1. Non-wildcard Routes 2. Wildcard Routes 3. Fallback Routes
Email Route - Get All For Connector
Creating an Email Route
When a email route is created, whether it is a wildcard or not, its order is based on the criteria is determined by the order (stated above). Route orders can be adjusted accordingly after creation.
Email Route - Create
Moving an Email Route
Routes can only be rearranged within their respective type ranges. For example, if it's a wild card route, the system allows moving it within the wild card order range (min-max). The same applies to non-wildcard routes, where the system permits movement within the non-wildcard order range (min-max). If routes are moved beyond their designated range, the system will generate an error.
Email Route - Move Route
To help users understand how using wildcard routes will impact BCC emails the table below shows the possible scenarios that can occur:
| Scenario | Result |
|---|---|
No wildcard routes in connector - Sent an incoming email with BCC connector. No TO/CC.
Email will land in 'Unprocessed Emails'
No wildcard routes in connector - Sent an incoming email with BCC connector. With TO/CC that don't correspond with any current Routes.
Email will land in 'Unprocessed Emails'
Wildcard routes in connector - Sent an incoming email with BCC connector. Without TO/CC.
Work Item should be created with BCC email address.
Wildcard routes in connector - Sent an incoming email with BCC connector. With TO/CC that don't correspond with any current Routes.
Work Item should be created with BCC email address.
Wildcard routes in connector - Sent an incoming email with multiple connector addresses in BCC connector. No TO/CC that don't correspond with any current Routes.
Work Item will be created only for one (first received email address) connector. Rest of the arriving emails will be marked duplicate and therefore ignored.
Wild card routes in connector - Sent an incoming email with multiple connector addresses in BCC connector. With TO/CC that don't correspond with any current Routes.
Work Item will be created only for one (first received email address) connector. Rest of the arriving emails will be marked duplicate and therefore ignored.
Wild card routes in connector - Sent an incoming email with multiple connector addresses in TO/CC and BCC connector.
Work Item should be processed for TO/CC address. The BCC will not be processed.
Wildcard routes in connector, which contain Multiple 'Sender List Contains' values. Send an incoming email from one of the sender list addresses, BCCing the connector address.
Work Item should be created with BCC email address.
Wildcard routes in connector. Disable the Wildcard route. Send an incoming email from one of the sender list adresses and BCC the connector address.
Email will land in 'Unprocessed Emails'
Wildcard routes in connector. Configure the non Wildcard route with the same set of rules. Send an incoming email from one of the sender list adresses, BCCing the connector address.
Work item will be created for the wildcard route.
