Non-working day calendars are used to define periods when resources are not available for work. Use non-working day calendars when the period of non-availability applies to more than one resource for example public holidays. You can have more than one non-working day calendar defined.



For example you could have a non-working day calendar for US public holidays which is applied to US resources and a non-working day calendar for UK public holidays which is applied to UK resources.


Non-working day calendars can be set against named resources and resource teams.



Adding a non-working day calendar


  • Select the set up menu option.


  • Select the non-working calendar option.


  • Enter the calendar name.


  • Click create.


  • Click edit against the newly created calendar to open the calendar and set the non-working days.


Setting the non-working days


  • Open the non-working calendar you want to update if not already open.


  • Select the dates you want to make non-working by clicking the date(s) to highlight them.


  • When done, close the calendar using close (X) icon.


You can also un-select dates that are currently marked as non-working. Any resources assigned to the calendar will then use the working patterns defined in the resource to determine working days.


In the following example, Wednesday 2nd is marked as a non-working day.




Setting a resource non-working day calendar against a resource

Edit the resource to set the resource non-working day calendar for the resource.






Resource working time exceptions and non-working day calendars restrictions


#1 You can't overlap resource working time exceptions with non-working day calendar entries


A resource working time exception cannot be added that overlaps with a non-working day calendar entry.


Example:

  • We have a resource who is on vacation from 20 December to 28 December.
  • The resource is using a non-working day calendar Public Holidays and this has 25 December as a non-working day. 


  • Two resource working time exceptions need to be added for 20 December to 24 December and 26 December to 28 December to enter the vacation.


  • The resource will now have the period 20 December - 28 December as non-working days.



#2 Non-working day calendar exceptions that are edited at the resource level become resource level exceptions


A resource is using a non-working day calendar and you update the resource directly to make one of the non-working days a working day. The working day now becomes a resource working time exception and any further changes for the date need to be made at the resource working time exception level.



Example: 

  • You have a resource using a non-working day calendar Public Holidays and this has 25 December as a non-working day.


  • You want to set the 25 December as a working day for the resource. 


There are two ways to do this:


  • Edit the resource working time exception for the 25 December (that has been inherited from the non-working day calendar and will currently be set as a non-working day) and set the 25 December to be a working day. 


  • Delete the resource working time exception for the 25 December (meaning the normal working time for the resource will be used instead).