‘Expire Old Messages To Device’ Feature Not Working
(Doc ID 2548879.1)
Last updated on OCTOBER 06, 2022
Applies to:
Oracle Utilities Mobile Workforce Management - Version 2.3.0.2.0 to 2.3.0.3.0 [Release 2.3]Information in this document applies to any platform.
Symptoms
On : 2.3.0.2.0 version,
We created a crewshift and the assignment was stuck in 'Pending Dispatch'. We duplicated the algorithm 'M1-EXOLDRMMS' to 'CM-EXOLDRMMS' and set the value of 'Days to expire' parameter as 2 in the duplicated algorithm. We plugged the duplicated algorithm in 'M1-MessageToDevice' business object and inactivated the 'M1-EXOLDRMMS' algorithm. We expected the activity to get expired after running batch M1-CLMDT today but nothing happened.
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! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |