In this article we will cover:

• What are field types in Rossum
• Different field type options
  • Captured field
  • Data field
  • Manual field
  • Unset (kept for backward compatibility)
• Editing options
• Setting up the field type and editing options

Field types explained

Rossum has added three new field types to streamline and improve the annotation process: Captured, Data, and Manual fields. Each of these field types has distinct characteristics and allows you to choose whether annotators can edit the field value. We understand that different fields require different annotation processes. By introducing these new field types and editing options we hope to make it easier for users to improve their document processing, avoid errors, and maintain their automation potential while preventing incorrect data from entering downstream systems.

Different field type options

Captured field

Our AI directly extracts the Captured field value from the document. It does not have a specific icon and always includes a bounding box when selected.

When you select a Captured field, a message in the left panel provides annotation guidance. Users can permanently hide this message by selecting “Don’t show this again.” If you lose track of what the field is for, hovering over it will give you a hint.

Data field

The Data field gets its value from extensions like Master Data Hub or other data sources you have set up. It has an icon with math symbols, and when selected, it does not have a bounding box.

When you select a Data field, a helpful message appears in the left panel. Users can permanently hide this message by selecting “Don’t show this again.”

Manual field

The Manual field is for annotators to manually type in values and is not linked to any data source. It does not have a bounding box and can be easily recognised by it’s icon with lines.

Unset (kept for backward compatibility)

Unset is a “null-type” field used only for backward compatibility. It can be recognised in the schema as it lacks both the field type and the editing options. Users can change it’s value by adjusting the bounding box or typing in a new value.

Nothing changes for our existing customers’ queues. You can switch between the new and Unset type fields in the UI. New clients will be using the new fields by default.

As we add new field types, the navigation on the annotation screen will change slightly. When you press the Tab key on your keyboard, it will direct you to fields that usually need your attention, such as Captured field. This will result in Data fields and Manual field being skipped.

Editing options

The editing options of a field refer to the user’s ability to modify the data within the field during annotation. This can be by either moving, redrawing the bounding box, or simply typing in a value. Available options are “Enabled”, “Enabled without warning” and “Disabled” (explained in the table below). When disabled, users are partially or completely restricted from changing the value. Though it is important to note that this restriction only applies to the UI, the value can still be changed via API.

Field Type	Enabled	Enabled without warning	Disabled
Captured Field	Users can modify the field by moving the bounding box or simply typing in the value. It’s recommended to modify a field only by adjusting it’s bounding box if possible. The messages suggesting how to edit the field in the best way is displayed.	Users can type and edit the text in the field. You will not see any messages suggesting how to edit the field in the best way.	The only way to modify the extracted value of this field is to move the bounding box’s position. The value cannot be typed in. Hovering on a field, users will see the message: “Text editing is disabled.”
Data Field	Users can modify the field’s data by simply typing in the value. The messages suggesting how to edit the field in the best way is displayed.	Users can type and edit the text in the field. You will not see any messages suggesting how to edit the field in the best way.	The value is read-only and cannot be modified. A different mouse icon indicates that the field is also not clickable in the left panel. Hovering on a field, users will see the message: “Text editing is disabled.”
Manual Field	Users can type in the value.	Users can type and edit the text in the field. You will not see any messages suggesting how to edit the field in the best way.	The value is read-only and cannot be modified. This option does not allow for input and is not connected to any external data source. Hovering on a field, users will see the message: “Text editing is disabled.”
Unset	–		–

Setting up field types and editing options

In Rossum’s queue schema editor, users have the ability to fine-tune both field types and editing options.

New queues created from the templates automatically include the new field types. Nothing changes for existing queues – they keep their previous field types and settings.

Setup in the UI

• Navigate to the “Queue Settings”
• Click on the “Fields to capture” tab
• Select the field and click on the “Edit” option
• In the field’s edit window, choose the “Field type and “Editing” to match your preferences
• Save your changes, and you are all set to use this field in your workflow

Existing customers will be able to see “Unset” as a field type option in the UI; this will imitate previous field behaviour.

Setup in the JSON code editor

• Navigate to the “Queue Settings”
• Click on the “Edit JSON” button
• Click on the field you would like to adjust
• Specify the “type“ and “edit“ attributes within the ui_configuration attribute of the datapoint (you can find more details here) e.g.

"ui_configuration": {
          "type": "captured",
          "edit": "enabled"
        }