Field-Service-Consultant Practice Test

Explanation:

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

Explanation:

A custom lightning component that displays work order progress can be created using Lightning Web Components or Aura Components and deployed to technicians through the Field Service Mobile App using Mobile App Extensions. Adding the work order line items related list to the work order page layout would not show the work progress on the work order line-item card in the Field Service Mobile App. Creating a custom visual force page or a report chart would not be compatible with the Field Service Mobile App user interface.

References:

https://developer.salesforce.com/docs/componentlibrary/documentation/en/lwc

https://developer.salesforce.com/docs/atlas.enus.lightning.meta/lightning/

https://help.salesforce.com/s/articleView?id=sf.fs_mobile_app_extensions.htm&type=5

Explanation:

To perform multi-staged jobs, where the second job can only begin after completion of the first job, two service appointments can be created and linked by setting the Related Service Appointment field on the second service appointment to point to the first one, and setting the Time Dependency field to After Previous. Creating one service appointment with the total duration of the two jobs and assigning two resources would not ensure that the second job starts after the first one. Creating two service appointments and scheduling them to the same resource or creating one service appointment and scheduling it to two different resources would not create a dependency between the jobs.

References: https://help.salesforce.com/s/articleView?id=sf.fs_service_appointments.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_service_appointment_dependencies.htm &type=5

Explanation:

Drip Feed Dispatching is a feature that allows dispatching groups of service appointments to technicians at regular intervals instead of all at once[121]. Enabling Drip-feed to dispatch the next appointments would allow Northern Trail Outfitters to improve overall responsiveness to customers by providing the greatest schedule flexibility and allowing technicians to adjust their schedules based on real-time conditions[122]. Shuffling daily work manually via the Gantt would not provide the greatest schedule flexibility. The Gantt is a tool that allows dispatchers to view and manage service appointments on a timeline[123]. Leveraging Resource Schedule Optimization would not provide the greatest schedule flexibility.

Resource Schedule Optimization is a feature that allows optimizing service appointments based on predefined criteria such as travel time or priority[124]. Configuring the Auto Dispatch scheduled job would not provide the greatest schedule flexibility. Auto Dispatch is a feature that allows automatically assigning service appointments to resources based on predefined criteria such as skills or availability[125].

References:

https://help.salesforce.com/s/articleView?id=sf.fs_drip_feed_dispatching_overview.htm&typ e=5
https://help.salesforce.com/s/articleView?id=sf.fs_drip_feed_dispatching_enable.htm&type =5
https://help.salesforce.com/s/articleView?id=sf.fs_gantt_overview.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fs_resource_schedule_optimization_overvie w.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fs_auto_dispatch_overview.htm&type=5

Explanation:

These two configurations allow adding a new status to the existing status flow for Service Appointments, and defining which statuses can transition to or from the new status. References: https://help.salesforce.com/s/articleView?id=sf.fs_status_transitions.htm&type=5