Which feature is not available unless a Google private key and client ID are configured?

Which feature is not available unless a Google private key and client ID are configured?

• A. Time Sheet Portal
• B. Auto-routing and auto-dispatch
• C. Dynamic Scheduling Criteria
• D. Task route cannot be optimized

Answer: (B)

The capability to automatically route and dispatch relies on the Google Maps integration. When the Google private key and client ID are configured, the scheduling engine can call Google Maps to compute distances, travel times, and optimal routes, which enables auto-routing and auto-dispatch to automatically assign tasks and plan efficient itineraries. Without those credentials, the optimization logic can’t access Google Maps data, so automatic routing and dispatch aren’t available. The other options don’t depend on Google Maps: the Time Sheet Portal is a user interface feature, and Dynamic Scheduling Criteria are internal rules used by the scheduler. The statement about a route not being optimizable describes the outcome when optimization isn’t possible, not a separate feature.

The capability to automatically route and dispatch relies on the Google Maps integration. When the Google private key and client ID are configured, the scheduling engine can call Google Maps to compute distances, travel times, and optimal routes, which enables auto-routing and auto-dispatch to automatically assign tasks and plan efficient itineraries. Without those credentials, the optimization logic can’t access Google Maps data, so automatic routing and dispatch aren’t available. The other options don’t depend on Google Maps: the Time Sheet Portal is a user interface feature, and Dynamic Scheduling Criteria are internal rules used by the scheduler. The statement about a route not being optimizable describes the outcome when optimization isn’t possible, not a separate feature.