...
| Flow | Specifications |
|---|
|
| ID | AP-UC04-AF02 | | Name | Delete an out-of-office. | | Description | / | | Actor(s) | One healthcare professional | | Requirements | / | | Trigger | A user wants to delete an out-of-office. | | Precondition(s) | - The user is logged in.
- The user has atleast one out-of-office period.
- The user wants to delete an out-of-office.
| | Flow | - see Use case: login.
- When opening the OoO section, the application should automatically
request a list of already inserted OoO periods.
| | Postcondition(s) | - The OoO is successfully deleted.
- There is one less OoO period than there was before the delete.
| | Test Data | | | Endpoint(s) | |
|
Alternative flow 3 (to do)
| Flow | Specifications |
|---|
|
| ID | AP-UC04-AF02 | | Name | Update an out-of-office. | | Description | / | | Actor(s) | One healthcare professional | | Requirements | / | | Trigger | A user wants to update an out-of-office. | | Precondition(s) | - The user is logged in.
- The user has atleast one out-of-office period.
- The user wants to update an out-of-office.
| | Flow |
| | Postcondition(s) | - The OoO is successfully updated.
| | Test Data | | | Endpoint(s) | |
|