page layout assignment to record type

Salesforce Tutorial

Page layouts and record types in salesforce, page layouts and record types.

Page Layout

The organization of fields, custom links, and related lists on an object detail or edit page.

Used to organize UI pages for your users:

• Which fields, related lists, and Custom links a user’s sees.
• Field properties – visible, read-only and required.
• Page section customizations.

NOTE: Establish unique layouts for different business scenarios.

Creating page Layouts

Following is an example to create a page layout for case object.

Set Up->Customize->Case->Page Layout->Click on New button

Fill Mandatory details

Drag and drop required to the layout and save page layout.

Record Types

Record types allow you to associate different business processes and subset of pick list value to different users based on their user profile.

They are used to drive which page layouts users see when viewing records, based on their user profile.

Benefits of record types:

  Tailors user interaction experience to specific business needs.

Allows for easier administration as there are fewer fields to maintain.

Creating Record Types:

Example to create record types: In this example, I am creatinga a record type for Case object.

Setup->Customize->Case->Record Type

Click on New button and fill all mandatory fields and select profiles.

Create a support process before creating record type

Click on NEXT button

Select page layout and click SAVE.

Page Layout Assignment

Go to Record Type or Page Layout and click on Page layout Assignment

assign page layout to record types based on profiles.

Interview Questions on Page Layouts and Record Types in Salesforce

What is a page Layout and record type?

• Page Layout :- Field can be made mandatory from the page layout when it needs to be made mandatory for a set of users.
• Field Level Security :- Field can be made mandatory from the FLS when it needs to be made mandatory for all the users in the Organization and even from the API’s.
• Validation Rule :- Field can be made mandatory from the Validation Rule when it needs to be made mandatory for user who is using the same Page layout used by other usersSalesforce.com recommends using the Page Layout option for making the field mandatory.

How can we make a field mandatory from page layout?

Go to page layout edit that layout and then click on properties of the field that you going to make it mandatory

• Check the required checkbox.

  When are the Record types used?

Record Types are used t o assign the different Page layouts to different users based on their profiles. And to  enable different sets of Standard/Custom Picklist values for two different users using the same page layout.

what is the use of creating support process,before creating a record ?

Support Process is only for the “Status” picklist, as you might know. The picklist values available in the status of a case record type determine a support process. It is only a business relevant feature as the status field is the most process-specific field on a case. The status field cannot be customized on a record type, it can only be customized in a support process.

You can understand support process. https://help.salesforce.com/articleView?id=customize_processes.htm&type=5

https://developer.salesforce.com/forums/?id=906F0000000AfiyIAC

• +44 (0) 118 403 2020
• [email protected]
• Help Center
• Customer Community
• SCHEDULE A DEMO

Give us a call: (800) 961 8205

U.K. Office: +44 (0) 118 403 2020

 Validity Community

Data Quality

Record types in salesforce: what they are and how to use them efficiently.

 on February 13, 2024

minute read

Many customer data management tasks are repetitive, time-consuming, and even downright boring. Plus, the more data you generate, the more difficult it becomes to maintain.  

Fortunately, Salesforce —the world’s leading customer relationship management (CRM) platform––offers a variety of features to help streamline your data and enhance your user experience. Among these features, Record Types play a pivotal role. 

Below, we’ll delve deep into Salesforce Record Types: what they are, how to customize them, and how to use them effectively.

What is a Record Type in Salesforce?

Short answer: A Salesforce Record Type is a way to group records within a specific object.

Longer answer: Imagine you have a form to fill out, but the information you need to put in changes depending on the situation. Record types let you have multiple versions of this form, each with different fields and options, all within the same category. This way, you can choose the right object for each specific situation. Some examples of standard objects include Accounts, Contacts, Leads, Products, Users, Contracts, Reports, and Dashboards but users can create custom objects as well.

When to use Record Types in Salesforce

Say, you use an Opportunity object to track potential sales. A Record Type allows you to have different versions of an Opportunity record for different sales processes (for example: retail versus wholesale sales). Each Record Type can have its own set of fields, Page Layouts, and logic, tailored to the specific needs of your business processes.

In terms of how many record types are in Salesforce, while technically the sky’s the limit, Salesforce recommends no more than 200 record types per Object (more on why later).

Types of records in Salesforce

As previously stated, Salesforce Record Types are used to manage different aspects of the business effectively. The following Record Types, for example, are tailored to handle specific data and processes relevant to the retail and ecommerce sector:

• Customer accounts: Record types built against this object might be used to store information about your customers, such as contact details, purchase history, and preferences. These will be  crucial for managing customer relationships, personalizing marketing efforts, and providing effective customer service.
• Orders: Record types built against this object are used to manage the details of customer purchases, including products ordered, quantities, prices, and delivery status. In other words, they’re essential for tracking sales, inventory, and fulfillment processes.
• Products: Record types built against this object will typically store information about the products you sell, such as descriptions, pricing, and inventory levels. These will help facilitate sales and inventory management.
• Opportunities : Record types built against this object will likely be used to track potential sales and revenue and are key for sales forecasting and managing the sales pipeline.
• Cases: Record types built against this object will be used for customer service and support, tracking customer inquiries, complaints, and feedback. They’re especially important for resolving customer issues and maintaining high customer satisfaction.
• Leads: Record types built against this object will be used to track potential customers who have shown interest but have not yet made a purchase. This information is vital for lead generation and conversion efforts.

Remember, not only can you create custom Record Types but each of these Record Types can be further customized with specific fields, Page Layouts, and picklist values to suit the unique needs of your business.

5 key benefits of SF Record Types

As you can imagine, using Record Types in Salesforce offers several benefits for businesses of all sizes (but especially those managing large amounts of data).

• Enhanced user experience (UX): Record types allow you to tailor the information you collect and how it’s displayed based on different scenarios. Customized Record Types help streamline workflows by presenting users with the appropriate options and fields, reducing clutter and confusion.
• Improved data quality: By guiding users to enter specific information for different situations, Record Types help maintain consistency and accuracy in the data. This leads to better data quality , which is crucial for reliable reporting and analysis.
• Controlled access: Record types can be used in combination with profiles and permission sets to control who can view and edit certain types of records. This helps in enforcing security and privacy policies within the organization.
• Simplified reporting: By categorizing records into different types, it becomes easier to segment and analyze your data. This level of segmentation can be invaluable for generating targeted reports and gaining insights specific to different areas of your business.
• Scalability: As your business evolves, Record Types provide the flexibility to add new categories or modify existing ones without affecting the underlying structure of your Salesforce instance. This adaptability is key for businesses that need to scale or change their processes over time.

What is the Record Type ID?

When you create a Record Type in Salesforce, the system automatically assigns it a unique ID. This unique code allows Salesforce to link data, configure Page Layouts, and control which users can access certain Record Types based on their permissions.

In simple terms, the Record Type ID is like a label or tag that helps Salesforce know exactly which version of a form or layout to use for a particular record. 

Knowing the Record Type ID is useful in situations such as:

• Automation : When setting up automation rules, knowing the Record Type ID ensures the correct application of these rules.
• Data migrations : The ID is crucial for correctly mapping data during migrations or integrations with other systems.
• Complex reporting : For generating detailed reports where data needs to be segmented by Record Type.

Managing Record Types in Salesforce

Managing Record Types in Salesforce is relatively simple. Below is a step-by-step guide covering how to create, edit, and delete Record Types based on different needs.

Creating Record Types

For establishing new Record Types tailored to specific business needs.

• Log in to Salesforce.
• Click on the gear icon in the top-right corner, and select Setup . Then, find and click Object Manager.
• Choose the object (ex. Account, Contact, Opportunity ) for which you want to create a new Record Type.
• Click on Record Types in the sidebar, then click the New button.
• Fill in the necessary details like Record Type Label, Record Type Name, and Description . Select the Active checkbox to make it available for use.
• Choose the Page Layouts that will be used for this Record Type.
• Decide which user profiles will have access to this Record Type. Select the profiles and save your changes.
• Click the “Save” button to create the new Record Type.

Editing Record Types

For modifying existing Record Types to align with evolving processes.

• Go to the Object Manager , select the object, and click on Record Types .
• Find the Record Type you want to edit and click on it. Then, click the Edit button.
• Update whichever details you wish (ex. label, name, description, or associated Page Layouts).
• Click the “Save” button to apply your changes.

Deleting Record Types

To remove obsolete Record Types and maintain data integrity.

• As before, go to the Object Manager , select the object, and click on Record Types .
• Locate the Record Type you wish to delete. Click on the drop-down menu next to the Edit button, and select Delete . Salesforce will prompt you for confirmation. Note that deleting a Record Type is a significant action that can affect data and users. Ensure that it’s no longer needed and backup your data before proceeding.
• Complete the deletion:
•  Click OK or Delete to confirm and complete the deletion process.

Remember, when working with Record Types, it’s important to understand how they’re being used in your Salesforce environment. Changes to Record Types can have wide-ranging effects on how users interact with data, so it’s best to make changes carefully and with a clear understanding of the implications. There are plenty of technologies that can help with this— elements.cloud is one popular example.

Record Types and Page Layouts in Salesforce

Earlier we explained that Record Types let you have multiple versions of a form, complete with different fields and options, all within the same category.

Well, Page Layouts, aligned with specific Record Types, allow you to dictate how data is displayed and interacted with.

How to customize Page Layouts using Record Types

Customizing Page Layouts is what enables you to tailor the UX to your specific needs. However, to customize them, you must already have an associated Record Type created. Beyond that, here’s how to get customizing:

• Click on the gear icon in the top-right corner and select Setup .
• In the Setup menu, find and click on Object Manager .
• Select the Object for which you want to customize the Page Layout.
• Click on Record Types in the sidebar for your chosen object. 
• Click on the name of the Record Type you want to customize the Page Layout for.
• Scroll down to Page Layouts and click Edit next to the profile whose Page Layout assignment you want to change.
• If you don’t have a custom Page Layout yet, go back to the object’s main page, click on Page Layouts , and create a new layout by cloning an existing one or starting from scratch.
• Once you have the desired Page Layout, assign it to the appropriate Record Type for each profile. You can do this by selecting the new layout from the dropdown menu next to each profile in the Edit Page Layout Assignment page.
• After assigning the Page Layouts to the Record Types for the desired profiles, click Save .
• Test the Record Types by creating or editing records. Ensure that the correct Page Layout appears for each Record Type and profile combination.

Customizing Page layouts for different Record Types allows you and other users to see the most relevant information based on the specific context of the record. This further enhances user experience and ensures data consistency throughout your Salesforce implementation. 

Remember, changes to Page Layouts can significantly impact how users interact with Salesforce, so it’s important to plan and test these changes thoroughly.

6 Salesforce Record Types best practices 

Salesforce data management can be tricky for even the most experienced users but the following best practices will help you make the most of your SF records.

• Clearly define business processes: Understand the different business processes within your organization and how they map to Salesforce Record Types. This clarity will help you create Record Types that align with specific business needs.
• Limit the number of Record Types: Avoid creating too many Record Types for a single object. Having too many can lead to confusion and complexity. Instead, create Record Types only when they serve a distinct purpose.
• Use detailed names and descriptions: Give each Record Type a clear, descriptive name and a detailed description. This practice helps users understand the purpose of each Record Type and choose the right one.
• Customize Page Layouts thoughtfully: Tailor Page Layouts for each Record Type to include only the fields and sections necessary for that particular business process. This customization reduces clutter and makes data entry more efficient.
• Train users thoroughly: Ensure that users understand the purpose of different Record Types and how to use them. Proper training can significantly improve Salesforce data quality and increase user adoption.
• Regularly review and update: Business processes evolve, so regularly review and update your Record Types and Page Layouts to ensure they remain relevant and effective.

Turn your Salesforce data woes into wins

When used correctly and strategically, Record Types can transform your CRM processes. From setting up automation to customizing user interfaces, understanding and leveraging Record Types is key to effective Salesforce data management. Remember, the aim is to enhance productivity without compromising data integrity or user experience.

Wondering how your CRM stacks up against the rest? Check out our benchmark guide for users and stakeholders, Today’s Top 7 Data Management Challenges . 

Read the guide!  

What to read next

April 17, 2024

Unlocking Success with Enterprise Data Management: Strategies, Benefits, and Best Practices

When it comes to running a business in our interconnected world, data is like gold. And, for any business striving to stay...

April 15, 2024

Mastering Revenue Forecasting: How to Forecast Revenue for Increased Competitiveness

Mastering revenue forecasting is a vital skill for any sales or marketing professional looking to impact their company's bottom line and strategic...

April 10, 2024

B2B Customer Relationship Management Strategies for Growth

When it comes to business-to-business (B2B) operations, the significance of Customer Relationship Management (CRM) can’t be overstated. It's the linchpin that holds the...

• Marketing Cloud

Experiences

Access Trailhead, your Trailblazer profile, community, learning, original series, events, support, and more.

Tips & Hints for Page Layouts and Field-Level Security

What are page layouts and field-level security.

Salesforce has two WYSIWYG tools for editing page layouts: the original page layout editor and a new enhanced page layout editor. The enhanced page layout editor is enabled by default and provides all of the functionality of the original editor, as well as additional functionality and an easier-to-use interface.

The following sections describe the characteristics and behaviors of page layouts, mini page layouts, and field-level security.

• Control the layout and organization of fields, Visualforce related lists, and custom links on detail and edit pages
• Show or hide standard and custom buttons on detail pages.
• Set which fields are visible, read only, or required on detail and edit pages.
• In Personal, Contact Manager , Group , and Professional Editions, control which fields users can access in list views, reports, Force.com Connect Offline, and when synchronizing data.
• Control the fields displayed on portal objects in the Customer Portal .
• Control the layout and organization of fields, related lists, and custom links on records in the mini view of the Console tab.
• Inherit record type and profile associations, related lists, fields, and field access settings from their associated page layout.
• The visible fields and related lists of the mini page layout can be further customized, but the other items inherited from the associated page layout cannot be changed on the mini page layout itself.
• The order of related lists on a page layout determines the order of related lists on its mini page layout.

For example, if a field is read-only on the page layout, that same field will be read-only on the mini page layout. To change the field properties of fields on the mini page layout, you must change the field properties of fields on the page layout. Note that the console respects field-level security in organizations where it is available.

• Pages that display due to standard button overrides or custom buttons display in the console without the header or sidebar.
• Overrides for the Edit and View buttons for an object do not affect the Edit and View buttons in the mini page layouts.
• Available in Enterprise, Unlimited, Performance , and Developer Editions only.
• Restrict users’ access to view and edit fields on detail and edit pages.

For example, if a field is required in the page layout and read only in the field-level security settings, the field-level security overrides the page layout and the field will be read only for the user.

• Control which fields users can access in list views, reports, Force.com Connect Offline, Customer Portal pages, and when synchronizing data.

Getting Started with Page Layouts and Field-Level Security

• In Enterprise, Unlimited Performance , and Developer Editions, use field-level security to restrict users’ field access; use page layouts primarily to organize pages. In Personal, Contact Manager , Group , and Professional Editions, field-level security is not available. Use page layouts to restrict access to fields and to organize pages.
• To reduce the number of page layouts to maintain, use the same page layout for all profiles for a specific record type.

Plan which fields you want users to be able to view or edit, which fields you want required for each tab, and how you want the pages to display for users.

• Go to the fields area to create any custom fields, custom buttons, or custom links for each tab.

All users automatically use the same page layout for each tab.

• If you have a Professional Edition organization and you plan to use the Console tab, define mini page layouts to organize how fields and related lists will appear in the console’s mini view. From a page layout, click Mini Page Layout .
• Go to Buttons, Links, and Actions or to Buttons and Links to create any custom fields, custom buttons, or custom links.
• Go to Record Types to create record types for different business scenarios. You can show different page layouts to different users based on record types. For example, you can have different layouts for “Partner” accounts and “Customer” accounts. Record types are available in Professional, Enterprise, Performance, Unlimited, and Developer Editions.
• Customize your pages, related lists, and Customer Portal pages.
• If your organization plans to use the Console tab, define mini page layouts to organize how fields and related lists will appear in the console’s mini view. From a page layout, click Mini Page Layout .
• Assign page layouts to users based on profiles and record types. This determines which layouts users will see when viewing different record types. From a page layout, click Page Layout Assignment .
• Go to the fields area to verify that all field access settings are correct. Click a field, then click View Field Accessibility .
• Apply field-level security if different users need different field access.
• Click Preview while editing a page layout to see how the page will look for users with different profiles. This preview includes any extra security that is set in field-level security.
• Click Quick Save to save and continue editing the page layout.
• To see why users can or cannot access a field, view the field accessibility. From Setup, enter Field Accessibility in the Quick Find box, then select Field Accessibility , and then select an object.
• Manage access to specific fields with profiles or permission sets.

The Differences Between Salesforce Record Types and Page Layouts

Many new Admins and Users make the same mistake: Creating too many record types. Why is this a problem? Too many record types can make your org more complex than it needs to be. As new Admin comes along, or as changes are needed for your org, the more technical debt   you have, the more time will be wasted in the future on people trying to understand or change the org.

You probably need fewer record types than you think. This is because most of the time, you can achieve the desired results you need with page layouts instead. Oftentimes, Users will create completely new record types with a new page layout, when all they need to do is create just a new page layout. We will go over what exactly record types and page layouts are, what their key differences are, and how you can get started building them today.

First, What is a Page Layout?

Okay, Now What Are the Salesforce Record Types?

Record Types help control what business processes, picklist values, and page layouts are available to different users for different reasons. They are easy to create and can be assigned to different Users. Let’s say your company keeps track of US Accounts and UK Accounts in separate ways. This may include keeping track of shipping preferences on the Account level. Let’s say that with US Accounts, you have 3 picklist options: Rail, Air, and Truck. But with UK Accounts, you want to add one more option: Sea. This is one case where you may want to create two different record types because you need two different picklists for the same field.

So, When Do I Use Salesforce Record Types and Page Layouts?

You should use Salesforce record typey (with a page layout!) when you need records to have different:

• Processes – Like a Sales Process
• Picklist Values – Like “Shipping Type” in our above example
• Page Layouts – Use different page layouts to reveal the different picklist options and further differentiate between record types

You should use only page layouts if you just want different fields shown to different Users. Even if you have 10 fields that only Marketing Users should see, you still don’t need a separate Marketing record type, unless you need some of the fields to contain different picklist values. You should use a page layout when you need records to look different for different Users. Use page layouts if:

• You want some fields required to be populated for certain Users
• Related lists
• Custom Links
• Visualforce Components
• You want to make certain fields “Read Only” for certain Users

*Note: This is not a permanent way to hide fields! Users can still access them in Salesforce, like through Salesforce reports

Assigning Salesforce Record Types Page Layouts

Now that you understand the differences between page layouts and record types, you can start creating and assigning them. If you have already created the different record types and page layouts, you can navigate to a specific Profile type to assign them. In a Profile, you can see an overview of all of the different page layouts assigned per record.

Picture Credit: Salesforce

Sometimes, the page layout assignment will vary per record type. For example, in the image above, for the High Volume Customer Portal Type profile, all Accounts have a page layout called “Account Layout”. However, for Idea records, the page layouts vary by assignment. That means that there are multiple record types for the idea object that may have different page layouts.

To apply existing page layouts to the different record types for the Idea object, click on Edit Assignment.

Test Thoroughly!

With page layouts, you are controlling who has access to seeing and potentially editing which fields on a record. With this being the case, it’s important to thoroughly test new page layouts ensuring only the most important fields and information are shown to the right Users. Sometimes, Users can get overloaded with the amount of information on a page. This can be discouraging and even make Users more prone to making mistakes when inputting data. Previously we have discussed different ways how custom fields can help avoid such mistakes and keep your data clean . Remember, taking a field off of a page layout doesn’t keep a User from having access to that field as they can still see it on reports.

A good way to test how your page layouts look to different Users is to actually log into Salesforce and test as that User. This way, you see a record exactly how Users of that Profile are seeing it (depending on your sharing rules too). You can even click around as that User to see which fields are editable, but remember to not make any changes if you’re in Production!

In order to  log in as another User , you have to ensure that you have been granted login access or that you are a System Administrator with permission to log in as any user. To set this as a Sys Admin, search and select “Login Access Policies” in the Quick Search bar. You will be taken to the Login Access Policies page where you can adjust the settings accordingly.

Get More Salesforce Tips from Inspire Planner Blog

Recent posts, best salesforce events to attend in 2024, top 5 salesforce project management apps, alternative resources to learn salesforce.

You may also like

One of the incredible things about being involved in the Salesforce ecosystem is the wonderful…

Salesforce Project Management apps exist for a reason. Despite Salesforce’s wide range of products for…

Becoming Salesforce certified is one of the secrets to a successful Salesforce career — certified…

Don’t miss an article

Get actionable tips and useful advice to improve your team’s performance in Salesforce.

Privacy Overview

User Guidance Simplified!

By Products

Screenshot Guidance Platform

For Individuals/Teams/Agency

Guidance on any process without the need for video sharing.

Knowledge Base Platform

For SaaS Applications

Self-serve application guidance for users no need for a support team

Digital Adoption Platform

For Enterprise Applications

software training for employees - end to lengthy training sessions

AI driven Application Support Platform

For Individuals/Enterprises

Self-serve training and support on enterprise software

• Resources Blog Webinars Navigate'23 - L&D summit
• Install Free Extension

Salesforce learning is made easy with our free Chrome extension!

Assign Record Types and Page Layouts in the Enhanced Profile UserInterface

• From Setup, enter Profiles in the Quick Find box, then select Profiles.
• Select a profile.
• In the Find Settings... box, enter thename of the object you want and select it from the list.
• Click Edit.
• In the Record Types and Page Layout Assignments section, makechanges to the settings as needed.SettingDescriptionRecord TypesLists all existing record types for the object.--Master-- is a system-generated record type that's usedwhen a record has no custom record type associated with it. When --Master-- is assigned, users can't set a record typeto a record, such as during record creation. All other record typesare custom record types.Page Layout AssignmentThe page layout to use for each record type. The page layoutdetermines the buttons, fields, related lists, and other elementsthat users with this profile see when creating records with the associatedrecord type. Since all users can access all record types, every recordtype must have a page layout assignment, even if the record type isn'tspecified as an assigned record type in the profile.Assigned Record TypesRecord types that are checked in this column are availablewhen users with this profile create records for the object. If --Master-- is selected, you can't select any custom recordtypes; and if any custom record types are selected, you can't select --Master--.Default Record TypeThe default record type to use when users with this profilecreate records for the object.The Record Types and Page Layout Assignments settings havesome variations for the following objects or tabs.Object or TabVariationAccountsIf your organization uses person accounts, the accounts objectadditionally includes Business Account Default Record Type and Person Account Default Record Type settings,which specify the default record type to use when the profile's userscreate business or person account records from converted leads.CasesThe cases object additionally includes Case Close settings, which show the page layout assignments to use for eachrecord type on closed cases. That is, the same record type may havedifferent page layouts for open and closed cases. With this additionalsetting, when users close a case, the case may have a different pagelayout that exposes how it was closed.HomeYou can't specify custom record types for the home tab. Youcan only select a page layout assignment for the --Master-- recordtype.
• Click Save.

Related Questions

• Set Page Layouts and Field-Level Security
• Assign Record Types to Profiles in the Original Profile UserInterface

Gyde Platform 30 minutes Demo

About 30 mins

Learning Objectives

Accessibility, record pages, create a custom lightning record page, customize related lists, activate the page, view the customized page.

• Challenge +500 points

Customize Record Page Components and Fields

• Create, customize, and manage Lightning pages.
• Use the Lightning App Builder.
• Assign a Lightning page to a profile.

This unit requires some additional instructions for screen reader users. To access a detailed screen reader version of this unit, click the link below:

Open Trailhead screen reader instructions .

What you see when you log in to Salesforce for the first time is just the start. You can customize and personalize many things on object record pages using a combination of the Lightning App Builder and page layouts.

Most of the pages you see in Lightning Experience, such as the Home page and record pages, are Lightning pages. Lightning pages are a collection of components arranged in regions on the page. You can customize the structure of the page, the position of its components, and the record detail fields it displays with the Lightning App Builder. (Learn more in the Lightning App Builder module right here on Trailhead)

The Lightning App Builder lets you:

• Control which components appear on Lightning pages
• Create custom Lightning pages for different apps and users
• Control which fields appear on record pages
• Control which lists of related records and custom links users see
• Control which standard and custom buttons appear on records and related lists
• Control which quick actions appear on the page

You’re probably thinking, "Buttons, lists, record details? What is all this stuff?" Let’s tour the record page by looking at an example contact record, and then we’ll dive in and customize a page.

• In the previous unit, you learned about record highlights (1) and how to customize the fields it shows using compact layouts. The record highlights area also contains a set of buttons and actions  (2), which you’ll learn how to customize in a later unit.
• The Related tab (3) contains related lists , which are lists of other records that are associated with the record you’re viewing. For example, an account can have related products, contacts, opportunities, and other custom records.

We’ve mentioned buttons, links, and actions. We’ll go over those in more detail and how to modify them on Lightning pages in later units. In this unit, we focus on customizing the page structure, components, record detail fields, and related lists.

Maria wants to create an Energy Audit record page just for her sales team so they can have the necessary field and related list information at their fingertips when they view the Energy Audit records.

When the Energy Audit custom object was created, a system default Energy Audit record page was created too. Right now, everyone in the org who views an Energy Audit record sees the information from that default layout. Maria is going to create a customized record page just for the sales people.

Let’s follow along.

• Open the All list view.
• Select Burlington evaluation .

• In the page properties, change the Label to Energy Audit Record Page for Sales.
• Change the API Name to Energy_Audit_Record_Page_for_Sales.
• Click the Details tab on the canvas, then click the Record Detail component (where the fields are). There are all the fields for the Energy Audit object. But they’re all in one non-customizable block. With the click of one button, we can change that.

• Step through the wizard, select Energy Audit Layout , then click  Finish . The right-hand column is almost empty, and the fields could be in a better order. Let’s fix that.
• Click the Audit Notes field and drag it to the right column, above Owner.
• Do the same for the Type of Installation field.
• If it's not already there, move Account below Energy Audit Name.
• Click Save , then  Not Yet .  Activating the page makes it available to your users. This page isn’t quite ready for users, however. Maria wants to add a related list.

Because Energy Audit is a custom object, it doesn’t have any related lists…yet. Let’s add one. We can do that in the page layout editor.

• Click Object Manager , then find and click Energy Audit in the list of objects.
• Click Page Layouts , then Energy Audit Layout .
• Scroll down to the Related Lists section.
• In the palette, click Related Lists , and drag the  Files element down to the Related Lists section. With the Files related list, Ursa Major Solar sales reps can add files to a record and see a list of files associated with the record.
• Click Quick Save , then click Yes .

Maria’s done with customizing the page for now, but no one can see it. It’s time to activate the Lightning page and make it live for her Sales users.

• From Setup, click the Home tab.
• Enter App Builder in the Quick Find box, then select Lightning App Builder .
• Click Edit next to the Energy Audit Record Page for Sales page.
• Click Activation .

There are four options for activation.

• Make the page the org default for the object.
• Make the page the default object record page for specific Lightning apps.
• Assign the page to a combination of Lightning apps, record types, and profiles.
• Assign the page to a form factor, such as a desktop or phone.

Maria wants Ursa Major Solar’s salespeople to see this new record page. She’s going to assign it to her sales team’s user profile so that when they view Energy Audit records, they’ll see the revised view of the fields and the new related list. She’s also going to make sure it’s assigned to both the desktop and phone form factors, so her users can view it when working on their desktops and when on the road from their mobile devices. Let’s get started. 

• Click the App, Record Type, and Profile tab.
• Click Assign to Apps, Record Types, and Profiles .
• Step through the wizard and assign the page to the Energy Consultations app, the Desktop and phone form factor, the Master record type, and both the Custom: Sales Profile and the System Administrator profile. Normally, Maria would select only Custom: Sales Profile, but since you’re logged in as a System Administrator, we select that too so that you can see how the new page layout looks.
• Review the page assignments. The New Page column is populated with the name of the page we’re activating: Energy Audit Record Page for Sales.
• Click Save .

• Click the  Related tab. Now you can see the Files related list there, just waiting for someone to upload something.

Great job! Now that you’re more familiar with Lightning page customization, you can start creating pages that give your users just what they need. By arranging components and fields in logical sections, you can make it even easier for your users to store and manage the data that’s important to your business.

• Salesforce Help:  Create and Configure Lightning Experience Record Pages
• Salesforce Help:  Activate Lightning Experience Record Pages
• Salesforce Help:  Lightning App Builder Considerations
• Get personalized recommendations for your career goals
• Practice your skills with hands-on challenges and quizzes
• Track and share your progress with employers
• Connect to mentorship and career opportunities

Product Area

Feature impact.

• What's New in Industries Order Management for Winter '24
• Order Management Roles
• Order Management Process Flow
• Order Fulfillment States
• Industries Vlocity Documentation Locations
• Definition of an Order in Industries Order Management
• Order Management Design and Implementation Best Practices
• Order Management Plus Only: Patch Releases
• One-to-One Decomposition
• One-to-Many Decomposition Relationship
• Many-to-One Decomposition Relationship
• Create a Decomposition Relationship
• Associate Child Products in a Bundle with a Product Class
• Create a Product Class
• Test a Product Class Decomposition Relationship
• Grouping Multiple Fulfillment Requests into One Request
• Model a Product as an Attribute
• One-Time Decomposition
• Augment Callout with Temporary Information
• Mapping Temporary Information to a Technical Product
• Order Decomposition Configuration
• Order Decomposition Conditions
• Parent-Child Relationships in Decomposition with Top Order Item Scope
• Types of Mapping Rules
• How Mapping Works When a Commercial Product Relies on another
• Configure Mapping with a Relies On Relationship
• Multi-Level Decomposition Modeling
• Setting the Product Scope
• Account Scope
• Order Item Scope
• Relies On Scope
• Configure Relies On Scope
• Downstream Order Item Scope
• Top Order Item Scope
• Order Scope
• Order Management and Offer Specifications
• Order Management and Change of Plan
• Decomposition Visualization
• Choose the Card Labels in the Decomposition View
• Creating Technical Products
• Vlocity Solution in Modeling Decomposition
• Suppressing Synchronization Check Before Submitting an Order
• Dynamically Generated Workflows
• Orchestration Plan Definition
• Make the Fulfillment Designer Tabs Visible
• Add the Fulfillment Diagram Component to your Record Page
• Create a Fulfillment Diagram with an Orchestration Plan Definition
• Open an Existing Fulfillment Diagram
• Import an Orchestration Scenario into a Fulfillment Diagram
• Create Orchestration Item Definitions in a Fulfillment Diagram
• Create Dependencies in a Fulfillment Diagram
• Manage Dependencies in a Fulfillment Diagram
• Edit the Swimlane Order in a Fulfillment Diagram
• Edit Definitions in a Fulfillment Diagram
• The Orchestration Plan View
• Assetized Root Order Items and Orders
• Activated Root Order Items and Orders
• Staged Assetization
• Set Up an Orchestration Plan for Staged Assetization
• Orchestration Scenarios
• Orchestration Item Types: Auto Task
• Orchestration Item Types: Callout
• Associate a Manual Task with a Salesforce Queue
• Mapping of Salesforce Tasks to and from Manual Tasks
• Orchestration Item Types: Milestone
• Orchestration Item Types: Push Event
• Orchestration Item States
• Orchestration Item Conditions
• Orchestration Item Associations to Fulfillment Request Lines and...
• Control How Orchestration Item Dependency Loops Are Treated
• Create Dependency Definitions
• Orchestration Dependencies Across Orders
• Create Orchestration Dependencies Across Orders
• The New Orchestration Dependency Definition Screen
• Add the Related Order option to Orchestration Dependency Definition...
• View or Create an Orchestration Item Definition
• Orchestration Item Definition Attributes Encoding Style
• Orchestration Item Definition Request Items Encoding Style
• Orchestration Scope
• Create the XOMAutoTaskCopyAttributes Item Implementation
• Sample DataRaptor JSON for the XOMAutoTaskCopyAttributes Auto Task
• Create the XOMAutoTaskCopyAttributes Auto Task
• Set a Future Time for OM to Process an Orchestration Item
• Configure a Callout to Send Empty Attribute Values
• Manipulating Attributes with a Vlocity Calculation Matrix
• Propagate Attributes from Fulfillment Requests to Order Items...
• Saving Values from Order Management Plus to Salesforce
• Set Up Re-­Propagation for Attribute Values
• Information About Synchronizing Data across Order Items from...
• Synchronize Data across Order Items from Different Orders
• Start a Manual Task
• Queue Types
• Bulk Operations
• Configure filterable attributes in OM Standard
• Configure filterable attributes in OM Plus
• Attributes-Based Queues
• Configure Manual Queue Assignment Rules
• Add a Member to, or Remove one from, a Manual Queue
• Manual Queue Displayed Fields
• Obtaining an OmniScript URL
• Creating a Manual Task that Uses an OmniScript
• Launch an OmniScript from a Manual Task
• Launch an OmniScript from the Manual Queue
• Launch an OmniScript from the Orchestration Plan View
• Launch an OmniScript from the Orchestration Item
• OM Plus: Configuring Orchestration Queue Assignment Rules
• Partial Assetization of Product Attributes
• Use Assetization and Encryption Options for Product Attributes
• Set Up Non Case-Specific and Case-Specific Components
• Key Components for Updating Salesforce Records During Order...
• Features for Predicting Order Delay
• Sync Data from Necessary Objects
• External Order Data
• Import of Your External Order Data into CRM Analytics
• Create an App to Sync Imported External Order Data with CRM Analytics
• Create an App to Predict Delays in Order Fulfillment
• Update of the Order Delay Prediction Recipes
• Update of the Order Delay Predictions Model
• Predicted Order Delay Dashboard
• Order Management Plus: Accessing Pricing Information
• Considerations for Configuring In-Flight Amendments in OM
• Workflow for amending an order
• Overview of Canceled and Amended In-Flight Orders in Order Management
• Decomposition flow supplemental orders
• Decomposition use cases
• Conflict of attributes
• In-Flight Amendment Orchestration Plan Update Algorithm
• Allow a Supplemental Order to Override a Change to an Attribute
• Rules for How Point of No Return (PONR) Propagates through a...
• Configure Plan Definitions for Rollback or Amendment
• Dependencies Within and Between Orchestration Plan Definitions
• Overview of Rollback Groups
• Create a Rollback Group
• In-Flight Amendment: Changing the Default Behavior of a Running...
• Amend Push Event
• Allow Supplemental Changes after PONR (Point of No Return)
• Creating a Technical Product
• Creating an Offer
• Creating a Decomposition Relationship Between the Offer and the...
• Add Orchestration Items to the Plan
• Define Dependencies for Orchestration Items
• Use an Attribute or Field in the Scenario Condition in Order...
• Creating and Decomposing an Order
• Example: A DSL Order
• Integration Configuration Workflow
• XOMAsyncSystemInterface
• Methods Included with XOMAsyncSystemInterface
• XOMEnhancedSystemInterface
• Methods Included with XOMEnhancedSystemInterface
• Create a System Record for Industries Order Management
• Create a System Interface for Integration
• Creating a Callout Orchestration Item Definition
• Put a System Interface into Offline Status
• View or Edit a System Interface
• Custom Asynchronous Callouts
• Configure a Custom Asynchronous Callout
• Custom Synchronous Callouts
• Authentication for Integration Adapters
• Create an Auto Task with the Create an Auto Task with the...
• Creating DataRaptor Bundles for Asynchronous Integration
• Defining the Callout
• Overview of Extending the Asynchronous System Interface
• Extend the Asynchronous System Interface
• Integration DataRaptor Bundles
• Creating and Importing DataRaptor Bundles
• Passing Pricing Information to Fulfillment Systems
• Add a Number of Retries to an Orchestration Item Definition
• Set Up Retry Policies for Failed Callouts
• Enable Retry Policies in the Custom Record Type Settings
• Configure an Integration Retry Policy
• Associate a Retry Policy with an Orchestration Item Definition
• Schedule the Integration Retry Job in Order Management Standard
• Custom Settings for Integration Retry and System Interface Online Mode
• System-Wide Timeouts and Retry Policies in OM Plus
• OM Plus: Managing System Instances
• OM Plus: Set the State for a System Instance
• Creating a Callout Orchestration Item for Asynchronous Integration
• Add a sub-action to the Order Product Object or Orchestration...
• Deactivate Metadata Fields for Plan Items in the Orchestration Plan...
• Modify a List of Fields Displayed for Plan Items in the...
• Add a Missing Custom Label in OM Plus
• Naming Conventions for Custom Labels
• Custom Labels and Translation
• Translate Custom Labels
• OM Plus: Synchronizing Labels
• Technical Inventory
• How Technical Inventory Works
• Impact of Technical Inventory on Decomposition
• Impact of Technical Inventory on Fulfillment
• Impact of Technical Inventory on Migration of Existing Assets
• Managing Technical Inventory
• Viewing and Updating Technical Inventory from Within Salesforce
• Order Fields
• Manual Queues for Fallout Handling
• Managing Fallout at Runtime
• Delete the Resolve Fallout Orchestration Item Definition
• Jeopardy Dates
• Set the Requested Completion Date for an Order in Order Management
• Configure the JeopardyNotificationQueueName Custom Setting
• Create a Queue for Items in a Jeopardy State
• Configuring a Calendar for Manual Tasks in Order Management
• Configuring Batch Jobs
• Start the Schedule Jeopardy Management Job
• Order Management Plus Integration Reference Documents
• OM Plus: Database Structure
• OM Standard: Optimize Large Order Submission with OrderSubmitMode
• Order Fulfillment Status When OrderSubmitMode is Set to Queueing
• OM Standard: Optimize Large Order Decomposition with...
• Deploy Custom Extensions to the DEV Environment
• Migrate inventory items and fulfillment request lines to...
• View the Order Management Custom Settings
• List and Description of Order Management Custom Settings
• Set all DataRaptors to be synced
• Use an Auto Task Implementation in the Catalog with OM Plus
• Use a Callout in the Catalog with OM Plus
• Example of Alerts
• Activate the NotifySumoLogic Event Listener for OM Plus
• Set Up a Sumo Logic Named Credential for OM Plus
• Deploying Vlocity Order Management Plus to a System Integration Test...
• OM Plus: Test the Performance of SQL Queries
• Add Required Indexes for Industries Order Management Implementations
• Enable Complex Conditions in Custom Settings
• Schedule and Manage an Order Management Purge Job
• Configure Settings for the Order Management Purge Job
• Check the Status of the Purge Job
• Configuring OM and OM Plus Interfaces
• Order Management LWC Components
• Add a Lightning Component to a Record Page
• OM Standard: Request and Response Data Storage
• OM Standard: Configure Request and Response Storage in Custom Settings
• Verify That the OM Plus Administration Screen Appears Properly
• Synchronize with OM Plus and check the status
• Verify that the OM+ Status job is scheduled
• Settings for Order Management Permission Sets and Permission Set...
• Upgrading OM: Activate or Delete...
• Data Security
• Data Protection Requirements Summary
• OM Plus: Manage Secrets
• Perimeter Security
• Set Object Security in Order Management Plus
• Set Attribute Security in Order Management Plus
• Setting Up Key-Manager and Encrypt Service
• Perform Data-in-Transit (DIT) Key Change using AWS Lambda
• Exposing an API Service to the Internet with Basic Authentication
• How OM Plus Prevents Exposure of Personally Identifiable Information...
• OM Standard: Considerations about PlatformEvents Mode
• Order Management Standard: Edit the OrchestrationMode Custom Setting
• Order Management Standard before Fall '19: Set Platform Events to...
• Order Management Standard: Schedule the Orchestration Recovery Job
• Order Management Standard: Platform Event Error Handling
• Restoring Lost Data
• OM Plus: Corrupt Data
• Restore Corrupt Data
• Backup and Restore Operations
• Order Management Plus: Syncing Delta Objects
• OM Plus Data Event Streaming
• Configuring or Running the OM Plus Status Job
• Add a Custom Setting to Order Management
• Configure Automatic Order-Submit Queuing
• Order Object Model Components for Submitting Queued Orders
• Set SuppressUsersSync to control user synchronization between...
• Enable user access to Order Management Plus
• Test that user info exported from OM Standard to OM Plus
• OM Plus:­ Assign a User Profile to a User
• Named Credentials Support for Order Management Standard
• Open the XOM Administration Panel
• XOM Administration Panel Options
• Order Management Plus: Pushing an Order to Salesforce
• Apex CPU Time Limit Exceeded Error in Industries Order Management
• Correct the OdinAPIHandler interface implementation
• Correct the XOMSupplementalOrderLifeCycle interface implementation
• Configure the Environment for Order Management Standard
• OM Plus: Attribute Values aren't Visible in a Log
• Cannot Change Tab Names in the All Tabs Page in Salesforce
• After You Set the Language to Hebrew, Orders No Longer Decompose...
• OM Plus: ? Appears on Some Buttons or Labels
• OM Plus: Delta Sync Doesn't Show Change to Email Address Field for...
• OM Plus: Order Sync Failure
• Enable Custom Settings
• If You Are Upgrading from a Version Earlier Than Fall '20: Upgrade...
• Add the Sales Bundle Scope to the Appropriate Picklists
• OM Plus only: As a test, submit an order from Salesforce to OM Plus
• OM Plus only: Set appropriate DataRaptor bundles and DataRaptor map...
• OM Standard: Ensure the Order Value Has Been Added to the Scope...
• OM Standard Only: Run XOMPopulateMainOrderItemIDBatchJob
• Order Management Plus: Set DataRaptors to Sync from Salesforce to OM...
• Add and Enable the OMStdBundleActivationBackCompatibility Custom...
• Applying Record Types and Page Layout Assignments for OM Fall '19...
• Verifying that Order Management Plus is Working with Salesforce
• Configure Settings from the XOM Admin Panel
• Order Management Standard (optional): Set up Platform Events
• Creating a Remote Site Setting for the Callout
• Enabling Triggers for Order Management Fall '19 and Later

You are here:

• Salesforce Help
• Industries Order Management

Applying Record Types and Page Layout Assignments for OM Fall '19 and Later

When you install Industries Order Management, you must apply record types and page layout assignments. Doing so configures or restores Order Management record type visibility and page layouts.

In Vlocity Insurance, some objects and page layouts have different names:

Manual Queues = Work Queue (Manual)

Orchestration Dependencies = Work Dependencies

Orchestration Dependency Definitions = Work Dependency Templates

Orchestration Items = Work

Orchestration Item Definitions = Work Templates

Orchestration Plan Definitions = Workstream Templates

Orchestration Plans = Work Projects

Orchestration Queues = Work Queue (System)

Orchestration Scenarios = Work Scenarios

Orchestration Scheduler Implementations = Work Scheduler

System Interface = Work System Interface

To apply record types and page layout assignments:

• Go to the Vlocity XOM Administration tab.
• Next to Apply Record Types and Page Layout Assignments, click Open. The Apply Record Types and Page Layout Assignments page opens, showing a list of profiles.

In orgs before Spring '22, the process is a little different. Select XOM Admin in any profile used by Fulfillment designers

The difference between the System Administrator profile and the base profile is the range of objects to which the layouts are applied. Users assigned to the Admin profile have full access to Vlocity Order Management functionality. They can design and manage fulfillment processes, including order decomposition and orchestration.

• Click Update.

Cookie Consent Manager

General information, required cookies, functional cookies, advertising cookies.

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings. Privacy Statement

Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.

Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.

Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.

Cookie List

• Collapse All