Newly Released Salesforce Field-Service-Consultant Exam PDF

A Service Appointment can be shared by clicking Sharing on the record if manual sharing is enabled in Field Service settings[51]. Auto-generated scheduled Service Appointments will be shared with resources if automatic sharing is enabled in Field Service settings[52]. The Service Appointment’s parent record can be shared with the assigned resource, but this would not affect the sharing of the Service Appointment itself. Making the dispatcher the assigned resource on the Service Appointments would not make sense if they are not performing field service tasks. References: & &type=5

This option allows applying different prices for the same product based on the customer agreement, and avoids duplicating products that have standard prices. &type=5

Crew Management is a feature that allows creating and managing crews of multiple service resources who share the same service appointments[163]. The Preferred Resource service objective is ignored for active Crew Members because it only applies to individual resources and not crews[164]. Capacity-based scheduling is not supported for Service Crews because crews do not have capacity limits and can be assigned unlimited service appointments[165]. A service resource can be a member of multiple crews and can switch between them depending on their availability and skills[166]. Salesforce Field Service does not consider the Recommended Crew Size when assigning appointments because it only considers the Required Crew Size which indicates the minimum number of crew members needed for a service appointment[167]. References: &type=5 &type=5 &type=5 id=sf.fs_service_crews_create_edit_delete.htm&

Global optimization is a process that reschedules all service appointments within a specified time frame based on predefined criteria such as travel time or priority[82]. Global optimization doesn’t reschedule appointments that have rule violations becauseit assumes that those appointments are manually scheduled by dispatchers for valid reasons[83]. There are no service resources available with the required skill levels because updating the skills required on the most common work types has increased the complexity of jobs and reduced the pool of qualified resources[84]. The optimizer uses a scheduling policy different from what is used on the dispatch console would not explain why the jobs are still scheduled to resources that lack the appropriate skill level. Scheduling policies are records that define the optimization criteria for scheduling service appointments such as minimizing travel time or maximizing resource utilization[85]. The territory of the resources was not included in the global optimizationrequest would not explain why the jobs are still scheduled to resources that lack the appropriate skill level. Global optimization requests are records that specify which service territories and time frames should be optimized[86]. References: &type=5 &type=5 &type=5 & &type=5