ADM-201 · Question #4
Ursa Major Solar tracks both user issues and customer issues. A user issue can be logged as: - new - waiting for reply - closed A user issue can be logged as: - new - working - closed An…
The correct answer is C. Record Types and Support Processes. To track two distinct types of cases with different lifecycle statuses, an administrator should use Record Types to differentiate the case types and Support Processes to define their unique status picklist values.
Question
Ursa Major Solar tracks both user issues and customer issues. A user issue can be logged as:
- new
- waiting for reply
- closed
A user issue can be logged as:
- new
- working
- closed
An administrator needs to track both case types. Which features should be used?
Options
- AWorkflows and Automated Case Users
- BPage Layouts and Process Builder
- CRecord Types and Support Processes
- DPage Layouts and Record Types
How the community answered
(31 responses)- A13% (4)
- B3% (1)
- C77% (24)
- D6% (2)
Why each option
To track two distinct types of cases with different lifecycle statuses, an administrator should use Record Types to differentiate the case types and Support Processes to define their unique status picklist values.
Workflows are automation tools for actions and rules, not for defining different record types or picklist lifecycles. "Automated Case Users" is not a standard Salesforce feature for this purpose.
Page Layouts control the user interface and field arrangement for a record, while Process Builder is an automation tool. Neither is designed to define distinct record types with different picklist value lifecycles.
Record Types allow administrators to define different business processes, picklist values, and page layouts for records on the same object. For cases, Support Processes specifically define the lifecycle stages (status picklist values) available for each record type, perfectly addressing the need for distinct issue tracking flows.
While Page Layouts would be used in conjunction with Record Types to customize the UI, Record Types alone, combined with Support Processes (which manage the picklist values/lifecycle), directly address the core requirement of different status values. Page Layouts don't define the picklist values themselves.
Concept tested: Record Types and Support Processes for Cases
Source: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm&type=5
Topics
Community Discussion
No community discussion yet for this question.