Comment on page
Auto-extract document data - Document Extraction
The Document Extraction component, available in Enate Marketplace, automatically extracts the relevant data from files attached to incoming emails so that this data can be used in further processing of the work item, saving your agents time and effort. This also means that documents such as PDFs can be scanned and used both to start Cases in Enate and to form part of the ongoing process's activities.
When a Document Extraction Action runs for a Case, documents attached to the Case can be submitted to your desired technology for scanning and the processed output files will be returned and automatically attached to the Case.
If at any point the technology you're using is not confident enough of the results, based on a confidence threshold that you can set, Enate will instantly transfer the work to an agent in Work Manager to look over and verify, giving you that 'human in the loop' support.
Check out this video to find out more:
When the Case is run in Work Manager, relevant data from files attached to incoming emails for it will be automatically analyzed and extracted.
If the technology you're using is confident enough about its data extraction results, this Action won't even need to be seen by a human user, it will simply be completed automatically and the Case will move on to the next Action. The completed data extraction Action can still be viewed if you click on it, but it won't need to be handed over to a human user for involvement.
However, if the extraction technology is less confident in its data extraction results, the Action will be handed over to a human user when they next hit 'pull from Queue' in their home page, to pick up and look over. When an agent opens the Action, they'll see that it's been given to them because some further checks are required.
To do this, the agent just needs to scroll to the 'validation station' screen in the action, which shows the scanned document image and the resulting extracted table of data values. This lets the agent see where those lower confidence levels are highlighted, review them and make any necessary corrections manually. This can viewed in-situ, or expanded out to a popup to display full screen.
Every time this is done, the technology will learn and get a little bit better at its data extraction suggestions. If you notice that the technology is regularly getting its suggestions wrong, speak to your admin team about modifying the confidence threshold.
Once the agent is happy that the extracted data is as desired, they can click to mark the Action as completed successfully.
There are a few steps to follow when it comes to switching Document Extraction component on with Infrrd.
You'll first need go to the to Marketplace section of Enate Builder and click to activate the Infrrd Document Extraction component.
In the following pop-up, you'll need to add the URL and account ID of your Infrrd platform, as well as the model(s) you want to use.
To add a model, you'll first need to make sure that it is already configured in your Infrrd platform. You'll then need to enter the following information, all of which can be found in your Infrrd platform.
- Model ID
- Model name
- API key
You can add as many models as you like. These models are what determines how documents get classified. For example, you might have configured a model that is trained to only identify invoices, so that would be the model you would want to use for your invoice processes.
Once you have entered all of the above information, you'll need to test the connection.
Once the connection has been tested successfully, click to activate.
You'll then need to set up your Case flow to support the Document Extraction component. This involves adding an 'IDP Data Extraction' Action in Enate Builder to use in your desired Case flows.
You can either add an existing one from the Actions list if one has already been created, or you can create a brand new one.
IDP Data Extraction Actions can be created in the same way any other Action is created in Enate: either from the Service Line page, or directly from within your Case flow.
To create an IDP Data Extraction Action from the Service Line page, select to create a new Action under the desired service line, give the action a name and a description and choose approval action from the type drop down. You can also give the Action a global checklist if you wish.
To create an IDP Document Extraction Action directly from the Case flow itself, open a Case flow in edit mode, click on an Action's menu and then instead of clicking to add an existing Action, select to create a new Action by clicking the '+' icon.
Give the Action a name, add a description if you wish and for its type, select 'Approval'. When you click 'OK, the Action will be created and added to the Case flow.
Once you have added your approval action to your flow, you will then need to fill out its settings.
On the Action Info tab you will need to set when it's due and set an Allocation rule.
Note that this Allocation should be who the Action should go to to review if the extraction technology is not confident enough in its data extraction results. If the technology you're using is confident enough about its data extraction results, this Action won't even need to be seen by a human user, it will simply be completed automatically and the Case will move on to the next Action.
There's also general settings for the Action too, and ability to set a custom card, again only really for use in the unlikely event that someone needs to intervene and view the action in Work Manager.
Next, go to the IDP Document Extraction tab to define the settings which specifically relate to the approval activities.
You'll need to fill in the Extraction Model - this is the ID of the model you want to use for that process.
You'll also need to fill in the input and output tags. The input tag is the tag that the file/document must be tagged with in Work Manager in order to be eligible for document extraction processing and output tags. The output tag is the tag that will be assigned to the file/document in Work Manager once the document extraction process has completed.
Once you have filled in the above settings details, set the Case live.
In order to integrate with ABBYY FlexiCapture, you need to:
Watch this video to find out more about integrating Enate and ABBYY FlexiCapture.
Note: Only filetypes supported by ABBYY v12 onwards will be submitted. See the following link for list of formats supported by ABBYY: https://help.abbyy.com/en-us/flexicapture/12/standalone_operator/input_formats
In order to enable ABBYY FlexiCapture integration, a connection to an active ABBYY instance must be configured in Enate's Builder app. These settings are accessed from the ABBYY section in Enate's Marketplace:
Clicking on 'Activate' will take you to a page where you can view your OCR Connections. Click to add a new connection and then in the subsequent pop-up, provide the following details:
Once you have supplied this information, click to test the connection.
Once the connection has been tested successfully, your ABBYY integration is successfully connected with Enate. Enate will now automatically sync project lists with ABBYY; ABBYY projects do not need to be manually added to Enate.
Important note: The ABBYY server must be accessible from the Enate Application tier AND from the browsers of your end users. In the case of Enate SaaS this means that ABBYY must be internet-facing.
Once you have successfully set up an ABBYY FlexiCapture connection, you then need to create an ABBYY FlexiCapture Action type.
To do this, in the Service Lines page select, which service line you would like to add the ABBYY Action to and then click on the plus symbol next to the 'Process Search' box. This will bring up a drop down menu where you can select an Action.
This will open up a new Action for you to create.
Add a name and description to your Action and then in the 'type' drop down select 'ABBYY OCR'.
You can then choose to add a global checklist to your ABBYY FlexiCapture Action. This contains a standard checklist of activities that will be added any time this Action type is added to a Case flow. See here for more information on checklists.
Once you are happy with your Action, hit save to create it. This Action can now be added to new and existing business processes by selecting it from the dropdown list when adding a new Action to a Case.
Alternatively, you can add an ABBYY FlexiCapture Action type directly from the Case flow itself.
To do this, open your desired Case flow in edit mode, click on an Action's menu and then instead of clicking to add an existing Action, select to create a new Action by clicking the '+' icon.
Give the Action a name, add a description if you wish and for its 'type', select 'ABBYY OCR'. This will add the ABBYY FlexiCapture Action to the Case flow.
Once you has successfully set up an ABBYY connection, you then need to add an ABBYY FlexiCapture Action in your Case flow.
Select the '+' icon on the Add Action Menu in the desired Case flow. Give the ABBYY Action a name and then assign it as an ABBYY OCR Action Type. This will add an ABBYY Action to the Case flow.
Once an ABBYY FlexiCapture Action has been added to your Case flow, a new section will display in the Action info grid.
You now need to configure the settings for the new Action you have added to your Case.
Click on the Action in the flow to highlight it in the info section. In the Action Info tab, you need to add the following information:
Additionally, once an ABBYY Action has been added to your Case flow, a new 'ABBYY FlexiCapture' tab will display in the info grid.
Here you need to add the following settings that are only relevant for ABBYY Actions:
Note : As an additional validation check, when configuring Case flows that includes ABBYY Actions, if any of the referenced platform are now deleted, the system will prompt you to replace this with an active ABBYY Platform.
Your ABBYY FlexiCapture Action is now ready to be used in your Case flows at runtime.