---
sourceDocument: Australia Enable AI
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/intelligent-experiences

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Enable AI

ft:clusterId :

    - platai

bundleId :

    - platai

workflow :

    - Platform


---

# Table form

# Table form {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 min. de leitura

The Table form enables you to define a table for extraction.
Importante:  
Starting with the Zurich release, Document Intelligence is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported. For details, see the Deprecation Process article \[[KB0867184](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0867184)\] in the Now Support Knowledge Base. Instead, you can extract information from documents using the Now Assist in Document Intelligence application. For more information, see [Now Assist in Document Intelligence](https://servicenow-prod.fluidtopics.net/Dq_6c8JJ_cu9yJcvDkosRA "Use ServiceNow Now Assist in Document Intelligence to analyze and extract information from unstructured documents with generative AI.With ServiceNow Now Assist in Document Intelligence, you can use generative AI to get key information from digital documents into your automation workflows.").

The Table form includes the following fields.  
{#table-form__table_wxp_lpt_bzb__entry__2}

| Field | Description |
|-|-|
| Table |   |
| Table name | The name for the table as it appears in the Document Intelligence workspace. |
| Target table | The table that stores the document processing results for these table fields. |
| Parent mapping to field | Field on the target table that you want to align this table with. Nota: You must first select a target table. |
| This table is required for extraction | Option to make the table fields required. Required table 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. Required fields affect how document tasks are processed in the Fully automated extraction mode. For more information, see [Configure data extraction modes](https://servicenow-prod.fluidtopics.net/SwkPc22T~MBJttuF4tIz2w "Configure the extraction modes for use cases to define how Document Intelligence extracts fields from documents."). |
| Columns |   |
| Column title | Name of the column header in the table. |
| Type | The type of the field in the table column. For example, a text or date field. Some field types convert the extracted value into a standard format. For more information, see [Data normalization](https://servicenow-prod.fluidtopics.net/4~v_g_D83~pUF8UUzZThsQ "Certain types of data extracted from documents are converted into a standard format so that they appear the same across all fields."). |
| Select target field | Field on the target table that you want to align this field with. This field is used for integration with other applications. For more information, see [Integrate with a custom application or workflow](https://servicenow-prod.fluidtopics.net/CCVJ12OyOO0cUVcjiMhRPw "Configure an integration to trigger document task processing or value extraction. Integrations can be used to quickly set up flows with other applications."). |
| 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 <kbd class="ph userinput">Date</kbd>. |
| 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 <kbd class="ph userinput">Month first</kbd> 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 <kbd class="ph userinput">Day first</kbd>, it will interpret it as February 1. This field is available when the Type field is set to <kbd class="ph userinput">Date</kbd>. |
| When the currency is ambiguous in a document, DocIntel will interpret it as | The default interpretation of the currency format. For example, if you select <kbd class="ph userinput">Canadian Dollar</kbd> in this field, DocIntel will interpret an ambiguous currency symbol like $ as Canadian dollars instead of US dollars when it extracts that value from a document. The Select currency and Select decimal separator fields are available when the Type field is set to <kbd class="ph userinput">Currency</kbd>. |
| 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 <kbd class="ph userinput">1,00</kbd> 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 <kbd class="ph userinput">Integer</kbd>, <kbd class="ph userinput">Decimal</kbd>, or <kbd class="ph userinput">Float</kbd>. |
| 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 <kbd class="ph userinput">Reference field</kbd>. |
| 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](https://servicenow-prod.fluidtopics.net/4~v_g_D83~pUF8UUzZThsQ "Certain types of data extracted from documents are converted into a standard format so that they appear the same across all fields."). This field is available when the Type field is set to <kbd class="ph userinput">Reference field</kbd>. |
| 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 <kbd class="ph userinput">Reference field</kbd>. |
| This field is required for extraction | Indicates whether a column required. It's automatically selected or cleared based on whether the table is required. Required column 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](https://servicenow-prod.fluidtopics.net/SwkPc22T~MBJttuF4tIz2w "Configure the extraction modes for use cases to define how Document Intelligence extracts fields from documents."). |
| Select one of these options for cases when: * the date/currency/number is ambiguous in the document * there are multiple reference matches in the document {#table-form__ul_xqw_djv_4bc} | 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. |
| New column | Option to add a column to the table. Use the reorder icon (![Reorder icon.]()) to reorder a column in the table. |
| Create multiple tables | Option to keep the pop-up window displayed on the screen. Enable this option If you're adding more than one table to the use case. |
[Tabela 1. Table form]

{#table-form__table_wxp_lpt_bzb}