Roos-fs-ZIP

General
Use case - there are some open contracts that dictate that some services may be made without any preliminary appointmnet booking - that means that the car enters the Workshop and it is requested to perform to change telematic device (real case) and the technician at the location ened to perform following steps: find the car using the VIN/LP number. As soon as found the user needs to create a service for this car, be able to assign the task from the list. And then take care about this task.

Expeted result

• Mobile app user is able to enter all the fields in the service creation mask analog to the web app part
• the service creation include also the selection of the tasks templates from the list (that is fetched from the DB)
• Ensure API responses are optimized for mobile use (lightweight payloads)
• The API is secure and API could be called only by the authorised user (Requires valid access token)
• the API documentation is provided in the https://redmine.matecube-internal.ddns.net/projects/roos-fs/wiki part
• The user can add the task to already created service
• User can fill out the check lists attached to the Task
• User is able to see this data at any time
  NOTE
• the tasks could be created only within the existing service or attached to newly created service
• mobile user CAN NOT create a task TEMPLATE
• mobile user CAN only edit the description to the task but not the FIELDS