Mobile Events

The Go event triggers the moment of final assignment. As soon as the Go event has been chosen, the GPS device will be activated. This will guarantee that the GPS location at the moment of the on site event will be available for further processing (see checkForGeocodeOverwrite preference).

Confirm Go

If the taskConfirmGo process flow preference is true, the application shows the current location and asks for confirmation when the Go button is pressed. The confirmation dialog has a dedicated button to start navigation.

taskConfirmGo
Type Default Value Example Android HTML 5
Boolean true false + -

As soon the mobile worker is on the way, the navigation is available unless the icon has been deactivated (see below).

The Navigation icon allows mobile workers to activate the device's navigation. To disable the icon, set the showNavigationIcon preference to false.

showNavigationIcon
Type Default Value Example Android HTML 5
Boolean true false + +

The On Site event is used to mark the arrival at the task's location. In case the GPS device is activated, i.e. the Go button has been pushed, the on site event will contain the current location for further processing. The timestamp of the event is used to store the actual start of the task. Additionally, it determines the actual duration of a task in combination with the Finish event.

Note that the GPS service is deactivated once the mobile worker has pressed the on site icon.

Milage

The mobile application asks for the actual mileage in case the alwaysAskForMilage process flow preference set to true and the on site button is pressed.

alwaysAskForMilage
Type Default Value Example Android HTML 5
Boolean true false + -

Hide On-Site

By default, the app shows the Go and On Site buttons at the same time. This allows immediate starting with a new task, if it is executed nearby and travel can be disregarded. However, the On Site button can be hidden, until the Go button has been pressed, by setting the hideOnSiteBeforeGo flow preference.

hideOnSiteBeforeGo
Type Default Value Example Android HTML 5
Boolean false true + +

Finish

The Finish icon is always available by default once the task has been signed, but it can be set inactive in exceptional cases where tasks are closed on the server-side or by internal staff.

The timestamp of this event determines the actual duration of a task in combination with the On Site event.

showFinishIcon
Type Default Value Example Android HTML 5
Boolean true false + +

Normally, the Finish icon is only visible once the task is signed. However, The Finish icon can be made visible immediately after arriving on site by setting the allowFinishShortcut preference to true. The availability of the Finish icon is dependent on the following constraints:

  • There are no untouched attachments that require the quantities to be changed (requiresChangedQuantities on item level is true).
  • There is no unconfirmed rule in the task attachment.
  • There are no untouched items that require confirmation.
allowFinishShortcut
Type Default Value Example Android HTML 5
Boolean false true + +

Ask When Closing

Mobile Workers are asked by default if they want to close the task after having pressed the Finish icon. To avoid this question, one may turn the askWhenClosing preference off.

askWhenClosing
Type Default Value Example Android HTML 5
Boolean true false + -

Automated Go

Setting the goOnClose preference to true will immediately start the next task in the agenda once a task is finished.

goOnClose
Type Default Value Example Android HTML 5
Boolean false true + -

Automated End Of Day

Setting the openEODAfterLastClosure preference to true will make the app ask the the mobile worker if the app should open the end of the day screen, immediately after the last task on the agenda was closed or canceled.

openEODAfterLastClosure
Type Default Value Example Android HTML 5
Boolean false true + -

Follow-On

Follow-Ons are defined in the configuration part of OMD Go. Depending on the follow-on type, a new task is created for the same mobile worker on the same day (type 1) or the new task remains unplanned (type 2) until the planner assigns the task to a mobile worker. Follow-on tasks are internal OMD tasks, they are not created in the connected ERP system.

Follow-on type 3 is used to indicate that the task needs to be replanned by the planner (back to planner functionality). In this case, an attachment with subtype backToPlanner is created.

See here for more details.

showFollowOnIcon
Type Default Value Example Android HTML 5
Boolean true false + +

Geocode Deviation

An alert message can be shown after pressing on-site, if the geocode of the current position of the device is too far away from the expected task location. By default, the deviation is not checked and no deviation alert will be shown.

If a value for onSiteGeocodeDeviation is specified, an alert will be shown if the distance of the current position to the expected task location is later than the defined value (in m).

onSiteGeocodeDeviation
Type Default Value Example Android HTML 5
Integer undefined 500 +

Go

To show or hide the Go Button set the following preference.

showGoButton
Type Default Value Example Android HTML 5
Boolean true true - +

Automated On-Site

With the following preference, the status of the task change directly to onSite when opening a task in the today's agenda.

onSiteWhenOpeningTask
Type Default Value Example Android HTML 5
Boolean false true - +

results matching ""

    No results matching ""