![ninox download ninox download](https://www.itespresso.de/wp-content/uploads/2019/01/Ninox_Android-333x250.png)
The main reason for doing this is so that it’s possible to create an Employee user type and limit their access to the system - one of the things they can see is the Leave Requests - and only their own records. In addition to the basics of absence calculations and reporting, there is also a need to implement a request process and I chose to do this by having a separate table for these in the database. The following screenshot is most of the Absence tab from the employee record within KasPer Pro: Public Holiday Set (to allow for more than one jurisdiction).
NINOX DOWNLOAD PRO
In terms of the implementation of this in my KasPer Pro template, I use the following tables (in addition to the basic People table) for leave management: This all sounds very complex - and it is - but Ninox’s language makes it much simpler than any other platform that I have used over the years. Without an Absence Days table, it’s very hard to answer questions such as ‘who is off today’ or determine the amount of leave taken between any two dates. I also recommend that records are generated and maintained for each day of each period of leave - in other words, when we enter a period of leave with a start and end date, the system automatically generates a record for each day with the type of leave and number of hours. There needs to be a workflow for requesting and approving leaveįrom this, it’s clear that any solution will need somewhere to describe leave rules, a record of public holidays, a way to hold an employee’s working pattern and carry over etc.Leave entitlement may be accrued over time.People may carry over some leave from one year to the next.Public holidays (or Bank Holidays) need to be considered.Staff have differing working hours / patterns - often working different numbers of hours on different days of the week.
![ninox download ninox download](https://3nif81vi8bo1yn2g42p20vw1-wpengine.netdna-ssl.com/wp-content/uploads/2018/11/Ninox-125-Front-Iso-gray.png)
Many businesses have more than one set of Leave rules / entitlements.However, whilst this sounds simple, there are some complexities which shouldn’t be underestimated: This is often one of the most pressing needs people have for an HRMS solution - managing holidays and absence well can have a big impact for any business. With the Manager(s) field calculated using the formula above along with their department which is also calculated based on their Job. You can then use Ninox’s amazing formula fields to show a person’s manager on their records like this: Job.'Reports To'.People.'Full Name (Natural)'Īnd your staff’s job related information might look something like the screenshot (above). So my first recommendation is to create a ‘Jobs’ table in your database and configure reporting via Jobs - i.e.
NINOX DOWNLOAD UPDATE
This leads to you needing to update quite a few records (which is often forgotten) and your data can become out of date quickly. Why, I hear you ask? It’s simple really, should a manager leave or change jobs, it’s likely that all their previous reports are now reporting to their replacement. a direct link to another People record) here. Nothing wrong with this of course - but it is usually a mistake to include information about who a person reports to (i.e.
![ninox download ninox download](https://is4-ssl.mzstatic.com/image/thumb/Purple114/v4/6b/83/f6/6b83f6c2-58b7-3da1-1d8f-499ae7b56977/source/175x175-75.png)
The starting point for an HR applications tend to be setting up a People (Employee, Team Member) table which contains all the details of the people in the organisation. Setting up Personal Details and Reporting Structures in Ninox