Sormas-project: “Event” printing function

[carolinverset]

Situation Description

Sormas does not offer a print function. It would be interesting in that it allows information to be transmitted to a third party without giving them access as a user. The print function would be particularly interesting for tracking events and associated actions.

Feature Description

Develop a function allowing users to print an HTML page from the information entered for each event:

• title of the event

• event identifier

• event status

• event date

• description of the event

• Region, department and municipality of the event

• Community Contact Person

• For each action :

Title of the action
Description of the action
Creation date
Date of last modification
Status of the action

Possible Alternatives

Additional Information

@xavier-calland @bernardsilenou

[xavier-calland]

@ftavin

[JonasCir]

@syntakker @markusmann-vg Maybe we can build this on top of the template engine we are currently working on? I have the feeling that we can share logic here :smiley:

[bernardsilenou]

@markusmann-vg I did not know we already started implementation. Please share the logic so that we can have the same design and method for other entities too. Do we need to call or there is already an issue about the specification?
The french team team has this on their plate for this sprint, so its good we quickly share ideas
Thanks,

[JonasCir]

https://github.com/hzi-braunschweig/SORMAS-Project/issues/2696 is the issue, it is in the current sprint. I don't mind a call to see how we can share functions :D

[syntakker]

@bernardsilenou We are working on document generation for quarantine orders in this branch:
https://github.com/ImisDevelopers/SORMAS-Project/tree/feature-2696-document-generation-quarantine

Document generation is based on XDocReport using the velocity template engine.
We read docx templates and generate docx documents. Currently I'm working on a generic mapping of variable names to entityDto values, such that, e.g., "case.person.firstName" maps to the respective value in the caseDto according to the Data Dictionary.

The approach is intended to be generic and work for all entityDtos, so the code can be extended to further workflows including documents.

[bernardsilenou]

@syntakker This sounds good. Generic approach is the way to go.
There is also the need to print the summary of followup (or clinical course) for cases, contacts, event participants, .... This generic approach will be very helpful.
@JonasCir I suspect issue #2696 will be done in this sprint, or it is a multi-sprint issue?
@carolinverset Since this similar issue is currently under development, I think is is better for the French dev team to wait until it is completed before extending the feature to events. What do you think please?

[syntakker]

@bernardsilenou I think I will have a working example for document generation from EntityDto data by Monday.
For the complete version we have to see if we can finalize everything in this sprint, but we surely get it done in the next sprint.

[bernardsilenou]

@syntakker Many thanks. I think it will be fine to wait until it is done and then the french dev team can then build on a working module. @carolinverset hope this is fine by you?

[syntakker]

@bernardsilenou the working example is ready and can be seen in said branch https://github.com/ImisDevelopers/SORMAS-Project/tree/feature-2696-document-generation-quarantine .
We start from a docx template and a root Dto, where variable naming is generic and follows the SORMAS_Data_Dictionary. So if the root is CaseDataDto, case.person.phone references the phone number of the case's person.
For a start on document generation, see test cases TemplateEngineServiceTest and QuarantineOrderFacadeEjbTest, for accessing Dto properties see EntityDtoAccessHelperTest.
We've built a preliminary button in the Case Information page and prepared a docx template in the cargoserver setup, so if you start the cargoserver you can generate a quarantine order from a case in the db.
All this is WIP, feedback is appreciated.

[carolinverset]

@syntakker Many thanks. I think it will be fine to wait until it is done and then the french dev team can then build on a working module. @carolinverset hope this is fine by you?

Yes, it's ok ! Thanks

[ftavin]

Short-term alternative using css : #3020