FaultTicket
- Extends
| Field | Required | Nullable | Type | Description | Constraints | Example |
|---|---|---|---|---|---|---|
|
Yes |
No |
|
When sub-classing, this defines the sub-class Extensible name |
||
|
No |
No |
|
When sub-classing, this defines the super-class |
||
|
No |
No |
|
A URI to a JSON-Schema file that defines additional attributes and relationships |
||
|
No |
No |
|
Unique identifier |
2d7ed5fd-9f62-4211-bc84-357f5f7b80f5 |
|
|
No |
No |
|
Hyperlink reference |
||
|
No |
No |
|
Name of the trouble ticket, typically a short description provided by the user that create the ticket |
||
|
No |
No |
|
|||
|
Yes |
No |
|
Date when the order was posted by the requester |
2023-01-01T08:00:00+01:00 |
|
|
No |
No |
|
The severity of the issue. Indicate the implication of the issue on the expected functionality e.g. of a system, application, service etc.. Severity values can be for example : Critical, Major, Minor |
||
|
Yes |
No |
|
|||
|
No |
No |
|
File(s) attached to the trouble ticket. e.g. picture of broken device, scaning of a bill or charge |
||
|
No |
No |
||||
|
No |
No |
|
The date on which the trouble ticket was created |
||
|
No |
No |
|
The resolution date requested by the user |
||
|
No |
No |
|
The expected resolution date determined by the trouble ticket system |
||
|
No |
No |
|
The date and time the trouble ticket was resolved |
||
|
Yes |
No |
|
|||
|
No |
No |
|
The date and time that the trouble ticket was last updated |
||
|
No |
No |
|
The note(s) that are associated to the ticket. |
||
|
No |
No |
|
The priority of the trouble ticket and how quickly the issue should be resolved. Example: Critical, High, Medium, Low. The value is set by the ticket management system considering the severity, ticket type etc… |
||
|
No |
No |
|
An entity that is related to the ticket such as a bill, a product, etc. The entity against which the ticket is associated. |
||
|
No |
No |
|
The related party(ies) that are associated to the ticket. |
||
|
No |
No |
|
|||
|
No |
No |
|
The date and time the status changed. |
||
|
No |
No |
|
Message for the status change described as a combination of a text and a code. |
||
|
No |
No |
|
The status change history that are associated to the ticket. Populated by the server |
||
|
No |
No |
|
A list of trouble ticket relationships (TroubleTicketRelationship [*]). Represents a relationship between trouble tickets |
||
|
No |
No |
|
List of characteristics of the trouble ticket |
||
|
No |
No |
|
List of TroubleTicketJeopardyAlerts. A TroubleTicketJeopardyAlert represents a predicted exception during a trouble ticket processing that would brings risk to resolve successfully the trouble ticket. |
||
|
No |
No |
|
List of TroubleTicketMilestones. A TroubleTicketMilestone represents an action or event marking a significant change or stage in processing of a trouble ticket. |
||
|
No |
No |
||||
|
No |
No |
|
Boolean amended by the provider defining if the processing of the TroubleTicket is charging relevant |
false |
|
|
No |
No |
|
Technical identifier for a physical connection |
DEU.DTAG.FTYLIQ7PFT |
|
|
Yes |
No |
|
A reference to an agreement defined in the context of the product order |
||
|
No |
No |
|
Defines if direct contact with end user is allowed |
||
|
No |
No |
|
Defines if an appointment with the endUser is necessary |
||
|
No |
No |
|
|||
|
No |
No |
|
An array of questions and answers |
minimum items |
|
|
No |
No |
|
Defines if interim messages are requested to be provided |
||
|
No |
No |
|
Describes the location of the network termination in the building |
Flur |
|
|
No |
No |
|
Indicates the reason why the resolution of the trouble ticket is disputed |
||
|
No |
No |
||||
|
No |
No |
||||
|
No |
No |
|
Identifier of the trouble ticket category |
||
|
No |
No |
|
Array/List of billing items |
minimum items |