Initial API model with Create Correspondence focus for discussion.
Description
Added controllers for Attachments and Correspondence.
Attachments can be Initialized / uploaded separately and thus shared among different Correspondences / Correspondence Services.
A Correspondence can have 0-multiple attachments.
Notifications can be created as part of a correspondence, but only according to pre-defined templates.
Discussion points:
Should Message body also become an Attachment?
Implemented as that for now.
Should attachments be named "content" or "contentparts"
Additional field to specify their functional role, such as "HumanReadableMessageBody", "humanReadAbleAttachment", etc?
Initial API model with Create Correspondence focus for discussion.
Description
Added controllers for Attachments and Correspondence. Attachments can be Initialized / uploaded separately and thus shared among different Correspondences / Correspondence Services. A Correspondence can have 0-multiple attachments. Notifications can be created as part of a correspondence, but only according to pre-defined templates.
Discussion points:
Related Issue(s)
42
Verification
Documentation