Single field form

  • Release version: Xanadu
  • Updated August 1, 2024
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Single field form

    The Single field form in Document Intelligence allows ServiceNow customers to define and configure a single specific field for data extraction from documents. This form is essential for extracting consistent, normalized, and accurate data to integrate with target tables and applications within ServiceNow.

    Show full answer Show less

    Key Features

    • Single field name: The identifier for the field as shown in the Document Intelligence workspace.
    • Type: Specifies the data type of the field, such as text, date, integer, decimal, float, or reference field. Some types support data normalization to standard formats.
    • Converted date format: Defines the normalized date format when the field type is Date.
    • Target table and field: Specifies where the extracted data is stored and aligns the field with the corresponding column for integration with other ServiceNow applications or workflows. Selecting a target table is mandatory.
    • Ambiguity handling for dates and numbers: Allows configuration of default interpretations when extracted dates or numbers are ambiguous (e.g., day/month order for dates or decimal separators for numbers).
    • Reference table and columns: For reference field types, enables linking to reference data tables and columns to find exact matches and normalize extracted values.
    • Distinguisher(s): Additional reference columns to differentiate between similar records when using reference fields.
    • Required field option: Marks the field as mandatory, preventing empty, ambiguous, or unmatched values. This is critical for ensuring data quality, especially in fully automated extraction scenarios.
    • Agent review option: Determines whether ambiguous required fields interrupt full automation to allow manual verification or continue automatic processing without review.
    • Create multiple single fields: Keeps the form open to add several fields consecutively, improving efficiency when defining multiple extraction fields for a use case.

    Practical Benefits for ServiceNow Customers

    • Ensures precise data extraction from documents by defining fields with specific types and normalization rules.
    • Supports integration with ServiceNow tables and workflows, enabling seamless data flow into custom applications.
    • Improves data quality and automation reliability by handling ambiguous data and enforcing required fields.
    • Offers flexibility in managing extraction workflows by allowing agent intervention for ambiguous data or continuing automated processing.
    • Facilitates efficient setup of multiple extraction fields through the multi-field creation option.

    The Single field form enables you to define a single field for extraction.

    The Single field form includes the following fields.

    Table 1. Single field form
    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.
    Note:
    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:
    • the date/number is ambiguous in the document
    • there are multiple reference matches in the document

    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.