Salesforce TVB-201 Exam Questions

To display the screen flow, the administrator should create a tab and add the screen flow to the page. The administrator can also use a flow element and add the screen flow to the record page.

The other options are not relevant to this scenario. Adding the flow in the utility bar of the console will not display the screen flow. Installing an app from the AppExchange is not necessary to display the screen flow.

Here are the steps on how to create a tab and add the screen flow to the page:

Go to Setup > Tabs.

Click New.

Enter a name and label for the tab.

Select the Screen Flow tab type.

Select the screen flow that you want to display.

Click Save.

Here are the steps on how to use a flow element and add the screen flow to the record page:

Go to Setup > Customize > Lightning App Builder.

Select the record page that you want to add the screen flow to.

Click Edit.

Drag the Flow element from the Palette to the canvas.

Select the screen flow that you want to display.

Click Save.

A dependent picklist and a custom picklist are the two features that can be used to fulfill the requirement. A global picklist and a multi-select picklist are not features that can be used to fulfill the requirement.

Here is a more detailed explanation of why A and B are the correct answers:

a) Dependent Picklist

A dependent picklist is a picklist whose values are dependent on the value selected in another picklist. This is useful for ensuring that only valid values are selected for a field. In this case, the administrator can create a dependent picklist for the category field on accounts and cases, with the values for the picklist being dependent on the record type selected. This will ensure that only the relevant picklist values are available for selection based on the record type selected.

For example, the administrator could create a dependent picklist for the category field on accounts and cases with the following values:

Record Type: New Account

Picklist Values: Residential, Commercial

Record Type: Existing Account

Picklist Values: Renewal, Upsell, Cross-sell

This would ensure that only the relevant picklist values are available for selection when creating a new account or an existing account.

b) Custom Picklist

A custom picklist is a picklist that is created by the administrator. This is useful for creating picklists with values that are specific to the organization's needs. In this case, the administrator can create a custom picklist for the category field on accounts and cases, with the values for the picklist being specific to the organization's needs. This will ensure that the picklist values are relevant to the organization and its customers.

For example, the administrator could create a custom picklist for the category field on accounts and cases with the following values:

Picklist Values: Residential, Commercial, Land, Multi-Family

This would ensure that the picklist values are relevant to the organization and its customers.

An escalation rule is a tool that allows administrators to automatically escalate cases based on certain criteria and time triggers. For example, an escalation rule can change the owner of a case, send an email notification, or update a field value when a case has been open for more than 7 days. An escalation rule consists of multiple rule entries that define the criteria and actions for each escalation scenario. Reference: https://help.salesforce.com/s/articleView?id=sf.case_escalation.htm&type=5

One possible reason why a manager receives an error when trying to approve a record is that the user in the next approver step is inactive or missing, which means there is no valid user to assign the record to after approval. To troubleshoot this issue, an administrator should check if the user in the next approver step is active and exists in Salesforce; if not, they should activate or create the user or change the approval process to assign the record to another user. Adding a delegated approver for the next approver in the process does not solve this issue because delegated approvers are only used when approvers are unavailable; they do not replace approvers who are inactive or missing. Updating the field level security to view on fields that are updated in the process does not solve this issue because field level security does not affect approval processes; it only affects what fields users can see or edit on page layouts. Reviewing the page layout to ensure fields updated in the process are visible does not solve this issue because page layouts do not affect approval processes; they only affect what fields users can see or edit on page layouts. Reference: https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm&type=5

The $Record global variable allows you to reference the values of the active record the flow is running on.