Pass the Salesforce Field Service Lightning program Field-Service-Consultant Questions and answers with ExamsMirror

This option reflects the sharing rules for Service Appointments, which grant access to the assigned resources, the owner of the record, and the members of the service territory associated with the record. References:https://help.salesforce.com/s/articleView?id=sf.fs_sharing_rules.htm &type=5

Capacity-Based Service Resources are service resources that have a limited number of hours available for work per day or week[150]. Setting the Contractor Manager as a Capacity-BasedService Resource would allow Universal Containers to outsource 100 hours of weekly maintenance to an external Contractor by setting up criteria such as capacity hours per week equals 100 and capacity type equals weekly[151]. Creating the individual Technicians as Service Crew Members would not work because Service Crew Members are service resources that belong to a crew and share the same service appointments[152]. Setting the individual Technicians as Capacity-Based Service Resources would not work because Universal Containers does not have visibility into the individual external technicians. Creating the Contractor Manager as a Crew Service Resource would not work because Crew Service Resources are service resources that act as leaders or managers of a crew and can assign crew members to service appointments[153]. References: https://help.salesforce.com/s/articleView?id=sf.fs_service_resources_capacity_based.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_resources_capacity_based_create_edit.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_overview.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_create_edit_delete.htm &type=5

Field History Tracking on Assets allows tracking location and status changes in the lifecycle of a specific component in a customer’s install base by recording the date, time, nature, and user of each change. A Work Order related list on Assets would show the work orders associated with an asset, but not the location and status changes of the asset. A custom installation date field on Products Consumed would show when a product was installed,but not the subsequent changes in the asset lifecycle. A Product related list on Assets would show the products related to an asset, but not the location and status changes of the asset. References: https://help.salesforce.com/s/articleView?id=sf.tracking_field_history.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_work_orders.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_products_consumed.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_products.htm &type=5

This option allows generating a report in the customer’s language by selecting the language from a picklist field on the work order record. References:https://help.salesforce.com/s/articleView?id=sf.fs_service_reports_language.htm &type=5

Arrival Window Start and Arrival Window End are fields on the Service Appointment that indicate when a technician is expected to arrive at a customer site based on travel time and service duration calculations. These fields can be shared with customersto set expectations around upcoming appointments. Scheduled End and Scheduled Start are fields on the Service Appointment that indicate when a technician is scheduled to start and end their service based on their availability and assigned time slots. These fields are not accurate indicators of when a technician will arrive at a customer site, as they do not account for travel time and service duration variations. References:https://help.salesforce.com/s/articleView?id=sf.fs_service_appointments.htm &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: https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_limitations.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_limitations.htm &type=5 https://help.salesforce.com/s/articleView? id=sf.fs_service_crews_create_edit_delete.htm&type=5https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_serviceappointment_requiredcrewsize.htm

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 wouldallow 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”. References: https://help.salesforce.com/s/articleView?id=sf.fs_status_transitions_overview.htm &type=5https://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=5https://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 byrunning 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 workidentified 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. References: 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=5https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_batch_interface.htm