10,587
edits
Important: Deprecating old WebView — Publish failed error
Releases/Autumn 2021: Difference between revisions
Jump to navigation
Jump to search
→Routes AI
| Line 75: | Line 75: | ||
See [[Configure Run Report command]] for more information. | See [[Configure Run Report command]] for more information. | ||
== Routes AI == | == Route plan and Routes AI == | ||
* [[Route plan]] configuration in Woodford now includes a new parameter '''Activity Name Field''' which allows you to define which field is displayed as the title of the record in the list and on the map.<br>[[File:Edit route plan.png|600px]] | * [[Route plan]] configuration in Woodford now includes a new parameter '''Activity Name Field''' which allows you to define which field is displayed as the title of the record in the list and on the map.<br>[[File:Edit route plan.png|600px]] | ||
* Route plan has considerable configuration options in Woodford, but some customers need even more control and automation. For this reason, we have brought support for [[Resco JavaScript Bridge]] to route plans. Attach a script to the route plan configuration in Woodford.<br>[[File:Route plan iframe.png|600px]] | |||
* Mobile users can now optimize their routes even if there's an incomplete fixed-time appointment (ongoing or past). | * Mobile users can now optimize their routes even if there's an incomplete fixed-time appointment (ongoing or past). | ||
* [[Routes AI]] now considers traffic information when optimizing routes. When optimizing current tasks, live traffic information is used. When optimizing tasks for later days, historical data is used. | |||