Hi All
Does any one, have experience with the drip feed functionality ?
We are trying to understand how drip feed its suppose to work, and how is related with the "Set recurring auto dispatch jobs". I'v read all the technical documentation available, but its not clear for me the following: A) the system dispatch the first SA, and the second one is dispatched if the first one ends, or if the time to start the second, approach. But what is the rule here ? how many minutes or hours before the system dispatch the second (in a situation where the first SA is not finished ) ?; B) we need to configure the recurring auto dispatch jobs in a specific way ? can be: each hour the batch can run ?; there is any implication in the drip feed ?
Somebody as any thoughts or experience on this ?
Forum Ambassador
Heiko Lindner (Privat)Hi @Jorge Nunes Monteiro I don't have any customer with activated drip feed.
My understanding is, that if you have drip feed enabled and you have set, e.g.:
- Service Appointments to Dispatch = 2
- two appointments assigned to a resource
- first appointment is "In Progress"
- second appointment is "Scheduled"
- If you change the status of the first appointment to any final status (completed or cannot completed or canceled) the second appointment will be dispatched directly without any time delay.
- you need just a simple active auto-dispatch job configured
- only thing to be considered is the auto-dispatch horizon in days
- if horizon is set to 1 day, then only the current day will be considered
- if horizon is set to 7 day, the second appointment can be scheduled within the next 7 days
- If the last appointment finished before the next one will be assigned (scheduled) I mean it will not be considered for drip feed directly. The next auto-dispatch job should consider it then
- Service Appointments to Dispatch = 2
