Last updated on JUNE 30, 2017
Applies to:Oracle Network Management for Utilities - DMS - Version 22.214.171.124 to 126.96.36.199 [Release 1.12]
Oracle Utilities Network Management System - Version 188.8.131.52 to 184.108.40.206 [Release 1.12]
Information in this document applies to any platform.
Appointment Date/Time not saving within Call History window
The Appointment Date/Time is not saving when attempting to set the appointment Date/Time via the Call History window.
When select the value from the DateTimeSelector, the APPT_TIME datastore it sets it to date format:
DEBUG com.splwg.oms.jbot.DefaultDataStore: DefaultDataStore.setValue: setting "APPT_TIME" to value "20/05/16 08:31" (datastore = "DS_CALL_HISTORY")
But, when clicking the Save button on Call History window the APPT_TIME is set to a timestamp format:
2016-05-16 08:31:57,504 [pool-2-thread-9] DEBUG com.splwg.oms.common.intersys.Incident: name = "APPT_TIME"
value = "2016-05-20 08:31:00.0"
The issue can be reproduced at will with the following steps:
1. In jconfig/ops/callentry/xml/DLG_CALL_DETAILS_CUSTOMER_AND_CALLBACK.inc
Make CD_CMB_APPT, CD_TXTF_APPT_RANGE and CD_TXTF_APPT_TIME all Enabled ="true" and
Editable = "true".
2. Submit a call for someone, say, HARRY (top guy on the returned list).
3. Load HARRY again.
4. Bring up the Call History for him.
5. Select the most recent call.
6. In the Appointment fields, select "After", set range to 06:00, and set the date to 2 days out.
8. Close the call history.
9. Bring up Call History again.
The appointment type and range are set. The date is empty.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms