Skip to main content

Hello!

 

I have couple of questions with respect to FSL Scheduling, Drive Time and Resource Absences.

 

1. I have a resource absence with "Non Availability" as the record type on few of my service resource's calendars. With the resource absences what I am trying to achieve is that the resource is not being assigned service appointments on their calendars where they should not be required to drive during the resource absence timeframe. For example, I have a resource absence from 10-11AM on a service resource calendar, I want FSL to return the 1130AM slot only if the drive time is less than 30 minutes. If the drive time is more than 30 minutes, I don't want FSL to return 1130 as an available slot for this resource. Is this possible? If yes, what is the process to make this possible? I looked up to Work rules but couldn't exactly relate to my usecase.

2. I have time slots setup in my calendar for 1 hour duration work types. For Example, 8AM-9AM, 10AM-11AM & 12PM-1PM. The slot 10AM - 11AM was taken(Service Appointment Scheduled) to a resource. When using FSL.AppointmentBookingService.GetSlots method, we see the slot 8AM-9AM being returned as an available slot, however the estimated travel time between the 2 Service Appointments(8AM-9AM and 10AM-11AM) is more than 60 minutes(9AM-10AM). If the drive time is more than 60 minutes which is the maximum allowed drive time between appointments, why would FSL return the slot at 8AM as an eligible appointment that the same resource could perform? Is there anything that I am missing in this that could relate to my usecase.

 

Many thanks in advance for any help/direction on this.

 

Thank you.

13 件のコメント
  1. 2021年3月17日 19:15
    @Krishna V echo @Steve Hupp's comment above about it potentially using aerial calculation in case of a conflict and then rendering travel based on SLR. Can you try checking the flag in FS settings " Avoid aerial calculation upon callout DML exception" and see if that helps? Also, if you enable point-to-point routing, do you have the same problem?
0/9000