Salesforce offers lots of customization options that allow you to tailor your org to fit the needs of your teams. Like a gearhead tricking out a muscle car, you can add some pretty sleek bells and whistles—creating processes and record types, customizing fields, and creating picklists—all to suit the needs of your business and keep its engine purring.
Your users need custom fields to capture their unique business data. You can add custom fields for each of the tabs and objects that your organization uses, with a limit of 800 fields.
A custom field name and label must be unique for that object to avoid merge and display issues. For example, if you create a field label called Email and a standard field labeled Email already exists, the merge field may be unable to distinguish between them. Adding a character or a qualifier to the custom field name makes it unique. For example, Email2 or Email Leads.
Manager Kenya Collins would like you to create a custom Support Plan Start Date field for her team. Here’s how to get that done for her:
Field | Value |
---|---|
Field Label | Support Plan Start Date |
Description | Start date of current support plan |
Help Text | When did the current support plan begin? |
Let's begin at the heading level three called Establish Field Security.
Below the heading level 3, we have a few buttons followed by a table confirming the data you've previously entered for your new field. Next, we have some text explaining the second table on the page.
We'll be focusing on this second, longer table to complete the next couple instructions. The table has three columns.
Column 1: Displays the profile name
Column 2: Contains a checkbox for toggling whether or not the field will be visible to that profile
Column 3: Contains a checkbox for toggling whether or not the field will be read-only for that profile
Note that in the first row in the table, selecting or unselecting the checkboxes will do the same for all profiles in the list. This first row is referred to as the column header, as it is at the top of one column.
With all that in mind, let's complete our instructions.
Kenya also requested you show a few members of her support team how to update support plan information on an account. Use the Edge Communications account as an example:
Dependent picklists help users enter accurate and consistent data. A dependent picklist is a custom or multi-select picklist for which the valid values depend on the value of another field, called the controlling field. Controlling fields can be any picklist (with at least one and fewer than 300 values) or checkbox field on the same record.
Create a dependency between the Stage field and the Delivery/Installation Status field:
Field | Value |
---|---|
Controlling Field | Stage |
Dependent Field | Delivery/Installation Status |
Let's pause again to examine the layout of this page. We'll begin at the Edit Field Dependency heading at level 1.
There are a few buttons followed by a table confirming the controlling and dependent fields you have chosen.
Below this is a heading level 3 marker giving some instructions for manipulating this interface. We'll dive into keyboard specific instructions in a moment. We’ll go through the layout of the interface here, but you can also take a look at the
Using the Field Dependency Matrix with a Keyboard or Screen Reader
help article.
We see buttons for including and excluding values.
Following that, there is text explaining how many columns are currently visible. These columns represent the picklist values available for the Stage field.
We see a link for Next. Activating this link scrolls the table horizontally so that columns to the right come into view. Think of it like pushing a spinning display to the left so you can see what's hanging on the other side. The previous and next links located here spin the display of the table left or right so you can see the rest of the columns on the Stage field.
The button controls and links are duplicated below the table.
Note: Users of JAWS 2023 have reported difficulty reading the table correctly once the first value has been included. JAWS 2022 and NVDA behave as expected.
Let's continue with our instructions.
After another meeting with Kenya, it’s come to light that your support team needs two different processes for keeping track of the status of customer product support and billing inquiries in your Salesforce org.
Create a new support process for them:
Field | Value |
---|---|
Existing Support Process | Master |
Support Process Name | Product Support |
Description | Process for logging customer support |
Field | Value |
---|---|
Existing Support Process | Master |
Support Process Name | Billing |
Description | Process for logging billing inquiries |
Picklist values specific to a situation reduce your users’ frustration and improve accuracy over a generic bucket where a catch-all would be otherwise selected. A customer calling with a product issue has different needs than one with a billing issue, and the agent entering the case will need to select different values to handle them.
Add new Case Type picklist values for agents to choose from.
Record types determine the business processes, picklist values, and page layouts that are available to you when creating records. Create Billing and Product Support record types so they can be utilized by your support team.
Here’s how to create the two new record types:
Field | Value |
---|---|
Existing Record Type | Master |
Record Type Label | Product Support |
Record Type Name | [auto-generated] |
Support Process | Product Support |
Description | Use to log customer support issues. |
Active | Select the checkbox |
Field | Value |
---|---|
Existing Record Type | Master |
Record Type Label | Billing |
Record Type Name | [auto-generated] |
Support Process | Billing |
Description | Use to report customer billing issues. |
Active | Select |
Since you’ve created new support processes and record types for Kenya’s team, they’re now able to create cases for Billing and Product Support that help them more efficiently take care of customer needs. Kenya would like you to show the team leads how to do this task.
Here are the instructions to create a new Product Support case:
Field | Value |
---|---|
Product | (choose any product from drop-down) |
Type | Electrical |
Case Origin | Phone |
Case Reason | Performance |
Subject | Laptop Power |
Description | Laptop does not turn on when the power button is pressed |
The instructions for creating a new Billing case are very similar:
Field | Value |
---|---|
Product | (choose any product from the drop-down) |
Type | Electronic |
Case Origin | |
Case Reason | Other |
Subject | CC overpayment not refunded |
Description | Overpayment for a purchase not refunded to customer |
Now that you’ve completed the actions in this step, your support team has what it needs to efficiently address their customers’ concerns. Move on to the next step, where we’ll add a little customization to daily communications.
Click to return to the unit on Trailhead to verify this step.