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

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/a rticleView?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.sales force.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

To make custom actions visible in the Field Service mobile app,they need to be added to both the Classic Publisher Quick Actions section and the Mobile and Lightning Actions section on the page layout.

References: https://help.salesforce.com/s/articleView?id=sf.fsl_mobile_actions.htm &type=5

This work rule should be used to assign service resourcesbased on related object records, such as accounts or assets, by matching field values between objects. References:https://help.salesforce.com/s/articleVi ew?id=sf.fs_work_rules_match_field.htm&type=5

Capacity-based scheduling is a feature that allows the system to schedule service appointments based on the capacity of the resources. This feature is supported for service crews, which are groups of resources that worktogether on service appointments.

These are three factors that should be considered when configuring routing. Routing is the process of finding the best resource for a service appointment based on variouscriteria and constraints. A schedule policy is used to define the routing preferences and rules for a service territory or operating hours. A work rule is used to define a scheduling constraint or preference for a service appointment or a resource. A service objective is used to define a scheduling goal or metric for a service appointment. The Resource Availability work rule is used to calculate travel time and breaks as part of the resource’s availability. The Default Travel Speed is used to estimate thetravel time between locations if a different travel speed is not specified for the resource.

Service reports are documents that summarize the details and outcomes of a service appointment such as work performed, products consumed, customer feedback, etc.[25]. Configuring signature blocks for service report templatesallows capturing customer signatures as proof of job completion before generating invoices[26]. Adding service report templates to the appropriate repair work type allows automatically generating service reports based on the work type of the service appointment[27]. Generating service in the organization’s default language would not verify that a repair job has been completed to the customer satisfaction. Sending a feedback survey to the customer when a service appointment is completed would not ensure thatan invoice can be generated. References: https://help.salesforce.com/s/articleView?id=sf.fs_service_reports_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_reports_signature_blocks.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_service_reports_work_types.htm &type=5

Skills are records that define specific abilities orqualifications that service resources have[158].Skill Levels are fields on the skill object that indicate the proficiency or experience of a service resource in a skill[159]. Assigning Contractor 1 and 2 different Skill Levels for repair Work Type would allow Universal Containers to configure the Contractors’ experience by setting up criteria such as skill name equals repair and skill level equals high for Contractor 1 and low for Contractor 2. Assigning Contractor 1 as a Preferred Resource would not configure the Contractors’ experience. Preferred Resources are optimization criteria that prioritize assigning service appointments to resources who have previously completed similar work orders or who are preferred by customers[160]. Assigning Contractor 1 and2 different capacities for repair work would not configure the Contractors’ experience. Capacities are fields on the service resource object that indicate the number of hours available for work per day or week[161]. Assigning Contractor 2 as an Excluded Resource would not configure the Contractors’ experience. Excluded Resources are optimization criteria that prevent assigning service appointments to resources who are explicitly excluded by customers or dispatchers[162]. References: https://help.salesforce.com/s/articleView?id=sf.fs_skills_overview.htm &type=5 https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_skill_skilllevel.htm https://help.salesforce.com/s/articleView?id=sf.fs_scheduling_policies_optimization_criteria_preferred_resources.htm &type=5 https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_serviceresource_capacityhoursperday.htmhttps://help.salesforce.com/s/articleView?id=sf.fs_scheduling_policies_optimization_criteria_excluded_resources.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 workperformed 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

 A quick action is used to create a record from another recordwith predefined field values. By defining a quick action to create a work order from a case, the agent can easily create a work order for on-site support after verifying the customer’s entitlement and product.

Earliest Start Permitted is a field on the Service Appointment object that defines the earliest date and time that a service appointment can start[222]. Due Date is a field on the Service Appointment object that defines the latest date and time that a service appointment must be completed by[223]. Using Earliest Start Permitted and Due Date fields on Service Appointments would help ensure that they are completed within the agreed upon Service Level Agreement (SLA) with Universal Containers’ customers by setting the boundaries for when a service appointment can start and finish according to the SLA terms[224]. Actual Start andActual End are fields on the Service Appointment object that capture the actual date and time that a service appointment started and ended[225]. Using Actual Start and Actual End fields on Service Appointments would not help ensure that they are completedwithin the agreed upon SLA with Universal Containers’ customers because they are recorded after the service appointment is performed and do not enforce any SLA terms. Arrival Window Start and Arrival Window End are fields on the Service Appointment objectthat define the expected date and time range that a resource will arrive at a service appointment[226]. Using Arrival Window Start and Arrival Window End fields on Service Appointments would not help ensure that they are completed within the agreed upon SLA with Universal Containers’ customers because they only indicate when a resource will arrive and do not enforce any SLA terms. Scheduled Start and Scheduled End are fields on the Service Appointment object that define the planned date and time range thata service appointment will take place[227]. Using Scheduled Start and Scheduled End fields on Service Appointments would not help ensure that they are completed within the agreed upon SLA with Universal Containers’ customers because they only indicate whena service appointment is scheduled and do not enforce any SLA terms. References: https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_serviceappointment.htmhttps://help.salesforce.com/s/articleView?id=sf.fs_sla_overview.htm &type=5