In order to simplify the connection to the third party server, we think is best if we encapsulate into a client class all the details between request/response http.

Bambooing is offering the possibility to add entries for a week manually, however every day registers exactly 8 hours of work done. In reality, a clocker does not work 8 hours sharp every single day so we will need to tweak the algorithm to be more aligned with employees daily hours rate.

Currently bambooing offers timesheet data insertion on weekly basis. Since we are sending timesheets for approval on a monthly basis, a rake to populate hours for the 'current' month will reduce the manual triggering of the rake from 4 to 1.

Currently, bambooing is adding entries for any weekday but it is not taking into account that any weekday given, the employee could be off. We would like to exclude a weekday if the employee is not working. For that, the following endpoint https://www.bamboohr.com/api/documentation/time_off.php might help

Currently bambooing is offering to possibility to fill up your current weekday, however if you missed to run the rake during a week, you would have to enter these hours manually. In order prevent adding entries manually, we would like to create a rake task that permits adding random time for a given day passed.

There are several places that get today's date however we would like to have it in just one place. That refactoring will make it easy to change today's date behaviour manually

Currently only the approved PTO time off type (77) is excluded from the timesheet entries. However there are more time off types that could be also taken into account:

• 81 - Floating day
• 91 - Overtime
• 102 - Digital Disconnect Day
• 104 - FlyBetter Days
• 80 - Sick Policy
• 92 - Personal days
• 98 - Parental leave
• 89 - Personal leave
• 97 - Carryover PTO

The beginning of the month day is always added to the list of current month weekdays without taking into account whether or not that day is a weekday.