The FTE Parser Node has a number of required and optional components. Complete profile definitions are defined in the node itself.
Connection Settings
A Release Channel (stable, labs) is required. Unless otherwise directed, customers are encouraged to use the “stable” channel.
A License Key is required. If you have not been provided a license key for FTE, requests into the service will fail.
These settings can be applied literally in the node, or they may be applied using Process Field Notation ({p_LicenseKey}).
Page Selection
Directly beneath the connection settings, a checkbox option for Process all pages can be seen. By default, FTE will only ever process Page 1 of a document. If your use case demands multi-page processing, this option should be checked.
It is not advised to enable Process all pages on all documents. Doing so will likely introduce extra/incorrect data points into the process, and can results in additional costs as well. Only process all pages when the specific use case demands it.
In use cases where some but not all processing might need to span pages of a document, customers are strong encouraged to fork their processes so multiple FTE nodes may be used with the appropriate settings for each specific scenario..
Headers / Footers
This section is leveraged for managing Key / Value responses from the OCR step. You are not required to set header fields.
The Process Field dropdown will contain a list of all process fields added to the workflow. Select the process field you wish to assign from the list. If the list is empty, note you must first add fields to the workflow.
AI Field Expressions is used to store the parsing expression for the process field. Do note, the expression assigned here will set a single value to a “header” field type. This section of the node does not interface with Table fields.