How to Use Claris Studio Custom Views to Create a Process-Specific Workspace

Custom views turn Claris Studio into a true design tool.

Prebuilt views in Claris Studio are helpful, but custom views make the platform much more engaging for technical teams.

Claris says custom views give you “absolute control over form and function.” You can combine fields, data controls, summary objects, and static objects to create purpose-built workspaces rather than generic record displays. Some processes do not fit neatly into a spreadsheet, kanban board, or list-detail view. Sometimes, you need a focused workspace that brings different types of information together in one place.

Begin by focusing on a single process, not just a screen.

The best custom views start with a specific process question.

For example:

• How should an approver review and act on incoming requests?
• How should a dispatcher assign work across a team?
• How should a manager monitor and resolve exceptions?
• How should a reviewer compare summary metrics with the underlying records?

These are workspaces designed for specific processes, not just “custom layouts.”

This distinction is important because it changes your design approach. The goal is not to display everything, but to help one role do one job well.

Know the hierarchy before you start building.

Claris highlights data inheritance as a key concept for custom views. There are three main data layers: view, subview, and frame. A view can have up to three frames, and each frame can show one subview at a time. It helps to think hierarchically from the beginning.

The view acts as the main workspace.
Subviews define focused record areas within the workspace.
Frames let you place and organize those areas within a single layout.

This is why custom views feel more like designing a workspace than just building a layout.

Use frames to group related information, not to add unrelated clutter.

Frames are only available in custom views. Claris describes them as a way to display data and content from multiple tables in a single view, but this can also make it easy to add too much.

A good custom view usually includes only the information needed for the process. For example, an approval workspace might have:

• A card list or spreadsheet of pending items
• A detail panel showing the selected record
• Summary metrics across the queue

This is a strong use of frames because all three areas support the same task. It is not effective to keep adding panels just because you can.

Rely on data controls for the main workflow.

Claris offers several data controls for custom views, such as card lists and spreadsheets. A card list can display records as cards, allow filtering and sorting, and update other objects in the view when a record is selected. A spreadsheet object can show records as rows and columns. With these controls, custom views become practical. A card list can serve as the navigation area, the selected record can drive the rest of the view, summary objects can show workload or status, and static objects can provide labels, grouping, or instructions.

This creates a pattern like this:

Frame 1: queue or record list

Frame 2: selected record detail

Frame 3: summaries, actions, or supporting context

This approach is much better than trying to copy a full FileMaker layout field by field.

A good example is building an approval workspace.

Imagine a capital request approval process.

An approver does not need the whole database. They need:

• a list of requests waiting for review
• the currently selected request
• key fields, supporting notes, and attachments
• summary context, such as total pending by department or aging by status

A custom view works well here because you can set up a queue on one side, a focused detail area in another frame, and summary objects above or next to it.

This gives the user a real workspace, not just a record browser.

Use custom views when prebuilt view types are not enough.

Prebuilt views are usually the right starting point.

Choose a custom view when you need to combine different behaviors, not just change the appearance. This includes situations where you want:

• A queue plus a detail panel on one screen
• Summary metrics tied to the currently selected workflow
• Multiple tables represented in one work surface
• A highly specific operational console for one role

Claris’s documentation makes it clear that custom views are designed for this level of control, especially when you need to combine different types of objects in one interface.

Custom views are powerful, but they should not be the place to create your core process rules.

The same discipline still applies here:

• Validation logic belongs in the source system
• Status rules belong in the source system
• Cross-record side effects belong in the source system
• Audit-sensitive actions belong in the source system

The custom view should offer a better interface for a role, not act as a hidden rules engine.

This is especially important when the underlying data comes from FileMaker.

A clear build sequence usually looks like this:

1. Define the role and the process.
2. List the decisions the user needs to make.
3. Identify the records and summary data needed for those decisions.
4. Decide which parts belong in queue, detail, and summary areas.
5. Use frames and subviews to support that flow.
6. Keep your first version focused and simple.

This last point is important. Custom views are flexible, so it is easy to try to build too much at once.

When to use custom views

Custom views are strongest when:

• One role needs a purpose-built workspace
• The process benefits from combining queue, detail, and summary
• The built-in view types are close, but not enough
• You want to expose a cleaner operational experience than a broad default interface

They are less compelling when:

• A spreadsheet, list-detail, or kanban view already solves the problem
• The team has not defined the workflow clearly
• The workspace would become a dumping ground for unrelated information
  
  

A better way for technical teams to think about custom views

The most helpful way to think about a custom view is not as just “a prettier layout.”

Instead, it is a process-specific workspace with a clear information hierarchy.

This way of thinking leads to better design choices, clearer layouts, and a higher chance that the view will help someone work more efficiently.