Logic

Forms and fields support a number of events that trigger actions, built up as an action flow.

In version 4.3, the older rules system was replaced by the combination of events and action flows. Existing rules are automatically converted to action flows when updating to 4.3 or higher.

Events

Select the Events tab in the right sidebar, choose the applicable event, and add one or more actions.

• Form events: for example On form open, which triggers when a new form is created or opened from the overview or a subform field.
• Field events: most fields support on value change (triggered when the user changes the value, data is received for a linked field, or a set-value action changes it); some fields, like Button, instead support on click. Support varies per field: see the individual field pages.

Actions

The available actions depend on the event, and are grouped by category:

Category	Actions
Values and validation	Set field property, Set field value, Validate field value, Refresh, Set selectable option, Set non-selectable option, Manage attachments
Form messages	Save form, Save and return, Save and new, Save and copy, Copy form, Delete form
Subform messages	Open subform, Add subform, Create subforms
Form modification	Open definition, Create form for definition, Edit form for definition, Copies form for definition, Perform subform navigation
Navigation	Show dashboard, Back, Show chat, Hide chat, Show workflow overview, Show timeline, Show settings, Go to website, Compose mail, Navigate
Scanning	Trigger main scan
Export	Export form to PDF
Logic	Trigger action flow, Execute dataflow
AI (beta)	Extract data from source, Analyze image, Task AI, Extract subform data from source

Most actions cancel any follow-up actions in the flow if they fail: for example if a save is cancelled, or a required AI action doesn’t complete successfully.

Action flow

An action flow always starts with a logical operation:

• If condition: similar to the older rule conditions, but supports combining multiple expressions into more powerful conditions.
• Switch condition: handles multiple cases in one action flow, for example handling different form states.

Conditions can be combined, and you can set a title on each operation to keep longer action flows readable.

Messaging

Customize and translate the text shown for messages on form pages and fields, through display texts.

Form page messages include things like the toast shown when a message is saved or deleted, the confirmation shown before deleting a form or when unsaved changes would be lost, and the message shown when an execute-dataflow action fails.

Field messages are validation and confirmation texts specific to a field type: for example the “required” message shown when a mandatory field is empty, mask or length validation on a Textbox, an out-of-bounds value on a Datepicker, or a barcode-not-found message on a Subform’s scan.