Begin Date is Not Updated with Proper Value Through OMA RESTFUL APIs
(Doc ID 2685142.1)
Last updated on JUNE 26, 2020
Applies to:Oracle Network Management for Utilities - DMS - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 2.3 to 2.4]
Oracle Utilities Network Management System - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 2.3 to 2.4]
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Web Workspace
Begin Date is not updated with proper value through OMA RESTFUL APIs
We have created a Planned switching sheet with 2 steps OPEN and CLOSE. When we complete the OPEN step from NMS or through OMA webservice, the step is completed and the event is created.
But the issue here is with the event Begin Date - the begin date is not updated with the current server time. It may get updated sometimes to a previous date, or sometimes it is getting updated with hours difference between current server time. It is not stable all the time.
Expected that the event begin time is not always at the time of the execution.
The issue can be reproduced at will with the following steps:
Create switching sheet with an Open and a Close step
Execute the switching sheet from the Operations Mobile App (OMA)
Note that the event begin Date/Time displayed in Workagenda is not updated with the current server time when the step is executed.
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