9.3 Record Types, Business Processes & Picklist Control

9.3 Record Types, Business Processes & Picklist Control

Organizations frequently use a single Salesforce object to track records that follow fundamentally different business lifecycles. For example, a company might use the standard Opportunity object to manage both simple consumer e-commerce transactions and complex multi-year enterprise software contracts. Consumer transactions require only 3 stages and minimal fields, whereas enterprise deals require a 7-stage negotiation process, executive approval fields, and specialized product categories.

Instead of creating custom objects that duplicate standard CRM capabilities, Salesforce provides Record Types. Record Types allow administrators to take a single object and offer different:

1. Business Processes (lifecycle stages and statuses).
2. Picklist Values (filtering available dropdown choices per record type).
3. Page Layouts / Lightning Record Pages (presenting customized field layouts to different users).

Understanding the precise architectural prerequisites, configuration sequence, and security boundaries of Record Types is one of the most critical topics on the Platform App Builder examination.

---

The Prerequisite: Business Processes on Standard Objects

In Salesforce data modeling, certain standard objects possess a special lifecycle picklist field that drives forecasting, conversion, or closure logic. Because these fields govern fundamental CRM mechanics, Salesforce isolates them into dedicated Business Process metadata containers.

Before you can create a Record Type on any of the four core standard objects, you must first create an active Business Process:

1. Opportunity $\rightarrow$ Sales Process: Controls which values appear in the Stage picklist field (including Forecast Category and Probability percentages).
2. Lead $\rightarrow$ Lead Process: Controls which values appear in the Lead Status picklist field (including the "Converted" indicator).
3. Case $\rightarrow$ Support Process: Controls which values appear in the Case Status picklist field (including the "Closed" flag).
4. Solution $\rightarrow$ Solution Process: Controls which values appear in the Solution Status picklist field.

[Standard Object Record Type Dependency Chain]
1. Picklist Field Definition (Stage / Status Master Values in Object Manager)
     ↓
2. Business Process (Sales / Lead / Support / Solution Process selects subset)
     ↓
3. Record Type (Associated with exactly ONE Business Process)
     ↓
4. Profile / Permission Set (Assigned to users; determines Default Record Type)

---

Picklist Filtering per Record Type

One of the most powerful declarative capabilities of Record Types is picklist value filtering. Instead of creating redundant custom fields (such as Industry_Enterprise__c and Industry_Retail__c), an App Builder uses the single standard Industry field and customizes which values are available for each Record Type.

Master Picklist Values vs. Record Type Values

• Master Picklist Definition: Located in Object Manager under the field's definition. Contains the master superset of all possible values for that field across the entire organization.
• Record Type Picklist Assignment: Within each Record Type configuration page, Salesforce lists every picklist field on the object. Clicking Edit next to a picklist allows the administrator to select which subset of master values is visible, and designate a Default Value specific to that Record Type.

The Impact of Modifying Master Values

When an administrator adds a new picklist value to the master definition, Salesforce displays a checklist of existing Record Types. If the administrator does not explicitly assign the new value to a Record Type, that value will not appear in the dropdown for users working with that Record Type.

---

Record Type Assignments: Profiles vs. Permission Sets

Controlling which users can create and interact with specific Record Types involves both Profiles and Permission Sets:

Profile-Level Record Type Settings

On a user's Profile, administrators configure:

• Assigned Record Types: Which record types the user has permission to select when creating or editing records.
• Default Record Type: The specific record type automatically selected when the user clicks "New". If a user has access to only one record type, the record-type selection prompt may be skipped; the record creation form still opens.

Permission Set Record Type Settings

Permission Sets can also grant access to Record Types additively. If a user's base Profile only grants access to the "Standard Support" Record Type, an administrator can assign a Permission Set that grants access to the "Premier Support" Record Type.

---

The Master Record Type

Every object in Salesforce begins with a single, underlying system record type known as the Master Record Type:

• When an object has no custom record types, all records are assigned to Master behind the scenes.
• A profile can still be assigned Master, but cannot combine Master and custom record types in that profile. Permission sets can grant custom record types, not Master.
• Existing Master records remain subject to normal security. New-record behavior depends on the combination of profile and permission-set record type assignments; creating custom record types does not universally force every user to use them.

---

The Four Core Business Processes Reference

---

Common Exam Traps and Best Practices

• Trap: Creating Custom Objects for Process Variations. If two business units manage the same core entity (e.g., direct sales vs. channel sales) and require different stages and picklist options, use Record Types on the standard Opportunity object, not a custom object. This preserves standard forecasting, pipeline analytics, and platform integrations.
• Trap: Missing Sales/Lead/Support Process Errors. When creating a new Record Type on Opportunity, Lead, Case, or Solution via the metadata API or Setup wizard, forgetting to create the corresponding Business Process first results in an immediate platform block.
• Trap: Confusing Record Type Access with Record Sharing. Record Type assignment on a profile controls record creation and editing defaults. It does not prevent users from viewing records of other record types! If an Account's Organization-Wide Default is Public Read Only, a user assigned only the "Domestic" Record Type can still view "International" Account records.
• Best Practice: Consolidate with Dynamic Forms First. Before creating a new Record Type solely to display a different page layout, evaluate whether Dynamic Forms conditional visibility can achieve the requirement. Record Types should be reserved for scenarios requiring different picklist values or business process stages, not simple field hiding.

Official Source Check

Checked October 19, 2026: Record type access and Master behavior.