Single field form
The Single field form enables you to define a single field for extraction.
The Single field form includes the following fields.
| Field | Description |
|---|---|
| Single field name |
The name for the field as it appears in the Document Intelligence workspace. |
| Type |
The type of the field. For example, a text or date field. Some field types convert the extracted value into a standard format. For more information, see Data normalization. |
| Converted date format |
The date format that the extracted value is converted to for data normalization. This field is available when the Type field is set to Date. |
| Target table |
The table that stores the document processing results for this use case. |
| Target field |
Field on the target table that you want to align this field with.
Remarque : The use case must have a target table selected. This field is used for integration with other applications. For more information, see Integrate with a custom application or workflow. |
| When the date is ambiguous in a document, DocIntel will interpret it in the following order |
The default interpretation of the date format. For example, if you select Month first in this field, DocIntel will interpret an ambiguous date like 1/2/2024 as January 2 when it extracts that value from a document. If you select Day first, it will interpret it as February 1. This field is available when the Type field is set to Date. |
| When the number is ambiguous in a document, DocIntel will interpret it as |
The default interpretation of the number format. For example, if you select 1,00 in this field, DocIntel will interpret an ambiguous number like 5 as 5,00 instead of 5.00 when it extracts that value from a document. This field is available when the Type field is set to Integer, Decimal, or Float. |
| Reference table |
The table that stores the reference column. It’s automatically populated based on the selected target field. This field displays when the Type field is set to Reference field. |
| Reference column |
The column in the reference table that contains the referenced data. DocIntel uses the reference column to find data that matches the extracted field value when processing a document task. The field value is then converted to the format of the reference. For more information on converted values, see Data normalization. This field is available when the Type field is set to Reference field. |
| Distinguisher(s) |
Additional columns in the reference table that help the user to distinguish between similar records. This field is available when the Type field is set to Reference field. |
| This single field is required for extraction |
Option to make the field required. Required fields can’t be left empty or unreviewed. They also can’t contain ambiguous values. An ambiguous value is a field entry that can be interpreted in more than one way. If it's a reference field type, the required field must have a valid, exact match. By default, DocIntel uses the first matched record. Required fields affect how document tasks are processed in the Fully automated extraction mode. For more information, see Configure data extraction modes. |
Select one of these options for cases when:
|
Option for agent review in situations when DocIntel encounters an ambiguous value in a required field. In such cases, the selected default interpretation will apply to the extracted value. The option is whether to interrupt full automation of document tasks to allow agents to verify the interpreted values. Otherwise, continue automatic processing of document tasks without the agent review. |
| Create multiple single fields | Option to keep the pop-up window displayed on the screen. Enable this field if you’re adding more than one single field to the use case. |