MWM v2.0.1 Sends Obsolete Shifts To Scheduler

(Doc ID 1985231.1)

Last updated on JULY 02, 2015

Applies to:

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

Symptoms

A shift is obsolete (dated year 2013), but it is being sent everyday to the scheduler. Why? Even though scheduler does mark it as inactive, does this cause overhead or not?

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