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

Field History Tracking on Assets allows tracking location and status changes in the lifecycle of a specific component in a customer’s install base by recording the date, time, nature, and user of each change. A Work Order related list on Assets would show the work orders associated with an asset, but not the location and status changes of the asset. A custom installation date field on Products Consumed would show when a product was installed, but not the subsequent changes in the asset lifecycle. A Product related list on Assets would show the products related to an asset, but not the location and status changes of the asset. References: https://help.salesforce.com/s/articleView?id=sf.tracking_field_history.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.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_products.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

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

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

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

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

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 viewing the asset relationships on the Asset object, where the primary asset is the parent asset and the related assets are the child assets. References: https://help.salesforce.com/s/articleView?id=sf.fs_asset_relationships.htm &type=5

Time sheet entries are records that track the time spent by a service resource on a work order or a work order line item[28]. Time sheet entries can be associated to work order line items or work orders using lookup fields[29]. Assigned resources are records that assign a service resource to a service appointment[30]. Service resources are records that represent the people or equipment that perform field service tasks[31]. Time sheet entries cannot be associated to assigned resources or service resources directly. References: https://help.salesforce.com/s/articleView?id=sf.fs_time_sheets_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_time_sheet_entries_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_assigned_resources_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_resources_overview.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 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

These two options allow creating skills that represent qualifications and assigning them to service resources and work orders, and using a work rule to match skills when scheduling appointments. References: https://help.salesforce.com/s/articleView?id=sf.fs_skills.htm &type=5

This option reflects the sharing rules for Service Appointments, which grant access to the assigned resources, the owner of the record, and the members of the service territory associated with the record. References: https://help.salesforce.com/s/articleView?id=sf.fs_sharing_rules.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

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 access to 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=5 https://help.salesforce.com/s/articleView?id=sf.fs_skills_overview.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

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