...
Filtering and attribute selection rules are described in the TMF REST Design Guidelines.
Notifications are also described in a subsequent section.
| Anchor |
|---|
| _Toc404092929 |
|---|
| _Toc404092929 |
|---|
|
GET /API/troubleTicket/{ID}}/?{fields=attributes}&{filtering expression}This Uniform Contract operation is used to retrieve the representation of a ticket.
Note that collections can be retrieved via GET /API/troubleTicket/ with no {ID}
Filtering is allowed on all attributes. See example below. Attribute selection is possible for all attributes. See example below.
...
- GET /api/ticket/1/status,statusChangeReason
| Anchor |
|---|
| _Toc404092930 |
|---|
| _Toc404092930 |
|---|
|
PUT API/troubleTicket/{ID}Description :
- This Uniform Contract operation is used to completely update the representation of a ticket.
- Resource represents a managed entity.
...
Example see TMF REST Design Guidelines.
| Anchor |
|---|
| _Toc404092931 |
|---|
| _Toc404092931 |
|---|
|
| Anchor |
|---|
| _Ref234978967 |
|---|
| _Ref234978967 |
|---|
|
| Anchor |
|---|
| _Toc235288517 |
|---|
| _Toc235288517 |
|---|
|
| Anchor |
|---|
| _Toc236554611 |
|---|
| _Toc236554611 |
|---|
|
| Anchor |
|---|
| _Toc236554912 |
|---|
| _Toc236554912 |
|---|
|
| Anchor |
|---|
| _Toc236555375 |
|---|
| _Toc236555375 |
|---|
|
| Anchor |
|---|
| _Toc225613455 |
|---|
| _Toc225613455 |
|---|
|
| Anchor |
|---|
| _Toc225603244 |
|---|
| _Toc225603244 |
|---|
|
| Anchor |
|---|
| _Ref226733430 |
|---|
| _Ref226733430 |
|---|
|
| Anchor |
|---|
| _Ref230885009 |
|---|
| _Ref230885009 |
|---|
|
| Anchor |
|---|
| _Ref231980155 |
|---|
| _Ref231980155 |
|---|
|
| Anchor |
|---|
| _Ref232940733 |
|---|
| _Ref232940733 |
|---|
|
| Anchor |
|---|
| _Ref232940829 |
|---|
| _Ref232940829 |
|---|
|
PATCH API/troubleTicket/{ID}Description :
- This Uniform Contract operation is used to partially update the representation of a ticket.
- Resource represents a managed entity.
...
REQUEST |
PATCH API/ troubleTicket /{ID}
Content-type: application/json
{
"status": "Close",
"statusChangeReason": "Dispute has been resolved in favor of the customer."
} |
RESPONSE |
201
Content-Type: application/json
{
"id": "1",
"correlationId": "TT53482",
"description": "Customer complaint over last invoice.",
"severity": "Urgent",
"type": "Bills, charges or payment",
"creationDate": "2013-07-23T08:16:39.0Z",
"targetResolutionDate": "2013-07-30T10:20:01.0Z",
"status": "Closed",
"subStatus": "",
"statusChangeReason": "Dispute has been resolved in favor of the customer.",
"statusChangeDate": "2013-07-24T08:55:12.0Z",
"relatedParty": [
{
"href": "/customer/1234",
"role": "Originator"
},
{
"href": "/operator/1234",
"role": "Owner"
},
{
"href": "Roger Collins",
"role": "Reviser"
}
],
"relatedObject": [
{
"involvement": "Disputed",
"reference": "/invoice/1234"
},
{
"involvement": "Adjusted",
"reference": "/invoice/5678"
}
],
"note": [
{
"date": "2013-07-24T09:55:30.0Z",
"author": "Arthur Evans",
"text": "Already called the expert"
},
{
"date": "2013-07-25T08:55:12.0Z",
"author": "Arthur Evans",
"text": "Informed the originator"
}
]
} |
| Anchor |
|---|
| _Toc404092932 |
|---|
| _Toc404092932 |
|---|
|
POST API/ticketDescription :
- This Uniform Contract operation is used to create a ticket.
- Resource represents a managed entity.
- Mandatory attributes that must be provided when you create the ticket :
...