Maximum travel from home distance threshold is always calculated in kilometers
Last updated 17 days ago ·Reference W-8600681 ·Reported By 1 users
In Review
Summary
Maximum travel from home distance threshold is always calculated in kilometers.
Repro
1. Log in as a System Admin
2. Set your org Travel Speed Unit to MPH in FSL settings --> Scheduling --> Routing.
3. Set Latitude and Longitude values on your Service Territory and create 1 Service Appointment with a different geolocation but within this same Service Territory.
4. Measure the aerial distance between the Service Territory and a Service Appointment
5. Add the work rule of type "Field Service - Maximum Travel From Home" (this is its record type) to your policy and set its fields as follow:
Maximum Travel From Home Type = Distance
Maximum Travel From Home = (some value higher than the aerial distance in MPH and lower than the one in KM).
6. Make sure to have a resource in this territory that can get this service using Get
7. Candidates with the policy from step #4.
8. Send an optimization with the policy from step #4.
Actual Results
==============
Service Appointment is not scheduled.
Expected results
==============
Service should get scheduled (he has candidates in the MP).
Workaround
As a workaround, consider changing the Travel Speed Unit in your org to KM instead of MPH:
1. Go to Field Service Settings tab | Scheduling | Routing
2. Set Travel Speed Unit to KM and save the changes
3. Convert the current distance in the 'Maximum Travel From Home' works rules in your policy from miles to kilometers and save the changes
Reported By (1)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.
