What is a page layout?
If you want to reorganize the way information is laid out in the records on a custom object, you can customize the page layout. The layout determines how records will appear when you create them and when you view them throughout Rippling.
Page layouts are highly customizable. You can:
- Drag and drop fields and sections into your preferred order.
- Add tabs to further organize information.
- Provide the full picture by adding information from related objects.
- Embed analytics right within the record so no one has to go hunting for the right report.
To edit the record layout of an object, you must have admin permission for the object. People can only view records based on their permissions.
Default page layout
By default, records you add to custom objects display information in three areas:
- A header containing the record name, owner, and last modified date
- A Details section displaying most of the fields on the record
- An Additional details section that displays the date and time the record was created, the person who created it, the date and time it was last modified, and the person who last modified it
You can customize the page layout to specify exactly which details are displayed and where. For example, you might want to:
- Add the project’s start date to the header.
- Add a new section and move the financial information related to the project to that section.
- Create a separate tab with details related to a project post-mortem analysis that appears only if the field Post mortem needed? is marked as Yes.
You can customize the header, sections, and tabs in Catalog under Page layouts. You can also add related lists and related fields, embed a report, add a content block, and dynamically hide or display information.
Add a block
You can customize the custom object record layout by adding content blocks that contain elements such as text, notices, or images. For example:
- Embed a block displaying badges earned by an employee.
- Add a rich text block that has instructions for seasonal work.
- Include a block that displays a notice reminding people about important deadlines.
Create the block in App Studio and configure who can see it. For more information, see Blocks and dynamic content. Then, on the object's Page layouts tab in Catalog, add the block to the layout.
If the block uses functions or other logic to change what it shows, use Configure after you add it. The block is visible in the layout according to the access settings you set when you created it.
Add a report
Adding reports to custom object page layouts is a handy way to embed analytics in the places where the data is most relevant rather than requiring people to go and find it somewhere else.
For example, if you’ve built a report to track bill rates vs. actuals on a project, you can add it to the page layout of project records so that anyone reviewing the details can see that information at a glance.
People will only see an embedded report if that report has been shared with them.
When you add a report to a record, you can filter it so that, by default, it only displays information related to the record you’re viewing. For example, say you’re adding a report listing project assignments to the Project object, and you add a filter by Project. When you view the Logistics Optimization project, the report will only show assignments related to that project. It will not show assignments related to any other projects. The ID field in the filter is the ID for the object tied to the page layout you’re editing.
Add reports from the object's Page layouts tab in Catalog. You can put more than one report in a section and change whether a charted report displays as a grid.
Dynamically hide or display information
You can set up dynamic views so that sections and tabs in a page layout only appear when conditions you define are met.
For example, in a custom object for projects, you might set up dynamic views to do the following:
- Display a “Post-mortem” tab only when the value in a field “Post-mortem required?” gets marked as yes.
- Create unique views for different types of projects: one view with a certain set of fields for marketing projects, one view with a different set of fields for engineering projects, etc.
Sections and tabs with dynamic views will only appear or disappear when the values used in the conditions have been saved. For example, say you create a section that will only appear when the field “Accepted” is set to true.
- When you initially create the record, the section will appear because no value has been saved for the “Accepted” field. After you save the record, the section will appear or disappear depending on the value you selected in the “Accepted” field.
- If you saved the record with the “Accepted” field marked as false, the section will not be shown. If you then edit the record and mark “Accepted” as true, the section stays hidden until you save it again. At that point, the section will reappear on the page. You can then re-edit and select the fields that just appeared.
Set these conditions on the object's Page layouts tab in Catalog. You can use any of the fields in the object or related lists.