available activityBookingOptions are not appropriate
Summaryavailable activityBookingOptions are not appropriate
We are implementing Capacity and Availability based booking to one of our clients. Below are the steps performed and the issue that we are facing.
Make getCapacity API call against a bucket - response shows count 2 and minutes 70.
Make activityBookingOptions call with postalCode that matches the same bucket as in above getCapacity call. The type of Activity is configured to 90min default duration in the ActivityType configuration. It is clear that this Activity cannot be completed in 70 min but still 'activityBookingOptions' still returns a TimeSlot as available without a 'reason' indicating that the we can go ahead and create the Activity. This may cause the Technician to work Overtime. Is there a threshold limit that the activityBookingOptions considers while responding that a TimeSlot is not available? Or should the capacity completely exhaust to 0 or negative for the activityBookingOptions