Script workspace organization and naming

Expert

Apply naming conventions, folder structure, and documentation practices that keep the script workspace navigable as solutions grow.

What you'll learn

A practical naming convention for scripts by context and purpose
How to organize scripts into folders by module or workflow
How to document scripts without cluttering them

A FileMaker solution with hundreds of scripts becomes unmanageable without deliberate organization. Consistent naming conventions, folder structure, and brief inline comments allow new developers to navigate the script workspace and understand the solution architecture at a glance.

1/3

Naming conventions

Prefix each script name with the context it runs in, followed by a verb-object pair. Common prefixes: "NAV" (navigation), "CRUD" (data operations), "UI" (interface changes), "BG" (background/server-side), "UTIL" (reusable utilities).

FileMaker Script

# Examples of well-named scripts:
NAV - Go to Contacts List
NAV - Open Contact Detail [ id ]
CRUD - Contact: Create
CRUD - Contact: Update Status
CRUD - Invoice: Generate PDF
BG - Server: Rebuild Search Index
UTIL - Format Phone Number
UTIL - Validate Email Address

Allow User Abort and script cancellation control Perform Script via URL (Deep Links)