Salesforce Certified Field Service Consultant Practice Test - Questions Answers, Page 8

Service Resources are records that represent the people or equipment that perform field service tasks[199]. Permission Set Licenses are records that grant users access to specific features or apps such as Salesforce Field Service[200]. Creating one Service Resource and assigning the relevant Permission Set Licenses would allow Universal Containers to configure Salesforce Field Service to support an employee who performs the role of a Dispatcher and a Technician by creating a service resource record for the employee and assigning them the Salesforce Field Service Dispatcher and Mobile permission set licenses[201]. Creating two Service Resources and assigning them to the employee would not work because an employee can only be associated with one service resource record[202]. Creating one Service Resource and assigning the Technician and Dispatcher role would not work because roles are records that define the level of access users have to data in an organization hierarchy[203]. Creating two Skills records and assign them to the Service Resource record would not work because skills are records that define specific abilities or qualifications that service resources have and do not affect their access to features or apps[204].

Reference: https://help.salesforce.com/s/articleView?id=sf.fs_service_resources_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.perm_sets_license_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_perm_sets_license_assign.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_resources_create_edit_delete.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.roles.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_skills_overview.htm&type=5

Status Transitions are settings that define which status updates are allowed or restricted for service appointments[205]. Pinned Statuses are settings that prevent service appointments from being rescheduled or unscheduled by scheduling or optimization services[206]. Ensuring that Status Transitions are configured to prevent the update from ''Cannot Complete'' to ''Scheduled'' and defining ''Cannot Complete'' as a Pinned Status for Scheduling and Optimization Services would allow Universal Containers to ensure that Service Appointments in a ''Cannot Complete'' status are unable to be rescheduled or unscheduled for history tracking purposes by restricting the status change from ''Cannot Complete'' to ''Scheduled'' and preventing scheduling or optimization services from moving or removing service appointments with the ''Cannot Complete'' status[207]. Defining ''Cannot Complete'' as a Pinned Status for Auto-Dispatch Services would not affect whether Service Appointments in a ''Cannot Complete'' status are able to be rescheduled or unscheduled. Auto-Dispatch Services are settings that automatically assign service appointments to resources based on predefined criteria[208]. Ensuring that Status Transitions are configured to allow the status update from ''Cannot Complete'' to ''Scheduled'' would not ensure that Service Appointments in a ''Cannot Complete'' status are unable to be rescheduled or unscheduled. It would enable the status change from ''Cannot Complete'' to ''Scheduled''.

Reference: https://help.salesforce.com/s/articleView?id=sf.fs_status_transitions_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_pinned_statuses_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_status_transitions_create_edit_delete.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_auto_dispatch_overview.htm&type=5

Reshuffle is an action within the Gantt that allows rescheduling multiple service appointments at once based on predefined criteria such as emergency priority, travel time, or skills[209]. Reshuffle would allow Universal Containers to dispatch emergency work identified throughout the day that needs to be completed before lower-priority work by running a reshuffle action that prioritizes emergency work and assigns it to the best available resources[210]. Defining a Global Optimization job to run hourly would not allow Universal Containers to dispatch emergency work identified throughout the day that needs to be completed before lower-priority work. Global Optimization is a feature that allows rescheduling multiple service appointments at once based on predefined criteria such as emergency priority, travel time, or skills[211]. Running a Global Optimization job hourly would not be responsive enough for emergency work identified throughout the day. Creating a custom Gantt action to call an Apex class to reschedule appointments would not be necessary for Universal Containers to dispatch emergency work identified throughout the day that needs to be completed before lower-priority work. Custom Gantt actions are actions within the Gantt that can be customized using Apex code to perform specific tasks such as sending notifications or updating fields[212]. Creating a custom Gantt action would require additional development and maintenance and would not leverage the existing Reshuffle action. Writing a batch Apex class to unschedule low priority work orders would not allow Universal Containers to dispatch emergency work identified throughout the day that needs to be completed before lower-priority work. Batch Apex is a way of processing large volumes of data asynchronously using Apex code[213]. Writing a batch Apex class would require additional development and maintenance and would not leverage the existing Reshuffle action.

Reference: https://help.salesforce.com/s/articleView?id=sf.fs_gantt_reshuffle_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_gantt_reshuffle_run.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_optimization_global_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_gantt_custom_actions_overview.htm&type=5 https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_batch_interface.htm

Permission Sets are records that grant users access to specific features or apps such as Salesforce Field Service[214]. Scheduling licenses are records that grant users access to scheduling features such as Dispatcher Console or Optimization[215]. Creating Permission Sets and assigning the Salesforce Field Service Resource Permission Set and Scheduling license to each Technician would allow Universal Containers' Technicians to update their own appointments' status using the Dispatcher console Gantt chart by granting them access to Salesforce Field Service mobile app features such as updating status and granting them access to scheduling features such as viewing Gantt chart[216]. Creating Permission Sets and assigning the Salesforce Field Service Scheduling and Mobile Permission Sets to the Resource profile would not allow Technicians

The Preventative Maintenance Gantt is a view within the Dispatcher Console that shows the scheduled service appointments for preventive maintenance work orders[217]. The Dispatcher Console Appointment list is a view within the Dispatcher Console that shows the list of service appointments with various details such as status, priority, or assigned resource[218]. Filtering is a feature that allows narrowing down the list of records based on specific criteria such as date, status, or territory[219]. Using the Preventative Maintenance Gantt and filter the list to show only desired work orders and using the Dispatcher Console Appointment list and filter the list to show only desired service appointments would allow Universal Containers' Managers to monitor Preventative Maintenance work orders using the Dispatcher Console by showing them the preventive maintenance service appointments on a Gantt chart or a list view and allowing them to apply filters to see only the relevant records[220]. Using the Dispatcher Console Map and filter the list to show only desired service appointments would not allow Universal Containers' Managers to monitor Preventative Maintenance work orders using the Dispatcher Console. The Dispatcher Console Map is a view within the Dispatcher Console that shows the locations of service appointments and resources on a map[221]. Using the Dispatcher Work Order Polygon and filter the list to show only desired service appointments would not work because there is no such feature as Dispatcher Work Order Polygon.

Reference: https://help.salesforce.com/s/articleView?id=sf.fs_gantt_preventive_maintenance_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_gantt_appointment_list_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_gantt_filter_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_gantt_preventive_maintenance_view.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_gantt_map_overview.htm&type=5

Earliest Start Permitted is a field on the Service Appointment object that defines the earliest date and time that a service appointment can start[222]. Due Date is a field on the Service Appointment object that defines the latest date and time that a service appointment must be completed by[223]. Using Earliest Start Permitted and Due Date fields on Service Appointments would help ensure that they are completed within the agreed upon Service Level Agreement (SLA) with Universal Containers' customers by setting the boundaries for when a service appointment can start and finish according to the SLA terms[224]. Actual Start and Actual End are fields on the Service Appointment object that capture the actual date and time that a service appointment started and ended[225]. Using Actual Start and Actual End fields on Service Appointments would not help ensure that they are completed within the agreed upon SLA with Universal Containers' customers because they are recorded after the service appointment is performed and do not enforce any SLA terms. Arrival Window Start and Arrival Window End are fields on the Service Appointment object that define the expected date and time range that a resource will arrive at a service appointment[226]. Using Arrival Window Start and Arrival Window End fields on Service Appointments would not help ensure that they are completed within the agreed upon SLA with Universal Containers' customers because they only indicate when a resource will arrive and do not enforce any SLA terms. Scheduled Start and Scheduled End are fields on the Service Appointment object that define the planned date and time range that a service appointment will take place[227]. Using Scheduled Start and Scheduled End fields on Service Appointments would not help ensure that they are completed within the agreed upon SLA with Universal Containers' customers because they only indicate when a service appointment is scheduled and do not enforce any SLA terms.

Reference: https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_serviceappointment.htm https://help.salesforce.com/s/articleView?id=sf.fs_sla_overview.htm&type=5

Frequency is a field on the Maintenance Plan object that defines how often work orders should be generated from maintenance plans such as daily, weekly, or monthly[228]. Generation Timeframe is a field on the Maintenance Plan object that defines how many work orders should be generated from maintenance plans at a time such as 1, 2, or 12[229]. Auto-generate work orders is a field on the Maintenance Plan object that enables or disables the automatic generation of work orders from maintenance plans[230]. Setting Frequency to 1 Month; Generation Timeframe of 12; uncheck Auto-generate work orders would allow Universal Containers to offer customers a Maintenance Plan that provides 12 monthly checkups where the customer will call to schedule each visit by creating maintenance plans that generate one work order per month for 12 months but do not generate them automatically until the customer calls[231]. Setting Frequency to 1 Month; Generation Timeframe of 1; check Auto-generate work orders would not allow Universal Containers to offer customers a Maintenance Plan that provides 12 monthly checkups where the customer will call to schedule each visit. It would create maintenance plans that generate one work order per month for one month and generate them automatically without waiting for customer calls. Setting Frequency to 1 Month; Generation Timeframe of 12; check Auto-generate work orders would not allow Universal Containers to offer customers a Maintenance Plan that provides 12 monthly checkups where the customer will call to schedule each visit. It would create maintenance plans that generate one work order per month for 12 months and generate them automatically without waiting for customer calls. Setting Frequency to 1 Month; Generation Timeframe of 1; uncheck Auto-generate work orders would not allow Universal Container

Use all-or-none scheduling for related appointments is a setting in Field Service Settings that enables or disables the simultaneous scheduling of service appointments that have dependencies[232]. Dependency Type is a field on the Service Appointment object that defines the relationship between two service appointments such as Start After Finish, Start Before Finish, or Finish Before Start[233]. Same Resource and Same Day are fields on the Service Appointment object that indicate whether two service appointments with dependencies should be assigned to the same resource and scheduled on the same day[234]. Selecting the checkbox Use all-or-none scheduling for related appointments in Field Service Settings, setting the Dependency Type to Start After Finish and Same Day on the first service appointment in the dependency, and making sure the Same Resource and Same Day fields appear on the Service Appointments page layout would allow Universal Containers to ensure that a customer makes one appointment for the sales department, and another appointment for the service department, that should be handled on the same day, but should be created as separate appointments, where the Technician must complete one appointment before starting the next, and that these two appointments are scheduled together and in sequence by enabling simultaneous scheduling of dependent service appointments, defining the order and timing of the service appointments, and ensuring that the service appointments are assigned to the same resource and scheduled on the same day[235]. Creating a dependency between the two appointments and setting the start times to be the same would not work because it would not ensure that one appointment is completed before starting the next. Adding the Complex Work Visualforce page to the Service Appointments page would not work because it is not a feature of Salesforce Field Service.

Reference: https://help.salesforce.com/s/articleView?id=sf.fs_settings_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_appointment_dependencies_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_appointment_dependencies_create_edit_delete.htm&type=5

Service Territory Location is a junction object that links Service Territory and Location objects[236]. Related Lists are components on page layouts that show records that are related to a record through a lookup or master-detail relationship[237]. Adding the Service Territory Location Related List on the Service Territory page layout and adding the Service Territory Location Related List on the Location page layout would allow Universal Containers to show how Locations are associated to Territories by displaying a list of Service Territory Locations on each record[238]. Creating the Service Territory Location as a Service Territory lookup field or creating the Service Territory Location as a Location lookup field would not work because they are not valid fields on either object.

Reference: https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_serviceterritorylocation.htm https://help.salesforce.com/s/articleView?id=sf.customize_related_lists.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_territory_locations_overview.htm&type=5