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

This option allows tracking the work performed for each asset separately and associating it with a work order and a service appointment. References: https://help.salesforce.com/s/articleView?id=sf.fs_work_order_line_items.htm &type=5

User Territories are records that associate users with service territories for sharing purposes[90]. Creating a new user territory associated with the Service Territory and dispatcher would allow giving access to all relevant Midwest records by linking them with their corresponding service territory[91]. Configuring and running the User Territory Sharing Job in Field Service Settings would allow updating sharing rules based on user territories automatically at regular intervals such as daily or weekly[92]. Assigning a new user territory and adding each of the assigned service resources would not give access to all relevant Midwest records

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 card in 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=5 https://help.salesforce.com/s/articleView?id=sf.customize_related_lists.htm &type=5

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

Multi-day service appointments are used when jobs can take longer than the available resources hours in a day or require consecutive days of work and can span over weekends. Jobs that need to be performed at the same site on the same day of the week or require multiple stages of work performed by different resources can be handled by single-day service appointments with appropriate scheduling policies and optimization rules. References: https://help.salesforce.com/s/articleView?id=sf.fs_multiday_service_appointments_overview.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

Reshuffle is an action within the Gantt that allows rescheduling multiple service appointments at once based on predefined criteria such as emergency priority, travel time, or skills[209]. Reshuffle would allow Universal Containers to dispatch emergency work identified throughout the day that needs to be completed before lower-priority work by running a reshuffle action that prioritizes emergency work and assigns it to the best available resources[210]. Defining a Global Optimization job to run hourly would not allow Universal Containers to dispatch emergency work identified throughout the day that needs to be completed before lower-priority work. Global Optimization is a feature that allows rescheduling multiple service appointments at once based on predefined criteria such as emergency priority, travel time, or skills[211]. Running a Global Optimization job hourly would not be responsive enough for emergency work identified throughout the day. Creating a custom Gantt action to call an Apex class to reschedule appointments would not be necessary for Universal Containers to dispatch emergency work identified throughout the day that needs to be completed before lower-priority work. Custom Gantt actions are actions within the Gantt that can be customized using Apex code to perform specific tasks such as sending notifications or updating fields[212]. Creating a custom Gantt action would require additional development and maintenance and would not leverage the existing Reshuffle action. Writing a batch Apex class to unschedule low priority work orders would not allow Universal Containers to dispatch emergency work identified throughout the day that needs to be completed before lower-priority work. Batch Apex is a way of processing large volumes of data asynchronously using Apex code[213]. Writing a batch Apex class would require additional development and maintenance and would not leverage the existing Reshuffle action. References: https://help.salesforce.com/s/articleView?id=sf.fs_gantt_reshuffle_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_gantt_reshuffle_run.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_optimization_global_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_gantt_custom_actions_overview.htm &type=5 https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_batch_interface.htm

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 ensures that the service territory member’s operating hours are aligned with the service territory’s time zone, and avoids scheduling conflicts or gaps. References: https://help.salesforce.com/s/articleView?id=sf.fs_operating_hours.htm &type=5

Maintenance Plans are records that define recurring work orders for preventive maintenance such as inspections or tune-ups[188]. Auto-generate Work Orders is a setting that enables or disables the automatic generation of work orders from maintenance plans[189]. Generation Timeframe is a setting that defines how often work orders should be generated from maintenance plans such as daily, weekly, or monthly[190]. Generation Horizon is a setting that defines how far in advance work orders should be generated from maintenance plans such as 7 days or 30 days[191]. Auto-generating Work Orders with a 14 day Generation Timeframe and a 14 day Generation Horizon would allow Universal Containers to automatically generate Work Orders 14 days before the next suggested maintenance date by creating work orders from maintenance plans every 14 days within 14 days of their scheduled date. Associating a Required Skill called Site Visit to a Maintenance Plan would not affect how far in advance work orders are generated from maintenance plans. Required Skills are fields on the maintenance plan object that indicate which skills are needed for performing preventive maintenance[192]. Associating a Work Type called Site Visit to a Maintenance Plan would not affect how far in advance work orders are generated from maintenance plans. Work Types are records that define the standard tasks and duration for a specific type of work[193]. References: https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_auto_generate_work_orders.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_generation_timeframe.htm