HostTaskId Cannot Be Updated On An Existing Appointment Until v18.104.22.168.2
(Doc ID 1981932.1)
Last updated on MARCH 25, 2019
Applies to:Oracle Real-Time Scheduler - Version 22.214.171.124.0 to 126.96.36.199.2 [Release 2.2]
Oracle Utilities Mobile Workforce Management - Version 188.8.131.52.0 to 184.108.40.206.2 [Release 2.2]
Information in this document applies to any platform.
'hostTaskId' is not getting updated while updating an already existing appointment through M1-MaintainActivitiesByHost service. A hostTaskId was provided during booking an appointment (M1AD) and then later updated the hostTaskId to a new value by updating that appointment (M1UP). The book slot response showed the newly updated hostTaskId however, when the activity is inquired through M1-ActivityStatusInquiry, the hostTaskId that was used during the initial booking still remains.
The information passed in the hostTaskId is critical. A booking can be transferred to different customer orders and hostTaskId is used to track the order information. If the hostTaskId is not updated with the correct order number, manifest will be incorrect and it will impact the customer experience.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!