# Service Problem Management

Create and manage a service problem for a given line/service.


## Create a problem/incident for an active service owned by the communications provider (CP).

 - [POST /service-problems](https://docs.thefibrecafe.net/openapi/prod/supplier-api/gen/service-problem-management/handlecreateproblem.md): This endpoint is called to raise a problem with the supplier to resolve a potential issue with a service.

The supplier should validate and accept the request if the validation is successful or otherwise reject it.
If the request is rejected, a 422 code should be returned with reason(s) for the rejection in the response.

If the request is accepted, the supplier may return a 202 accepted response without acknowledging the service
problem if further validation/processing is required. In this scenario, the supplier must then send an update
(KCI) to later acknowledge the service problem and provide the problem reference.

Alternatively, the supplier can synchronously acknowledge the service problem by returning a 201 created response
with the response containing the problem reference and status of ACKNOWLEDGED. The service problem can also be
committed at this stage by returning the status of IN_PROGRESS.

## Request to amend an inflight service problem.

 - [POST /service-problem-amendments](https://docs.thefibrecafe.net/openapi/prod/supplier-api/gen/service-problem-management/handleamendproblem.md): This endpoint is called to request amendment of an existing inflight service problem on an active service.

A request will contain 1 or more fields to be amended - only fields supplied should be changed.

The supplier should validate the amendment request. If the request is invalid or not possible then a 422 code
should be returned with reason(s) for the rejection in the response.

The supplier may return a 202 accepted response without confirming the amendment if further validation/processing
is required. In this scenario, the supplier must then send an update (KCI) to later confirm the amendment was 
applied or if rejected.

Alternatively, the supplier can confirm the amendment immediately by returning a 201 created response.

## Request to cancel an inflight service problem.

 - [POST /service-problem-cancellations](https://docs.thefibrecafe.net/openapi/prod/supplier-api/gen/service-problem-management/handlecancelproblem.md): This endpoint is called to request cancellation of an existing inflight service problem on an active service.

The supplier should validate the cancellation request. If the request is invalid or not possible then a 422 code
should be returned with reason(s) for the rejection in the response.

The supplier may return a 202 accepted response without confirming the cancellation if further validation/processing
is required. In this scenario, the supplier must then send an update (KCI) to later confirm the cancellation was
completed or if rejected.

Alternatively, the supplier can confirm the cancellation immediately by returning a 201 created response.

## Request to accept or reject resolution of an inflight service problem.

 - [PATCH /service-problem-resolutions/{id}](https://docs.thefibrecafe.net/openapi/prod/supplier-api/gen/service-problem-management/handleserviceproblemresolution.md): This endpoint is called to signify acceptance or rejection of a supplier's resolution to an inflight
service problem.

Where the tenant is satisfied with the resolution, the status of the resolution will be set to ACCEPTED and the
service problem can be closed with the status set to COMPLETED.

Alternatively, the status will be REJECTED if the tenant is not satisfied and they should provide a reason in
the tenantNotes field. The status problem will be re-opened with the status set back to IN_PROGRESS.