...
Filtering and attribute selection rules are described in the TMF REST Design Guidelines.
Notifications are also described in a subsequent section.
...
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
...
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.
...
PATCH API/troubleTicket/{ID}
Description :
- This Uniform Contract operation is used to partially update the representation of a ticket.
- Resource represents a managed entity.
Behavior :
Description :
- This Uniform Contract operation is used to partially update the representation of a ticket.
- Resource represents a managed entity.
Behavior :
Patching of status is only allowed to transition :
...
REQUEST |
PATCH API/ troubleTicket /{ID} |
RESPONSE |
201 |
...
POST API/ticket
Description :
- 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 :
...