Work with scripts

FileMaker scripts are ordered steps with parameters, calculations, options, and control flow. Ask the coding agent to read the complete existing script before changing it.

Read before editing

Read the Submit Order script, explain its parameter and result contract, and identify the smallest change needed to add validation. Do not edit it yet.

The script description includes stable identifiers for its steps. Those identifiers let the agent patch a specific step or insert new steps without recreating the entire script.

Create a script

Describe the input, output, side effects, and error behavior. The agent applies the active script naming and comment-header standards, chooses supported FileMaker steps, and validates their option shapes against FileMaker Pro 26 help.

Keep related scripts in the project's established folders. A folder changes Script Workspace organization; it does not create a namespace, so script names must still be unambiguous.

Modify a script safely

Prefer step-level edits to replacing the full body. A complete replacement can lose steps or options that ADT can read but cannot express for writing.

Ask the agent to preserve every unnamed step, then read the full script back after the batch commits. Review calculation context, target fields, called script names, and parameter/result handling.

Unsupported steps

ADT exposes the supported step roster through its live FileMaker operation help. If a step or option is unsupported, the agent must report that limitation rather than substitute a different step or silently omit the option.

See the filemaker operation catalog for supported script verbs.