Route plan: Difference between revisions

Jump to navigation Jump to search
Line 9: Line 9:
Route plans are configured for each [[app projects|app project]] in [[Woodford]]. Select '''Route Plan''' from the '''Project''' menu of [[Woodford]] to display a list of route plans. You can design multiple different route plans. After you're done designing a route plan, add it to the [[home screen]] of the app.
Route plans are configured for each [[app projects|app project]] in [[Woodford]]. Select '''Route Plan''' from the '''Project''' menu of [[Woodford]] to display a list of route plans. You can design multiple different route plans. After you're done designing a route plan, add it to the [[home screen]] of the app.


The configuration of a route plan is divided into three tabs.
The configuration of a route plan is divided into multiple tabs.
* Activity: Use it to configure created appointments
* '''Activity''': Use it to configure created appointments
* Filter Fields: Filter which appointments are shown on the map.
* '''Filter Fields''': Filter which appointments are shown on the map.
* Source Views: Select entities that should be displayed on the map. User can click the map pins to add an appointment with the entity to their daily route.
* '''Smart Planning''':
* '''Source Views''': Select entities that should be displayed on the map. User can click the map pins to add an appointment with the entity to their daily route.


Set up the route plan, then click '''Save & Close'''.
Set up the route plan, then click '''Save & Close'''.
Line 24: Line 25:
; View-only Mode: Enable to make the route plan ready only for app user. User won't be able to modify route items.
; View-only Mode: Enable to make the route plan ready only for app user. User won't be able to modify route items.
; Filter user-owned records: Check if the route plan should explicitly filter records owned by the current user of the app. Similar functionality can also be achieved by setting a proper [[Sync Filter]] for the route plan entity.
; Filter user-owned records: Check if the route plan should explicitly filter records owned by the current user of the app. Similar functionality can also be achieved by setting a proper [[Sync Filter]] for the route plan entity.
; Enable completion: Check to allow users to complete appointments directly from the map annotation. When this field is enabled, you also need to define the Completion Status below.
; Enable completion: Check to allow users to complete appointments directly from the map annotation. When this field is enabled, you also need to define the Completion Status field and optionally also Excluded Status Values.
; Status field: Choose the entity field that is used as status field.
; Completion Status: Choose the status code that's set when a user marks an appointment as complete on the map. Appointments with this status code are not shown on the route.
; Completion Status: Choose the status code that's set when a user marks an appointment as complete on the map. Appointments with this status code are not shown on the route.
; Excluded Status Values: Choose additional status codes that should also be not shown on the route.
; Excluded Status Values: Choose additional status codes that should also be not shown on the route.
Line 32: Line 32:
; Default Work Location: Enter the altitude and longitude of the default work location.
; Default Work Location: Enter the altitude and longitude of the default work location.
; Start/end route at work: Check if work is used as the default starting and ending location. Clear if you want to use the current location instead.
; Start/end route at work: Check if work is used as the default starting and ending location. Clear if you want to use the current location instead.
; Alternative visit location: If you define alternative location fields, you can then define an alternate location for route items (appointment/activity).
=== Smart Planning tab ===
TBD.


=== Filter Fields tab ===
=== Filter Fields tab ===

Navigation menu