Layouts are an important part of your system because they determine what your users see when they work with records. For each table, you can set up a power user layout, end user layout, and summary layout.
Every table must have a layout for users to open or edit records. Summary layouts are only necessary if you use popovers in the table view, or if you want to make that possible for users setting up their own views. For more information about how summary layouts work and when you might use them, see Summary Layouts.
All these layouts are configured in the table wizard on the Layout tab. Each available field is listed on the left sidebar, which you can search to find specific field names. Drag and drop the fields into place on the layout. The top toolbar offers Undo, Redo, options to add or remove rows and columns, controls for section headings and tabs, and more. Fields that aren't dragged onto the layout are not shown to users.
|
You must create a record layout for every table so that users can access the table fields they need to see and edit. For that reason, we'll start with the standard record layout. Summary layouts are covered in the next section.
This is the layout users see when they open a record from the table view. Depending on the interface they use to access the table view, they see either the power user layout or the end user layout. End user layouts typically have fewer fields than power user layouts, so it's easiest to design the power user layout first, copy it to the end user layout, and then remove unnecessary fields from the end user layout.
The Common Area is a section that always shows in the record form, even when the user changes tabs. This way, you can make important fields easily accessible from every tab, both for reference and editing purposes. For example, Common Areas often include the record ID and name, a summary field, and a status field. Make sure the Common Area includes fields users frequently need, without making the area too large and overtaking the rest of the form, or requiring users to scroll down a long sidebar.
The Common Area can be formatted as a horizontal section across the top of the form, a sidebar across the right or left side of the form, or not used at all.
To decide how to format the Common Area for a table, consider the fields you want to place there and the way users will interact with the form. For example, if your Common Area will function as a passive reference for the record ID, title, and creator, you might place it at the top so users can always scroll up to see the information. In contrast, if your Common Area houses several action buttons that users might need to click at any time, you might place it as a sidebar so it is always visible and users don't need to scroll up to access the buttons.
Showing the Common Area as a sidebar might require more trial and error when configuring your layout, especially if you originally designed the Common Area in the default position and want to move it.
Because the sidebar is narrower, field names and content might be too long or look too cluttered. Some common solutions include:
It's also more noticeable if a sidebar Common Area is disproportionate to the rest of the form.
Finally, consider if and how you want to include action buttons.
It can be useful to plan or sketch your form before you begin building, especially for tables with many fields. Think about how users will use the form and what they need to accomplish, in what order. For example, if users need to complete all the fields on the first tab before using any action buttons, you might place the action buttons at the bottom of the first tab. In general, create a layout where users complete forms from top to bottom and move sequentially from the first tab to the last tab.
Here are some questions to guide your planning:
You don't need to place every field ahead of time, but you'll save yourself time if you have an idea of the sections and tabs you want to create, and how you plan to use the Common Area. At a minimum, consider whether to show the Common Area at the top of the form or move it to the right or left sidebar, and consider which fields you want to add to the Common Area to be available on every tab of the form.
When you're ready to create your layout:
If you set the Common Area to show on the left or right, set the maximum width and then adjust the alignment to make your fields fit better in the sidebar. You can change the default to Left or Right alignment, or you can place all the field labels above the values to accommodate slimmer sidebars.
The layout editor doesn't show the Common Area as a sidebar, even if you configure it that way. It will show as a sidebar when users access actual records. |
With your Common Area complete, you can start setting up the rest of your tabs.
Add tabs by clicking the plus icon on the rightmost tab. To remove a tab, select that tab and click Delete > Delete Tab. Click Rename Tab to change the name of the current tab.
To maximize loading speed, avoid placing related tables on the first tab. This lets them load in the background. Also, try to place all or at least most required fields on the first tab. |
Use the Heading buttons to insert or edit headings inside a tab. New headings are added above the selected cell. Use the Delete menu to remove the selected heading.
Text headings help organize the form, so use them liberally. You may also want to have a text heading collapsed by default if the fields it contains aren't typically displayed to users. Note that if the form is refreshed, the default settings will be reapplied. |
When you have all the fields and tabs arranged the way you want, click Set Alignment to configure the alignment, spacing, and width of field labels, fields, and columns.
Alignment selections are critical and have a major impact on the layout, and some trial and error may be necessary to obtain the best result:
|
If a field on the layout is grayed out and can't be moved, it is likely a link to a deactivated table. You must reactivate the table before moving these fields on the layout. |
You can configure a third layout, the Summary layout, if you plan to use view or edit popovers in your table view. Popovers make it easy to skim records from the table view and make simple changes without opening the full record form. After you add a popover to a table view, users can hover over the popover field to open your configured summary layout.
You can use the summary layout to show more detail about the record than the table view shows, without requiring the user to open the full record. This can be useful for data entry, reassignments, short working notes, related tables which can't be shown in the table view, and much more. It can also make workflows smoother where users would otherwise use multiple Quick Edit fields in the table view. To set up a Summary layout:
When you've created a Summary layout, you need to add the popover to a table view.
|
Related articles |