...
The response contains a success status code or a business error. The business error
enables you to identify which messages where not successfully deleted, even though all other have been deleted
successfully.
Basic flow
Flow | Specifications |
---|
|
ID | AP-UC09-BF | Name | Delete one or more messages from the message list view | Description | / | Actor(s) | One healthcare professional | Requirements | - Atleast two message in one of the message boxes.
| Trigger | A healthcare professional wants to delete one or more messages. | Precondition(s) | - The user is logged in.
- The user wants to delete one or more messages.
| Flow | - See use case: login.
- The user wants to view the contents of one of his message boxes.
The user will see a list with all of his message for the specific folder he/she requested. See use case: consultation for more information about the GetMessagesList method. - The user selects one or more messages. The user wants to delete this/these message(s).
- The user gets a confirmation screen. The user can chose to confirm (4a) or not (4b).
- The user confirms and the message(s) get(s) deleted.
A request will be sent to delete the message(s). Afterwards, a request will be sent to update the message list. - The message(s) remain(s) the same. Nothing happens.
| Postcondition(s) | Path 4a: - The deleted message(s) is/are no longer available.
Path 4b: - The message(s) is/are still available. Nothing has changed.
| Test Data | GetMessagesList DeleteMessage | Endpoint(s) | |
|
...