Documentation Index
Fetch the complete documentation index at: https://knowledge.goautonomous.io/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Fields are added from within any of the three tabs (Summary, Line Items, or Stocklines) in a configuration. Click + Add field within a group or section to open the Field editor dialog. The same dialog is used when editing an existing field — click any field row to open it. The field editor has two tabs: Details and Configuration.Details tab
Field name
The display name shown to your team in Flow. If you change it from the system default, a Reset to default field name link appears below the input.System name
The internal identifier for the field (field_id). This is read-only and is used in integrations and API mappings.
Description
Optional free-text description. When set, an info icon appears on the field row — hovering it shows the description text. Useful for documenting what the field captures for your team.Attributes
Type
The data type controls how the field value is displayed, edited, and validated in Flow.| Type | Description |
|---|---|
| Text | Free-form string input. |
| Number | Numeric value only. Uses a dot as the decimal separator. |
| Date | Date value, rendered with a date picker. |
| Toggle | Boolean true/false switch. |
| Email address input. | |
| Link | A read-only clickable URL. Link fields are automatically set to read-only and cannot be mandatory. |
- Toggle and Email cannot be used on fields marked as mandatory.
- Toggle and Email cannot have reference data attached.
- Date and Link cannot have reference data attached.
Visible
Controls whether the field appears in Flow. Invisible fields are useful when you need to include information that is mandatory to create or simulate an order, but don’t want it visible to the user — for example, a system reference code that must be present but has no meaning to the reviewer.- Turning on sets the field to optional.
- Turning off marks the field as not applicable. The AI will still extract a value and it will still be passed to integrations.
Mandatory
When enabled, the field must have a value before a request can be confirmed. Flow will block confirmation and highlight the field if it is empty. Mandatory cannot be enabled when:- The field type is Toggle (tooltip: “Field cannot be mandatory when configured as toggle”)
- The field type is Email (tooltip: “Field cannot be mandatory when configured as email”)
- The field has Read only behaviour enabled
Marking a field as mandatory on a live configuration will immediately block confirmation on any open requests that don’t have a value for that field — including requests already in progress.
Configuration tab
Reference data
Attach a reference data set to make the field a searchable dropdown in Flow. Users (and the AI) can then select from a list of valid values rather than typing freeform. Click Add to open the reference data assignment dialog:- Select a reference data source from the left panel.
- Choose the Value column — the internal value stored when an option is selected.
- Choose the Display Value column — what the user sees in the dropdown.
- Click Apply.
- Under “When the following field has a value”, select the parent field.
- Under “Then only show options for this field where the following columns match”, select the matching column in the parent’s reference data and the corresponding column in this field’s reference data.
Dependent fields are not available on Stocklines fields.
Default value
Set a fallback value that is pre-populated when the AI finds no value for the field. The input type matches the field’s data type:| Field type | Default value input |
|---|---|
| Text / Number | Text input |
| Date | Preset options: Today, Tomorrow, In 3 days, In 1 week, In 2 weeks, In 1 month — or a custom “In __ days” offset. An Include weekends checkbox is shown once a value is selected. |
| Toggle | On/off switch |
| Multi-email input — type and press Enter to add each address | |
| Reference data | Searchable dropdown from the linked reference data |
Behaviour
Behaviour options add additional rules to how the field works. Available options depend on the field’s location (Summary, Line Items, or Stocklines) and data type.| Option | Description |
|---|---|
| Read only | The field is visible but cannot be edited in Flow. Cannot be combined with Mandatory, Select only, or Simulate on update. |
| Select only | The user can only select a value from the reference data dropdown — they cannot type a freeform value. Requires reference data to be attached. |
| Simulate on update | Changing this field’s value triggers a re-simulation automatically. Cannot be combined with Read only. |
| Include in vendor quote | The field is included in vendor quotation requests. Maximum 5 fields allowed (product name and number are excluded from the count). |
| Show in stockline | (Stocklines fields only) Displays the field in the inline stockline row within the product cart. |
| Show in tableview | (Stocklines fields only) Displays the field in the expanded stockline table dialog. |
Reordering fields
Drag and drop fields within a tab to change their order. In the Summary tab, you can also drag entire groups to reorder them. In the Line Items tab, reordering fields changes the left-to-right column order in the product cart — use the preview strip at the top to see the result as you drag.Deleting a field
Hover a field row and click the trash icon. A confirmation dialog appears. If the field is part of a sum definition or a one-time delivery configuration, the dialog will warn you that removing the field will also remove those definitions.Effect on requests
- New requests — the field is active immediately for all new requests matching the configuration.
- Existing open requests — the field column will appear but with an empty value. Default values are not backfilled onto existing requests. If the field is mandatory, users on existing requests will need to fill it in before confirming.