Follow up on the time tracking web app (using easysys api)

- Adjust the template to match the sample - Change the programming to it actually does it this way 1. POST /monitoring whichI think will give yo ualso back and ID and than 2. POST /monitoring/1/start and 3. POST /monitoring/1/stop and 4. PUT /monitoring/4 (to overwrite the times and make them correct) I can also describe process quickly: The web app is for our support team, so if a supporter goes to a client he opens up the web app on his iphone or what ever. He selects the client (so there has to be a api call to get the client list), next he selects the business service (api call to the business services we offer) and than there has to be a date field and also a note field where the supporter can select the date and add some notes (for example what he did for the client). The api now has to write all this down into the database of the software. So practial example our supporter leaves the office, drives to client a, as soon as he is there he opens up the web app, selects client a, and service a, and starts the stop watch. Then he does some software upgrades or what ever at the client a. As soon as he is finished and leaves. he opens up the web app again. and stops the stop watch for client a. Also important is that in the last api call where we modify the original call the web app also have to write down the following in the notes: <b>$client_service$</b> "Datum der Leistung: "$date$ "Uhrzeit der Leistung: "$start_time$ - $end_time$ " Uhr" <note>