Field form for use case setup
The Field form enables you to define a single field for extraction.
| Field | Description |
|---|---|
| Field name |
The name for the field as it appears in the Document Intelligence workspace. Clearly state the information you want to extract. Be specific, clear and concise. For example: "Order number" |
| Details |
A description of the information you want to extract. Along with the field name, the description is used to help the LLM predict the text to extract from the document. Include any relevant context or additional details to identify the right information. This might include keywords. For example, "The contract number or the number of the reference contract”. Provide examples of what information you want to extract. For example, “AGR-2023-0042”, “CON2039739”, or “BV-22122KEY”. Example of a description: Field name: “Currency” Details: “The currency in which the contract is denominated. Only valid for Order Forms. Otherwise, leave it empty (''). If the currency symbol is '$', answer 'USD'. Examples: 'USD', 'EUROS', 'GBP', etc.” 팁:
View the Field assistance tab for additional guidance on forming an effective field. |
| Field Type |
The type of field. For example, a text or date field. For more information, see Field types in Now Assist in Document Intelligence. Some field types convert the extracted value into a standard format. For more information, see Data normalization. |
| Target table |
The table that stores the document processing results for this use case. |
| Target field |
Field on the target table you want to align this field with. The use case must have a target table selected. |
| This single field is required for extraction |
Option to make a field required. Required fields can’t be left empty or unreviewed. |
| Create multiple single fields |
Option to keep the form displayed on the screen. Enable this if you are adding more than one single field to the use case. |