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

Polygons are geographic areas that define service territories for scheduling and optimization purposes. The Polygon Assignment Policy determines which polygon in a service territory hierarchy is used to assign service appointments to service resources based on their location or skills. Setting it to the Lowest Level ensures that service appointments are assigned based on the polygon of the child service territory in the hierarchy1. Setting it to the Highest Level would use the polygon of the parent service territory in the hierarchy1. TheTerritory Assignment Policy determines which territory in a hierarchy is used to filter available resources for scheduling. It does not affect polygon assignment. References: 1 https://help.salesforce.com/s/articleView?id=sf.fs_polygons_overview.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_territories_overview.htm &type=5

Creating a new Service Appointment on the original Work Order is the bestoption because it will allow Universal Containers to track the work that was done on the initial visit and the work that needs to be done on the return visit. Rescheduling the Service Appointment for the new date is also a good option because it will allowUniversal Containers to track the date and time of the return visit.

The other two options are not as good because they will not allow Universal Containers to track the work that was done on the initial visit. Creating a new Work Order and Service Appointment would create a new record for the return visit, which would not be linked to the original Work Order. Rescheduling the Work Order for the new date would reschedule the entire Work Order, including the initial visit, which would not be accurate.

Lightning Components are reusable units of user interface that can be customized and embedded in different pages or apps[180]. Work Order Line Items are records that track specific tasks or products related to a work order[181]. Creating a custom Lightning Component that displays Work Order progress and deploying it to Technicians through the Salesforce Field Service mobile app would allow Universal Containers’ Technicians to view work progress through the Work Order Line Item card in the Salesforce Field Service mobile app by creating a component that shows the status or completion percentage of work order line items and adding it to the work order line item card layout in the mobile app settings[182]. Creating a custom Visualforce page and adding an external link in the Salesforce Field Service mobile app to view the page in the mobile browser would not allow Technicians to view work progress through the Work Order Line Item cardin the Salesforce Field Service mobile app. Visualforce pages are web pages that can display custom user interface using HTML, CSS, JavaScript, and Apex[183]. Creating a Report Chart that summarizes Work Order Line Items and adding a link to the Service Appointment layout would not allow Technicians to view work progress through the Work Order Line Item card in the Salesforce Field Service mobile app. Report Charts are visual representations of report data that can be added to different pages or layouts[184]. Adding the Work Order Line Items related list to the Work Order page layout and assigning the layout to the Technician’s profile would not allow Technicians to view work progress through the Work Order Line Item card in the Salesforce Field Service mobile app. Related lists are lists of records that are directly related to another record and can be added to different page layouts[185]. References: https://developer.salesforce.com/docs/component-library/overview/components https://help.salesforce.com/s/articleView?id=sf.fs_work_order_line_items.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_mobile_custom_cards_overview.htm &type=5 https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/pages_intro_what_is_it.htm https://help.salesforce.com/s/articleView?id=sf.reports_charts_adding_to_layouts.htm &type=5https://help.salesforce.com/s/articleView?id=sf.customize_related_lists.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

Scheduling, dispatching, and knowledge base are three field service processes that can help reduce the mean-time-to-service. Scheduling is the process of assigning service appointments to resources based on their availability, skills, and location. Dispatching is the process of sending service appointments to resources and tracking their status and location. Knowledge base is a repository of articles that provide information and solutions for common issues and questions.

Service Resources are records that represent the people or equipment that perform field service tasks[53]. Permission Set Licenses are licenses that grant users access to specific features such as Field Service Dispatcher Console or Field Service Mobile App[54]. Creating one service resource and assigning the relevant permission set license would allow an employee at Universal Containers to perform both dispatcher and technician roles using one record and one license. Creating two skills records and assigning them to service resources record would not affect their roles or accessto features. Skills are records that define specific abilities or qualifications that service resources have[55]. Creating two service resources and assigning them to the employee would create duplicate records and require two licenses for one employee. Creating one service resource and assigning the technician and dispatcher role would not work because roles are not fields on the service resource object. References: https://help.salesforce.com/s/articleView?id=sf.fs_service_resources_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_permission_set_licenses_overview.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_skills_overview.htm &type=5

This option should be recommended to implement this process, as it allows scheduling two technicians to complete a job at different times by creating two separate service appointments and assigning them to different resources. References:https://help.salesforce.com/s/articleView?id=sf.fs_service_appointments.htm &type=5

Reshuffle allows the dispatcher to automatically reschedule service appointments for a specific date range based on the current schedule and optimization rules1. In-day Optimization allows the dispatcher to optimize the schedule for a specific resource or territory based on real-time events such as cancellations or delays2. References: 1 https://help.salesforce.com/s/articleView?id=sf.fs_reshuffle.htm &type=5 2 https://help.salesforce.com/s/articleView?id=sf.fs_in_day_optimization.htm &type=5

Assets are records that represent products or equipment that customers have purchased or installed[174]. Related Assets are records that track the relationships between assets such as parent-child or swap[175]. Product Requests are records that track the products or parts that are requested, transferred, or returned for a service appointment[176]. Adding the Related Asset related list to the Asset Page and configuring the Product Request object would allow Universal Containers to track the Asset lifecycle when equipment has been swapped out by creating related asset records forswapped assets and creating product request records for transferring or returning assets[177]. Adding the field history tracking related list to the Asset Page would not track the Asset lifecycle when equipment has been swapped out. Field history trackingis a feature that allows tracking changes to specific fields on an object over time[178]. Configuring the Asset Relationship object would not track the Asset lifecycle when equipment has been swapped out. Asset Relationship is an object that defines the types of relationships between assets such as parent-child or swap[179].References: https://help.salesforce.com/s/articleView?id=sf.asset.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_related_assets_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_product_requests_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_related_assets_swap.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.field_history_tracking.htm &type=5https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_assetrelationship.htm