Examkin

Question

Difficulty: Very hardSupport Processes and Case Record Types

A financial services institution is setting up a new specialized Tier 3 Technical Support unit alongside its existing Customer Operations team. The Tier 3 team requires a distinct case lifecycle with specific status values (such as 'In Engineering Review' and 'Patch Pending') that should not be visible to general customer service representatives. The system administrator creates the new custom picklist values on the Case Status field, creates a dedicated Page Layout, and then opens the Case Record Type creation wizard. However, the administrator discovers that the wizard requires selecting an existing process, and the new Tier 3 status values cannot be associated with the new Record Type. Which prerequisite step did the administrator fail to perform before creating the Case Record Type?

  1. Creating a dedicated Support Process containing the required Case Status picklist values.Answer
  2. B
    Modifying the Case Status field-level security settings to grant Edit access to the Tier 3 Support user profile.
  3. C
    Configuring the picklist value selection directly under the record type edit menu on the Case object manager.
  4. D
    Setting up a Case Assignment Rule to dynamically assign the new status values upon record creation.

Answer

The administrator failed to create a custom Support Process containing the required Case Status values prior to defining the Case Record Type.
In Salesforce, the Case Status field is a special business process field. Unlike standard picklist fields, Case Status values associated with a specific Case Record Type are determined by a Support Process. The required sequence of operations is to create the custom Case Status picklist values, define a Support Process that includes those specific status values, and then create the Case Record Type while selecting the newly created Support Process. Omitting the Support Process step prevents associating custom status values with the new record type.

Step-by-Step Solution

1
Identify the relationship between Case Status, Support Processes, and Record Types in Salesforce.
Recognize that Case Status is a special picklist field linked to business processes, similar to Opportunity Stage and Lead Status.
In Salesforce Core Administration, special lifecycle picklist fields cannot be assigned directly to Record Types without an intermediate process object.
2
Determine the required administrative workflow for configuring new Case lifecycles.
The correct sequence is: (1) Add custom Case Status picklist values, (2) Create a Support Process to select available Case Status values, (3) Create the Case Record Type and associate it with the Support Process, (4) Assign Page Layouts.
Creating a Record Type on the Case object explicitly requires selecting an existing Support Process in the setup wizard.
3
Evaluate the cause of the administrator's roadblock during configuration.
Because no dedicated Support Process was created for Tier 3 Support, the administrator could only select existing Support Processes which lacked the new status values.
Omitting the Support Process creation step prevents new Case Status values from being assigned to the new Case Record Type.

Key Concept

Support Processes pre-requisite for Case Record Types
Rate this question

Topics

Support Processes and Case Record Types

More questions from this topic