...
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.
Add a new Header Mapping if you care to set data from the AI response to additional fields.
If you have a mapping that isn’t needed, click the Delete link to the right of that mapping.
Table Fields
Handling table fields is slightly different than handling header fields. To start, some additional information is required in the form of (1) the table field to target and (2) the “table of interest” from the AI response.
...
Set the name of the table field that will be used to collect data. The is the name of a GlobalCapture process field that is of type “Table”.
Set the table of interest / assign $toi. When table expressions are evaluated, any occurrence of the string $toi will be replaced with the expressions provided in the Table AI Table of Interest field. This essentially allows for shorthand notation to reference that part of the expression without having to rekey it, potentially multiple times, in more complex expressions and / or functions.
When mapping values to table fields, with a properly formed Table of Interest expressing the rest of the statement can be significantly simpler and less error prone. Use of this replacement is highly encouraged.
Table Field Cell is the Column Field’s name in the table you wish to target. This is the field name, as it is presented in the table.
AI Field Expressions is used to store the parsing expression for the process field. As with Header/Footer, the expression provided here sets the value of the field from the AI response.