Universal Containers needs to establish two distinct business support channels: Premier Managed Support and Standard Operations. Premier Managed Support requires a customized lifecycle with specialized Case Status values ('In Triage', 'Vendor Escalation', and 'Pending Sign-off') that should not be visible to Standard Operations users. Additionally, Premier Managed Support requires a tailored page layout and specific choices for the Case Reason picklist. Which TWO administrative actions must be completed to satisfy these requirements? (Select 2 answers)
- Create a custom Support Process for Premier Managed Support to define its distinct Case Status picklist lifecycle prior to creating the associated record type.Cevap
- Create a Case Record Type for Premier Managed Support, associate it with the new Support Process, and configure the Case Reason picklist values and page layout assignment for that record type.Cevap
- CEdit the Case Page Layout directly to filter out unneeded Case Status picklist values for the Standard Operations team.
- DConfigure profile-level picklist field security to restrict Case Status value visibility directly on user profiles without creating a Support Process.
Cevap
The correct configuration steps are to create a custom Support Process defining the specific Case Status values prior to record type creation, and then create a Case Record Type linked to that Support Process while configuring page layout assignments and Case Reason picklist options.
On the Case object, Case Status picklist values are governed strictly by Support Processes. To implement distinct status lifecycles across different business groups, an administrator must first build a custom Support Process containing the required status values. Afterward, a Case Record Type must be created to link that Support Process, assign the appropriate Page Layout, and filter non-status picklists such as Case Reason.
Adım Adım Çözüm
Anahtar Kavram
Support Process and Record Type prerequisites for the Case object