As an administrator, you can manage page layouts specific to certain users or instances. If you do not want to allow certain groups to see data, like sensitive pricing information, you can use Page Layouts. Next to the Master Layout, which will apply to all users, you can create a specific Page Layout for a business object and assign it to a Business Role and an Instance Type.
The bullet points below differentiate between the master layout and the page layout. I would say: Differences between master layout and page layout:
- Master layout is the global template managed by global admin. Any changes made in the master layout are inherited by the page layout.
- Page layout is the local template managed by local admin; local admin can make fields mandatory/read only/invisible.
- Only properties such as mandatory, read-only, and invisible are stored in the page layout.
- Changes such as the following are always stored in the master layout: new field, changed label, moved fields.
You can disable personalization for all users if desired and export extension fields, layout changes, and code list restrictions from one tenant to another.
You can restrict the values available from a dropdown list by creating and maintaining code list restrictions for different business objects. By default, the system allows all the code values for a business object to be visible. You can restrict these values based on either an instance field or a business role, or a combination of both the field and the business role.
Business case - Best Run Bike Company page layout requirements
Modifying a page layout
In this simulation, you will learn how to create and assign a page layout.