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

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

Arrival Window Start and Arrival Window End are fields on the Service Appointment that indicate when a technician is expected to arrive at a customer site based on travel time and service duration calculations. These fields can be shared with customersto set expectations around upcoming appointments. Scheduled End and Scheduled Start are fields on the Service Appointment that indicate when a technician is scheduled to start and end their service based on their availability and assigned time slots. These fields are not accurate indicators of when a technician will arrive at a customer site, as they do not account for travel time and service duration variations. References: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

hese two configurations allow adding a new status to the existing status flow for Service Appointments, and defining which statuses can transition to or from the new status. References:https://help.salesforce.com/s/articleView?id=sf.fs_status_transitions.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.

Customer Entitlements are records that specify customers’ support terms based on their contracts or warranties[38]. Customer Entitlements can be used to offer appropriate appointment booking windows for Gold versus Standard Customers by defining different appointment windows for different entitlement levels[39]. Service Due Date is a field on the work order object that indicates when a work order must be completed by[40]. Customer Working Hours are records that define when customers are available for service appointments[41]. Service Urgency is a field on the work order object that indicates how quickly a work order must be completed[42]. References: https://help.salesforce.com/s/articleView?id=sf.entitlements_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_appointment_windows_entitlements.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_work_orders_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_customer_working_hours_overview.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_work_orders_fields.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 Jobin 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

Frequency is a field on the Maintenance Plan objectthat defines how often work orders should be generated from maintenance plans such as daily, weekly, or monthly[228]. Generation Timeframe is a field on the Maintenance Plan object that defines how many work orders should be generated from maintenance plans at a time such as 1, 2, or 12[229]. Auto-generate work orders is a field on the Maintenance Plan object that enables or disables the automatic generation of work orders from maintenance plans[230]. Setting Frequency to 1 Month; Generation Timeframe of 12; uncheck Auto-generate work orders would allow Universal Containers to offer customers a MaintenancePlan that provides 12 monthly checkups where the customer will call to schedule each visit by creating maintenance plans that generate one work order permonth for 12 months but do not generate them automatically until the customer calls[231]. Setting Frequency to 1 Month; Generation Timeframe of 1; check Auto-generate work orders would not allow Universal Containers to offer customers a Maintenance Plan that provides 12 monthly checkups where the customer will call to schedule each visit. It would create maintenance plans that generate one work order per month for one month and generate them automatically without waiting for customer calls. Setting Frequency to 1 Month; Generation Timeframe of 12; check Auto-generate work orders would not allow Universal Containers to offer customers a Maintenance Plan that provides 12 monthly checkups where the customer will call to schedule each visit. It would create maintenance plans that generate one work order per month for 12 months and generate them automatically without waiting for customer calls. Setting Frequency to 1 Month; Generation Timeframe of 1; uncheck Auto-generate work orders would not allow Universal Container

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

Service Reports aredocuments that summarize the details and outcomes of a service appointment such as work performed, products consumed, customer feedback, etc.[72]. Using the standard Service Report would allow Field Service Technicians to capture details and customer approval on completed work and send them to the customer electronically by generating and emailing service reports from the Field Service Mobile App or the web browser[73]. Creating a Process Builder to generate a report would not allow Field Service Technicians to capture details and customer approval on completed work. Process Builder is a tool that allows users to automate workflows based on specified criteria and actions[74]. Creating a custom report would not allow Field Service Technicians to capture details and customer approval on completed work. Custom reports are reports that allow users to view data based on specific criteria such as objects, fields, filters, or charts[75]. Using the standard Work Order email template would not allow Field Service Technicians to capture details and customer approval on completed work. Email templates are templates that allow users to send predefined emails with merge fields[76]. 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_generate.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.process_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.reports_builder_overview.htm &type=5https://help.salesforce.com/s/articleView?id=sf.email_templates_overview.htm &type=5

Customgantt filters are filters that allow dispatchers to view service appointments based on specific criteria such as status, priority, or custom fields[67]. Creating a custom gantt filter would allow providing a view of emergency work that is only visible to dispatchers by setting up criteria such as status equals emergency and sharing the filter with dispatchers only[68]. Custom lightning component is a component that allows developers to create custom user interfaces using Lightning Web Components or Aura Components[69]. Creating a custom lightning component would require coding and would not leverage the existing gantt chart functionality. Custom report in a private report folder is a report that allows users to view data based on specific criteria such as objects, fields, filters, or charts[70]. Creating a custom report in a private report folder would not provide a view of emergency work on the gantt chart and would not allow dispatchers to schedule or reschedule service appointments. Custom list view is a list view that allows users to view records based on specific criteria such as filters, fields, or sorting[71]. Creating a custom list view would not provide a view of emergency work on the gantt chart and would not allow dispatchers toschedule or reschedule service appointments. References: https://help.salesforce.com/s/articleView?id=sf.fs_gantt_filters.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_gantt_filters_create.htm &type=5 https://developer.salesforce.com/docs/component-library/documentation/en/lwc https://help.salesforce.com/s/articleView?id=sf.reports_builder_overview.htm &type=5https://help.salesforce.com/s/articleView?id=sf.customize_listviews.htm &type=5

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.

The book appointment action is used to schedule a service appointment based on service objectives and resource availability. Theaction displays a list of potential time slots with service objective scores for each slot. The higher the score, the better the slot meets the service objectives.

Contractors are external users who can access Field Service features such as work orders, service appointments, assets, products consumed, etc… There are two types of contractor licenses available: Contractor (Full Access) and Contractor (Limited Access). Contractor (Full Access) licenses allow users to access all Field Service features except scheduling optimization. Contractor (Limited Access) licenses allow users to access only work orders assigned to them or their crew members via mobile appor web browser[22. Universal Containers should deploy 25 Contractor (Full Access) licenses to contractors who need to schedule resources and 75 Contractor (Limited Access) licenses to contractors who need access to work orders, assets, mobile app, and chatter. References: https://help.salesforce.com/s/articleView?id=sf.field_service_contractors_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.field_service_contractors_license_types.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.field_service_contractors_full_access_license_features.htm &type=5https://help.salesforce.com/s/articleView?id=sf.field_service_contractors_limited_access_license_features.htm &type=5

This option allows the Resource Skill to expire when the certification expires, and prevents the resource from being scheduled for jobs that require that skill. References:https://help.salesforce.com/s/articleView?id=sf.fs_resource_skills.htm &type=5

Serialized inventory allows tracking individual product items by serial number, which is useful for traceability from factory to customer sites. Unsterilized inventory allows tracking product quantities without serialnumbers, which is suitable for disposable kits that are not reused or returned. Creating both products and kits as serialized or unsterilized inventory would not meet the requirement of traceability for products and disposability for kits. References: https://help.salesforce.com/s/articleView?id=sf.fs_serialized_inventory_overview.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_unserialized_inventory_overview.htm &type=5

Work types are used to define the standard duration and skills required for a specific type of work. By creating work types for similarsite visits, the creation of work orders can be streamlined and standardized.

This option allows capturing multiple signatures on a service report by creating different signature types (such as customer approval or technician verification) and adding themto the service report template. References:https://help.salesforce.com/s/articleView?id=sf.fs_signature_types.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 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

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

The Exclude Technician from Geolocation Tracking permission allows disabling geolocation tracking for specific service resources by assigning them a permission set with this permission. Setting the Geolocation Update Frequency field tozero for contractors would not disable geolocation tracking, but would make it update less frequently. Unchecking the Geocoding field on the Contractor’s profile or the Collect Service Resource Geolocation History field in Field Service Mobile Settings would not affect geolocation tracking, as these are not related settings. References: https://help.salesforce.com/s/articleView?id=sf.fs_geolocation_tracking_permissions.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_geolocation_tracking_settings.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

These two ways should be recommended to track these inventory requirements in Salesforce, as they allow specifying which products are needed for work orders or work order line items and updating the inventory accordingly. References:https://help.salesforce.com/s/articleView?id=sf.fs_products_required.htm &type=5

To perform multi-staged jobs, where the second job can only begin after completion of the first job, two service appointments can be created and linked by setting the Related Service Appointment field on the second service appointment to point to the first one, and setting the Time Dependency field to After Previous. Creating one service appointment with the total duration of the two jobs and assigning two resources would not ensure that the second job starts after the first one. Creating two service appointments and scheduling them to the same resource or creating one service appointment and scheduling it to twodifferent resources would not create a dependency between the jobs. References: https://help.salesforce.com/s/articleView?id=sf.fs_service_appointments.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_service_appointment_dependencies.htm &type=5

This option allows handling unplanned service during times of severe weather by creating a policy that overrides the existing scheduling policy and using a wizard to reschedule service appointments based on the emergency policy. References:https://help.salesforce.com/s/articleView?id=sf.fs_emergency_wizard.htm &type=5

This object can be used to share service appointments with service resources in Salesforce Field Service by assigning service resources to service territories and assigning service appointments to the same service territories. References:https://help.salesforce.com/s/articleView?id=sf.fs_service_territories.htm &type=5

This option allows creating a record to request products from another inventory location and adding product request line items for each product requested. References:https://help.salesforce.com/s/articleView?id=sf.fs_product_requests_overview.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 generateand schedule recurring work orders. References: https://help.salesforce.com/s/articleView?id=sf.fs_operating_hours.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_maintenance_plans.htm &type=5

This option allows creating a service resource that represents a group oftechnicians who work together on the same service appointment. References:https://help.salesforce.com/s/articleView?id=sf.fs_crew_management.htm &type=5

The Products Consumed section on the Work Order allows the technician to record the products used and adjust the inventory levels of their van stock. The Product Item Transactions Related Liston the Product Item shows the history of product movements, but does not allow recording new transactions. The Work Order Line Item associated with the completed Work Order shows the products required, but not the products used. The Product Request Line Item associated with the Product shows the products requested, but not the products consumed. References: https://help.salesforce.com/s/articleView?id=sf.fs_products_consumed.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_product_item_transactions.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_work_order_line_items.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_product_request_line_items.htm &type=5

Drip feed is a feature that automatically dispatches service appointments to resources based on predefined criteria and time intervals. By enabling drip feed, the system can dispatch one service appointment per technician at a time, and adjust their schedule accordingly.

A Service Appointment can be shared by clicking Sharing on the record if manual sharing is enabled in Field Service settings[51]. Auto-generated scheduled Service Appointments will be shared with resources if automatic sharing is enabled in Field Service settings[52]. The Service Appointment’s parent record can be shared with the assigned resource, but this would not affect the sharing of the Service Appointment itself. Making the dispatcher the assigned resource on the Service Appointments would not make sense if they are not performing field service tasks. References: https://help.salesforce.com/s/articleView?id=sf.fs_sharing_manual.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_sharing_automatic.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 Assetto 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=5https://help.salesforce.com/s/articleView?id=sf.fs_service_appointments.htm &type=5

Sort by Average Utilization is an option on the Resources Tab of the Gantt chart that allows sorting resources by their average utilization percentage[239]. Utilization is a metric that measures how much time a resource spends on service appointments compared to their total working hours[240]. Selecting Sort by Average Utilization on the ResourcesTab would allow Universal Containers to identify which resources need more or fewer appointments by showing them how busy each resource is based on their utilization percentage[241]. Selecting Date Resolution on the Hours Tab would not allow Universal Containers to identify which resources need more or fewer appointments. Date Resolution is an option on the Hours Tab of the Gantt chart that allows changing how many hours are shown per column such as 1 hour, 2 hours, or 4 hours[242]. Selecting Travel Time and Breaks as skills on the Skills Tab would not allow Universal Containers to identify which resources need more or fewer appointments. Skills are records that define specific abilities orqualifications that resources have[243]. Travel Time and Breaks arenot skills but fields on the Resource object that define how much time a resource spends traveling between service appointments and how much time they take for breaks[244]. Selecting Hours, Absences and Overtime on

This option allows recording the required work for each component separately, and tracking the status and progress of each Work Order Line Item. References:https://help.salesforce.com/s/articleView?id=sf.fs_work_order_line_items.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.

Crew Management is a feature that allows creating and managing crews of multiple service resources who share the same service appointments[163]. The Preferred Resource service objective is ignored for active Crew Members because it only applies to individual resources and not crews[164]. Capacity-based scheduling is not supported for Service Crews because crews do not have capacity limits and can be assigned unlimited service appointments[165]. A service resource can be a member of multiple crews and can switch between them depending on their availability and skills[166]. Salesforce Field Service does not consider the Recommended Crew Size when assigning appointments because it only considers the Required Crew Size which indicates the minimum number of crew members needed for a service appointment[167]. References: https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_limitations.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_limitations.htm &type=5 https://help.salesforce.com/s/articleView? id=sf.fs_service_crews_create_edit_delete.htm&type=5https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_serviceappointment_requiredcrewsize.htm

Soft Boundariesand Customer First are two default scheduling policies that meet the requirement of committing preferred resources to accounts and providing prompt service. Soft Boundaries prioritize resources that are assigned to the same account or service territory asthe service appointment. Customer First prioritize resources that have the highest customer satisfaction rating.

Service Resources are records that represent thepeople or equipment that perform field service tasks[199]. Permission Set Licenses are records that grant users access to specific features or apps such as Salesforce Field Service[200]. Creating one Service Resource and assigning the relevant Permission Set Licenses would allow Universal Containers to configure Salesforce Field Service to support an employee who performs the role of a Dispatcher and a Technician by creating a service resource record for the employee and assigning them the Salesforce FieldService Dispatcher and Mobile permission set licenses[201]. Creating two Service Resources and assigning them to the employee would not work because an employee can only be associated with one service resource record[202]. Creating one Service Resource andassigning the Technician and Dispatcher role would not work because roles are records that define the level of access users have to data in an organization hierarchy[203]. Creating two Skills records and assign them to the Service Resource record would not work because skills are records that define specific abilities or qualifications that service resources have and do not affect their access to features or apps[204]. References: https://help.salesforce.com/s/articleView?id=sf.fs_service_resources_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.perm_sets_license_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_perm_sets_license_assign.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_resources_create_edit_delete.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.roles.htm &type=5https://help.salesforce.com/s/articleView?id=sf.fs_skills_overview.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

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

This feature shouldbe used to reduce travel time and increase technician productivity by automatically scheduling service appointments based on predefined criteria and objectives, such as minimizing travel distance or maximizing utilization. References:https://help.salesforce.com/s/articleView?id=sf.fs_optimizer_overview.htm &type=5

This option allows automatically dispatching a certain number of Service Appointments to a technician after they complete their current one, based on a predefined criteria. References:https://help.salesforce.com/s/articleView?id=sf.fs_drip_feed_dispatch.htm &type=5

This option allows reporting on assets and their attributes, including hierarchical relationships, by using the standard asset reports and fields. References:https://help.salesforce.com/s/articleView?id=sf.fs_asset_hierarchy.htm &type=5