A custom Price Book allows different prices for the same products in different markets. A standard

Price Book has the same prices for all markets. Pricing rules are not available for Field Service

Lightning.

Reference:

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

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

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

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.

Reference:

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

To provide access to the Salesforce Field Service Mobile App, the user’s profile must have the Field

Service Mobile permission enabled. Updating Public Group membership, assigning a Field Service

Mobile License to the user, or modifying the user record would not grant access to the mobile app.

Reference: https://help.salesforce.com/s/articleView?id=sf.fs_mobile_app_permissions.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.

Reference:

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

Reference:

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

Permission Sets are records that grant users access to specific features or apps such as Salesforce

Field Service[214]. Scheduling licenses are records that grant users access to scheduling features such

as Dispatcher Console or Optimization[215]. Creating Permission Sets and assigning the Salesforce

Field Service Resource Permission Set and Scheduling license to each Technician would allow

Universal Containers’ Technicians to update their own appointments’ status using the Dispatcher

console Gantt chart by granting them access to Salesforce Field Service mobile app features such as

updating status and granting them access to scheduling features such as viewing Gantt chart[216].

Creating Permission Sets and assigning the Salesforce Field Service Scheduling and Mobile

Permission Sets to the Resource profile would not allow Technicians

Street Level Routing is a feature that calculates travel time between service appointments based on

actual road distance and traffic conditions[131]. Default Travel Speed is a setting that defines the

average speed of resources when traveling between service appointments[132]. Using Street Level

Routing and Default Travel Speed would allow improving travel time accuracy by taking into account

real-time road conditions and resource speed. Minimum Grade, Default Operating Hour would not

affect travel time accuracy. Minimum Grade is a setting that defines the minimum skill level required

for resources to be matched with service appointments[133]. Default Operating Hour is a record that

defines the default working hours for resources[134]. Estimated Travel Time, Minimize Travel would

not affect travel time accuracy. Estimated Travel Time is a field on the service appointment object

that shows the expected travel time for the assigned resource[135]. Minimize Travel is an

optimization

criterion

that

prioritizes

reducing

travel

time

when

scheduling

service

appointments[136]. Travel Speed Unit, Actual Travel Time would not affect travel time accuracy.

Travel Speed Unit is a setting that defines the unit of measurement for travel speed such as miles per

hour or kilometers per hour[137]. Actual Travel Time is a field on the service appointment object that

shows

the

actual

travel

time

recorded

by

the

resource[138].

Reference:

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

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

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

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

https://developer.salesforce.com/docs/atlas.enus.api.meta/api/sforce_api_objects_serviceappointment_estimatedtraveltime.htm

https://help.salesforce.com/s/articleView?id=sf.fs_scheduling_policies_optimization_criteria.htm&t

ype=5

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

https://developer.salesforce.com/docs/atlas.enus.api.meta/api/sforce_api_objects_serviceappointment_actualtraveltime.htm

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

Reference:

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

https://developer.salesforce.com/docs/atlas.enus.api.meta/api/sforce_api_objects_serviceappointment_requiredcrewsize.htm

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]. Reference:

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