Examkin

Question

Difficulty: HardSupport Processes and Case Record Types

Cloud Kicks is establishing a dedicated Partner Vendor Escalation team to handle complex third-party warranty and hardware replacement cases. This team requires a customized Case lifecycle with specialized Case Status picklist values, including 'Vendor Review', 'Awaiting RMA', and 'Vendor Resolved', which must not be visible to the general Customer Support team. While creating a new Case Record Type for this team, the Salesforce Administrator notices that the required custom Case Status values cannot be selected or assigned directly within the record type picklist edit menu. Which two configuration steps must the administrator perform to make these specialized Case Status values available for the new Case Record Type? (Select 2)

  1. Create a new Support Process and select the appropriate Case Status picklist values required for the vendor escalation lifecycle.Answer
  2. Associate the newly created Support Process with the new Case Record Type during or after record type creation.Answer
  3. C
    Add the custom status values directly to the default Case Page Layout picklist field settings.
  4. D
    Adjust the Organization-Wide Defaults on the Case object to allow custom status picklists per profile.

Answer

The administrator must create a new Support Process containing the required custom Case Status values and then assign that Support Process to the new Case Record Type.
On the Case object, the Case Status field is controlled by Support Processes. Before custom Case Status values can be used on a specific Case Record Type, an administrator must create a dedicated Support Process that includes those status values, and then assign that Support Process to the Case Record Type.

Step-by-Step Solution

1
Identify the dependency mechanism for Case Status picklist values.
Recognize that Case Status picklist availability is governed by Support Processes, not direct picklist edit menus on Record Types.
Salesforce enforces business process controls on stage-like fields (such as Opportunity Stage, Lead Status, and Case Status).
2
Create a customized Support Process.
Define a new Support Process containing 'Vendor Review', 'Awaiting RMA', 'Vendor Resolved', and any standard lifecycle statuses required.
A Support Process acts as the master filter for valid Case Status values.
3
Assign the Support Process to the Case Record Type.
Link the newly created Support Process to the Partner Vendor Escalation Case Record Type.
A Case Record Type requires an assigned Support Process to dictate which Case Status values are available to users.

Key Concept

Support Processes must be created before Case Record Types when customizing Case Status picklist values.
Estimated Time:2m 0s
Rate this question

Topics

Support Processes and Case Record Types

More questions from this topic