Examkin

Question

Difficulty: HardSupport Processes and Case Record Types

An organization is launching a specialized Tier 3 Infrastructure Support team to work alongside its general IT Service Desk. The Tier 3 team requires a distinct lifecycle for cases, including custom Case Status picklist values such as 'Vendor Investigation' and 'Patch Pending' that should not be visible to general IT agents. When the Salesforce administrator attempts to configure a new Case Record Type for Tier 3 Support, the required Case Status values are unavailable for selection during record type creation. What must the administrator do first to make these specific status values available for the new case record type?

  1. Create a custom Support Process that includes the required status values and assign it to the new Case Record Type.Answer
  2. B
    Edit the Case Status picklist field on the Case object to directly assign the values to the user profiles of the Tier 3 Support team.
  3. C
    Configure a Case Assignment Rule to dynamically update the Case Status picklist choices based on the record owner.
  4. D
    Modify the Component Visibility rules on the Lightning Record Page layout to expose the missing picklist options.

Answer

Create a custom Support Process containing the required status values and select it when defining the new Case Record Type.
On the standard Case object, the Case Status field is controlled by a Support Process. To make unique Case Status picklist values available to a specific Case Record Type, an administrator must first create a Support Process that includes those values. Once created, the Support Process is assigned during the Case Record Type setup.

Step-by-Step Solution

1
Identify the dependency architecture for Case lifecycle stages in Salesforce.
Recognize that Case Status is a special picklist field tied directly to Support Processes.
Unlike standard custom picklists, Case Status options cannot be filtered solely at the Record Type level without an underlying Support Process.
2
Define a new Support Process.
Select and save the specific subset of Case Status values ('Vendor Investigation', 'Patch Pending', etc.) required for the Tier 3 team.
The Support Process acts as the master filter for case lifecycle stages.
3
Associate the Support Process with the new Case Record Type.
The new Record Type inherits the status picklist values configured in the designated Support Process.
Creating the Record Type requires selecting an active Support Process as its structural baseline.

Key Concept

Support Process as a Prerequisite for Case Record Types
Rate this question

Topics

Support Processes and Case Record Types

More questions from this topic