Field-Service-Consultant Salesforce Certified Field Service Consultant (SP23) Questions and Answers

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 Orders are records that track customer requests for service such as repairs or maintenance[47]. Work Order Line Items are records that track specific tasks or products related to a work order[48]. Service Appointments are records that track the date, time, duration, and assigned resource for a work order or work order line item[49]. Adding each Asset to a separate Work Order Line Item or a separate Work Order would allow handling the service associated with each container independently by creating different records for different containers. Creating a Service Appointment for each Line Item or each Work Order would allow scheduling and dispatching the service associated with each container independently by assigning different resources and time slots for different containers. Adding each Asset to a separate child Work Order would create an unnecessary hierarchy of Work Orders that could complicate reporting and scheduling. Creating a Service Appointment for the parent Work Order would not allow handling the service associated with each container independently by assigning one resource and time slot for all containers. References: https://help.salesforce.com/s/articleView?id=sf.fs_work_orders.htm &type=5 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_service_appointments.htm &type=5

This option should be recommended to control the technicians’ view of work orders and appointments in the field service lightning mobile app, as it allows customizing which fields are displayed on different screens of the app. References: https://help.salesforce.com/s/articleView?id=sf.fs_mobile_field_sets.htm &type=5

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

Service Resources are records that represent the people or equipment that perform field service tasks[143]. Work Orders are records that track customer requests for service such as repairs or maintenance[144]. Resource Absences are records that mark resources as unavailable for work for specific time periods due to sickness, vacation, or other reasons[145]. If the Field Service Lightning User Territory feature is enabled, these three objects will be visible to users who are part of the User Territory by default[146]. Accounts are records that represent companies or individuals involved in business with an organization[147]. Work Types are records that define the standard tasks and duration for a specific type of work[148]. These two objects will not be visible to users who are part of the User Territory by default unless sharing rules are configured[149]. 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_work_orders.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_resource_absences_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_user_territories_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.account.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_user_territories_sharing_rules.htm &type=5

Operating Hours define when service resources are available for work and when customers can book appointments. The Time Slots for Appointment Booking setting determines how operating hours are divided into time slots that can be assigned to service appointments. The Maintenance Plan for the Account or the Due Date of the Service Appointment do not affect operating hours, but are used to generate and schedule recurring work orders. References: https://help.salesforce.com/s/articleView?id=sf.fs_operating_hours.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans.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 and Skill Requirements for Install, Break-fix, and Inspections, Universal Containers can standardize creation of Work Orders with the correct skills and estimated time to completion. Work Order Record Types for Break-fix, Install, and Inspection would allow creating different page layouts and picklist values for different types of work orders, but not define skills and duration. Work Type Line Items for Install, Break-fix, and Inspections would allow creating templates for work order line items, but not work orders. Work Order custom fields to define Install, Break-fix, and Inspections would allow capturing additional information for different types of work orders, but not define skills and duration. References: https://help.salesforce.com/s/articleView?id=sf.fs_work_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_order_line_items.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

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 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

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

Service Appointments are records that track the date, time, duration, and assigned resource for a work order or work order line item[117]. Creating a new Service Appointment for each site visit would allow Universal Containers to track when Technicians need to visit a customer site multiple times to resolve an issue by creating different service appointments for the same work order and capturing notes and status updates for each service appointment. Creating a new Child Work Order for each site visit would create unnecessary records and complexity. Child Work Orders are work orders that are related to another work order as part of a hierarchy[118]. Creating a new Product Consumed for each site visit would not track the site visits. Products Consumed are records that track the products or parts that are used or installed during a service appointment[119]. Creating a new Work Order Line Item for each site visit would not track the site visits. Work Order Line Items are records that track specific tasks or products related to a work order[120]. References: https://help.salesforce.com/s/articleView?id=sf.fs_service_appointments.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_products_consumed_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_work_order_line_items.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

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

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

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

These two scenarios are fully supported by Maintenance Plans, which allow creating recurring work orders and service appointments based on various criteria. References: https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans_overview.htm &type=5