Locations and Leave Policies
by Robin FisherI made some design decisions back in the day which have not really stood the test of time.
The first was that a user's location was a string in the database. Literally, "London". This was OK but to really evolve the application it needed to become a fully-fledged model in its own right.
This update does that and also integrates with the Abstract API geolocation API to create a location automatically when a new user signs up.
The second part of the update is to allow creation of default leave policies per location e.g. each employee gets 20 days leave and can carry forward 3 days to the next year.
Both of these changes streamline adding new users as it allows admins to configure defaults based on where the employee is working.
