‘Expire Old Messages To Device’ Feature Is Not Working In MWM 2.3 SP2 Upgrade
(Doc ID 2511458.1)
Last updated on DECEMBER 04, 2019
Applies to:
Oracle Utilities Mobile Workforce Management - Version 2.3.0.2.0 and laterInformation in this document applies to any platform.
Goal
**Any examples provided in this article do not represent real life personal/confidential information**
**Disclaimer:** This KM article may include the following abbreviations:
MWM - Oracle Utilities Mobile Workforce Management
MCP - Mobile Communication Platform
RSI - Remote Scripting Invocation
On : 2.3.0.2.0 version, Mobile Communications Platform
Why ‘Expire Old Messages To Device’ feature is not working in MWM 2.3 SP2 upgrade ?
As per the description, Messages queued for a specific mobile device that have not been delivered for a configurable amount of time are automatically cancelled. The default value is set to 30 days and may be overridden as need on the “Expire Old Remote Messages” (M1-EXOLDRMMS) algorithm. Have duplicated the algorithm ‘M1-EXOLDRMMS’ to ‘CM-EXOLDRMMS’ and set number of days to 1 for testing purpose. Changed setting in ‘M1-MessageToDevice’ business object to test this.
As specified in MWM_Business_User_Guide_v2_3_0_2.pdf, ‘M1-RMMSG’ batch expire messages and finalize the state of processed messages. But, the messages are not getting expired after 1 day with ‘M1-RMMSG’ batch.
Solution
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
| Goal |
| Solution |
| References |