4.51. Approver - Approve or reject update vertical cabling request
| Id | 4.51. |
| Description |
As an Approver,
I need to be able to approve an update vertical cabling request
So that I can guarantee that the data updates performed on the registry are accurate and meet the needed data quality standards. |
| Priority | High |
| Actors | Approver |
| API Calls |
GET /physical-links POST /physical-links/<physical-link-id>/approve POST /physical-links/<physical-link-id>/reject PUT /physical-links/<physical-link-id> PATCH /physical-links/<physical-link-id> |
| Linked Processes | |
| Status | Implemented |
Preconditions
- The User must be authenticated and have the Approver role.
- The User has a valid Physical Link ID that has to be validated
Postconditions
- The system returns a confirmation that the decision (validation/rejection) has successfully been applied
Main flow
- The Approver retrieves the list of physical links to be approved (GET)
- The Approver can perform amendments if needed prior to the approval
- The Approver uses an API call to approve/reject the physical link by ID (POST).
- The System validates the approval request.
- The System returns the confirmation that the request has been approved/rejected
Exceptions
[400 Bad Request] Invalid input:
If mandatory fields are missing or invalid, the system returns an error message.
[404 Not Found] Physical link not found
Error returned by the system if the physical link is not found.
[500 Internal Server Error] System Error
If the system fails to save changes due to an internal error, it displays an appropriate message and logs the error for further investigation.
No comments to display
No comments to display