Master the fundamentals:
A-Z glossary of Claris FileMaker and low-code terms

Welcome to your comprehensive guide to Claris FileMaker and low-code development terminology.

This curated glossary cuts through the technical talk to provide clear, practical definitions for the terms you'll encounter.

Whether you're a business professional building your first app or a developer streamlining your workflow, a shared vocabulary is the foundation of success. 

Click any letter below to instantly jump to the section of the glossary containing terms that start with that letter.

A

Anchor-buoy
A popular method for organizing the Relationships Graph, where one main table (anchor) connects to supporting tables (buoys).

API (Application Programming Interface)
A set of protocols and tools that allows different software applications to communicate with each other.

App builder
A visual tool for assembling software through drag-and-drop interfaces.

Automation
The use of scripts or workflows to perform repetitive tasks automatically within a FileMaker solution or low-code platform.

Authentication
The process of verifying the identity of a user or system, often via a password or SSO.

Authorization
The process of determining what resources or actions an authenticated user is permitted to access.

B

Backend
The underlying database or logic layer where data is stored and processed, often hidden from users.

Browse mode
The mode where users interact with data, enter information, and navigate through records.

Business logic
The rules and algorithms that define how data is processed and business operations are conducted.

Business Process Automation (BPA)
The use of technology to automate complex business processes and workflows.

C

Calculation
A defined formula that returns a result. Calculations are used in calculation fields, script steps, and conditional formatting.

Calculation engine
The component that performs computations, text parsing, and logical evaluations in fields, scripts, and reports.

Calculation field
A field whose value is not manually entered but is automatically determined by a formula you define (e.g., `Full Name` = `First Name` & " " & `Last Name`).

Cardinality
The relationship type between tables, typically one-to-one, one-to-many, or many-to-many.

Citizen developer
A non-professional developer (e.g., a business analyst, manager, or operations expert) who creates applications for their own team or department using low-code/no-code platforms.

Cloud computing
The delivery of computing services—servers, storage, databases, and software—over the internet.

Component library
A collection of reusable UI elements and functionality modules available within a development platform.

Connector
A pre-built integration component that links a low-code platform to external systems, APIs, databases, or third-party services.

Container field
A special type of field that can store non-text data like images, documents (PDFs), videos, and other files directly within the database or by reference.

Context
The current table occurrence from which a script, calculation, or layout operates, affecting which relationships and fields are accessible.

Cross-platform
The ability to generate applications that run on multiple operating systems (e.g., Windows, macOS) and device types (e.g., desktop, web, mobile) from a single codebase.

Custom app
A tailor-made solution created in FileMaker for specific business workflows or processes without traditional coding (e.g., CRM, asset tracker, inventory management).

Custom function
A user-defined calculation that can be reused throughout a FileMaker solution, extending the built-in function library.

D

Dashboard
A visual display of key metrics and data points, often used for monitoring and decision-making.

Data integration
The process of securely connecting the low-code application to external data sources (like databases, cloud services, and legacy systems) and automating the flow of data between them.

Data management
Handling and modeling data visually, including setting up database tables and relationships.

Data model
The conceptual structure that defines how data is organized, stored, and related within a database.

Data validation
Rules that ensure data entered into a system meets specific criteria for accuracy and consistency.

Data viewer
A development tool that allows developers to monitor field values, variables, and calculation results while debugging.

Deployment
The process of making an application available for use in a production environment.

Drag-and-drop interface
A user interface paradigm where components are added and arranged by dragging them from a palette onto a canvas.

E

Entity-relationship diagram (ERD)
A visual representation of how tables (entities) relate to each other in a FileMaker database.

ExecuteSQL
A powerful calculation function that allows developers to perform SQL queries directly on FileMaker tables. This provides advanced data manipulation capabilities beyond the standard Find and Relationship models.

Event-driven architecture
A software design pattern where actions are triggered by specific events or state changes.

F

Field
A single column in a Table that holds one piece of data (e.g., 'First Name,' 'Date,' 'Price'). Similar to a cell or column in a spreadsheet.

File
The single container, often referred to as the database file or custom app itself, that stores all the tables, data, layouts, and scripts.

Find mode
The mode used to search for records based on specific criteria.

G

Governance
Policies and procedures that ensure applications meet organizational standards for security, compliance, and quality.

Graphical Relationship Diagram (GRD)
The visual workspace in FileMaker Pro where you define tables and the relationships between them, often called the "ERD" (Entity-Relationship Diagram) in other systems.

GUI (Graphical User Interface)
The visual layer of an application through which users interact with its features. In low-code platforms like FileMaker, GUIs are designed visually using drag-and-drop tools rather than traditional coding.

H

Hosting
The process of running and managing a FileMaker solution on a server (on-premise or cloud) for multi-user access.

I

Integration
The process of connecting different systems, applications, or data sources to work together seamlessly.

J

JSON (JavaScript Object Notation)
A common text-based format for representing structured data, often used in FileMaker for exchanging data with APIs and web services.

K

Key
A field (like a Primary Key or Foreign Key) used to uniquely identify records and establish relationships between tables.

L

Layout
The visual user interface for viewing, editing, and interacting with the data in records. A single table can have multiple layouts for different purposes (e.g., a data entry layout, a report layout, a dashboard).

Layout mode
The development environment where layouts are designed and modified.

Legacy system
Older technology or applications still in use, often targeted for replacement or integration with modern solutions.

Low-code
A visual approach to application development that minimizes manual coding using visual tools and pre-built components.

Low-code development
A development approach that allows users to create business applications with minimal manual coding. It uses a visual, drag-and-drop interface, pre-built components, and models to speed up the development process.

Low-code platform
A software development environment that enables application creation through visual interfaces, drag-and-drop components, and minimal hand-coding.

M

Metadata
Data that describes other data, such as field properties, table structures, or document attributes.

Mobile-first design
A design approach that prioritizes the mobile user experience before adapting to larger screens.

Model-driven development
An approach where the application is generated from a visual model of its data structures, relationships, and business logic.

N

Normalization
The process of organizing database structure to reduce redundancy and improve data integrity.

O

One-click deployment
The ability to publish a completed application to a live (production) environment with a single action, dramatically simplifying the release process.

P

Plugins
Add-on modules that extend FileMaker functionality.

Portal
A layout object that displays related records from another table.

Pre-built components
Ready-to-use elements (forms, buttons, logic blocks) that accelerate development.

Primary key
A unique identifier field for each record in a table.

Privilege set
A collection of access permissions that defines what users can view, edit, create, or delete within a solution.

Professional developer
A trained software developer who uses low-code platforms to accelerate development, build complex applications, and integrate with other systems, often supplementing the platform with custom code.

Q

Query
A request for specific data from one or more tables, often performed through FileMaker’s Find mode or SQL functions.

R

Rapid Application Development (RAD)
Methodology focused on fast prototyping and iterative software build cycles, often associated with low-code tools.

Record
A single row in a Table, containing all the information for one specific item or entity (e.g., one client, one invoice). Similar to a row in a spreadsheet.

Relationship
A defined link between two or more tables that allows data from one table (like 'Contacts') to be displayed or used in a related table (like 'Invoices').

Relational database
A database organized into tables with relationships between them, using keys to link related data.

Relationships graph
A visual diagram showing how tables are connected through relationships.

Report generation
The process of creating formatted documents that present data in meaningful ways for analysis or presentation.

Responsive design
Design approach ensuring applications work well across different screen sizes and devices.

Reusable components
Pre-built modules, templates, connectors, and design elements provided by a low-code platform that developers can use across different applications, saving time and ensuring consistency.

S

SaaS (Software as a Service)
A software distribution model where applications are hosted by a provider and accessed via the internet.

Sandbox environment
A testing environment isolated from production where changes can be safely tested, without affecting live data or systems.

Scalability
The ability of an application to handle growth in users, data volume, and transaction load without performance degradation.

Schema
The blueprint or structure of a FileMaker database — includes tables, fields, and relationships.

Script
A series of automated actions created to perform complex or repetitive tasks, such as generating a report, navigating between layouts, or importing data.

Script step
An individual, pre-built command within a script (e.g., `Go to Layout`, `Perform Find`, `Set Variable`). Scripts are built by sequencing these steps.

Script trigger
An event that automatically executes a script when specific actions occur (e.g., when a field is modified, a record is opened, or a layout is loaded).

Single Sign-On (SSO)
An authentication scheme allowing users to log in once and access multiple applications.

Summary field
A field type that performs aggregate calculations (sum, average, count) on groups of records.

T

Table
A structure within the FileMaker file that organizes a specific type of information (e.g., 'Contacts,' 'Invoices,' 'Products'), similar to a worksheet in a spreadsheet.

Table occurrence
A representation of a table in the Relationships Graph. A single table can have multiple occurrences to create different relationship paths.

Technical debt
The implied cost of future rework required when choosing an easy or quick solution over a better long-term approach.

Template
A pre-designed application structure or component that can be customized for specific needs.

Trigger
An event that automatically runs a script (e.g., when a record is opened or a field is modified).

U

UI Components
Pre-built, reusable elements of a user interface, such as buttons, form fields, data grids, charts, and calendars. These are dragged onto a canvas to build the app's interface.

User Interface (UI)
The visual elements through which users interact with an application.

User Experience (UX)
The overall experience and satisfaction a user has when interacting with an application.

V

Value list
A predefined list of options used in drop-down menus, radio buttons, or checkboxes for data entry.

Version control
A system that tracks changes to files over time, allowing rollback and collaboration.

Visual development
Building applications through graphical user interfaces rather than writing code in text editors.

W

WebDirect
A FileMaker feature that allows users to access FileMaker apps via a web browser without installing software.

Webhook
An automated message sent from one application to another when a specific event occurs.

Widgets
Pre-built, reusable elements of a user interface, such as buttons, form fields, data grids, charts, and calendars. These are dragged onto a canvas to build the app's interface.

Workflow
A sequence of tasks and decision points that define how a business process is executed.

Workflow automation
Ability to automate business processes visually, reducing manual intervention.

X

XML (Extensible Markup Language)
A structured format for storing and transporting data, supported by FileMaker for data import/export.

Bookmark this page and let it be your quick-reference guide as you build, innovate, and bring your ideas to life.