Shift Changes Made By Dispatcher Revert To Initial Values After Saved Because Old Shift Information Received From MDT
(Doc ID 2190196.1)
Last updated on OCTOBER 06, 2022
Applies to:
Oracle Utilities Mobile Workforce Management - Version 2.2.0.1.3 to 2.2.0.3.13 [Release 2.2]Oracle Real-Time Scheduler - Version 2.2.0.1.3 to 2.2.0.3.13 [Release 2.2]
Information in this document applies to any platform.
Symptoms
**Examples provided in this article do not represent real life personal/confidential information**
**Disclaimer:** This KM article may include the following abbreviations:
CCB - Oracle Utilities Customer Care and Billing
ETM/ETPM - Oracle Enterprise Taxation and Policy Management
OUAF/FW - Oracle Utilities Framework
MDT - Mobile Data Terminals
MWM - Oracle Utilities Mobile Workforce Management
ORTS/ORS/ERTS - Oracle Real-Time Scheduler
On v2.2.0.1.3
ACTUAL BEHAVIOR
---------------
Crew Shift end times changes back to initial setting after saved
The dispatcher will extend a Crew Shift out in the morning. They will save it, then the times will revert back to the initial setting.
EXPECTED BEHAVIOR
-----------------------
Crew Shift end times should not change back to initial setting after being saved
BUSINESS IMPACT
-----------------------
FAs are not scheduled when expected.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |