Field-Service-Consultant Exam Dumps : Salesforce Certified Field Service Consultant (FS-Con-101)

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 creating a record to request products from another inventory location and adding product request line items for each product requested. &type=5

Articles are records that contain information or instructions about products, services, or processes[168]. Work Orders are records that track customer requests for service such as repairs or maintenance[169]. Writing a workflow that associates Articles to Work Orders based on a picklist on the Work Order would allow Universal Containers to ensure its Technicians can access Knowledge Articles offline by creating a workflow rule that triggers when a picklist value on the work order is selected and adds the relevant articlesto the work order related list[170]. Using Work Types to assign associated Articles to Work Orders would not work because Work Types are records that define the standard tasks and duration for a specific type of work and do not have a direct relationshipwith articles[171]. Using the Salesforce mobile app with deep linking to the Salesforce Field Service mobile app would not work because deep linking is a feature that allows launching one app from another app and does not affect offline access[172]. Creating a custom mobile app that syncs articles based on Service Appointment assignments would not work because it would require additional development and maintenance and would not leverage the existing Salesforce Field Service mobile app features[173]. References: &type=5 &type=5 & &type=5 & &type=5