Form-level actions in Settings

The Settings tab stores reusable Code action definitions and the Form validator. Saving a Code action does not run it; a button or another component event must reference that action.

Settings vs button Actions

Field-level validation still lives on each field’s Rules tab.

Open Settings

1. Click Settings on the left panel.
2. Scroll to the Actions block.

Add a form action

1. Click Add a code action.
2. The bottom panel opens the code editor for the new form action.

3. Enter a Name, write or paste the script, and click Save.
4. Select the button or other component that should run the action.
5. Open its Actions tab and click Add an action under the event you want to use, such as onClick.
6. Open Code and select the saved action by name.
7. Coordinate with developers for production logic.

Form validator (optional)

1. In Settings, find Form validator.
2. Click Edit code.

3. Edit validator code only when your team assigns you that task. Many teams restrict this to developers.
4. Click Save when finished.

Test

1. Click Preview.
2. Trigger the component event to which you attached the action.
3. Use Preview mode tools to inspect Errors.

Summary

Settings stores reusable Code actions and the Form validator. Attach a saved action to a component event on the right, then trigger that event in Preview.

See also

• Actions basics
• Actions (developer depth)