Skip to main content

4.53. Organisation Approver - Approve deleted block request for organisation

Id 4.53.
Description

As an Organisation Approver,

 

I need to be able to approve block deletion requests from Editors linked to my Organisation,

 

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 Organisation Approver
API Calls

POST /blocks/<block-id>/approve

POST /blocks/<block-id>/reject

PUT /blocks/<block-id>

PATCH /blocks/<block-id>
Linked Processes

7.8. Approve delete block request
Status Implemented

Preconditions

  1. The User must be authenticated and have the Organisation Approver role.
  2. The User has a valid block ID that is marked as “to be deleted”
  3. The delete request has been performed by a user from the Approver’s organisation.

Postconditions

  1. The system returns a confirmation that the decision (validation/rejection) has successfully been applied

Main flow

  1. The Organisation Approver uses an API call to approve/reject the block deletion by ID (POST).
  2. The system validates the deletion request.
  3. 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.

No comments to display

Back to top