Field-Service-Consultant Exam Dumps - Salesforce Field Service Lightning program Questions and Answers

These three considerations should be taken into account when implementing service level agreements for work orders, as they affect how milestones are created and applied to work orders. References: https://help.salesforce.com/s/articleView?id=sf.fs_milestones_for_work_orders_overview.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-Based Service 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=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_create_edit_delete.htm &type=5

These two conditions would make the optimizer run slower and leave many Service Appointments unscheduled, as it would have to evaluate too many possible scenarios and combinations. References: https://help.salesforce.com/s/articleView?id=sf.fs_optimizer_run_time.htm &type=5

Working Location Enable Primary is a setting on the Working Territories work rule that defines whether resources should be matched with service appointments based on their primary territory only or any territory they belong to[186]. Match Territory is a work rule that defines whether resources should be matched with service appointments based on their territories[187]. Selecting Working Location Enable Primary on the Working Territories Work Rule and including the Match Territory Work Rule would allow Universal Containers’ scheduling policy to look at both primary and secondary service territories by enabling matching resources with service appointments based on any territory they belong to and prioritizing matching resources with service appointments based on their territories. Removing the Match Territory Work Rule would not allow Universal Containers’ scheduling policy to look at both primary and secondary service territories because it would disable matching resources with service appointments based on their territories. Deselecting Working Location Enable Primary on the Working Territories Work Rule would not affect Universal Containers’ scheduling policy because it is already deselected by default. References: https://help.salesforce.com/s/articleView?id=sf.fs_scheduling_policies_work_rules_working_territories.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_scheduling_policies_work_rules_match_territory.htm &type=5

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/component-library/documentation/en/lwc https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/ https://help.salesforce.com/s/articleView?id=sf.fs_mobile_app_extensions.htm &type=5

These two options allow creating skills that represent qualifications and assigning them to service resources and work orders, and using a work rule to match skills when scheduling appointments. References: https://help.salesforce.com/s/articleView?id=sf.fs_skills.htm &type=5

These two applications allow viewing all of the absence records at once, as they support displaying related lists on objects such as service resources or service territories. References: https://help.salesforce.com/s/articleView?id=sf.fs_absences_overview.htm &type=5

This option allows automatically associating certain products to Work Orders based on the work type selected, and generating Work Order Line Items for those products. References: https://help.salesforce.com/s/articleView?id=sf.fs_work_types.htm &type=5

Field Sets allow controlling which fields are displayed on the Work Order and Service Appointment cards in the Salesforce Field Service mobile app. References: https://help.salesforce.com/s/articleView?id=sf.fs_mobile_fields.htm &type=5

 Work Order Line Items can be used to link to specific Assets within an Asset Hierarchy that represents a Bill of Materials (BoM). Work Order Line Items can also be used to create a hierarchy of tasks that need to be performed in a sequence. Standard Reports do not show Parent and Root Work Order Line Items within Work Orders by Customer. Work Order Line Items do not automatically inherit the hierarchy of Assets attached to Work Order. References: https://help.salesforce.com/s/articleView?id=sf.fs_asset_hierarchy.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_work_order_line_item_hierarchy.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_reports_dashboards.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_work_order_line_items.htm &type=5