4.35. Editor - Update a block
| Id | 4.35. |
| Description |
As an Editor,
I want to be able to update wrong or missing block information,
So that I can improve the quality and reliability of the register. |
| Priority | High |
| Actors | Editor |
| API Calls |
PUT /blocks/<block-id> PATCH /blocks/<block-id> |
| Linked Processes | |
| Status | Implemented |
Preconditions
- The User must be authenticated and have the Editor role.
- The User has a block id for which he wants to send an update
- The User has the name of the block and list of zero or more addresses to be linked to that specific block
Postconditions
- The system returns the updated block
Main flow
- The Editor uses an API call to update a specific block by ID (PUT / PATCH).
- The system validates the input parameters.
- The system returns the updated block
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 given block does not exist.
[409 Conflict] Addresses already used
Error returned by the system if the all or some of the given address are already linked to another site or block.
[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.