Roos-fs-ZIP

General
USe case - the cancallation of the service/task is done most of the time by the same reasons, hence there is a need for a implimentation for the reasoning of the the rejection.

Expected result

• Description is always available for all the reasons
• Description input s mandatory in case the reason is "Other"
• a picture could always be attached to the reasoning
• the reasoning as well as the description and picture are to be seen in the task/service as well as represented in the final report pdf generated

Here are the reasons for cancellation grouped by the main cause:

• Customer
  -- Vechicle not available
  -- Key not available
  -- Vechicle defleeted
  -- Shorterm cancellation
  -- Vechicle user rejects service
  -- Vechicle damage (due to the car condition niot possible to service)
  -- Vechicle is blocked (No access)
  -- Others (+description obligatory field)

• Internal reasons
  -- no capacity (illness an co of the tech. )
  -- wrong date for the service/task
  -- wrong task for the service
  -- no material
  -- other (+description obligatory field)