Description
User Story
As a backend service, I want to provide an Endpoint to access all Mail/Message realated information so that the Web Frontend can display a Mail in it's entirety and can also work with Meta Data of a Mail.
Description
A request from the web Frontent contains identifying fields, so that the backend is able to load a Mail from the storage and provide all requested information to the caller. This covers not just the user relevant content of a Mail but also all available Meta information. The caller is able to limit the information returned to serve different purposes. Sanitisation of potential malicious content is NOT part of this story.
This ticket covers the implementation of the backend logic to support the creation of contacts with basic fields.
Value
- Fast an easy access to Mails
- Provides clean, reusable structure for future enhancements.
Acceptance Criteria
- Mail is correctly transferred via API to the Frontend
- Performance does not impact the backend Services
- Functionality is tested
Dependencies
- Backend storage for Mails is available
- API Framework for Communication
Description
User Story
As a backend service, I want to provide an Endpoint to access all Mail/Message realated information so that the Web Frontend can display a Mail in it's entirety and can also work with Meta Data of a Mail.
Description
A request from the web Frontent contains identifying fields, so that the backend is able to load a Mail from the storage and provide all requested information to the caller. This covers not just the user relevant content of a Mail but also all available Meta information. The caller is able to limit the information returned to serve different purposes. Sanitisation of potential malicious content is NOT part of this story.
This ticket covers the implementation of the backend logic to support the creation of contacts with basic fields.
Value
Acceptance Criteria
Dependencies