Configuration Parameter 'NumMinutesAfterInactivateCurrentShift' Added to DHTSVINI to Inactivate Old Shifts
(Doc ID 975134.1)
Last updated on DECEMBER 05, 2019
Applies to:Oracle Utilities Mobile Workforce Management - Version 184.108.40.206 and later
Information in this document applies to any platform.
Prior to Mobile Workforce Management (MWM) v220.127.116.11, old shifts could remain active indefinitely for as long as a crew did not have another shift scheduled. Shifts can possibly remain active forever if the crew has no future shifts. In an integrated environment, Oracle Real Time Scheduler (ORS) and MWM are out of sync during this time since these shifts are removed from ORS as they are disabled 'X' hours after the scheduled completion of the shift. The reason they are still active in MWM is because the logic is based on the start time of the next shift. Further, dispatchers can accidentally assign work to old shifts that have completed.
The activate next shift logic has been altered to address this issue.
This article is intended for use in MWM and ORS integrated environments. Any changes should be evaluated as a change in business process and implemented by a system administrator. The complete list of changes in the v18.104.22.168 maintenance release should be reviewed in its entirity for other effects on the system.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document