4.55. Organisation Approver - Approve delete equipment request for organisation
| Id | 4.55. |
| Description |
As an Organisation Approver,
I need to be able to approve equipment deletion requests from Editors linked to my Organisation,
So that I can guarantee that no equipment is deleted by mistake and to preserve the quality and reliability of the register |
| Priority | Medium |
| Actors | Organisation Approver |
| API Calls |
POST /equipments/<equipment-id>/approve POST /equipments/<equipment-id>/reject PUT /equipments/<equipment-id> PATCH /equipments/<equipment-id> |
| Linked Processes | |
| Status | Implemented |
Preconditions
- The User must be authenticated and have the Organisation Approver role.
- The User has a valid equipment id that is marked as “to be deleted”
- The delete request has been performed by a user from the Approver’s organisation.
Postconditions
- The system returns a confirmation that the decision (validation/rejection) has successfully been applied
Main flow
- The Organisation Approver uses an API call to approve/reject the equipment deletion by id (POST).
- The system validates the deletion 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] Equipment not found
Error returned by the system if the equipment 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