roos-fs tasks #143
Updated by Vadim Pariev 10 months ago
**General**
Use case - the report is to be created as soon as the service is ended. The report serves here as a confrmation and infromation for the customers. It is not billing info, it is more an informative part.
**Expected result*
- the PDF is stored within the service itself and could be downloaded from the Service screen
- Note that if there coule be multiple reports in the Service, hence think about how to show and store multiple reports
- the PDF is generated automatically as soon as the SERVICE is receiving a status done
- the PDF includes all the infroamtion provided by the user in the checl lists
- the PDF contains all the infromation about the task
- the PDF contains all the information that contains a Service
- the PDF contains the color sceme and the logo the ROOS Fleet services
!!! BUT NOT THE PRICCE AT ANY PLACE !!!
- the PDF shall have to have a structure like:
-- Key vechicle data
--- Service data
---- Task info
----- Filled out checklist
The current implimentation file could be found attached to this tticket.