UiPath Document Understanding

UiPath Document Understanding

Form Extractor

What is Form Extractor

The Form Extractor is an extraction approach that is best suited for use cases in which non-variable format documents need to be processed, with data extracted from them. In other words, if your documents have little to no variation in the document layouts, then the Form Extractor is a good choice.

The Form Extractor relies on templates defined up-front, at the design stage, and applies a complex set of rules to apply the configured templates to incoming documents that are to be processed, thus identifying and reporting the expected information.

The activity comes with a configuration wizard that assists you in defining the templates for the document types and fields you want to target for data extraction in this way.

The activity supports both simple field as well as table field extraction.

It is recommended to look into other extraction methods, in case:

  • there are many layouts that need to be handled
  • documents are not only skewed, rotated or coming in different sizes, but also manifest "warping" (curving in certain areas).


Evaluating if Document Layouts Are the Same

For fixed form extraction, to evaluate if layouts of two files are the same, try overlapping them in a tool, with some transparency, to see if all non-variable content overlaps (after de-rotation, de-skewing and bringing the two images to the same scale).

If you notice variability (non-variable content appears more to the left / right / top / bottom for certain areas of the document), then the layouts are not considered the same.

The Form Extractor allows you to define multiple templates for the same document type, and, at run-time, it:

  • identifies the best matching template for the incoming document and document type
  • applies the template matching algorithm, based on page-level anchors, to each page that data needs to be extracted from (missing or repeating pages are not supported)
  • applies all field-level anchor settings to each page, to capture values associated with any potential matches
  • reports the identified information from the target value areas.

It also supports fine-tuning of checkbox / boolean field processing, by allowing the configuration of "synonyms" for a "Yes" or "No" value, according to your use case.

This extractor does not have learning (training) capabilities and requires up-front configuration.

Special Requirements

You need to use your Automation Cloud Document Understanding API Key, or host your own instance of the Form Extractor in AI Center on-premises, to use this extractor.

How to Configure

Activity Configuration

The Form Extractor has two major configurations to be considered:

  • the Template Manager wizard - which allows you to define templates to be applied to incoming documents. This wizard also makes available the Template Editor wizard, along with the Boolean field interpretation settings.
  • the MinOverlapPercentage setting - which allows you to control how strict the value area matching should be. It accepts a value between 0 and 100, and it controls what words are accepted or rejected from being part of a given value, based on how well their location fits the area defined in the template.

The Template Manager Wizard

This wizard allows you to create, edit, manage, and export/import templates for the document types defined in the taxonomy.

Creating a template

  1. Add a Form Extractor activity to your workflow, within a Data Extraction Scope.
  2. Configure the extractor by clicking on the Manage Templates button.
    • The Template Manager window opens.
  1. Click the Create Template button for creating a new template.
  1. Select the document type you are defining the template for, from the Document Type drop-down list.



All Document Types are based on the Taxonomy. Make sure to add or create a Taxonomy inside the project's folder.

  1. Add the name of the template in the Template name field. Make sure it is a relevant name that represents what version of the document, or what layout, you are capturing and configuring throught it.
  2. Add the document's path in the Template document field.
    • Navigate to the file's path by using the Browse button.
  3. Select an OCR from the OCR Engine drop-down list, and configure it according to its needs.
  4. Click the Configure button to trigger template editing.

The OCR engine is applied only if necessary. If the document selected for building a template is a Native PDF, then no OCR engine is executed.

Each OCR engine comes with its own set of custom options. Here you can find more details about all options available for each OCR engine.

If you already created a template, then it can be edited, exported, or removed.
Delete and Export buttons become available only when at least a template is selected. The Edit and Remove options for an individual template are always available.

Configuring Boolean Field Processing

For the documents that include check boxes, you have the possibility to add known synonyms for the Yes and No options, or you can start from a list compiled by us (see the Add Recommended suggestions). These values are used for Boolean content interpretation, which is mapping a captured value to a Yes or No reported value.

Exporting and Importing Templates

You can import templates created and exported from other workflows. Use these features to share templates between projects, so that once a document type is configured using the Form Extractor, you won't need to re-configure the templates in a new implementation.

Exporting Procedure

Here are the steps you need to follow to export a template:

  1. Create one or more templates by following the steps explained at the beginning of this page.
  2. Select the templates you want to export.
  3. Select an Export option (with or without the original files) as shown in the below screenshot. Exporting with original files attaches them to the export. The second option doesn't attach the files used for template creation.
  1. Save the template's archive with the desired name.
  2. A message is displayed once the template is saved. Select the OK button.


With or Without Original Files?

If you cannot share the content of the documents you have built your templates on, then use the "Without Original Files" option. You will still be able to share and import the template archive in other projects, but you will not be able to edit or view them anymore.
If you want to be able to edit the templates once imported in a different project, make sure to use the "With Original Files" option when exporting and then importing them.

Importing Procedure

Here are the steps you need to follow to import a template:

  1. Select the Import button.
  1. Select an archive. The import wizard appears and presents all document types and all templates available in the selected export archive. Select the templates you wish to import and choose the right Import option (with or without the original files).



When templates are imported, document types are created automatically in the project's Taxonomy. If a document type with the same name already exists, another one is created by appending a count to the document type name.
If you are importing templates that have been exported without the original files, or if you choose to import templates without the original files, then you have no view or edit options for those templates.

Special Situations when Importing a Template

When a template is imported, several special situations might occur. The below table explains each situation and its particularities:

Import Type

Activity Behavior

New document type

If a new document type is imported, then a new field is added in the wizard configurator, informing you that a new template is to be created.

Duplicate document type

If an identical document type is imported, then the following warning message appears:
This template already exists and it will be overwritten.

Extended template

If a document type template that includes extra fields than the already existing one is imported, then the following warning message appears:
This document type will be updated as follows:
The following field(s) do not exist and will be created.

Extended document type

If the user imports a document type that includes extra fields than the already existing one, then the following warning message appears:
This document type will be updated as follows:
The following field(s) don't have configurations to import...

Document type with identical name but different content

If the user imports a document type that has the same name as the existing one but different fields, then the following warning message appears:
This document type will be updated as follows:
The following fields do not exist and will be created;
The following fields don't have configurations to import

Document type with missing table

If the user imports a document type that doesn't include a table, then the following warning message appears:
This document type will be updated as follows:
The following field(s) don't have configurations to import.

Document type with extended table

If the user imports a document type that includes a table with extra columns, then the following warning message appears:
This document will be updated as follows:
The following field(s) do not exist and will be created.

Document type with reduced table

If the user imports a document type that includes a table with missing columns, then the following warning message appears:
This document will be updated as follows:
The following field(s) don't have configurations to import...

Table template with different document types

If the user imports a document type template that includes a table with different document types, then a new template is created.
If your taxonomy includes a table that has a field with a different document type, then the following message appears:
The field with id xyz was found both in the imported taxonomy as well in the existing taxonomy but their types are incompatible (either both should be tables or neither of them).

The Template Editor

General Considerations

The Template Editor is building on top of the functionality present in the Validation Station.

To learn about the basic usage of the Validation station, read this section.

Besides the options available in the right part of the Validation Station screen, there are two options Template Editor specific:




Sets the Anchor selection mode


Clears the whole anchor selection

When creating a new template, an explanation text appears when first opening the Template Editor. In case you want to access the text again, follow the steps below:

Configuring Page-Level Anchors

When defining or editing a page-level template, the first thing that needs to be performed is the Page 1 Matching Info selection, for fixed form template definition.

This field that appears on the left side of the screen as the first field needs to be configured with words (tokens only are accepted) from the first page of the template that are constantly in the same position within that particular template layout, that form a unique graph of words (considering relative distances and angles between words) across all the templates defined for a particular document type. In other words, the Page 1 Matching Info (and all other Page Matching Info fields) are "fingerprints" of a particular page and are extensively used in identifying the right matching template at run-time.

For this reason, for the Page 1 Matching Info field, it is strongly recommended to select 10 to 20 words, preferably longer in length, spread across the entire page area, that would form a unique pattern across all defined templates for that document type.

The other Page Matching Info fields (one for each template page) must be filled in only if you are attempting data extraction from that particular page, and do not require cross-template uniqueness anymore. If no fields need to be extracted from a particular page, defining the page-level matching info for that page is not mandatory.

Configuring Simple Fields with Page-Level Anchors

For all fields other than Tables, configuring the template consists of selecting a Custom Area and assigning it to a particular field.

For fixed form configurations, data fields can only be configured using Custom Area selections.

For any field, you can define one or more such Custom Areas, using the (+) button. If you define two or more custom areas for a single field, then at run-time, if the field is defined in the Taxonomy as Single Value, then all values from all the custom areas will be concatenated into a single reported value. If on the other hand the field is defined as Multi Value, then each value from each custom area will be reported individually.

The below animation shows the difference between a Tokens or Custom Area selection:

You can also find out the type of accepted selection for each field by verifying the icon beside each field as shown in the below animation:


Selection Modes

If an empty area is selected, the selection is automatically set as Custom area. If text is detected inside the selected area, you are asked to choose the type of the selection between Tokens or Custom area.
Use the Validation Station selection mode feature to lock your selection between Tokens and Custom Areas.

Configuring Tables with Page-Level Anchors

As mentioned above, there are fields where information can be added only by using tokens (like the Page Matching Info fields) or only by using a custom area (like simple fields). For Table fields, you can

  • define each cell one by one, once the Table Editor is expanded - by adding Custom Area selection to each cell individually, or
  • use the table markup functionality - by marking the table area, drawing row and column separators, and then assigning the thus marked table to the field.

Check the animation below for learning how to use the table markup functionality:

Configuring Simple Field-Level Anchors

A distinctive method of defining the bounds of a custom area from which data is to be extracted is to use field-level anchors. These allow for targeting data extraction based on field-level configurations, thus allowing for more flexibility when defining your form extraction rules.

Consequently, at run-time the Form Extractor knows how to:

  • identify if a page-level template matches, and extract information according to the best page-level template match it recognizes;
  • identify if any anchor-based settings match, and extract information according to their application in the document to be processed;
  • compute appropriate confidence scores for all possible matches, so as to be able to report the best result (highest probability match) of all available options.

Creating a New Anchor Setting

  1. Make sure you are on the Anchor Selection mode.
  2. Draw a box around the value area.
  3. Select a Label (main anchor) for your value area by either clicking the first word and then Ctrl+Click the last word of the selection or click, drag, and then release to capture a word range.



A Label can only contain consecutive words from the same visual line.

  1. Select any additional anchors that would uniquely identify your Label. The same selection principle applies.
  2. Assign your anchor construct to the appropriate field by selecting Extract Value for that particular field.

Edit an Existing Anchor Setting

  1. Highlight your anchor setting.

  2. Make changes to it (delete any anchors, the label, even the value area if you wish, add new elements, etc.).

  3. Use the Change Extracted Value option to update your field association.


When Creating or Editing an Anchor Setting

If you delete the target area, all anchors get deleted and you start over.
If you delete the Label (main anchor), the first anchor in the order it was created becomes the new Label.

Delete an Existing Anchor Setting

To delete an anchor setting, you can:

  • use the Mark as Missing options for a saved value
  • use the Remove Value in case of a list of anchors defined for a given field

Mix and Match Configurations

You can define as many templates as you want for the same document type. You can have multiple page-level templates, multiple anchors for the same field, even templates containing both page-level as well as field-level anchors.


Tips and Tricks

When defining field-level anchors make sure your Label is close to your value area and it is supported by additional anchors if the same text construct can be found in multiple places within the same document.

The lengthier your labels and anchors are, the more precision you get.

The value area is always computed based on its relative position against your Label (main anchor). Choose your main anchors accordingly.

Having field-level anchors allows fields to move within the template and still be captured, offering more flexibility in document layout changes.

Updated about a month ago

Form Extractor

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.