Editing Trouble Codes on Calls and Events
(Doc ID 1157837.1)
Last updated on OCTOBER 21, 2021
Applies to:
Oracle Utilities Network Management System - Version 1.10.0 and laterOracle Network Management for Utilities - DMS - Version 1.10.0 and later
Information in this document applies to any platform.
Purpose
This FAQ clarifies the functionality and behavior when Trouble Codes are changed.
Questions and Answers
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
| Purpose |
| Questions and Answers |
| Can changing a Trouble Code on a call also change the event it is assigned to from a non-outage to an outage? |
| What will happen in the process when going from one type to another? |
| Will prediction be made for non-outage to outage? |
| Will the customer count be set to zero if the event is changed from an outage to a non-outage? |
| Are there any rules that the customer count needs to be zero before going to a non-outage type? |
| If a non-outage call is changed to an outage, and the non-outage event no longer has any calls, is it destroyed? |
| If the last outage call on an RDO is changed to a non-outage, does the RDO remain an outage event with no calls? |
| What happens if a user then does an 'Undo Open', which would theoretically change it from an RDO back to a PSO? |
| Our users tend to change the Trouble Type of the job to reflect what the job was, not the individual calls. How can we change the job? |
| Is there an audit trail for trouble code changes? |
| References |