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