FSM Dynamic Scheduling Task Filter Criteria

[Paddler]

We are fine-tuning Dynamic Scheduling and need to get clarity/understanding on a few OOTB Task Filter Criteria:

1. "Availability today"?  Is that truly "today"?  And would you use More is better or Less is better?
2. "Current Distance From Task" vs "Distance From Task" - What's the difference?
3. "Last Assigned" - This one is supposed to balance workload.  How does it actually work?  Does it avoid the last agent assigned or look for the last agent assigned or something different?  And would you use More is better or Less is better?
4. "Filter out off-shift agents" - Tried this but it didn't seem to do anything.   What is it supposed to do? When would you use this?  And would you use More is better or Less is better?

Thank you for any and all help!

[Joshua Chen FX]

availability today:   looks to be using Agent Work Schedules, and if none, will also try schedule on sys_user record (there is a property to tell system to skip this schedule). The more availability an agent has, the higher the contribution to the agent's overall rank.

Current Distance From Task": 

Current Distance From Task calculation occurs in the CurrentLocationFromTask Script Includes

CurrentLocationFromTask: Calculate distance between task locations and user location based real-time and historical data, external map services, and dynamic configurations to provide a more assessment of user’s proximity to a task, factoring in travel time and location history. After it compare and assigns users a proximity score between 0.0 and 1.0. It returns the list of users with there rate and there distance from the task.

- use this one if geolocation enabled with google map api, and also if using territory management (start end location)

vs "Distance From Task": 

Distance From Task calculation occurs in the LocationFromTask Script Includes

LocationFromTask: Calculate distance between task locations and static user locations based solely on cmn_location, acompare and assigns users a proximity score between 0.0 and 1.0. It returns the list of users with there rate and there distance from the task.

Distance From Task does not do any checks for Territory Planning active or not. Just a simple check of distance from agent’s sys_user location to the Work Order Task location.

Filter out off-shift agents: Excludes agents who are not available based on schedule  or having time-off events. 
- i haveN,t tried this one, seems useless, legacy criteria... if you have schedule set up or events it will not book