Manually Allocated Activity Never Dispatched Due To Expired ATW in MWM v2 (Doc ID 1424593.1)

Last updated on MARCH 05, 2012

Applies to:

Oracle Utilities Mobile Workforce Management - Version: 2.0.1.5 and later   [Release: 2.0 and later ]
Information in this document applies to any platform.

Symptoms

An activity with an expired ATW (Arrival Time Window) was manually allocated to an active Shift.

The System would not dispatch this activity to the Mobile Device. The user attempted to manually Dispatch the activity. However, the system did not Dispatch the activity and the activity remained in "Ready for Dispatch" status.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms