Record Type, Page Layout and more

What do Record Types control? (Choose 3)

• Path

• Fields

• Picklist values

• Pages Layouts

• Lightning App Builder Record Page Layout

Answer explanation

Record types let you offer different business processes, picklist values, and page layouts to different users. For example: You might create record types to differentiate your regular sales deals from your professional services engagements, offering different picklist values for each. Or you might display different page layouts for your customer support cases versus your billing cases.

At the other hand, Page layouts represent how an object is shown from a detail level. Lightning App Builder record pages almost always contain that detail, but also provide other features, like Flow embedding, or Chatter, or any other format.

Page layouts are close to the object, Lightning pages are close to the app.

Cloudy Computing has multiple different record types for Opportunities. Users are complaining that it is tedious having to select a record type each time they create an Opportunity.

As the Salesforce Administrator, what could you recommend?

• Administrator can set the default record type at profile level

• Users can set their default record type in Settings

• No default record type can be chosen

• Administrator can set the default record type at role level

Answer explanation

Only Sys Admin can set de Default record Type for each profile, por each object.

Cloudy Computing has two distinct teams for selling products and services. Each team follows a different set of steps, and collects different information during the sale.

What features in Salesforce will best support this situation?

• Create a page layout and record type for each team

• Create a sales process for each team

• Create a sales process and a page layout for each team

• Create a sales process, page layout, and record type for each team

Answer explanation

We must always consider that a Sales/Service Process are very strongly in relationship with the corresponding Page Layout and Record Type.

If the steps are different, two different Processes must be created, so any Record type and Page Layout must be related to them.

A company has a complicates Sales process regarding its opportunities. The company has three different lines of business (Widget A, Widget B, Widget C) that each contain fields specific to that lines of business´s industry and customers. For each line of business, there is a specific set of fields that Sales users should see and a different set of fields that Marketing users should see.

How should an Administrator configure Page Layouts and Record Types for the Opportunity object so that each team sees what it needs to see, without buttered layouts containing unnecessary fields?

• Create three Record Types (Widget A, Widget B, Widget C) with six Page Layouts (Sales Widget A, Sales Widget B, Sales Widget C, Marketing Widget A, Marketing Widget B, and Marketing Widget C)

• Create one Record Type with six Page Layouts (Sales Widget A, Sales Widget B, Sales Widget C, Marketing Widget A, Marketing Widget B, and Marketing Widget C)

• Create six Record Types (Sales Widget A, Sales Widget B, Sales Widget C, Marketing Widget A, Marketing Widget B, and Marketing Widget C) with six total Page Layouts, one for each Record Type

• Create six Record Types (Sales Widget A, Sales Widget B, Sales Widget C, Marketing Widget A, Marketing Widget B, and Marketing Widget C) with one Page Layout

Answer explanation

As a tip, always remember:

1) the number of record types is the number of different lines of business for any process.

2) the number of profiles commonly is the minimal number of page layouts that must be created FOR EACH RECORD TYPE.

3) Record types let you offer different picklist values, and page layouts to different users

Universal Containers has a private sharing model on Opportunities. The system Administrator has been asked to create a new custom object that will track customer payment information and will link to the Opportunity. Only those users with access to the Opportunity should be able to see the records on the new object.

What should the Administrator do to accomplish this task?

• Create a Master-Detail relationship with a Criteria Based Sharing Rule

• Create a Master-Detail relationship with Profile permissions

• Create a Lookup relationship with a Criteria Based Sharing Rule

• Create a Lookup relationship with Profile permissions

Answer explanation

As the new custom object will be linked to the opportunity object to track customer payment information, it must be a Master-Detail relationship. The new object depends on the Opportunity object.

If it is a master-detail relationship the accesses are guaranteed by the parent object (opp). And then you give it Profile permissions to read or edit.

A Universal Containers (UC) Administrator has created a new Lightning record page for the Sales team to display a report chart embedded on the Account page. There are no Record Types for Account at this time.

Which step should the Administrator take to make this page the default view of the UC app for the Sales team without impacting the Support team?

• Make the page the default object record page for the UC app for the Sales profile.

• Create an Account Record Type and make the page the default object record page

• Make the page the org default.

• Make the page the default object record page for the UC app.

Answer explanation

The page must be selected as the default object record page, and must be assigned to the required profile (Sales), so as not to in order to not impact the Support Team.

Universal Containers wants to create a custom object to capture account survey data. Users must be able to select an account from the survey record and view related surveys on the account record.

Which two actions should the System administrator take to meet this requirement? Choose 2 answers.

• Add the account related list to the survey page layout.

• Add the survey related list to the account page layout.

• Create a lookup relationship field on the survey object.

• Create a lookup relationship field on the account object.

Answer explanation

. User should be able to view related surveys on the account record --> Look up relationship field on the survey object: it should be possible to view many surveys in one account.

Account object should display Survey object --> Add the survey related list to the account page layout (within Account Object - Page Layouts)