Field-Service-Consultant Exam Dumps - Salesforce Certified Field Service Consultant (SP23)

The asset relationships object is used to track when equipment has been swapped out by creating parent-child relationships between assets. Adding the related asset related list to the asset page allows viewing and creating asset relationships from an asset record. Adding the field history tracking related list to the asset page would track field changes on an asset, but not asset relationships. Adding the product request related list to the asset page would allow requesting products from inventory for an asset, but not tracking asset relationships. References: https://help.salesforce.com/s/articleView?id=sf.fs_asset_relationships_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_asset_relationships_create.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.tracking_field_history.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_product_requests.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

Work Types are templates that define the duration, skills, and products required for a work order or work order line item. By creating Work Types with Products Required, agents and dispatchers can quickly create Work Orders with the appropriate materials. Creating Work Types with Products Consumed or Products Required would not populate products on Work Orders automatically, but would require manual entry or consumption by technicians. Creating Work Types and Locations would not affect products on Work Orders, but would affect scheduling and optimization of service appointments. References: https://help.salesforce.com/s/articleView?id=sf.fs_work_types.htm &type=5

Use all-or-none scheduling for related appointments is a setting in Field Service Settings that enables or disables the simultaneous scheduling of service appointments that have dependencies[232]. Dependency Type is a field on the Service Appointment object that defines the relationship between two service appointments such as Start After Finish, Start Before Finish, or Finish Before Start[233]. Same Resource and Same Day are fields on the Service Appointment object that indicate whether two service appointments with dependencies should be assigned to the same resource and scheduled on the same day[234]. Selecting the checkbox Use all-or-none scheduling for related appointments in Field Service Settings, setting the Dependency Type to Start After Finish and Same Day on the first service appointment in the dependency, and making sure the Same Resource and Same Day fields appear on the Service Appointments page layout would allow Universal Containers to ensure that a customer makes one appointment for the sales department, and another appointment for the service department, that should be handled on the same day, but should be created as separate appointments, where the Technician must complete one appointment before starting the next, and that these two appointments are scheduled together and in sequence by enabling simultaneous scheduling of dependent service appointments, defining the order and timing of the service appointments, and ensuring that the service appointments are assigned to the same resource and scheduled on the same day[235]. Creating a dependency between the two appointments and setting the start times to be the same would not work because it would not ensure that one appointment is completed before starting the next. Adding the Complex Work Visualforce page to the Service Appointments page would not work because it is not a feature of Salesforce Field Service. References: https://help.salesforce.com/s/articleView?id=sf.fs_settings_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_appointment_dependencies_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_appointment_dependencies_create_edit_delete.htm &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 articles to 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 relationship with 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: https://help.salesforce.com/s/articleView?id=sf.knowledge_article_types.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_work_orders_knowledge_articles.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_work_types_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_mobile_deep_linking.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_mobile_overview.htm &type=5

Pinned statuses prevent service appointments from being rescheduled or unscheduled by scheduling and optimization services3. Status transitions define the valid status changes for service appointments based on business rules. References: 3 https://help.salesforce.com/s/articleView?id=sf.fs_pinned_statuses.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_status_transitions.htm &type=5

This option should be recommended to meet this requirement, as it allows creating a service resource that represents a group of technicians who work together on the same service appointment. References: https://help.salesforce.com/s/articleView?id=sf.fs_crew_management.htm &type=5

Service Territory Location is a junction object that links Service Territory and Location objects[236]. Related Lists are components on page layouts that show records that are related to a record through a lookup or master-detail relationship[237]. Adding the Service Territory Location Related List on the Service Territory page layout and adding the Service Territory Location Related List on the Location page layout would allow Universal Containers to show how Locations are associated to Territories by displaying a list of Service Territory Locations on each record[238]. Creating the Service Territory Location as a Service Territory lookup field or creating the Service Territory Location as a Location lookup field would not work because they are not valid fields on either object. References: https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_serviceterritorylocation.htm https://help.salesforce.com/s/articleView?id=sf.customize_related_lists.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_territory_locations_overview.htm &type=5

This configuration can be used to brand the Salesforce Field Service mobile app by uploading a custom logo image that appears on the app’s login screen and navigation bar. References: https://help.salesforce.com/s/articleView?id=sf.fs_mobile_branding.htm &type=5

Sort by Average Utilization is an option on the Resources Tab of the Gantt chart that allows sorting resources by their average utilization percentage[239]. Utilization is a metric that measures how much time a resource spends on service appointments compared to their total working hours[240]. Selecting Sort by Average Utilization on the Resources Tab would allow Universal Containers to identify which resources need more or fewer appointments by showing them how busy each resource is based on their utilization percentage[241]. Selecting Date Resolution on the Hours Tab would not allow Universal Containers to identify which resources need more or fewer appointments. Date Resolution is an option on the Hours Tab of the Gantt chart that allows changing how many hours are shown per column such as 1 hour, 2 hours, or 4 hours[242]. Selecting Travel Time and Breaks as skills on the Skills Tab would not allow Universal Containers to identify which resources need more or fewer appointments. Skills are records that define specific abilities or qualifications that resources have[243]. Travel Time and Breaks are not skills but fields on the Resource object that define how much time a resource spends traveling between service appointments and how much time they take for breaks[244]. Selecting Hours, Absences and Overtime on

Match Fields work rules are rules that restrict travel distance between home location and first appointment location for resources[64]. Including a Match Fields work rule would allow limiting contractors to travel a maximum of 50 minutes from home by setting up criteria such as travel distance less than or equal to 50 minutes between home location field and first appointment location field[65]. Linking rules to Relevance Groups would not limit travel distance between home location and first appointment location for resources. Relevance Groups are groups of rules that apply only to specific types of services such as emergency or preventive maintenance[66]. Assigning a high efficiency score would not limit travel distance between home location and first appointment location for resources. Efficiency score is a metric that measures how well resources use their working hours based on factors

This option allows capturing the required information on the work order and updating the related case and service appointment records using a flow. References: https://help.salesforce.com/s/articleView?id=sf.fs_mobile_quick_actions.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

This option allows applying different prices for the same product based on the customer agreement, and avoids duplicating products that have standard prices. References: https://help.salesforce.com/s/articleView?id=sf.fs_price_books.htm &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. References: https://help.salesforce.com/s/articleView?id=sf.fs_price_books.htm &type=5

This configuration can be used to brand the Salesforce Field Service mobile app by uploading a custom logo image that appears on the app’s login screen and navigation bar. References: https://help.salesforce.com/s/articleView?id=sf.fs_mobile_branding.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