Interfaces
What this domain covers
Interfaces are purpose-built pages layered on top of your base - dashboards, data-entry forms, record review screens, and portals for people who shouldn't see the raw grid. A candidate must know that an interface is a separate object from a table and can combine elements from multiple tables on one page.
Concepts to master
- Interface elements: record review, grid, chart, button, text, and form elements can be arranged on a page.
- Data sources: each element is bound to a table and often a view; the view's filters limit what appears in that element.
- Interface-only users: you can invite collaborators to an interface without giving them base access, which is the key security concept.
- Actions: buttons can open forms, trigger updates, or link to other pages; some actions require configuration of a source table.
- Layout: pages can be organized into tabs and sections for navigation.
Traps in questions
A frequent trap is assuming an interface element can bypass a view's filters - it cannot; the element respects its configured view. Another is assuming interface users can edit records freely; editing depends on the element type and the permissions granted. Questions may also ask whether an interface can show data from two tables - it can, via separate elements.
Rule of thumb
Think of an interface as a window onto the base, not a copy. Filters on the underlying view still apply, and permissions still gate what a viewer can see or change.