Create a DocAI solution
Use the procedure in this topic to create a DocAI solution where you can add document types, configure field extraction, and enable other user operations.
- Open DocAI Studio.
-
For your first
DocAI
solution, select
Create new solution on the
DocAI
solutions page.
Otherwise, select New to create another DocAI solution.
-
In the
New solution window, set the following settings:
Setting
Description
Solution name
Enter a unique and description name for your DocAI solution.
-
Names can have a maximum of 40 characters.
-
This name is also used for processes created and forms generated with this DocAI solution.
-
If the given solution name already exists, an error is displayed.
-
If an existing item, such as a form group, has the same name as the solution, you can either change the name of the current item or rename the existing solution and republish.
-
If you rename a solution after it is published, the existing items, including the associated process, are updated with the new name.
-
No special characters are allowed. Exceptions are the hyphen and underscore.
Processing mode
Select how your solution is processed. Select from the following values:
-
Folder: Documents are scanned in a batch. (Default)
-
Document: Single documents are scanned one at a time to process documents independently. Rescan replaces the document with a new document.
When you process single documents, settings related to document separation and multiple document export are disabled.
Recognition provider
Select from:
- OmniPage:
-
Fast and ideal for machine-printed documents. (Default)
- Tungsten:
-
Sends documents to the Azure AI Document Intelligence Service using a Tungsten volume. This performs raw text and data recognition. We recommend this provider for difficult-to-read hand printed documents, or forms with fields with bounding boxes.
When selected, the following additional setting is available.
- Perform OCR on entire document at once:
-
When set to Yes, an entire document is sent to the Azure AI Document Intelligence Service in a single transaction. (Default: No)
When set to No, each page is sent to the Azure AI Document Intelligence Service separately.
- Tungsten with Layout:
-
Sends documents to the Azure AI Document Intelligence Service using a Tungsten volume. This performs document recognition using the text hierarchy and structure. For example, table fields.
When selected, the following table detection settings are available:
- Use for table detection:
-
When set to Yes, the Azure AI Document Intelligence Service performs table detection instead of Tungsten table detection.
The Azure AI Document Intelligence Service is more optimized to detect tables than the default Tungsten table detection.
When set to No, the default Tungsten table detection is used.
- Perform OCR on entire document at once:
-
When set to Yes, an entire document is sent to the Azure AI Document Intelligence Service in a single transaction. (Default: No)
When set to No, each page is sent to the Azure AI Document Intelligence Service separately.
If you are processing multi-page tables, select this setting. Otherwise, each page of the table will be extracted as a separate table.
Additional recognition providers may be available in this list if configured in TotalAgility Advanced Studio. For more information about configuring recognition engines, see the Tungsten TotalAgility Advanced Studio Help.
If you select a different Azure AI Document Intelligence Service endpoint, both the Use for table detection and Perform OCR on entire document at once settings are available. The same performance issues apply.
Enable generative AI classification
Set this setting to Yes to use generative AI classification when trainable classification fails. (Default: No)
I you change your mind about any of these settings, you can modify the Solution name on the page. You can edit the other settings on the page.
-
-
Select
Create solution.
Your newly added solution is displayed for configuration.