SORMAS-Project S2S_ Structure of comment field

S2S_ Structure of comment field

Open SahaLinaPrueger opened this issue 2 years ago • 1 comments

Feature Description

Each share must contain a comment by the person initiating the transfer to another entity. Each acceptance or rejection must contain a comment by the person who accepted or rejected the request. This is necessary in order to be able to trace when, why and by whom the data was transferred in the case of data protection requests.

Proposed Change

A comment is always structured according to the same principle and is saved as a string: "{1} {2} - {3}, {4} - {5}: {6}{7}{8}"

Part	Description
1	Date of creation of the comment. Localised according to the language set by the logged-in user.
2	Time of creation of the comment. (Current server time according to set time zone). Format → hh:mm
3	Last name of the currently logged in user
4	First name of the currently logged in user
5	District from user who created the comment, if the district is not available fallback to district from external ID from server
6	Line break → \r\n (little space, see example)
7	Comment as entered in the comment field of the form.
8	Line break → \r\n (more space, see example)

If a share request is accepted or rejected a comment has to be made according to #9946. This comment is also saved as a string and the new comment is concatenated to the existing string. The full history of all comments must be traceable at all times. So the comment of the 'share' - window of the source system and the comment of the 'preview share request' window of the target system must be visible in the 'preview share request' window of source AND target system once they exist (only exception: if target system rejects the share request. Due to data protection the rejected share request have to be deleted in target system)